Skip to content
AppsXone IT Solutions Discuss Your Project
AppsXone IT Solutions
Discuss Your Project
EDI 850 · 855 · 856 · 810 · 997

EDI Integration Services

We build ANSI X12 EDI inside your ERP. Purchase orders, acknowledgments, ship notices and invoices are read and generated inside your ERP using the EdiFabric .NET library, on SQL Server, with no external translation service. Amazon Vendor Central and Adorama connect directly over SFTP; others require their network, which validates and delivers your files.

WHAT THIS INVOLVES

The scope, and what has to get right.

  • 850 Purchase order. Arrives from the partner and has to become a real order in your ERP, with their SKUs mapped to yours.
  • 855 Acknowledgment. Confirms what you can actually ship, at what price, by when. Wrong here and the partner plans against numbers you cannot meet.
  • 856 Advance ship notice. It carries a lot of detail to get right. Carrier, pack structure and appointment all have to match what was agreed and what physically shipped.
  • 810 Invoice. Has to match the ASN line for line. A SKU substitution nobody recorded turns into a chargeback.
  • 846 Inventory advice. Stock levels back to the partner, which means your ERP has to be the accurate source.
  • 997 Functional acknowledgment. Confirms receipt. If it does not come back, that is the first thing to check.
  • 824 Application advice. The partner telling you what they rejected and why.
  • 753/754 Routing request and instructions. The Wholesale collect-shipment flow, before the ASN can go.
IN PRODUCTION

Trading partners in production

These are the trading partners running today on the ERP we built for a US consumer electronics brand, grouped by how each one connects. Every X12 file is read and generated inside the ERP using the EdiFabric .NET library. Where a network is involved, the ERP uploads its own files to the network's FTP, and the network validates and delivers them.

  • DIRECT Direct EDI over SFTP. Amazon Vendor Central (Wholesale and Direct Fulfillment) and Adorama.
  • SPS EDI through SPS Commerce. Best Buy Optics, Costco Wholesale and Colony Brands.
  • RITHUM EDI through CommerceHub / Rithum. Best Buy Purchasing, Bluestem Brands, QVC, Staples Advantage and Staples the Office Superstore.
  • RADIAL EDI through Radial. BI Worldwide and Mason Companies.
  • FTP File exchange over FTP. HSN, Harco Industries, Knocking and Verdi Commerce. Spreadsheet order files come in and ASN files go back, automated, without EDI.
  • API Marketplace APIs. Walmart Marketplace API, Amazon SP-API for Seller Central and FBA inbound, Shopify and eBay.
HOW WE BUILD IT

Inside the system, not bolted on.

01

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.

02

Direct, or through the retailer's network

SFTP, or an API, straight to the partner where the partner allows it. Where a retailer requires SPS Commerce, CommerceHub or Radial, your ERP uploads its own files to that network's FTP and reads the files it delivers. The network validates and delivers them, and every file is still read and generated inside your ERP.

03

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.

04

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. Wholesale and Direct Fulfillment can share one Vendor Central account, and Seller Central is a separate account. We build them separately because they are separate.

ANCHOR CASE STUDY

Multi-marketplace ERP, EDI and logistics automation for a US consumer electronics brand

A US CONSUMER ELECTRONICS AND CAMERA BRAND · CONSUMER ELECTRONICS AND IMAGING, MULTI-CHANNEL RETAIL AND DISTRIBUTION
  • 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: Every X12 document, including 850, 855, 856, 810, 846 and 997, is read and generated inside the ERP using the EdiFabric .NET library, with the mapping in its own code and no external translation service. Amazon Vendor Central (Wholesale and Direct Fulfillment) and Adorama connect directly over SFTP. Best Buy Optics, Costco Wholesale and Colony Brands run through SPS Commerce. Best Buy Purchasing, Bluestem Brands, QVC, Staples Advantage and Staples the Office Superstore run through CommerceHub (Rithum). BI Worldwide and Mason Companies run through Radial. The ERP uploads its own files to each network's FTP and reads the files the network delivers, and the network validates them and delivers them to the retailer. HSN, Harco Industries, Knocking and Verdi Commerce run on automated file exchange over FTP. Scheduled EDI jobs poll FTP on schedules as short as every ten minutes. Walmart runs through its API. The Walmart API integration imports WFS and seller-fulfilled orders, sends shipment confirmation and tracking back for seller-fulfilled orders, marks WFS orders shipped and invoices them automatically, turns returns into credit memos, and creates WFS inbound shipments. Every job is tracked on a monitoring dashboard.
  • 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.
  • FBA inbound shipment automation: End-to-end FBA inbound automation via SP-API: shipment creation, selection of the lowest-cost shipping plan, packing slip generation, label download and routing to the warehouse.
Read the full case study
COMMON PROBLEMS WE SOLVE

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 Start by checking the connection and the file naming before looking at the data. Having the raw outbound file stored is what makes this a quick check.
QUESTIONS

Common questions.

Do we still need SPS Commerce or Rithum?

Sometimes, because some retailers require their network. When they do, your ERP uploads its own files to the network's FTP and reads the files it delivers. Every file is read and generated inside your ERP using the EdiFabric .NET library, and the network validates and delivers it, so you are not depending on an external translation service. Amazon Vendor Central and Adorama connect directly over SFTP, with no network at all.

How long does onboarding one trading partner take?

It depends almost entirely on the partner, not on us. Their testing and certification cycle is a separate step to plan for. The mapping work itself is predictable once their specification is in hand.

What if we are already on a middleware provider?

The mapping can move into your ERP one partner at a time. Where a retailer requires its network, the network stays to validate and deliver the files, and only the translation moves into your ERP, using the EdiFabric .NET library. 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.

Who owns the mapping code?

You do. It sits in your ERP codebase.

RELATED

Where this connects.

Amazon EDI Integration Walmart EDI Integration EDI Transaction Sets Explained Amazon SP-API Integration Shipping API Integration Custom ERP Development
LET'S TALK

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.

Start a project