Vendor Central Shipping Workflow EDI Transaction Testing

Updated 5 days ago

Overview

This article discusses the tasks associated with testing the Amazon Vendor Central Electronic Data Interchange (EDI) transactions. It is part II of a process described in the Vendor Central Shipping Workflow article. The Vendor Central Shipping Workflow gives information on how to utilize the process and is the driving document. This article is cross-linked to the Vendor Central Shipping Workflow article and embedded in this document are links back for ease of navigation as shown following.

To access the Vendor Central Workflow article click here

The 753 routing request, the 856 tracking, and the 810 invoice files all need to be tested before you can begin using them in production.

Testing routing requests (EDI 753)

Vendor Central does not have a testing portal for the routing documents. To enable the sending and the receiving of routing instructions for your account, you will need to open up a case with three 753 routing request files and ask Amazon to validate them. You can generate 753 files for any three orders, as Amazon will not actually process them as routing requests.

  1. Follow the instructions above for adding orders to a shipping agenda, adding the info required for the routing document, and then downloading the routing instructions. (Make sure to choose the download option from the action menu rather than the upload option).
  2. Add all three 753 EDI files to a zipped folder, and then attach that folder to the case, asking Amazon to validate the files.
Once the files are validated and your account is approved for routing via EDI, you can still submit routing requests manually. Submitting the routing request via EDI facilitates Amazon processing the request and sending back the routing instructions via EDI.
To return to the Vendor Central Shipping Workflow article section explaining the Routing Request (EDI 753), click here.

Testing ASN tracking (EDI 856)

SellerCloud pretest setting requirement:

For testing, you will need to manually enter some information on the shipment that would normally be populated automatically.

  1. In SellerCloud, navigate to Settings > Company > Toolbox > Vendor Central Settings > General Settings > Enable Use Test Mode For ASN
  2. Click Save Settings.

Vendor Central testing process:

In Vendor Central, navigate to: EDI > Self Service Setup > Choose the vendor ID you are working with and click “View EDI Setup” > Click “Start” (or “Edit” if you have already started) on the Advance Shipment Notification (ASN).

Business Requirements: Read and then click “Acknowledge and continue".

Identifiers:

  • Message Format should be “X12”.
  • Inherit identifiers should be checked, click “Save and continue.

Settings: Select all checkboxes that apply to your account and click “Save and continue”.

Test Environment:

  1. Review the settings in the draft column. Changes can be made to any previous steps.
  2. Click Promote and then Confirm.
  3. Wait for the settings to be promoted (you can click "Refresh" until you see the data has been promoted) and then click Continue.
To return to the Vendor Central Shipping Workflow article section explaining advance shipping notifications, click here.

Integration testing process:

The types of ASN's required for testing may be different depending on the settings you have selected, but the process is similar for all tests. Test each scenario by downloading the PO order file, importing it into SellerCloud, creating a shipment, and then generating a tracking file.

  1. A list of test scenarios will be displayed.
  2. Click Start Test and then “Refresh” until the details are populated.
  3. Click “Download Purchase Order” to download the 850 txt file.

SellerCloud integration testing process:

The types of ASN’s required for testing may be different depending on the settings you have selected. The process is similar for all the tests.

Test each scenario by downloading the PO order file, importing it into SellerCloud, creating a shipment, and then generating a tracking file.
The test marked “Small Parcel” should be processed as a small parcel shipment. All other tests, including “ASN license plate receive (SSCC)” should be processed as Less-Than-Truckload (LTL).
  1. Open SellerCloud and navigate to Orders > Import Orders.
  2. Select the company to create the order in and “Vendor Central” as the channel.
  3. Choose the file that you just downloaded and click Process Order. A queued job will be created.
  4. Click on the link for the job and wait for it to finish processing.
  5. Once it is completed, you will see a “View Orders” link towards the top of the page. Click on that to open up the order that was just created.
  6. Open the order details page and choose “Check availability” from the action menu.
  7. Accept the full qty for both items and click “Save”. The order will be added to a Vendor Central Shipping Agenda.
    The checkbox to send the 855 should NOT be Checked.
  8. Add both items to the same shipment. For detailed instructions click here.
  9. Click the “Edit” link on the shipment.
    1. Set the fields required for the 753 (see Routing Requests above).
    2. Set the Amazon Reference ID - Any number can be used for this.
    3. Set the SCAC (Carrier) Code.
      1. Valid values for small parcel carriers - UPSN, FDEG.
      2. Valid values for Less-Than-Truckload (LTL) carriers - RDWY, ABFS, EXLA
The Amazon Reference ID and the Carrier Code normally come in from the 754 Routing Instructions, but since that step is skipped for testing, it needs to be set manually.
  1. The next step is to manage the pallets and cartons for this shipment. Click on the “Manage” link in the “Number of Cartons/Pallets” column in the grid and follow the instructions above to set up the pallets and cartons.
  2. Select the shipment and choose “Print SSCC Labels” from the action menu. This will create an SSCC code for all the pallets and cartons that do not yet have one. You do not need to send the labels to Amazon for approval, but the ASN does require the SSCC code so it must be generated.
  3. Enter the tracking info:
    1. For LTL test orders: Click on the “Ship” link towards the right of the grid.
      1. Enter the PRO number (you can enter any number since it is just a test).
      2. Click Update and Print BOL.
    2. For Small Parcel test orders:
      1. Click on the “Edit” link on the left side of the grid and enter one tracking number for each carton.
      2. You will also need to enter a BOL Number and check the “Include BOL # in Small Parcel ASN” checkbox. (Vendor Central requires the BOL Number on the Small Parcel ASN for testing only).
In production, shipping labels will need to be printed and that will update the tracking numbers.
  1. Select the shipment and choose Generate ASN Tracking and Download.
  2. In Vendor Central, click Upload Advance Ship Notification and choose the ASN file. It will take a few minutes for the test status to update.
  3. Once all the tests have been completed successfully, click Continue. On the following page, click Schedule Promotion and either choose Immediately or select a date and time and click Confirm.

Testing invoices (EDI 810)

  1. In Vendor Central, navigate to: EDI > Self Service Setup > Choose the vendor ID you are working with and click View EDI set up > Click Start (or Edit if you have already started) on the Invoice (INV).
  2. Click Continue on the first four steps until you reach the Integration Test section. Follow the same instructions as when testing the ASN to download the PO file, import it into SellerCloud, add it to a shipment, and mark the shipment as shipped.
  3. Select the shipment and choose Generate Invoice and Download from the action menu.
  4. In Vendor Central, upload the invoice file and wait for the test status to refresh. Once the test has been completed successfully, click Continue.
  5. On the following page, click Schedule Promotion and either choose Immediately or select a date and time and Confirm. If you would like invoices to be uploaded automatically from SellerCloud, make sure the setting to Enable Invoice Upload (810) is enabled on the Vendor Central General Settings page.
Parallel Testing: Vendor Central requires parallel testing for EDI invoices. This means that once you launch the 810 transaction and start sending invoices via EDI, you will still need to submit manual invoices. Vendor Central will validate the EDI invoices against the manual invoices, and once they determine that the EDI invoices have the correct data they will send you an email informing you that the manual invoices are no longer necessary. At that point, the EDI invoices will be considered in production.
To return to the Vendor Central Shipping Workflow article section explaining invoices, click here

Before launching to production

  1. Make sure the following are set as follows on the Vendor Central General Settings page in SellerCloud:
    1. ·         Disable Use Test Mode For ASN
    2. ·         Enable Enable Fulfillment Upload (856)
    3. ·         Enable Enable Invoice Upload (810)

Notes:

Even once a transaction is in production, you can still choose to submit routing, tracking or invoices manually for a particular shipment.
Inventory: Depending on the setting on the Vendor Central General Settings page, the orders will either begin reserving inventory as soon as they are created in SellerCloud, or once availability is checked (by marking the payment status as Authorized). The qty reserved will show in the inventory movement as a regular OrderReserve, even once it is added to a shipment. Once a shipment is shipped, the qty on that shipment will show as a CompletedShippingAgenda movement. If there is still some unshipped qty, it will remain as an OrderReserve.
Kits: Vendor Central only knows about the kit parent, so the kit cannot be split between shipments or even between cartons /pallets. Of course if there are multiple kit parents ordered, the kit PARENTS can be split between shipments or cartons, but all the components must stay with each parent.


How did we do?