Skip to main content

How do I check whether an EDI document reached the retailer, and why might it fail or be rejected?

Open the order’s EDI tab to check its documents. It lists the inbound 850 and each 855, 856, and 810 that Endless sent, with a status of Pending, Delivered, or Failed and the time it was delivered. Delivered means the Endless EDI service accepted the document for the retailer. Check the retailer’s portal for its acknowledgment or rejection.

Messages on the order:

  • “EDI 856 already sent unchanged; skipping duplicate” (or 855, 810): Endless rebuilt the document after an order event and it matched the one already sent, so it was not sent twice. A changed document is sent again.
  • “Could not build the EDI … document”: Endless could not fill in the retailer’s format from the order, usually because required data is missing. The error details name it. Fix the data and send again.
  • A Failed status with Delivery Errors: the EDI service refused the document. Select the error to read it.
  • “Failed to deliver transaction to EDI Partner” appears when a document you send by hand from the EDI tab, with the plus button, fails. Nothing was sent. Check the error and try again.

A retailer that did not receive a document usually means one of these:

  • the retailer connection is not set up to send that document for that event;
  • with 810 Invoice Scope set to One invoice per order, the invoice is sent only when the shipment that completes the order ships;
  • the document was skipped, could not be built, or failed;
  • the Partner EDI ISA ID, or Partner EDI ISA ID for 856 (ASN), does not match the retailer’s ID.

A retailer’s rejection of a ship notice appears in its portal or comes from your contact there. Common causes are a wrong partner ID, carton SSCCs that do not match the labels, or carrier codes the retailer does not accept. Contact Endless support for help comparing the document with the retailer’s specification.