EDI Integration Services
We build ANSI X12 EDI directly inside your ERP rather than through a middleware provider. Purchase orders, acknowledgments, ship notices and invoices are mapped in your own system, on .NET and SQL Server, so there is no per-document fee and no black box between you and your trading partner.
+ RULES
The scope, and what has to get right.
-
850Purchase order. Arrives from the partner and has to become a real order in your ERP, with their SKUs mapped to yours. -
855Acknowledgment. Confirms what you can actually ship, at what price, by when. Wrong here and the partner plans against numbers you cannot meet. -
856Advance ship notice. The one that gets rejected most. Carrier, pack structure and appointment all have to match what was agreed and what physically shipped. -
810Invoice. Has to match the ASN line for line. A SKU substitution nobody recorded turns into a chargeback. -
846Inventory advice. Stock levels back to the partner, which means your ERP has to be the accurate source. -
997Functional acknowledgment. Confirms receipt. Its absence is usually the first sign something broke. -
824Application advice. The partner telling you what they rejected and why. -
753/754Routing request and instructions. Amazon's collect-shipment flow, before the ASN can go.
Inside the system, not bolted on.
Mapping lives in your codebase
Segment and element mapping is written as part of the ERP, in C#, against your own data model. When a partner changes a requirement, that is a code change you own, not a support ticket.
Direct connections
AS2, SFTP or API straight to the trading partner. No SPS Commerce or Rithum layer, so there is no per-document cost and nothing sitting between you and the transaction.
Every transaction logged
Raw inbound and outbound files are stored alongside the parsed result, so a rejection can be traced to the exact segment that caused it rather than reconstructed from memory.
Amazon treated as three integrations
Vendor Central Wholesale EDI, Vendor Central Direct Fulfillment EDI, and Seller Central over SP-API have different rules and different backends even on one account. We build them separately because they are separate.
Multi-marketplace ERP, EDI and logistics automation for a US consumer electronics brand
- Off Sage, with the operating history intact: Customers, vendors, items and transaction history were migrated from Sage into a browser-based ERP covering order-to-cash and procure-to-pay, with a full general ledger, receivables and payables, so the business changed systems without losing its records.
- Native EDI inside the ERP: Direct trading-partner connections for Amazon Vendor Central, Walmart, HSN, QVC and Costco with 850, 855, 856, 810, 846 and 997 documents, polled on schedules as short as ten minutes. Every job is tracked on a monitoring dashboard, and there is no third-party EDI middleware in the chain.
- Every channel in one order queue: Amazon Vendor Central and Seller Central (SP-API), Walmart, HSN, QVC, Costco, several Shopify storefronts, eBay and direct wholesale accounts land in one system. Vendor Central purchase orders are accepted or rejected back to Amazon from the same screen that shows system, 3PL and allocated stock.
- Multi-warehouse and multi-3PL stock: Real-time inventory across an owned warehouse operated with a logistics partner, a second third-party warehouse and Amazon fulfillment locations, with warehouse transfer orders and an Amazon inbound shipment request action for FBA.
- International purchasing and landed cost: Ocean and air freight purchase orders carry ETD, bill of lading, ETA and vessel details, and the ERP calculates landed cost at receiving from tariff classification, duty, tariff, harbor surcharge and freight per item.
Real failure modes, and how they get diagnosed.
- An 856 rejected for a carrier mismatch The purchase order specified UPS Ground, the warehouse shipped FedEx Ground, and the ASN carried the wrong carrier. The retailer's system rejected it on arrival. Root cause traced to the mismatch, corrected through the partner portal because the automated feed was still pushing the wrong value, then resent clean.
- A routing request rejected on the delivery appointment The appointment slot on the transaction did not match what had actually been scheduled with the carrier. Diagnosed the discrepancy, had the appointment corrected, and the resend was accepted.
- An 810 rejected on line-item mismatch The SKU billed on the invoice did not match what physically shipped. A recurring pattern where a substitution at the warehouse never made it back into the order record.
- No 997 came back at all Usually a connection or file-naming problem rather than a data problem. Having the raw outbound file stored is what makes this a five-minute check instead of a day.
Common questions.
Do we still need SPS Commerce or Rithum?
Not if the transaction sets are built into your ERP. Middleware is useful when you have no development capability and need to onboard a partner quickly. It costs per document, and it puts a layer between you and the transaction that you cannot inspect when something is rejected.
How long does onboarding one trading partner take?
It depends almost entirely on the partner, not on us. Their testing and certification cycle is usually the longest part. The mapping work itself is predictable once their specification is in hand.
What if we are already on a middleware provider?
Partners can be moved one at a time. There is no need for a single cutover, and running both in parallel during testing is normal.
Does this work with an ERP we did not build?
Often yes. We have built integration and web layers over commercial ERPs where replacing the system was not an option. What matters is whether the data is reachable, not who wrote it.
Is Amazon EDI the same as Amazon SP-API?
No. Vendor Central uses EDI, Seller Central uses SP-API, and Vendor Central itself splits into Wholesale and Direct Fulfillment with different rules. They are three separate integrations even on one account.
Who owns the mapping code?
You do. It sits in your ERP codebase.
Which partner is giving you trouble?
Tell us the partner and the transaction set, and we will tell you what is likely causing the rejections before you commit to anything.