Amazon Marketplace v2 Connection Details

Introduction

Connector Version

This documentation is based on version 25.0.9368 of the connector.

Get Started

Amazon Marketplace Version Support

The connector leverages the Amazon Marketplace API to enable bidirectional access to Amazon Selling Partner (SP) API.

Establish a Connection

Connect to Amazon Marketplace

The following properties are required:

• Schema: Set this to SellerCentral.
• InitiateOAuth: Set this to GETANDREFRESH.
• Marketplace: Set this to the Marketplace region that you are registered to sell in.

Authenticate to Amazon Marketplace

OAuth

Amazon Marketplace uses the OAuth authentication standard.

To authenticate using OAuth, you must either use the embedded application or create a new custom OAuth app. The embedded application supports desktop applications and headless machines. Web applications require that you create a custom OAuth application.

You can use a custom OAuth application to authenticate with a service account or a user account. See Creating a Custom OAuth App for more information.

Downloading Embedded Credentials

Because Amazon Marketplace requires that embedded credentials rotate every six months, credentials are hosted on oa.cdata.com. If you do not specify custom credentials, the embedded credentials are downloaded from our web service and saved in the location specified in OAuthClientLocation by default.

Desktop Apps

You can use the embedded application or create a custom OAuth application. The key difference is that you must set additional connection properties if you use a custom application.

Get and Refresh the OAuth Access Token

After setting the following, you are ready to connect:

• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
• Marketplace: Set this to the Marketplace region that you are registered to sell in.
• AppId: Set this to the application ID for the Selling Partner application you created.
• Schema: Set this to SellerCentral to connect to Seller Central API.
• AWSAccessKey: This is the Access Key tied to the AWS user that is associated with the OAuthClientId.
• AWSSecretKey: This is the Secret Key tied to the AWS user that is associated with the OAuthClientId.
• OAuthClientId (custom applications only): Set this to the client ID assigned when you registered your app.
• OAuthClientSecret (custom applications only): Set this to the client secret assigned when you registered your app.

When you connect the connector opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The connector then completes the OAuth process:

1. Extracts the access token from the callback URL and authenticates requests.
2. Refreshes the access token when it expires.
3. Saves OAuth values in OAuthSettingsLocation. These values persist across connections.

Amazon Marketplace Data Retention Policy

For security, Amazon Marketplace restricts access to PII (Personally Identifiable Information). You can only retain PII for 30 days after order delivery and only for the purpose of, and as long as is necessary to

• fulfill orders
• calculate and remit taxes
• produce tax invoices
• meet legal requirements, including tax or regulatory requirements.

If you are required by law to retain archival copies of PII for tax or other regulatory purposes, you must store PII as a "cold" or offline encrypted backup (e.g., not available for immediate or interactive use).

This means, for example, that the Amazon Marketplace driver no longer displays customer shipping address information after 30 days. See the Amazon documentation for more information:

Amazon Marketplace Data Protection Policy

Create a Custom OAuth App

You can use a custom OAuth app to authenticate a service account or a user account.

Create an OAuth App for User Account Authentication

Follow the procedure below to register an app and obtain the OAuthClientId and OAuthClientSecret.

Create a Custom OAuth App

1. Log into the Selling Partner Console and open Develop Apps from Apps & Services.

2. Click Add new app client.

3. Provide name for the app and select SP-API as the API type.

4. Provide IAM ARN for the AWS account and Select Sellers.

5. Provide OAuth Login URI and OAuth Redirect URI values. After creating the app, the OAuthClientId and OAuthClientSecret are displayed under LWA credentials.

For a more in depth reading of how to create a custom OAuth app and configure the IAM role, please see the Amazon Selling Partner Guide.

Important Notes

Configuration Files and Their Paths

• All references to adding configuration files and their paths refer to files and locations on the Jitterbit agent where the connector is installed. These paths are to be adjusted as appropriate depending on the agent and the operating system. If multiple agents are used in an agent group, identical files will be required on each agent.

Advanced Features

This section details a selection of advanced features of the Amazon Marketplace connector.

User Defined Views

The connector supports the use of user defined views, virtual tables whose contents are decided by a pre-configured user defined query. These views are useful when you cannot directly control queries being issued to the drivers. For an overview of creating and configuring custom views, see User Defined Views.

SSL Configuration

Use SSL Configuration to adjust how connector handles TLS/SSL certificate negotiations. You can choose from various certificate formats. For further information, see the SSLServerCert property under "Connection String Options".

Proxy

To configure the connector using private agent proxy settings, select the Use Proxy Settings checkbox on the connection configuration screen.

Query Processing

The connector offloads as much of the SELECT statement processing as possible to Amazon Marketplace and then processes the rest of the query in memory (client-side).

For further information, see Query Processing.

Log

For an overview of configuration settings that can be used to refine logging, see Logging. Only two connection properties are required for basic logging, but there are numerous features that support more refined logging, which enables you to use the LogModules connection property to specify subsets of information to be logged.

User Defined Views

The Jitterbit Connector for Amazon Marketplace supports the use of user defined views: user-defined virtual tables whose contents are decided by a preconfigured query. User defined views are useful in situations where you cannot directly control the query being issued to the driver; for example, when using the driver from Jitterbit.

Use a user defined view to define predicates that are always applied. If you specify additional predicates in the query to the view, they are combined with the query already defined as part of the view.

There are two ways to create user defined views:

• Create a JSON-formatted configuration file defining the views you want.
• DDL statements.

Define Views Using a Configuration File

User defined views are defined in a JSON-formatted configuration file called UserDefinedViews.json. The connector automatically detects the views specified in this file.

You can also have multiple view definitions and control them using the UserDefinedViews connection property. When you use this property, only the specified views are seen by the connector.

This user defined view configuration file is formatted so that each root element defines the name of a view, and includes a child element, called query, which contains the custom SQL query for the view.

For example:

{
    "MyView": {
        "query": "SELECT * FROM Orders WHERE MyColumn = 'value'"
    },
    "MyView2": {
        "query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
    }
}

Use the UserDefinedViews connection property to specify the location of your JSON configuration file. For example:

"UserDefinedViews", "C:\Users\yourusername\Desktop\tmp\UserDefinedViews.json"

Define Views Using DDL Statements

The connector is also capable of creating and altering the schema via DDL Statements such as CREATE LOCAL VIEW, ALTER LOCAL VIEW, and DROP LOCAL VIEW.

Create a View

To create a new view using DDL statements, provide the view name and query as follows:

CREATE LOCAL VIEW [MyViewName] AS SELECT * FROM Customers LIMIT 20;

If no JSON file exists, the above code creates one. The view is then created in the JSON configuration file and is now discoverable. The JSON file location is specified by the UserDefinedViews connection property.

Alter a View

To alter an existing view, provide the name of an existing view alongside the new query you would like to use instead:

ALTER LOCAL VIEW [MyViewName] AS SELECT * FROM Customers WHERE TimeModified > '3/1/2020';

The view is then updated in the JSON configuration file.

Drop a View

To drop an existing view, provide the name of an existing schema alongside the new query you would like to use instead.

DROP LOCAL VIEW [MyViewName]

This removes the view from the JSON configuration file. It can no longer be queried.

Schema for User Defined Views

In order to avoid a view's name clashing with an actual entity in the data model, user defined views are exposed in the UserViews schema by default. To change the name of the schema used for UserViews, reset the UserViewsSchemaName property.

Work with User Defined Views

For example, a SQL statement with a user defined view called UserViews.RCustomers only lists customers in Raleigh:

SELECT * FROM Customers WHERE City = 'Raleigh';

An example of a query to the driver:

SELECT * FROM UserViews.RCustomers WHERE Status = 'Active';

Resulting in the effective query to the source:

SELECT * FROM Customers WHERE City = 'Raleigh' AND Status = 'Active';

That is a very simple example of a query to a user defined view that is effectively a combination of the view query and the view definition. It is possible to compose these queries in much more complex patterns. All SQL operations are allowed in both queries and are combined when appropriate.

SSL Configuration

Customize the SSL Configuration

By default, the connector attempts to negotiate TLS with the server. The server certificate is validated against the default system trusted certificate store. You can override how the certificate gets validated using the SSLServerCert connection property.

To specify another certificate, see the SSLServerCert connection property.

Data Model

The Jitterbit Connector for Amazon Marketplace models Amazon Marketplace objects as relational tables and views. An Amazon Marketplace object has relationships to other objects; in the tables, these relationships are expressed through foreign keys. The following sections show the available API objects and provide more information on executing SQL to Amazon Marketplace APIs.

Schemas for most database objects are defined in simple, text-based configuration files.

Using SellerCentral API

See Seller Central Data Model for the available entities in the Seller Central API.

Using VendorCentral API

See Vendor Central Data Model for the available entities in the Vendor Central API.

Seller Central Data Model

The Jitterbit Connector for Amazon Marketplace models the Seller Central API as relational views, and stored procedures.

To use Amazon Seller Central Data Model, simply set Schema to SellerCentral.

Views

Views are tables that cannot be modified, such as Orders, OrderItems. Typically, data that are read-only and cannot be updated are shown as views.

Stored Procedures

Stored Procedures are function-like interfaces to the data source. They can be used to search, update, and modify information in the data source.

Using Reports

For each report type there is a view exposed. For example, report type FEE_DISCOUNTS_REPORT will be exposed as a view named REPORT_FEE_DISCOUNTS_REPORT. These views can then be queried by using 'DataStartTime' and 'DataEndTime' optional datetime parameters. When both datetime parameters are specified, the driver automatically searches for an existing report that matches the specified interval, and if not found a new report is created. Reports can be manually created with the RequestReport stored procedure. You can also use ReportOptions JSON-aggregate pseudo-column to specify additional fields that may be required depending on report type. For more details about report options please check Amazon Selling-Partner API Documentation

After a report has been created and pushed to the result set, the next time you query this report type with the 'DataStartTime' and 'DataEndTime' same filters, the previously created report is downloaded instead of creating a new report.

Tables

The connector models the data in Amazon Marketplace as a list of tables in a relational database that can be queried using standard SQL statements.

Jitterbit Connector for Amazon Marketplace Tables

Destinations

Returns information about all destinations.

Columns

InboundDeliveryWindowOptions

Retrieves all delivery window options for a shipment.

Columns

Name	Type	ReadOnly	References	Description
InboundPlanId [KEY]	String	False		Identifier of an inbound plan.
ShipmentId [KEY]	String	False		The shipment to generate delivery window options for.
DeliveryWindowOptionId [KEY]	String	True		Identifier of a delivery window option. A delivery window option represent one option for when a shipment is expected to be delivered.
StartDate	Datetime	True		The timestamp at which this delivery window option starts. This is based in ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
EndDate	Datetime	True		The timestamp at which this delivery window option ends. This is based in ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
ValidUntil	Datetime	True		The timestamp at which this window delivery option becomes no longer valid. This is based in ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
AvailabilityType	String	True		Identifies type of Delivery Window Availability. Values: `AVAILABLE`, `CONGESTED`

InboundItemComplianceDetails

List the inbound compliance details for MSKUs in a given marketplace.

Columns

InboundPackingOptions

Retrieves a list of all packing options for an inbound plan.

Columns

Name	Type	ReadOnly	References	Description
PackingOptionId [KEY]	String	True		Identifier of a packing option.
InboundPlanId [KEY]	String	False		Identifier of an inbound plan.
Discounts	String	True		Discount for the offered option.
Fees	String	True		Fee for the offered option.
Expiration	Datetime	True		The timestamp at which this packing option becomes no longer valid. This is based in ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
Status	String	True		The status of the packing option. Can be: `OFFERED`, `ACCEPTED`, or `EXPIRED`.
ShippingConfiguration	String	True		Deprecated. Use SupportedConfiguration instead. List of supported shipping modes.
PackingGroups	String	True		Packing group IDs.
SupportedConfiguration	String	True		A list of possible configurations for this option.

InboundPlacementOptions

Provides a list of all placement options for an inbound plan.

Columns

Name	Type	ReadOnly	References	Description
PlacementOptionId [KEY]	String	True		The identifier of a placement option. A placement option represents the shipment splits and destinations of SKUs.
InboundPlanId [KEY]	String	False		Identifier of an inbound plan.
Discounts	String	True		Contains details about cost related modifications to the placement cost.
Fees	String	True		Contains details about cost related modifications to the placement cost.
Expiration	Datetime	True		The timestamp at which this packing option becomes no longer valid. This is based in ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
Status	String	True		The status of a placement option. Can be: `OFFERED`, `ACCEPTED`, or `EXPIRED`.
ShipmentIds	String	True		Shipment ids.
CustomPlacementInput	String	False		Provide units going to the warehouse.

InboundPlan

Provides a list of inbound plans with minimal information.

Columns

Name	Type	ReadOnly	References	Description
InboundPlanId [KEY]	String	True		Identifier of an inbound plan.
Name	String	False		Human-readable name of the inbound plan.
MarketplaceIds	String	False		A list of marketplace IDs.
CreatedAt	Datetime	True		The ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
LastUpdatedAt	Datetime	True		The ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
Status	String	True		Current status of the inbound plan. Can be: `ACTIVE`, `VOIDED`, `SHIPPED`, 'ERRORED'.
ShipmentSummary	String	True		Summary information about a shipment.
PlacementOptionSummary	String	True		Summary information about a placement option.
PackingOptionSummary	String	True		Summary information about a packing option.
StateOrProvinceCode	String	False		The state or province code.
PhoneNumber	String	False		The phone number.
City	String	False		The city.
Email	String	False		The email address.
CompanyName	String	False		The name of the business.
PostalCode	String	False		The postal code.
AddressLine2	String	False		Additional street address information.
AddressLine1	String	False		Street address information.
CountryCode	String	False		The country code in two-character ISO 3166-1 alpha-2 format.
AddressName	String	False		The name of the customer in the specified address.
InboundPlanAggregate	String	False		Parameter used for creating new inbound plans by passing the JSON aggregate.
InboundPlanItems	String	False		Inbound plan item's input parameters. Used for creating an inbound plan.

InboundSelfShipAppointmentSlots

Retrieves a list of available self-ship appointment slots used to drop off a shipment at a warehouse.

Columns

InboundShipmentContentUpdatePreview

Retrieve a paginated list of shipment content update previews for a given shipment.

Columns

ListingsItems

Returns details about a listings item for a selling partner.

The following filters are required:

• SKU
• SellerId: You can either specify SellerId as a pseudo-column condition in WHERE filters, or in the connection string.

Some example queries:

SELECT * FROM ListingsItems WHERE SKU = '12345' AND SellerId = 'XXXXXXXXXXXXXX'

INSERT INTO ListingsItems (ProductType, Requirements, Attributes, SKU, SellerId)
VALUES ('product_type', 'LISTING', '{\"AttributeName\": \"test_attribute\", \"AttributeValue\": \"value\"}', '12345', 'XXXXXXXXXXXXXX')

DELETE FROM ListingsItems WHERE SKU = '12345' AND SellerId = 'XXXXXXXXXXXXXX'

When inserting, you can also use temp tables in order to insert multiple attributes, as shown in the example below:

INSERT INTO Attributes#TEMP (AttributeName, AttributeValue) VALUES ('attr1', 'val1')
INSERT INTO Attributes#TEMP (AttributeName, AttributeValue) VALUES ('attr2', 'val2')
INSERT INTO Attributes#TEMP (AttributeName, AttributeValue) VALUES ('attr3', 'val3')

INSERT INTO ListingsItems (ProductType, Requirements, Attributes, SKU, SellerId)
VALUES ('product_type', 'LISTING', 'Attributes#TEMP', '12345', 'XXXXXXXXXXXXXX')

*The temporary table must be defined and used within the same connection. Closing the connection will clear out any temporary tables in memory.

Columns

ListingsItemsAttributes

Returns details about a listings item attributes for a selling partner.

The following filters are required:

• SKU
• SellerId: You can either specify SellerId as a pseudo-column condition in WHERE filters, or in the connection string.

Some example queries:

SELECT * FROM ListingsItemsAttributes WHERE SKU = '12345' AND SellerId = 'XXXXXXXXXXXXXX'
UPDATE ListingsItemsAttributes SET AttributeValue = 'test_value', ProductType = 'LUGGAGE'
WHERE SKU = '12345' AND AttributeName = 'item_name_value'

You can also retrieve all SKU fields from another sub-query, for example:

SELECT * FROM ListingsItems WHERE SellerId = 'XXXXXXXXXXXXXX' AND SKU IN (
        SELECT DISTINCT(SKUIdentifierSellerSKU) FROM CatalogItems WHERE MarketplaceId = 'XXXXXXXXXXXXXX' AND Query = 'test' AND SkuIdentifierSellerSku IS NOT NULL
)

Columns

OutboundFulfillmentOrders

Returns a list of fulfillment orders fulfilled after (or at) a specified date-time, or indicated by the next token parameter.

Columns

Subscriptions

Returns information about subscriptions of the specified notification type.

Columns

Views

Views are similar to tables in the way that data is represented; however, views are read-only.

Queries can be executed against a view as if it were a normal table.

Jitterbit Connector for Amazon Marketplace Views

CatalogItems

The Catalog Items table helps you retrieve item details for items in the catalog.

The following filters are required:

• MarketplaceId
• One of the following: Query, SellerSKU, UPC, EAN, ISBN, JAN

For example:

SELECT * FROM CatalogItems WHERE MarketplaceID = 'XXXXXXXXXXXXX' AND ISBN = 'XXXXXXXXXXXXX'

Columns

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

CatalogItemsClassifications

The Catalog Items Classifications table helps you retrieve classification details for items in the catalog.

Columns

CompetitivePricing

Returns competitive pricing information for a seller's offer listings based on seller SKU or ASIN.

Columns

Feeds

The GetFeedSubmissionList operation returns a list of feed submissions.

Select

The connector will use the Amazon Marketplace API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

Note: 'FeedType' attribute is required to query the view. You can view available values for 'FeedType' here.

• FeedId supports the '=' comparison.
• FeedType supports the '=' and 'IN' comparisons.
• MarketplaceIds supports the '=' and 'IN' comparisons.
• ProcessingStatus supports the '=' and 'IN' comparisons.
• CreatedTime supports the '=', '<', '>', '<=' and '>=' comparisons.

Following are example queries that are processed server side:

SELECT * FROM Feeds WHERE FeedId = '50950018754'

SELECT * FROM Feeds WHERE FeedType = 'POST_PRODUCT_PRICING_DATA'

SELECT * FROM Feeds WHERE FeedType IN ( 'POST_PRODUCT_PRICING_DATA', 'POST_INVENTORY_AVAILABILITY_DATA' )

SELECT * FROM Feeds WHERE FeedType = 'POST_PRODUCT_PRICING_DATA' AND MarketplaceIds = 'A1VC38T7YXB528'

SELECT * FROM Feeds WHERE FeedType = 'POST_PRODUCT_PRICING_DATA' AND ProcessingStatus = 'DONE'

SELECT * FROM Feeds WHERE FeedType = 'POST_PRODUCT_PRICING_DATA' AND CreatedTime > '2021-06-20' AND CreatedTime < '2021-08-01 12:00:00'

Columns

FeesEstimate

Returns the estimated fees for the listed products.

Columns

InboundDeliveryChallanDocument

Provide delivery challan document for PCP transportation in India marketplace.

Columns

Name	Type	References	Description
InboundPlanId [KEY]	String		Identifier of an inbound plan.
ShipmentId [KEY]	String		Identifier of a shipment. A shipment contains the boxes and units being inbounded.
Uri	String		Uniform resource identifier to identify where the document is located.
Expiration	Datetime		The timestamp of expiration of the URI. This is in ISO 8601 datetime format with pattern `yyyy-MM-ddTHHss.sssZ`.
DownloadType	String		The type of download. Can be `URL`.

InboundOperationStatus

Gets the status of the processing of an asynchronous API call.

Columns

InboundPackingGroupBoxes

Retrieves a page of boxes from a given packing group.

Columns

InboundPackingGroupItems

Retrieves a page of items in a given packing group.

Columns

InboundPlanBoxes

Provides a paginated list of box packages in an inbound plan.

Columns

InboundPlanItems

Provides a paginated list of item packages in an inbound plan.

Columns

InboundPlanPallets

Provides a paginated list of pallet packages in an inbound plan.

Columns

InboundShipmentBoxes

Provides a paginated list of box packages in a shipment.

Columns

InboundShipmentItems

Returns a list of items in a specified inbound shipment.

Select

The connector will use the Amazon Marketplace API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• MarketplaceId supports the '=' comparison.
• ShipmentId supports the '=' comparison.
• LastUpdatedDate supports the '=', '<', '>', '<=', '>=' comparisons.

For example, the following query is processed server side:

SELECT * FROM InboundShipmentItems  WHERE MarketplaceId = 'ATVPDKIKX0DER'

SELECT * FROM InboundShipmentItems  WHERE ShipmentId = 'FBA8J3K9LZPX'

SELECT * FROM InboundShipmentItems  WHERE LastUpdatedDate > '2020-01-01'

Columns

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

InboundShipmentPallets

Provides a paginated list of pallet packages in a shipment.

Columns

InboundShipments

Returns a list of inbound shipments based on criteria that you specify.

Select

The connector will use the Amazon Marketplace API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• ShipmentId supports the '=' and 'IN' comparisons.
• ShipmentStatus supports the '='and 'IN' comparisons.
• MarketplaceId supports the '=' comparison.
• LastUpdatedDate supports the '=', '<', '>', '<=', '>=' comparisons.

For example, the following query is processed server side:

SELECT * FROM InboundShipments WHERE ShipmentStatus = 'Working'

SELECT * FROM InboundShipments WHERE ShipmentStatus IN ('Working', 'SHIPPED', 'IN_TRANSIT')

SELECT * FROM InboundShipments WHERE ShipmentId = '503-9993250-1405404'

SELECT * FROM InboundShipments WHERE MarketplaceId = 'ATVPDKIKX0DER'

SELECT * FROM InboundShipments WHERE LastUpdatedDate >= '2016-12-12'

Columns

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

InboundTransportationOptions

Retrieves all transportation options for a shipment.

Columns

Name	Type	References	Description
InboundPlanId [KEY]	String		Identifier of an inbound plan.
TransportationOptionId [KEY]	String		Identifier of a transportation option. A transportation option represent one option for how to send a shipment.
ShipmentId [KEY]	String		Identifier of a shipment. A shipment contains the boxes and units being inbounded.
VoidableUntil	Datetime		Voidable until timestamp.
Amount	Decimal		Decimal value of the currency.
Expiration	Datetime		The timestamp at which this transportation option quote becomes no longer valid. This is based in ISO 8601 datetime with pattern `yyyy-MM-ddTHHss.sssZ`.
Code	String		ISO 4217 standard of a currency code.
Name	String		The contact's name.
EndTime	Datetime		The end timestamp of the appointment in UTC.
ShippingMode	String		Mode of shipment transportation that this option will provide. Can be: `GROUND_SMALL_PARCEL`, `FREIGHT_LTL`, `FREIGHT_FTL_PALLET`, `FREIGHT_FTL_NONPALLET`, `OCEAN_LCL`, `OCEAN_FCL`, `AIR_SMALL_PARCEL`, `AIR_SMALL_PARCEL_EXPRESS`.
StartTime	Datetime		The start timestamp of the appointment in UTC.
AlphaCode	String		The carrier code. For example, USPS or DHLEX.
ShippingSolution	String		Shipping program for the option. Can be: `AMAZON_PARTNERED_CARRIER`, `USE_YOUR_OWN_CARRIER`.
PlacementOptionId	String		The placement option to generate transportation options for.

InventorySupply

Returns information about the availability of inventory that a seller has in Amazon's fulfillment network and in current inbound shipments. You can check the current availability status for your Fulfillment by Amazon inventory as well as discover when availability status changes.

Select

The connector will use the Amazon Marketplace API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• SellerSKU supports the '=', 'IN' comparisons.
• GranularityType supports the '='comparison.
• GranularityId supports the '=' comparison.
• MarketplaceId supports the '=' comparison.
• StartDateTime supports the '=', '<', '>', '<=', '>=' comparisons.

Following are example queries which are processed server side:

SELECT * FROM InventorySupply WHERE GranularityType = 'Marketplace' AND GranularityId = 'ATVPDKIKX0DER' AND SellerSKU = '123'

SELECT * FROM InventorySupply WHERE GranularityType = 'Marketplace' AND GranularityId = 'ATVPDKIKX0DER' AND StartDateTime > '2020-01-01'

Columns

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ItemOffers

Returns the lowest priced offers for a single item based on ASIN.

Columns

ListingOffers

Generated schema file.

Columns

ListingsItemsIssues

Returns details about a listings item issues for a selling partner.

The following filters are required:

• SKU
• SellerId: You can either specify SellerId as a pseudo-column condition in WHERE filters, or in the connection string.

Some example queries:

SELECT * FROM ListingsItemsIssues WHERE SKU = '12345' AND SellerId = 'XXXXXXXXXXXXXX'

Columns

ListingsItemsOffers

Returns details about a listings item offers for a selling partner.

The following filters are required:

• SKU
• SellerId: You can either specify SellerId as a pseudo-column condition in WHERE filters, or in the connection string.

Some example queries:

SELECT * FROM ListingsItemsOffers WHERE SKU = '12345' AND SellerId = 'XXXXXXXXXXXXXX'

Columns

ListingsItemsSummaries

Returns details about a listings item summaries for a selling partner.

The following filters are required:

• SKU
• SellerId: You can either specify SellerId as a pseudo-column condition in WHERE filters, or in the connection string.

Some example queries:

SELECT * FROM ListingsItemsSummaries WHERE SKU = '12345' AND SellerId = 'XXXXXXXXXXXXXX'

Columns

OrderItems

Returns order items based on the Amazon Order ID that you specify.

Select

The connector will use the Amazon Marketplace API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector. OrderItems table supports server side filtering with = and IN operators for AmazonOrderId field.

• AmazonOrderId supports the '=' comparison.

For example, the following query is processed server side:

SELECT * FROM OrderItems WHERE AmazonOrderId = '503-9993250-1405404'

Columns

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

OrderMetrics

Returns aggregated order metrics for a given interval, broken down by granularity, for a given buyer type.

Columns

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Orders

Returns orders created or updated during a time frame that you specify.

Select

The connector will use the Amazon Marketplace API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• AmazonOrderId supports the '=' comparison.
• SellerOrderId supports the '=' comparison.
• PurchaseDate supports the '=', '<', '>', '<=', '>=' comparison.
• LastUpdateDate supports the '=', '<', '>', '<=', '>=' comparison.
• OrderStatus supports the '=', 'IN' comparison.
• FulfillmentChannel supports the '=', 'IN' comparison.
• PaymentMethod supports the '=', 'IN' comparison.
• MarketplaceId supports the '=' comparison.
• BuyerEmail supports the '=' comparison.
• IsISPU supports the '=' comparison.

For example, the following query is processed server side:

SELECT * FROM Orders WHERE AmazonOrderId = '249-7638334-8161403'

SELECT * FROM Orders WHERE SellerOrderId = '249-7638334' AND purchasedate > '2010-01-01'

SELECT * FROM Orders WHERE LastUpdateDate >= '2016-12-12'

SELECT * FROM Orders WHERE PurchaseDate >= '2016-12-12'

SELECT * FROM Orders WHERE MarketplaceId = 'ATVPDKIKX0DER'

SELECT * FROM Orders WHERE BuyerEmail = 'random@gmail.com'

SELECT * FROM Orders WHERE IsISPU = false

SELECT * FROM Orders WHERE PurchaseDate >= '2016-12-12' AND OrderStatus = 'Canceled'

SELECT * FROM Orders WHERE PurchaseDate >= '2016-12-12' AND FulfillmentChannel = 'MFN'

SELECT * FROM Orders WHERE PurchaseDate >= '2016-12-12' AND BuyerEmail = 'example@example.com'

SELECT * FROM Orders WHERE PurchaseDate >= '2016-12-12' AND PaymentMethod = 'Other'

Columns

OutboundFeatures

Returns a list of features available for Multi-Channel Fulfillment orders in the marketplace you specify, and whether the seller for which you made the call is enrolled for each feature.

Columns

OutboundFulfillmentOrderItems

Returns the fulfillment order items indicated by the specified order identifier.

Columns

OutboundFulfillmentsPreview

Returns a list of fulfillment order previews based on shipping criteria that you specify.

Columns

OutboundPackageTracking

Returns delivery tracking information for a package in an outbound shipment for a Multi-Channel Fulfillment order.

Columns

OutboundReturnItems

An array of items that Amazon accepted for return. Returns empty if no items were accepted for return.

Columns

OutboundReturnReasons

Returns a list of return reason codes for a seller SKU in a given marketplace.

Columns

ProductPricing

Generated schema file.

Columns

ReportList

Returns report details for the reports that match the filters that you specify.

Select

The connector will use the Amazon Marketplace API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the connector.

• ReportId supports the '=' comparison.
• ReportType supports the '=', 'IN' comparisons.
• MarketplaceIds supports the '=', 'IN' comparisons.
• ProcessingStatus supports the '=', 'IN' comparisons.
• CreatedTime supports the '=', '<', '>', '<=', '>=' comparisons.

Following are example queries that are processed server side:

SELECT * FROM ReportList WHERE ReportId = '51013018828'

SELECT * FROM ReportList WHERE ReportType = 'GET_FLAT_FILE_OPEN_LISTINGS_DATA'

SELECT * FROM ReportList WHERE ReportType = 'GET_FLAT_FILE_OPEN_LISTINGS_DATA' AND CreatedTime > '2021-06-12' AND CreatedTime < '2021-08-01 12:00:00'

SELECT * FROM ReportList WHERE ReportType = 'GET_FLAT_FILE_OPEN_LISTINGS_DATA' AND MarketplaceIds = 'A1VC38T7YXB528'

SELECT * FROM ReportList WHERE ReportType = 'GET_FLAT_FILE_OPEN_LISTINGS_DATA' AND ProcessingStatus = 'DONE'

Note: When filtering with CreatedTime, values older than 90 days will not be accepted.

Columns

ReportTypes

Returns report details for the reports that match the filters that you specify.

Select

This view lists all the available Report Types of Seller Central API and their respective format (JSON, XML, CSV, TSV, PDF, XLSX).

SELECT * FROM ReportTypes

Columns

ShippingDocuments

Returns the shipping documents associated with a package in a shipment.

Columns

ShippingRates

Returns the available shipping service offerings.

Columns