Supply chain EDI: the integration we build for your partners
Supply chain EDI breaks down at partner onboarding, missing acknowledgments and peak-hour batches more often than at the message format. Agnotic Technologies builds the EDI integration layer to your partners' requirements.
Last reviewed by the Agnotic Technologies engineering team
What does a supply chain EDI integration need to handle?
A supply chain EDI integration must exchange X12 850 purchase orders, 855 acknowledgments, 856 ship notices, 810 invoices and 214 carrier status messages with every trading partner, answer each functional group with a 997 or 999, and absorb the busiest hour. Agnotic Technologies builds partner maps, acknowledgment tracking and monitoring for that layer.
Where does supply chain EDI go wrong?
The X12 standard is stable. The trouble comes from partners, timing and visibility.
Every partner reads the guide differently
Each partner's implementation guide can differ for the same transaction set, so each partner and set combination may need its own map or rules.
Missing acknowledgments go unnoticed
A missing 997 or 999 can be the first sign that a partner did not receive a ship notice or invoice, but few teams track each one against the document it answers.
Batching hides rejections
Grouping several transaction sets into one functional group cuts acknowledgment traffic, and it also means one rejected group can hold back several documents.
Peak-hour batches overload the translator
Ship notices sent in one batch after the last trucks leave can set the peak on their own, and a layer sized for the daily average falls behind.
Partner guide changes ripple out
When a partner updates its guide, every map for that partner is retested. More partners means more change requests each year.
A stopped feed is hard to spot
Without a picture of each partner's normal traffic, a feed that stops can go unnoticed until orders or invoices are missed.
Which EDI features do we build?
Agnotic Technologies builds the EDI integration layer to your requirements: your trading partners, the transaction sets they use and the ERP, WMS and TMS you run.
X12 maps per trading partner
Maps and validation rules for each partner and transaction set, built from that partner's implementation guide and kept under version control.
997 and 999 acknowledgment tracking
Each outbound document matched to the acknowledgment that answers it, with alerts when one is late or reports a rejection.
Partner onboarding and test cycles
A test environment, sample document exchange and sign-off checklist per partner and transaction set, so new partners go live in a repeatable way.
Exception queues
Rejected, unmapped or duplicate documents placed in a queue with the reason, so the team can fix and resend them without searching logs.
Peak-hour throughput design
A translator and queue designed for the busiest hour, with near real-time paths for documents such as 856s that must arrive before the truck.
Monitoring and alerting
Dashboards of traffic per partner and transaction set, with alerts when a partner's feed drops below its normal pattern.
ERP, WMS and TMS connectors
Connections that turn EDI documents into orders, shipments and invoices in your business systems, and back again.
VAN, AS2 or API connections
Each partner connected over the channel it supports, with every channel feeding the same maps, tracking and monitoring.
Which X12 transaction set does each order event create?
Each business event in the order cycle produces its own transaction set.
| Set | Name | Business event that triggers it | How many to expect |
|---|---|---|---|
| 850 | Purchase Order | The buyer places an order | One per purchase order |
| 855 | Purchase Order Acknowledgment | The seller accepts, changes or rejects the order | One per order the seller answers with an 855 |
| 856 | Ship Notice/Manifest | A shipment leaves, describing its contents and packing | One per shipment |
| 810 | Invoice | The seller bills for the goods | One per invoice |
| 214 | Transportation Carrier Shipment Status Message | A carrier reports pickup, transit, delay or delivery | One per carrier status update |
| 997 or 999 | Functional or Implementation Acknowledgment | The receiver confirms a functional group was accepted or rejected | One per functional group |
How do acknowledgments add to the traffic?
Every functional group you receive should be answered with a 997 or 999, and every group you send should come back with one. If each document travels in its own group, acknowledgments match documents one for one.
Batching several transaction sets into one functional group cuts the acknowledgment count. It also means one rejected group can hold back several documents, so check how your partners batch before you change it.
Acknowledgments also drive monitoring. A missing 997 or 999 can be the first sign that a partner did not receive a shipment notice or invoice, so your integration layer should track each one against the document it answers.
Why does partner count matter as much as message count?
Message volume sizes the translator and queues. Partner count sizes the work your team does before the first message flows.
Maps
Each partner's implementation guide can differ for the same transaction set, so each partner and set combination may need its own map or rules.
Onboarding tests
Each combination is tested with the partner before go-live, usually with sample documents in a test environment and a sign-off.
Change requests
When a partner updates its guide, every map for that partner is retested. More partners means more change requests each year.
Monitoring
Knowing each partner's normal daily traffic shows how quickly a stopped feed becomes visible.
Planning for the busiest hour
Size the translator and the queue between it and your ERP, WMS or TMS for the busiest hour, not the daily average.
Check partner cut-off times. If ship notices go out in a batch after the last trucks leave, that batch can set the peak on its own.
Decide which documents must be processed in near real time, such as 856s before trucks arrive, and which can wait in a queue.
Load test the integration layer at the busiest hour with your largest orders, because lines per order set message size.
How does Agnotic build an EDI integration layer?
We start with your trading partners, the transaction sets each one uses and their implementation guides, then onboard the first partners and add the rest in waves. Acknowledgment tracking and monitoring are part of the first release.
Our custom logistics software development team builds the layer between EDI and your ERP, WMS and TMS. Where shipment events are shown to users, our supply chain visibility software page covers that.
What does X12 say each transaction set is for?
Definitions from the X12 transaction set list, the standards body that publishes these sets, checked on 21 Oct 2026.
X12 defines the 850 Purchase Order for the placement of purchase orders for goods and services, and says it should not be used to convey purchase order changes or purchase order acknowledgment information.
Source: X12, Transaction Sets: 850 Purchase OrderX12 defines the 855 Purchase Order Acknowledgment for a seller's acknowledgment of a buyer's purchase order, and notes it can also be used as notification of a vendor generated order.
Source: X12, Transaction Sets: 855 Purchase Order AcknowledgmentX12 defines the 856 Ship Notice/Manifest to list the contents of a shipment of goods, with order information, product description, packaging, carrier information and the configuration of goods in the transportation equipment.
Source: X12, Transaction Sets: 856 Ship Notice/ManifestX12 defines the 214 Transportation Carrier Shipment Status Message for a transportation carrier to give shippers, consignees and their agents the status of shipments in terms of dates, times, locations, route, identifying numbers and conveyance.
Source: X12, Transaction Sets: 214 Transportation Carrier Shipment Status MessageX12 defines the 997 Functional Acknowledgment to report the results of syntactical analysis of transaction sets grouped in functional groups, and the 999 Implementation Acknowledgment to report syntactical and relational analysis against a full or implemented subset of X12.
Source: X12, Transaction Sets: 997 and 999 acknowledgments
Trusted by global innovators
Where should you go next?
- Supply chain visibility softwareShipment events and exceptions in one view.
- Supply chain planning softwareDemand, supply and inventory planning.
- Custom logistics software developmentIntegration layers between EDI, ERP, WMS and TMS.
- DSCSA interoperabilitySerial numbers and EPCIS events for pharma supply chains.