Amazon Selling Partner
Use Amazon Selling Partner to buy and print shipping labels for your Amazon Orders from ShipStream. Choose your setup according to whose Amazon account pays for shipping:
| Your use case | Connection to authorize | Connection Profile for Amazon Shipping (v2) |
|---|---|---|
| You ship your own Orders on your own Amazon account. | An Amazon Selling Partner Merchant Integration for your Merchant. | Seller (own orders) |
| You are a 3PL buying shipping on each seller's Amazon account. | A separate Amazon Selling Partner Merchant Integration authorized by each seller. | Seller (own orders) for each Merchant |
| You are a 3PL buying shipping for other sellers on your own Amazon account. | One Amazon Selling Partner Global Integration, shared by Merchant Integrations without their own connection. | 3PL (orders of other sellers), with Seller ID Override and the Linked Carrier Accounts of the Global Integration |
The Connection Profile setting is available only with Amazon Shipping (v2). Existing installations use Merchant Fulfillment (v0) until you change Shipping API. A Global Integration shares the Amazon authorization; each Merchant still needs its own Merchant Integration to enable Buy Shipping and configure allowed services.
Contact ShipStream support to enable Amazon Selling Partner on your instance before setup. For the third use case, Amazon must also have enrolled your Amazon account to buy shipping for other sellers.
Set Up Your Own Seller Account
Use these steps when you are a single Merchant shipping your own Amazon Orders.
- Navigate to System > Integrations > Merchant Integrations and click Add New Subscription.
- Choose your Merchant, then click Amazon Selling Partner.
- Set Enable Buy Shipping to Yes. Choose Allowed Shipping Services as needed, then click Save Subscription. Confirm that Status is Active; if it is Inactive, click Activate.
- In the same browser, sign in to Amazon Seller Central with the Merchant's seller account. Amazon connects whichever account is signed in, so sign out of any other Seller Central account first. For a 3PL connection that buys shipping through Seller ID Override, sign in with your enrolled 3PL account instead, and enter the Linked Carrier Accounts on this Merchant Integration.
- In OAuth Connection, click Authorize. On the Amazon Seller Central page, verify that the account shown is the Merchant's, then complete Amazon's authorization prompts.
- After returning to ShipStream, check that OAuth Connection shows Connection Active. Connection Status identifies the source as Using this Merchant Integration's connection.
- Navigate to System > Configuration > Shipping Methods > Amazon Selling Partner and select your Merchant's configuration scope. Set Enabled to Yes. To use v2, set Shipping API to Amazon Shipping (v2) and Connection Profile to Seller (own orders), then complete the v2 settings and click Save Config. Leave Seller ID Override empty.
The Authorize button on a Merchant Integration without an existing connection:

A successful authorization of the Merchant Integration's own account:

Set Up a 3PL Using Each Seller's Account
Each seller authorizes their own Amazon account; you do not need a Global Integration for this setup.
- Follow Set Up Your Own Seller Account for each Merchant, selecting the Merchant that owns that seller's Orders.
- Have each seller complete Authorize with their own Amazon account. Verify Using this Merchant Integration's connection. on each subscription.
- For each Merchant using Amazon Shipping (v2), choose Seller (own orders) as the Connection Profile and leave Seller ID Override empty. Configure the remaining v2 settings for that Merchant and click Save Config.
Choose the profile according to the account used for the purchase. A warehouse operated by a 3PL still uses Seller (own orders) when buying on the seller's own account.
Set Up a 3PL Using Its Own Amazon Account
Authorize your 3PL's Amazon account once through a Global Integration. Each participating Merchant then uses that connection to buy shipping for the seller named on its Merchant Integration.
Authorize the Global Integration
Before authorizing, set Use OAuth to Yes at System > Configuration > Integrations > Amazon Selling Partner, with Global selected in the configuration scope switcher. The Global Integration requires this instance-wide setting.
- Navigate to System > Integrations > Global Integrations.
- If Amazon Selling Partner is not yet set up, click Amazon Selling Partner in the list of supported integrations to add it. If it is already set up, open the existing Amazon Selling Partner Global Integration instead; it no longer appears in the list of integrations available to add. Use a single Amazon Selling Partner Global Integration: Merchant Integrations use the oldest active one.
- Set Active to Yes, provide a Notification Email if needed, and click Save.
- In the same browser, sign in to Amazon Seller Central with your 3PL's Amazon account, signing out of any other Seller Central account first. In OAuth Connection, click Authorize, verify that the account shown is your 3PL's, and complete Amazon's authorization prompts.
- After returning to ShipStream, verify Connection Active in OAuth Connection.
- Enter the Linked Carrier Accounts on this Global Integration.
Configure Each Merchant
- Ask your administrator or ShipStream support to enable Allow Seller ID Override at System > Configuration > Integrations > Amazon Selling Partner, selecting Global in the configuration scope switcher. This is an instance-wide setting; it cannot be enabled separately for one Merchant.
- Navigate to System > Integrations > Merchant Integrations. Add an Amazon Selling Partner subscription for the Merchant, or open its existing subscription.
- Set Enable Buy Shipping to Yes, choose Allowed Shipping Services, and enter the Amazon seller ID (Merchant Token) of the seller who owns the Orders in Seller ID Override. Save the subscription and confirm that Status is Active; if it is Inactive, click Activate. Leave the Merchant Integration without its own Amazon authorization to use the Global connection.
- Verify the message Using Global Integration "Amazon Selling Partner". Merchant authorization is optional. The Authorize button remains available if the Merchant later needs its own connection.
- Navigate to System > Configuration > Shipping Methods > Amazon Selling Partner and select this Merchant's configuration scope. Set Enabled to Yes, Shipping API to Amazon Shipping (v2), and Connection Profile to 3PL (orders of other sellers).
- Select an Amazon Shipping Business that belongs to the region of the authorized Amazon account. The Merchant uses the Linked Carrier Accounts saved for that business on the Global Integration, so make sure they are saved there.
- Configure Rate Source and the OTDR premium settings described below, then click Save Config.
Repeat the Merchant steps for every seller whose Orders you ship.
If Allow Seller ID Override is disabled, saved overrides are ignored. Enable the instance-wide setting before buying shipping for another seller.
When the Orders belong to the Amazon account that authorized the connection, leave Seller ID Override blank. ShipStream uses that account's seller ID automatically, including with a shared Global connection. Orders belonging to a different seller still require that seller's correct override.
Linked Carrier Accounts
The 3PL (orders of other sellers) profile buys labels with the carrier accounts that Amazon links to your 3PL's Amazon account. Enter them on the integration that owns the Amazon connection in use:
- Global Integration - for Merchants that use the shared Global connection. All of these Merchants use the accounts saved on the Global Integration.
- Merchant Integration with its own connection - for a Merchant whose Merchant Integration is authorized with your enrolled 3PL account. Its own accounts are used instead.
A Merchant Integration that uses the shared Global connection cannot add accounts of its own. It shows This Merchant Integration uses the shared Amazon connection of Global Integration "…", so the Linked Carrier Accounts saved there are used. A Merchant Integration that is not the one its Merchant buys Amazon shipping with does not show this message (see Messages in the Editor below).
Enter the Accounts
Discover Accounts uses the seller ID of the authorized connection automatically, regardless of a Merchant's Seller ID Override. If ShipStream reports that the connected Amazon seller ID is unavailable, contact support.
- Authorize the connection first. A new integration must be saved before its accounts can be entered, and after authorizing or changing the connection credentials, reload the page.
- Open the integration under System > Integrations > Global Integrations or System > Integrations > Merchant Integrations.
- In Linked Carrier Accounts, choose the Amazon Shipping Business. The list shows the businesses of the connection's region, for example AmazonShipping_US for North America, plus any other business that still has saved accounts, such as accounts saved before the connection moved to another region. Those accounts are read-only and can only be deleted. Each business has its own list of accounts.
- Click Discover Accounts to read the accounts Amazon links to the connection for that business. They are shown in the table for review and are not saved yet, each with the account number and nickname Amazon shows for it. If the table already has accounts, ShipStream asks before replacing them with the discovered accounts; when a carrier has several linked accounts and one of them is already in the table, only that one is kept. If Amazon returns no accounts, the table stays as it was and a message says so.
Accounts discovered from Amazon and not saved yet. UPS has two linked accounts, so one of them must be removed before saving:
- Review the rows. To enter an account by hand, click Add Account and fill in Carrier ID (Amazon's carrier code, for example UPS) and Carrier Account ID (the account ID Amazon shows for the linked account). Each carrier can have only one account per business. Click Remove to delete a row; when Amazon links several accounts of one carrier, remove the ones you do not use. The account number and nickname are shown only for discovered rows and are not saved. The last account of a business is deleted with Delete All Accounts for the business, described below.
- Click Save Accounts. Saving the integration does not save the accounts; if you leave the page or save the integration while rows are unsaved, ShipStream asks you to confirm that they can be discarded.
To delete every account of the selected business, click Delete All Accounts for and the business, for example Delete All Accounts for AmazonShipping_US. The accounts of the other businesses stay. The button is shown only for a business with saved accounts; it asks for confirmation and takes effect immediately, without Save Accounts. When the accounts cannot be changed, for example before the connection is authorized or while the integration is inactive, the rows are read-only and only this button is shown. If the saved accounts can no longer be read, the editor shows only Delete All Accounts, which deletes every list saved on the integration.
When a Merchant buys a 3PL label for a business that has no saved accounts, the purchase stops with Linked Carrier Accounts for AmazonShipping_US are required for the 3PL Connection Profile., followed by where to enter them: the warehouse's shared Amazon connection for the accounts of the Global Integration, or the Merchant Integration by its number and Merchant, for example Merchant Integration #7 of merchant "Acme". The Global Integration is not named, because label errors can appear in the Merchant's order history.
Messages in the Editor
- These accounts were saved for another Amazon connection and are not used. - The integration was connected to a different Amazon account since the accounts were saved. Labels are not bought with them. Click Delete All Accounts for the business, then discover or enter the accounts again.
- These accounts are not used while this Merchant Integration uses the shared Amazon connection. - The Merchant Integration lost its own connection and now uses the Global connection. Its old accounts can only be deleted.
- This integration is not selected for shared shipping - Merchants use only the active Amazon Selling Partner Global Integration with the lowest ID, so the accounts of any other Global Integration are not used.
- This Merchant Integration is not the one its merchant buys Amazon shipping with - Labels are bought through the Merchant's most recently created active Merchant Integration with Enable Buy Shipping set to Yes. This one is not it: it is inactive, Enable Buy Shipping is off, or a newer eligible Merchant Integration exists. Its accounts are not used.
- This integration is inactive. - The accounts of an inactive integration can be deleted but not changed.
- The Amazon Shipping (v2) API is not available for the "FE" marketplace region. - The Amazon connection is in the Far East region, which has no Amazon Shipping businesses, so no Linked Carrier Accounts can be entered for it.
- The Linked Carrier Accounts or the Amazon connection changed since this page was loaded. Reload the page. - Another user saved the accounts, or the connection changed, after you opened the page. Your edits stay on screen, but nothing more can be saved until you reload the page and review the saved accounts.
- The result of saving the Linked Carrier Accounts is unknown. - ShipStream could not confirm the save. Reload the page and check the saved accounts before trying again.
The Connection Profile setting points to the integration that owns the accounts:

Which Connection Is Used?
For OAuth connections, ShipStream uses this order:
- The Merchant Integration's own connection, when fully configured.
- The Amazon Selling Partner Global Integration, when the Merchant has no complete connection and the Global Integration is active, connected, and has not been deleted.
- A connection error when neither is available. The Merchant panel shows Connection is not configured. and v2 shipping reports The Amazon connection is not established.
Every Merchant Integration using OAuth without a complete connection uses the Global account when it is available, regardless of Shipping API or Connection Profile. Review all Merchants before enabling the Global Integration. For Merchants that buy shipping on each seller's own Amazon account, authorize that account on the Merchant Integration or set Enable Buy Shipping to No until it is configured.
The Merchant's Admin UI names the Global Integration. The Client UI reports Using the warehouse's shared Amazon connection. Merchant authorization is optional. and does not test the shared connection. Authorizing a Merchant Integration affects that subscription's own connection; it does not replace the Global authorization. A failed authentication does not cause ShipStream to switch to another account. Without a usable Global Integration, existing Merchant connections work as before.
Installations configured with Use OAuth set to No continue to use their manually configured credentials. They do not use the Global fallback.
Re-authorization After the Update
After the update, use Authorize on the integration you intend to use. Existing Merchant authorizations are not transferred to the Global Integration automatically.
Keep the existing Global Integration when reconnecting its account. Once you begin authorization, ShipStream retains its token secret and prevents deletion, even after Disconnect. You can Deactivate the integration instead. An integration whose authorization has never been started can still be deleted.
You can Disconnect and then Authorize the same Amazon account on that same Global Integration. Disconnect also releases the account on ShipStream Data Border, so it can then be authorized on a Merchant Integration instead. If ShipStream cannot reach ShipStream Data Border, the connection is kept and you are asked to try again in a few minutes. Disconnecting leaves Merchants that rely on the Global Integration without a usable connection until authorization is restored.
If you reconnect to a different Amazon account, operations on older labels stop with a message that the connection has changed since the purchase: voiding and tracking for v2 labels, and voiding for v0 labels whose OAuth purchase connection was recorded. Older v0 labels without a recorded purchase connection use the current connection when voided. Changing Shipping API alone does not have this effect: labels remain associated with the API and connection used to buy them.
One Amazon Account per Subscription
An Amazon Seller Central account can be connected to only one Amazon Selling Partner subscription at a time. If you authorize an account that is already connected to another subscription, you see a page titled This Amazon account is already connected and nothing is changed. Either:
- Sign in to Seller Central with the correct account and click Authorize again, or
- To move the account to this subscription, open the subscription it is connected to now, click Disconnect in the OAuth Connection section, then return to this subscription and click Authorize. Moving a 3PL connection stops Buy Shipping for every Merchant whose subscription used it.
Deleting a connected subscription from its subscription page also disconnects its Amazon account. If ShipStream cannot reach ShipStream Data Border at that moment, the disconnect or deletion is not carried out and you are asked to try again in a few minutes.
An Amazon account that was disconnected before ShipStream released accounts on disconnect can stay blocked with no subscription left to disconnect it from. If you see This Amazon account is already connected and no subscription shows the account as connected, contact ShipStream support to release it.
Service Selection
Amazon determines which shipping services are eligible for each Order. ShipStream selects from the supported services Amazon returns, subject to your Allowed Shipping Services and Warehouse restrictions. Configure the Merchant's allowed services in Plugin Configuration on its Merchant Integration; the instance-wide Allowed Shipping Services setting is under System > Configuration > Shipping Methods > Amazon Selling Partner.
If no eligible service is allowed, ShipStream cannot complete the Shipment through Amazon. Allow an eligible service or use another shipping method. If you complete a Shipment offline or outside the Amazon integration, ensure its tracking number is sent to Amazon.
Amazon Shipping (v2)
Settings
Navigate to System > Configuration > Shipping Methods > Amazon Selling Partner. You can set these values globally or override them for a Merchant. At Merchant scope, clear Use Global for a field to save an override.
| Setting | Description |
|---|---|
| Shipping API | Choose Amazon Shipping (v2) for the settings below. Merchant Fulfillment (v0) keeps the legacy service-selection behavior. |
| Connection Profile | Seller (own orders) buys shipping for the connected seller. 3PL (orders of other sellers) buys shipping for other sellers using an account that Amazon has enrolled for this purpose, with the Linked Carrier Accounts of the integration that owns the Amazon connection in use. |
| Amazon Shipping Business | Must match the region of the Amazon connection, for example AmazonShipping_US for North America. The Far East region is not supported by v2. |
| Rate Source | Amazon rates only uses Amazon's prices. Internal rates only uses your Rate Tables for matching carrier services and stops the purchase if an eligible service cannot be priced. Internal rates with Amazon fallback uses Amazon's price when a service has no matching shipping method, rate plan, zone, or fee schedule. A service forbidden for the Warehouse remains excluded. |
| OTDR Protection Premium Type | Choose Fixed amount per package or Percent of the package baseline price. |
| Maximum OTDR Protection Premium | The most each package may cost above its baseline for a rate that includes On-Time Delivery Rate (OTDR) protection. Use 0 to buy protection only when it costs no more than the baseline. |
| Preferred Carrier | Visible only with v2 and Amazon rates only. Choose None, FedEx, UPS, USPS, or DHL Express (Mexico). Protection and package price limits take precedence over this preference. DHL Express (Mexico) can be preferred only for single-package Shipments. |
| Savings Threshold for Secondary Carrier | With v2 and Amazon rates only, the minimum positive savings on the whole Shipment required to choose another equally protected courier instead of the preferred courier. Blank is treated as 0, so any positive saving can switch couriers. It is an amount, not a percentage, and is ignored when Preferred Carrier is None. |
| Order Item Ref Check | Before switching to v2, click Check Open Orders to find open Orders with an Amazon shipping method that lack an Order Item Ref. Click Check More Orders until all open Orders have been checked. |
With v2, the per-category Preferred Carrier for... fields and Require Rates from Preferred Carrier are hidden and ignored. Their saved values remain available if you return to v0, and a saved Require Rates from Preferred Carrier value does not prevent switching to v2. The single v2 Preferred Carrier starts at None; existing per-category preferences are not copied into it.
With either internal Rate Source, v2 hides Preferred Carrier and Savings Threshold for Secondary Carrier, and any saved preference has no effect. The threshold has one saved value shared between the API modes, so review it when switching modes or choosing Amazon rates only.
Choosing a Rate and OTDR Protection
ShipStream selects one value-added service from each group Amazon returns. It selects the requested signature option when offered; in other groups it chooses the lowest additional cost without adding an unrequested signature. Services already included in the rate's total charge have no additional cost and are not charged again. If a group has no suitable option, that rate cannot be used.
Amazon marks some rates as protecting the seller's On-Time Delivery Rate (OTDR). ShipStream first applies the same protection and price limits for all v2 rate sources:
- Consider only choices that can ship every package with one courier. FedEx Ground and FedEx Express are separate couriers; packages cannot be split between them.
- Find the cheapest complete Shipment. Each package's price in that Shipment is its baseline. When complete Shipments tie for the lowest total, ShipStream considers each tied baseline.
- Allow a protected package to cost up to its baseline plus its own premium limit. An unprotected package must cost no more than its baseline. Unused allowance from one package cannot increase another package's limit.
- Prefer the complete Shipment with the most protected packages.
- Among choices with that same number of protected packages, choose the lowest total price, unless the Amazon-rate carrier preference below applies.
For example, with Fixed amount per package and a Maximum OTDR Protection Premium of $2:
| Rates offered (package 1, package 2) | Result |
|---|---|
| FedEx $10 unprotected, $10 protected; UPS $13 protected, $10 protected | FedEx for $20 with one protected package. UPS would protect both, but package 1 exceeds its $2 premium limit. |
| FedEx $10 unprotected, $10 unprotected; UPS $11 protected, $11 unprotected | FedEx for $20 without protection. The unprotected UPS package 2 costs more than its baseline. |
With a 5% premium limit, suppose courier X offers $10 and $20, Y offers $20 and $10, and Z offers a protected $21 and an unprotected $10. X and Y both provide $30 baselines. Against Y, Z's first package adds $1 to a $20 baseline, within 5%, so ShipStream chooses Z for $31 with one protected package.
For a single package with a $10 baseline and a 20% limit, a protected $12 rate is allowed; a protected $12.01 rate is not.
Preferred Carrier with Amazon Rates
With Amazon Shipping (v2) and Rate Source set to Amazon rates only, Preferred Carrier applies only to complete Shipments that pass the package price limits and have the maximum number of protected packages.
Among those choices, the preferred courier wins unless another courier offers positive savings of at least the Savings Threshold for Secondary Carrier, measured across the whole Shipment. Equal prices never cause a switch away from the preferred courier, even when the threshold is 0. When the preference does not apply, ShipStream chooses the lowest total among the most protected eligible choices; tied totals use a consistent ordering.
| Example for one package | Result |
|---|---|
| Preferred rate $12 unprotected; other rate $10 unprotected; threshold $3 | The $10 rate wins. The preferred rate exceeds the unprotected package's $10 baseline. |
| Preferred rate $12 protected; other rate $10 protected; both within the premium limit; threshold $3 | The $12 preferred rate wins. Savings of $2 do not meet the threshold. |
| The same protected rates with threshold $2 | The $10 rate wins. The positive $2 savings meet the threshold. |
| The same protected rates with a blank threshold or threshold $0 | The $10 rate wins. Any positive saving meets the threshold. |
| Equally protected rates at the same price; threshold $0 | The preferred rate wins because there are no positive savings. |
If another courier protects more packages, it takes precedence. If the preferred carrier has no complete Shipment within the limits, ShipStream uses the best remaining choice. Shipment comments record the configured preference, the chosen courier, and why the preference did or did not apply. Refreshing an expired rate keeps the planned courier rather than selecting a new preferred courier.
With Preferred Carrier set to None, or with either internal Rate Source, ShipStream continues to rate shop using protection, package price limits, and total price. See Rate Shopping for configuring internal rates.
Preferred Carrier with Merchant Fulfillment (v0)
The v0 settings remain unchanged. Under System > Configuration > Shipping Methods > Amazon Selling Partner, use the five per-category fields: Preferred Carrier for Standard Delivery, Preferred Carrier for Free Economy, Preferred Carrier for Two-Day Delivery, Preferred Carrier for One-Day Delivery, and Preferred Carrier for Expedited Delivery.
When Require Rates from Preferred Carrier is No, Savings Threshold for Secondary Carrier allows another carrier when it offers positive savings that meet the threshold. In v0, leave the threshold blank to keep the preferred carrier regardless of savings, or enter 0 to switch for any positive saving. When Require Rates from Preferred Carrier is Yes, the threshold is hidden and a Shipment cannot be completed through another carrier. If Amazon offers no eligible rate for the required carrier, retry later or choose another shipping method.
These per-category preferences and the requirement below apply only to Merchant Fulfillment (v0):

Excluded Services
To exclude services for an individual Order, use Other Shipping Options. Its amazon_excluded_services value accepts a list of Amazon service IDs or PCRE regular expressions delimited with /. For example, {"amazon_excluded_services": ["/^UPS/"]} excludes UPS services for that Order. These exclusions further restrict the services Amazon offers; they cannot make an ineligible service available.
You can populate this option conditionally with a Before Create Order Script, for example to exclude a carrier on certain days.
List of Amazon Shipping Services
These are the services recognized by ShipStream. Availability depends on the Amazon account, destination, package, and services Amazon returns. The service IDs can be used in Other Shipping Options exclusions.
| Carrier | Service | Amazon service ID |
|---|---|---|
| USPS | USPS Priority Mail Express® | USPS_PTP_EXP |
| USPS | USPS Priority Mail Express Legal Flat Rate Envelope | USPS_PTP_EXP_LFRE |
| USPS | USPS Priority Mail Express Padded Flat Rate Envelope | USPS_PTP_EXP_PFRE |
| USPS | USPS Priority Mail® | USPS_PTP_PRI |
| USPS | USPS Priority Mail Cubic® | USPS_PTP_PRI_CUBIC |
| USPS | USPS Priority Mail® Large Flat Rate Box | USPS_PTP_PRI_LFRB |
| USPS | USPS Priority Mail Legal Flat Rate Envelope | USPS_PTP_PRI_LFRE |
| USPS | USPS Priority Mail® Flat Rate Box | USPS_PTP_PRI_MFRB |
| USPS | USPS Priority Mail Padded Flat Rate Envelope | USPS_PTP_PRI_PFRE |
| USPS | USPS Ground Advantage | USPS_PTP_PSBN |
| USPS | USPS Ground Advantage (1 - 70 lb) | USPS_PTP_GAH |
| USPS | USPS Ground Advantage (less than 1lb) | USPS_PTP_GAL |
| USPS | USPS Ground Advantage Cubic | USPS_PTP_GAC |
| UPS | UPS Ground | UPS_PTP_GND |
| UPS | UPS 2nd Day Air | UPS_PTP_2ND_DAY_AIR |
| UPS | UPS Next Day Air | UPS_PTP_NEXT_DAY_AIR |
| UPS | UPS Next Day Air (Saturday) | UPS_PTP_NEXT_DAY_AIR_SAT |
| UPS | UPS Next Day Air Saver | UPS_PTP_NEXT_DAY_AIR_SAVER |
| FEDEX | FedEx Priority Overnight® | FEDEX_PTP_PRIORITY_OVERNIGHT |
| FEDEX | FedEx Priority Overnight® (Saturday) | FEDEX_PTP_PRI_OVERNIGHT_SAT |
| FEDEX | FedEx Standard Overnight® | FEDEX_PTP_STANDARD_OVERNIGHT |
| FEDEX | FedEx 2Day®A.M. | FEDEX_PTP_SECOND_DAY_AM |
| FEDEX | FedEx 2Day® | FEDEX_PTP_SECOND_DAY |
| FEDEX | FedEx Express Saver® | FEDEX_PTP_EXPRESS_SAVER |
| FEDEX | FedEx Home Delivery® | FEDEX_PTP_HOME_DELIVERY |
| FEDEX | FedEx Ground® | FEDEX_PTP_GROUND |
| DHLMX | DHL Express International | DHLMX_PTP_PACKAGE_EXPRESS |
| USPS | USPS First Class International | USPS_PTP_FC_INTL |
| USPS | USPS Priority Mail International | USPS_PTP_PRI_INTL |
| USPS | USPS Priority Mail Express International | USPS_PTP_EXP_INTL |
Order Item Ref
Amazon Shipping (v2) requires the Amazon order item ID in Order Item Ref for every shipped Order item. ShipStream rejects a new Order, or a change to an Amazon shipping method, when a required reference is missing for a Merchant using v2. Packaging items are not sent to Amazon and do not need this reference. Items use the Order's units: six pieces shipped as two ordered packs are sent as a quantity of 2. Fractional quantities are rounded to whole units for Amazon.
Before switching an existing Merchant to v2, run Order Item Ref Check and correct the listed open Orders. A matching SKU does not replace the required Order Item Ref in v2.
Item Weights and Values
Both v2 connection profiles require item weights and customs values, including for domestic shipments. ShipStream sends the total physical weight and allocated customs value for each Order Item Ref within each package. For example, two items weighing 100 g and valued at USD 12 each are sent as quantity 2, weight 200 g, and value USD 24. Quantities remain in the Order's units when shipping packs or kit components.
Existing package-item customs allocations take precedence. Otherwise, ShipStream uses the Order item's customs value, the Order's customs value, or the Product's customs value, following the normal customs allocation rules. Kit and converted components need positive Product customs values to distribute the total, even when a value is supplied on the Order or Order item. A zero unit customs value is treated as unset; an allocated zero value remains zero. Values use the installation's default currency, without conversion. Domestic allocation is calculated for Amazon without adding customs fields or requiring international export information.
Item weights use the package's units: grams for metric packages or ounces for imperial packages. Each item line must have a positive weight representable to 0.01, and the combined item weights cannot exceed the package weight. Correct any missing values or invalid weights before buying a label. Changing effective item values after a label purchase can prevent reuse of that saved label; cancel the existing label before buying a replacement. Packing or voiding another Shipment does not by itself prevent reuse when the purchased Shipment and its value sources are unchanged.
Amazon Orders
Your Orders must identify the Amazon Order, its items, and an Amazon shipping method.
Amazon Order ID
Enter the Amazon Order ID in the form NNN-NNNNNNN-NNNNNNN, by itself, in Order # or Order Ref #. Alternatively, set amazon_order_id in Other Shipping Options. That explicit option takes precedence, followed by Order Ref #, then Order #.
Amazon ASIN or Seller SKU
With Merchant Fulfillment (v0), ShipStream can match the Amazon ASIN or seller SKU to the Order item's SKU, Product SKU, Product Vendor SKU, or Product External ID. An Order Item Ref containing the Amazon order item ID can identify the item directly. With Amazon Shipping (v2), every shipped item needs the Amazon order item ID as described above.
Shipping Method
Choose one of these Amazon shipping methods on the Order. Allowed Methods controls which are available to your Merchants. Amazon Merchant Fulfillment can be used when the Order's Amazon service level is unknown; these method names also apply when Shipping API is v2.
| Description | Code |
|---|---|
| Amazon Merchant Fulfillment | amazon_ANY |
| Amazon Standard Delivery | amazon_Standard |
| Amazon Free Economy | amazon_FreeEconomy |
| Amazon Two-Day Delivery | amazon_SecondDay |
| Amazon One-Day Delivery | amazon_NextDay |
| Amazon Expedited Delivery | amazon_Expedited |
Label Handling and Restrictions
Labels remain associated with the API and Amazon connection used for their purchase, so changing Shipping API does not prevent voiding an existing label. Keep the original Amazon connection available for label operations. ShipStream tracks labels purchased with Amazon Shipping (v2) through Amazon; v0 labels retain their existing tracking behavior.
Authorizing a Merchant's own connection applies to new purchases. Existing labels bought through the Global Integration continue to use that Global connection while it remains active and connected to the same Amazon account and region: v2 labels for voiding and tracking, and v0 labels for voiding. This includes labels completed through Packing Instruction recovery, and saved-label recovery retains the original connection too. If that connection is no longer available, voiding the label reports that the connection has changed since the purchase; a forced void still unpacks the Shipment, but the label is not refunded. Keep the original connection active and connected to the same Amazon account until its labels no longer need to be voided. Older Merchant Fulfillment (v0) labels, bought before ShipStream started recording the purchase connection, are voided through the Merchant's current connection.
Amazon Shipping (v2) supports normal goods only in ShipStream. Packages containing fully regulated hazardous materials, ORM-D, limited quantities, small quantities, or lithium batteries are rejected before purchase because ShipStream does not supply Amazon's required dangerous goods declarations. Use another carrier for those Shipments.