How to configure Amazon Vendor Direct Fulfillment in techSHIP
Last updated: October 5, 2026
This guide explains how to add and configure this carrier connection, review its available carrier-specific settings, and understand the shipment requirements and operational constraints that apply.
Carrier Requirements and Specifications
This section summarizes onboarding requirements and lists confirmed carrier-specific constraints.
To review all supported carriers and their specific requirements, see: techSHIP supported Carriers - Master List [Guides List].
Onboarding Requirements
The Amazon Vendor Direct Fulfillment integration supports:
Vendor Central authorization
Merge processing
Bundle processing
Item matching against the Amazon purchase order
Information to be Provided
The following credentials and data points are mandatory to connect to Amazon Vendor Direct Fulfillment. Ensure you have these items available before starting the setup:
DATA ELEMENT | SOURCE (HOW TO OBTAIN) |
|---|---|
Vendor Central account access | The account owner completes authorization directly through Amazon using Register with Vendor Central. |
Region and Country | The account owner provides the Amazon account's region and country. |
Contact email | Provided by the account owner. |
Sender information | Provided by the account owner for the Baseline Account's sender fields. |
Selling party | The Amazon selling-party identifier associated with the vendor's orders. Obtain it from the vendor's Amazon account or order data. |
Shipping party | The Amazon ship-from-party identifier associated with the shipping location. Obtain it from the vendor's Amazon account or order data. |
Settings to be Verified
The following account configurations must be validated to prevent errors during the connection setup or the shipping process:
FEATURE/SETTING | VALIDATION ACTION |
|---|---|
Vendor Central registration | Save the Baseline Account before using Register with Vendor Central, then complete Amazon authorization. |
Country | Confirm the country before registering. Re-register the account when changing it. |
Purchase order number | Ensure the configured reference resolves to the Amazon purchase order number. If the reference is empty, Customer order is used. |
Selling party and Shipping party | Confirm both identifiers correspond to the Amazon purchase order and shipping location. |
Multiple-package orders | Ensure each item has an item sequence number, either supplied with the order or resolved through Item match field. |
Merge processing | Use exactly one package per order when Package type is |
Bundle processing | Before enabling Allow bundles, ensure the order lines provide |
Specifications and Constraints
Operational Details
This section lists confirmed operational rules and limitations for this carrier:
The integration uses carrier identifier
AMAZONDFV3for Amazon Vendor Direct Fulfillment.Amazon supplies the actual shipping method and tracking numbers when returning the labels.
Label requests use synchronous processing by default. Asynchronous processing is available as a fallback for vendors whose labels cannot be generated through the synchronous flow.
Reprocessing an order whose labels already exist retrieves those labels from Amazon.
Multiple-package orders require an item sequence number for every line so Amazon can identify which items belong to each package.
Merge processing lets Amazon construct the shipment container and requires exactly one package per order.
For orders processed with explicit containers, each package must contain items. Orders without item lines must use Merge processing.
Supported package types are Carton, Pallet, and
[Merge].
Labels
The following table summarizes confirmed document support:
ITEM | SUPPORTED |
|---|---|
References | No |
BOL | No |
The standard Reference 1–4 fields do not customize the Amazon-generated label. Shipment unique identifier and Purchase order number serve separate operational purposes described under the Client Account settings.
For a comprehensive guide on how to use label references, see: Using order References in your labels [Step-by-Step guide].
Configuring a Baseline Account
A Baseline Account serves as the fundamental connection point between techSHIP and the carrier's system. It acts as a template that holds the credentials and fundamental properties required to process shipments.
The techSHIP AI Assistant is available from the Carrier page for supported Carrier configuration tasks. For detailed conceptual information and advanced configuration, refer to techSHIP AI Assistant: Overview & Availability [Information].
Adding a Carrier
Before adding an account, you must ensure the Carrier entity is available for your location.
Click My Carriers from the left menu under the Carriers category.
Click Add Carrier.

Select the desired Carrier.
You may encounter additional messages depending on the carrier status or your plan:
Subscription Required (⭐): If the carrier has a star icon, you will see a message stating "To use this carrier, a subscription upgrade is required." Press Contact to Upgrade to proceed.

Carrier Suspended: If the carrier has not been used for an extended period, you will see a message stating “This carrier is currently on hold...” Click Request Assistance to reactivate it.

Setup Fee Waived: If a carrier from the same carrier group is already installed in your location, you can add this carrier without incurring additional fees.

If needed, update the carrier Name.
Click Add Carrier. Once the Carrier is added, you will be automatically redirected to the Carrier page to continue setting it up.

Enter the Code of the Carrier as it appears in your host system.
The Code of the Carrier must match exactly the value defined in the host system. Any discrepancy (including casing or extra spaces) may prevent the carrier from working correctly.
Click Save.

If your facility utilizes the centralized Pickup Schedule, we highly recommend adding this new carrier to your calendar now. While not required to process labels, this ensures accurate induction metrics for your Insights dashboards. To learn more, see Understanding the Centralized Pickup Schedule & Expected Induction Logic [Information].
Adding a Baseline Account
From the Carrier page, click Add Account to create a new Baseline Account.

You will be redirected to the Baseline Account page to complete the setup.
Entering incorrect values will prevent the system from generating shipping labels.
General Tab
In the General tab, define the administrative properties:

Name: Enter a descriptive name for the account.
Ensure to enter a descriptive name based on unique properties. E.g.:
Carrier Name - Account Number (CarrierX - 123456789)
Carrier Name - Consolidator Name (CarrierY - MyConsolidator)
Carrier Name
Usage: Select the most suitable option:
Test: Used for sandbox or onboarding purposes.
Production: Used for live shipping.
Keep the Status field set to its default Active value. An account must be Active to remain fully editable. For detailed conceptual information on account statuses, refer to How to Inactivate and Activate a Carrier Baseline Account [Step-by-Step Guide].
Carrier Tab
The Carrier tab contains the Baseline Account fields used to identify the carrier connection and define confirmed carrier-specific behavior. Fields for Amazon Vendor Direct Fulfillment are:
Registration id: Filled in after registration. You can leave it empty when registering a new account or paste an existing registration ID to reuse a registration across accounts or portals.
Register with Vendor Central: Opens the Amazon authorization flow. Save the Baseline Account before using this link and complete authorization directly through Amazon.
Region: Select the region associated with the Amazon account.
Country (re-register to change): Select the country associated with the Amazon account. Re-register after changing this value.
Label request mode: Controls synchronous or asynchronous label processing. Synchronous processing is the default, including when the field is left unset. Use asynchronous processing only as a fallback when Amazon cannot serve the synchronous flow for the vendor.
Contact email: Enter the account's contact email. This field is required.
Phone: Enter the account's contact phone number if applicable. This field is optional.
Sender address: Complete the sender information, including the required Sender name, Sender company, Address 1, City, and Zip fields.
Labels Tab
The integration handles labels returned by Amazon in ZPL or PNG format. techSHIP also supports converting the returned image label to PDF.
Finalizing the Setup
Once you have entered the required information, click Save.

From the Carrier page, you can now see the Baseline Account listed with the status Active.

The Baseline Account is now connected. To start shipping, you must assign this connection to a specific Client by creating an Account as described below.
Configuring a Client Account
Adding an Account
Before adding a Client Account, ensure that the Client has been created. For instructions creating a Client, see: How to create a Client profile [Step-by-Step guide].
Click Clients from the left menu under the Clients section.
Click the Edit icon for the desired Client.

Click Add Accounts.

Optionally, use the Search box to search by Baseline Account Name or Carrier.
Select the Baseline Accounts that will serve as the foundation for your new Client Accounts.
Click Add Accounts.

A toast notification will confirm the accounts were successfully assigned. Click the Refresh icon if recently added accounts are not displayed.

Click Edit on each newly created account.

Configure the available options in each tab (except Carrier).

For complete instructions on configuring this settings, see How to configure the Billing Account General Options tab [Step-by-Step Guide].
Carrier Tab
The Carrier tab contains the Client Account fields used to define confirmed carrier-specific behavior for this client. Fields for Amazon Vendor Direct Fulfillment are:
Service code: Select Amazon Service Code. Amazon returns the actual shipping method with the generated labels.
Override WMS Service Code: Enable this option to use the Client Account's configured service code instead of the service code supplied by the WMS.
Selling party: Enter the Amazon selling-party identifier. This field is required.
Shipping party: Enter the Amazon ship-from-party identifier for the shipping location. This field is required.
Shipment unique identifier: Select the reference used to identify each package. If the reference is empty, the techSHIP package ID is used.
Purchase order number: Select the reference containing the Amazon purchase order number. If the reference is empty, Customer order is used. Processing fails if no purchase order number can be resolved.
Item sequence number: Configure the source of the Amazon item sequence number for each order line. If left empty,
customfields:AmazonItemSequenceNumberis used. EnterMATCHto resolve every line's sequence number through Item match field.Buyer product identifier: Configure the source of the Amazon buyer product identifier for each order line. If left empty,
customfields:AmazonBuyerProductIdentifieris used.Item match field: Configure a line value that matches the Amazon purchase order's vendor product identifier or ASIN. This resolves missing item sequence numbers. For example, use
{UPC}when the UPC matches the identifier stored on the Amazon purchase order.
For multiple-package orders, every line must have an item sequence number after matching. Check Item sequence number and Item match field if processing reports missing sequence numbers.
Allow bundles: Enable this option to process bundle lines as a single packed item using
AmazonIsBundle,AmazonBundleProductIdentifier, andAmazonBundleQuantity.Package type: Select the applicable package type. Carton and Pallet identify explicit containers.
[Merge]lets Amazon construct the container.
When using [Merge], include exactly one package per order.
Sender name and Sender company: Enter the sender identification for this Client Account.
Override sender address: Enable this option when the Client Account requires a sender address different from the Baseline Account.
Specifying Rate Shopping Service Codes
This integration exposes Amazon Service Code and receives the actual shipping method from Amazon with the generated labels. The configured service code does not select a specific delivery carrier or service in the label request.
For detailed instructions on how to configure service-code restrictions where Rate Shopping applies, see: Include or exclude Service Codes when Rate Shopping [Step-by-Step Guide].
Finalizing the Setup
Once you have entered the required information, click Save.

With the account configured and requirements verified, you can now proceed to process orders as described below.
Configuring an Order
The steps described in this section are not required for carrier setup, and they are offered as an optional review if further order-level configuration is required.
Follow the UI Navigation steps in How to Edit an Order [Step-by-Step guide], using the carrier-specific values provided in this guide.
The Carrier tab contains the Amazon Vendor Direct Fulfillment-specific fields available when editing an Order. These fields define confirmed order-level behavior for the selected shipment:
Service code: Use Amazon Service Code for processing. Amazon returns the actual shipping method with the generated labels. The remaining carrier-specific processing settings are configured in the Client Account.
Click Save to apply the order-level changes. After the Order is updated, continue with the standard shipping workflow.