EDI workflow: Amazon Vendor

EDI workflow: Amazon Vendor

Overview

Find step-by-step instructions to process an EDI order through the Amazon Vendor workflow, where you request and receive routing instructions and dispatch goods to Amazon’s fulfillment centers.

These instructions are general in nature and may not precisely match individual workflows, which can include automations or specific configurations. They do not explain how to change an EDI order before acceptance. Users are advised to consult their documentation for accurate guidance tailored to their unique circumstances.

1. Import the Purchase Order (850, ORDERS)

The Amazon Vendor workflow begins when you receive the Purchase Order (850, ORDERS)  from Amazon. You’ll see new Purchase Orders on the Ready For Import tile on your Amazon Vendor integration dashboard.

Start by importing the Purchase Order. Three things will happen automatically:

  • The order is added to your EDI Dashboard. There you’ll process the order through the workflow.

  • For each Amazon fulfillment center receiving goods in the Purchase Order, a sales order is created and linked to the order (the linked sales orders).

  • The Functional Acknowledgement (997, CONTROL)  of the Purchase Order is created, which you’ll see on the Ready for Import tile on your trading partner’s integration dashboard.

Immediately export the Functional Acknowledgement of the Purchase Order. Then review the Purchase Order (see next step).

2. Review the Purchase Order (850, ORDERS)

The Purchase Order (850, ORDERS) specifies the details of the order:

  • Delivery window

  • Products

  • Quantities

  • Prices

You must review the Purchase Order and decide whether to accept or reject the sale.

Find the order on your EDI Dashboard. It should say Acknowledged in the Purchase Order column. If it says Awaiting Acknowledgement, return to your trading partner’s integration dashboard and export the Functional Acknowledgement of the Purchase Order (see previous step).

Otherwise, start by reviewing the delivery window. You’ll dispatch one shipment per fulfillment center, and each shipment must arrive at its fulfillment center on or after the Start Date and on or before the Cancel Date.

Now open the order (select inside the Customer PO cell) to see the linked sales orders – remember, a separate linked sales order is created for each fulfillment center receiving goods in the Purchase Order. Open each linked sales order (select inside the Order Ref cell) and review the products, quantities, and prices.

If you’re unwilling or unable to fulfill any part of the order (that is, products, quantities, or prices on any sales order) in the delivery window, you’ll reject it. If you’re willing and able to fulfill it entirely, you’ll accept.

To accept or reject the order, create and export the Purchase Order Acknowledgement (855, ORDRSP; see next step).

3. Create and export the Purchase Order Acknowledgement (855, ORDRSP)

The Purchase Order Acknowledgement (855, ORDRSP)  tells Amazon whether you accept the sale: that includes the delivery window as well as the products, the quantities, and the prices on every linked sales order.

Before accepting or rejecting the order, ensure you’ve already exported the Functional Acknowledgement of the Purchase Order (see first step).

Then create the Purchase Order Acknowledgement. You’ve created the Purchase Order Acknowledgement when you see it on the Ready For Export tile on your Amazon integration dashboard, and when the order says Scheduled in the Order Response column on the EDI Dashboard.

Now export the Purchase Order Acknowledgement. You’ve exported the Purchase Order Acknowledgement when the order says Awaiting Acknowledgement in the Order Response column on the EDI Dashboard.

Eventually, you’ll receive the Functional Acknowledgement of the Purchase Order Acknowledgement. Import that Functional Acknowledgement. You’ve imported it when the order says Acknowledged in the Order Response column on the EDI Dashboard.

Now, if you've rejected the sale, importing the Functional Acknowledgement of the Purchase Order Acknowledgement ends the workflow and removes the order from the default view of the EDI Dashboard.

Otherwise, if you've accepted the sale, cartonize the order (see next step).

4. Cartonize the order

Cartonization involves:

  • Packing the goods into boxes.

  • Assigning each box a unique serial shipping container code (SSCC).

  • Recording which goods are in each box.

Depending on your workflow, you may use third-party logistics (3PL) for cartonization or perform cartonization yourself.

If you are using 3PL, have your 3PL cartonize order. Cartonization is complete when the order says 3PL Confirmed in the Dispatch column on the EDI Dashboard. Your 3PL will have organized routing and dispatched the order. Now create and export the Advance Shipping Notice (856, DESADV; go to step 6).

If you aren’t using 3PL, perform cartonization yourself. Cartonization is complete when the order says Done in the Dispatch column on the EDI Dashboard. Then get the routing instructions (see next step).

5. Get routing instructions

In the Amazon Vendor workflow, you or your third-party logistics (3PL) must organize routing instructions with Amazon – the routing instructions tell Amazon how their order is cartonized and when it’s ready for collection, and they tell you the name of the carrier and Amazon Reference Number (ARN).

If you are using a 3PL, you can skip this step: your 3PL organizes the routing instructions with Amazon.

If you aren't using a 3PL (that is, if you’ve performed cartonization yourself), you must get the routing instructions from Amazon yourself. Depending on how you’ve had you workflow configured, you’ll get the routing instructions in one of two ways:

1. Get routing instructions from Amazon Vendor Central: In this scenario, you must log in to Amazon Vendor Central and generate routing instructions.

2. Get routing instructions via Cin7 Omni EDI: In this scenario, you create and export a Request for Routing Instructions (753) to Amazon (in the Routing Request column on the EDI Dashboard, the order will say Scheduled after you create the message and Awaiting Routing Instructions after you export it). Once you receive the Routing Instructions (754) from Amazon, which you’ll see on the Ready For Import tile on your Amazon integration dashboard, you’ll import them.

Once you have the routing instructions, dispatch the order and promptly create and export the Advance Shipping Notice (856, DESADV; see next step) – if Amazon doesn’t receive the Advance Shipping Notice for a shipment, they may reject the delivery and you may incur a chargeback.

6. Create and export the Advance Shipping Notice (856, DESADV)

The Advance Shipping Notice (856, DESADV) confirms for Amazon exactly how the order is being delivered: which units of which products are in which boxes, who is the carrier and what is the tracking code, when it was shipped and will arrive – everything.

In this workflow, you’ll create and export one Advance Shipping Notice (ASN).

First create the ASN. You’ve created the ASN when you see it on the Ready For Export tile on your trading partner’s integration dashboard, and when the order says Scheduled in the ASN column on the EDI Dashboard.

Then export the ASN. You’ve exported the ASN when the order says Awaiting Acknowledgement in the ASN column on the EDI Dashboard.

Eventually, you’ll receive the Functional Acknowledgement of the ASN. Import that Functional Acknowledgement. You’ve imported the Functional Acknowledgement when the order says Acknowledged in the ASN column on the EDI Dashboard.

Finally, create and export the Invoice (810, INVOIC; see next step).

7. Create and export the Invoice (810, INVOIC)

The Invoice (810, INVOIC)  is your request for payment from Amazon.

First create the Invoice. Then the order will say Scheduled in the Invoice column. Next export the Invoice. The order will say Awaiting Acknowledgement in the Invoice column. Finally, once you’ve received it, import the Functional Acknowledgement of the Invoice.

This ends the workflow and removes the order from the default view of the EDI Dashboard.

Was this article helpful?

Have more questions? Submit a request