EDI Made Simple with Synctify

An EDI 810 is sent from the supplier to the sales channel to request payment for goods that have been delivered or shipped. It includes key billing details such as item quantities, unit prices, shipping charges, tax, and total amount due.

🔍 Use Case: Automates the invoicing process and helps suppliers get paid faster with fewer errors.

This document is used by the sales channel to inform the supplier about a financial adjustment related to an invoice. This could be a refund for returned goods, a discount applied after invoicing, or a correction to a previous charge.

🔍 Use Case: Simplifies post-payment adjustments and ensures accurate accounting between both parties.

The EDI 816 provides information about the structure of the sales channel’s organization. It includes addresses and identifiers for stores, warehouses, distribution centers, and other shipping locations—along with how they relate to the parent company.

🔍 Use Case: Helps suppliers accurately route shipments and comply with retailer-specific fulfillment rules.

Sent from a sales channel to a supplier, this document details payment confirmations, including invoice numbers, paid amounts, and any deductions. It is often used to explain how a bulk payment was applied across multiple invoices.

🔍 Use Case: Provides transparency and supports accurate payment reconciliation for suppliers.

The EDI 824 notifies the supplier whether a previously sent document—such as an invoice or order acknowledgment—has been accepted, rejected, or returned with errors.

🔍 Use Case: Prevents delays by allowing suppliers to correct issues early in the EDI workflow.

With this document, suppliers can share real-time inventory data with their sales channels, including on-hand quantities and stock availability across locations.

🔍 Use Case: Enables more accurate listing availability, prevents overselling, and supports replenishment planning.

This is one of the most important EDI documents. An EDI 850 is sent from a sales channel to a supplier to place an order. It includes order details like SKUs, product descriptions, quantities, pricing, shipping instructions, and requested delivery dates.

🔍 Use Case: Automatically creates sales orders in the supplier’s system and reduces manual order entry.

Once the supplier receives a purchase order, they send an EDI 855 to confirm whether the order is accepted, rejected, or accepted with changes. It allows the supplier to communicate availability or request modifications.

🔍 Use Case: Helps ensure order alignment early in the fulfillment process and avoids miscommunication.

The ASN is sent by the supplier to the sales channel before the goods arrive. It includes shipment details such as carrier name, tracking number, estimated delivery date, item contents, and how items are packed.

🔍 Use Case: Prepares retailers for incoming shipments and supports faster and more accurate receiving.

This EDI document is sent by the sales channel when they need to make changes to a previously issued purchase order. Changes might include delivery dates, quantities, or product substitutions.

🔍 Use Case: Ensures flexibility in order management and allows suppliers to respond quickly to changing demand.

A general-purpose EDI message used to transmit custom or unstructured text between suppliers and sales channels. It can be used for exceptions, alerts, or other operational messages.

🔍 Use Case: Adds communication flexibility for scenarios not covered by other EDI documents.

Used by the sales channel to ask for a current update on one or more orders. The document may request confirmation on shipping status, estimated delivery, or fulfillment progress.

🔍 Use Case: Provides sales channels with real-time updates without the need for manual communication.

This document is sent by the supplier to provide updates on the status of open or pending orders. It informs the sales channel of what has been shipped, delayed, or canceled.

🔍 Use Case: Keeps retail partners informed and helps reduce service tickets or shipment-related inquiries.

This confirmation document is used to acknowledge receipt of one or more EDI transactions. It tells the sender whether the document was accepted, accepted with errors, or rejected.

🔍 Use Case: Ensures successful communication between systems and helps monitor EDI transaction flow.