Vendor Central Shipping Workflow EDI Transaction Testing

Updated 3 weeks ago

Overview

Most of the EDI transactions used in the Vendor Central Shipping Workflow must be tested before they can be used in production. This includes the 753 routing request, the 856 tracking, and 810 invoice files. The 754 routing instructions file does not need to be tested.

This article details the step-by-step instructions for getting through the testing process. To access the main Vendor Central Shipping Workflow documentation click here.

Testing routing requests (EDI 753)

Vendor Central does not have a testing portal for the routing documents. To enable the sending and 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. Create three separate shipments (either within the same agenda or on separate agendas), and set all the information required for routing for each one. For detailed instructions on setting up shipping agendas and shipments, click here. For the details on what is required for routing, click here.
  2. Select each shipment and choose Generate Routing Request and Download from the action menu.
  3. Add all three 753 EDI files to a zipped folder, and then attach that folder to a support 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)

For testing, you will need to manually enter some information on the shipment that would normally be populated automatically. To enable those fields, the integration must be set to Test Mode in SellerCloud:

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

Initial steps:

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).

  1. Business requirements:
  • Read and then click Acknowledge and continue.
  1. Identifiers:
  • Message Format should be X12.
  • Inherit identifiers should be checked.
  • Click Save and continue.
  1. Settings:
  • Select all checkboxes that apply to your account and click Save and continue.
  1. Test environment:
  • Review the settings in the draft column. Changes can be made to any previous steps.
  • Click Promote and then Confirm.
  • Wait for the settings to be promoted (you can click "Refresh" until you see the data has been promoted) and then click Continue.
  1. Integration test:
  • 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 (see below).
    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) shipments.

Test cases:

  1. A list of test scenarios will be displayed on the Integration test tab in Vendor Central. Click Start Test and then Refresh until the details are populated.
  2. Click Download Purchase Order to download the 850 purchase order file.
  3. Open SellerCloud and navigate to Orders > Import Orders.
  4. Select the company to create the order in and choose “Vendor Central” as the channel.
  5. Choose the file that you just downloaded and click Process Order. A queued job will be created. Click on the link for the job and wait for it to finish processing.
  6. Once it is completed, you will see a “View Orders” link towards the top of the page. Click on that to find the order that was just created.
  7. Open the order details page and choose Check Availability from the action menu. 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 acknowledgement 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.
    2. Set the Amazon Reference ID. Any number can be used for this as it is just for testing.
    3. Set the SCAC (Carrier) Code. You can choose any code you'd like as long as it is valid.
      1. Example valid values for small parcel carriers - UPSN, FDEG.
      2. Example valid values for 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, they need to be set manually.
  10. The next step is to set up the pallets, cartons, and box content for this shipment. Click the Manage link in the “Number of Pallets/Cartons” column in the grid to set up the configuration.
  11. 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 (tracking file) does require the SSCC code so it must be generated.
  12. Enter the tracking info:
    1. For LTL test orders:
      1. Click the Ship link towards the right of the grid.
      2. Enter the PRO number (you can enter any number since it is just a test).
      3. Click Update.
    2. For Small Parcel test orders:
      1. Click the Edit link on the left side of the grid and enter one tracking number for each carton. (In production, shipping labels will need to be printed and that will update the tracking numbers.)
      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).
  13. Select the shipment and choose Generate ASN Tracking and Download.
  14. 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.
  15. Once all the tests have been completed successfully, click Continue to move to the Production environment section.
  16. Click Schedule Promotion and either choose Immediately or select a date and time and click Confirm. See below for more details about launching this transaction.
To return to the Vendor Central Shipping Workflow article section explaining advance shipping notifications, click here.

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) transaction.
  2. Click Continue on the first four steps until you reach the Integration Test section (similar to the steps above for the 856 ASN). Follow the same instructions (steps #1-12 above) 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, click Upload Invoice and choose the invoice file. It will take a few minutes for the test status to update.
  5. Once the test has been completed successfully, click Continue to move to the Production environment section.
  6. On the following page, click Schedule Promotion and either choose Immediately or select a date and time and Confirm. See below for more details about launching this transaction.
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. Set the following settings 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)
  2. Promote your Global Settings if they have not yet been promoted. In Vendor Central, navigate to EDI > Self Service Setup > Choose the vendor ID you are working with and click View EDI set up > Click the Edit button on the Global settings section.
    1. EDI Contacts: Click Acknowledge and continue.
    2. Identifiers: These settings should already be set up so you can just click Save and continue.
    3. Product ID and test items: These should also be set up already, but you may need to add List prices and Quantities for each of the test items if you have not yet done so. Click Save and continue.
    4. Test environment: Review the settings in the Draft column and go back to any of the previous steps to make changes if necessary. Click Promote and then Confirm. Click Continue.
    5. Production environment: Click Promote.

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?