Choose on three things: which of your retailers the provider already supports, who owns the mapping work when a routing guide changes, and what happens to a chargeback caused by their error. Price is the fourth question, not the first.
Major retailers require every document to move electronically, purchase orders coming in, invoices and shipping notices going out, through EDI, or Electronic Data Interchange. It is not optional. Being able to trade EDI is a condition of holding the account.
EDI is a standardised format that lets two companies exchange business documents computer to computer, without anyone rekeying an order. The standards are decades old and deliberately rigid, which is what makes them reliable and also what makes them unforgiving.
Each retailer publishes a routing guide setting out exactly which documents it expects, in what format, on what timing, with what labelling. Miss any part of it and the retailer deducts money from your invoice.
A provider translates between your systems and each retailer's required format, then transmits on the retailer's schedule.
What varies between providers is not whether they can send an advance ship notice. They all can. It is how much of the mapping, testing and ongoing compliance work they absorb versus hand back to you, and how quickly they move when a retailer changes its requirements.
The 856 is where most chargebacks originate. It has to be transmitted before the goods arrive and it has to match the cartons exactly. Getting that one right removes a large share of deductions before they happen.
Treat the subscription as the smallest number.
The larger costs are setup and testing per trading partner, document or volume charges that scale as orders grow, mapping changes every time a retailer revises requirements, and the internal hours your team spends clearing exceptions.
Third-party middleware typically runs on a monthly base fee plus a charge per document, and full contracts commonly land somewhere between fifteen and forty thousand dollars a year before custom mapping work. Onboarding a single retailer usually takes six to twelve weeks depending on the retailer's own testing queue.
It depends on how many retailers you expect to add and how much of the compliance work you want to own.
Several apparel-specific systems include EDI in the platform, among them AIMS360, Aptean Apparel, BlueCherry and Uphance. That means one system for inventory, orders and EDI, fewer integrations to manage, usually lower monthly cost, and data flowing into the ERP without a second mapping layer. Retailer library sizes vary considerably between them, and some maintain several hundred connections, so ask for the specific number and whether your retailers are on it.
The trade-offs are real. When a retailer changes its specification you are depending on the ERP vendor to keep pace rather than a firm whose only business is compliance, and if you later change ERP you lose the EDI solution with it. Against that, you remove a subscription, a contract and an integration point that can fail.
SPS Commerce, TrueCommerce, Cleo, Orderful, DiCentral, Crstl and Rithum are among the providers apparel brands commonly use. Retailer compliance is their entire business: prebuilt connections to thousands of retailers, mapping changes handled when requirements shift, and specialist support when a chargeback traces back to a document failure.
The costs are a higher ongoing spend, another vendor relationship, and an integration between the provider and your ERP.
If your ERP has a well-maintained EDI module that already covers the retailers you sell to, built in is usually simpler and cheaper, and that holds whether you are onboarding your second account or your fiftieth. A dedicated provider earns its cost when you are adding retailers your ERP vendor does not already support, or when you want compliance handled by a firm that does nothing else.
The question that matters more than either: who is responsible when a document fails or a retailer changes its specification? Get that answer in writing before you sign, whichever model you choose.
Department store programmes are where EDI gets strict. The document set is broadly consistent; the compliance detail is not.
Selling to Nordstrom, Saks, Macy's, Bloomingdale's or Dillard's generally means handling the 850 purchase order inbound, the 855 acknowledgement, the 856 advance ship notice with GS1-128 carton labels, and the 810 invoice outbound, plus inventory and shipping updates.
What varies between them, and what catches brands out, is the detail underneath: label placement and format, ASN timing windows, carton and pack structure, routing instructions, and the specific deduction schedule applied when any of it is wrong.
Each retailer publishes a vendor routing guide setting this out. Read it before you scope the project, not after. The guide, not the vendor demo, is the actual specification you are being held to.
Do not switch during peak, and do not switch on price alone. Migration means remapping every trading partner, and that cost usually exceeds the saving in the first year.
We scope what each partner genuinely requires before you commit to a date, choose a provider against that scope, and hold them to the go-live.
Book a callNearly every vendor in this market says they do EDI. The claim is almost never false and almost never sufficient. These are the questions that separate a mature capability from a functional one.
Retailer EDI is a discipline that rewards accumulated time. A vendor that has been maintaining retailer connections for decades has already encountered the routing guide revisions, the odd label requirements and the edge cases a newer entrant will meet for the first time on your account. Ask directly how long, and ask what they were doing before.
Ask for the number, then ask whether your specific retailers are on it and whether those connections are live with other customers today. A large existing library means your onboarding is configuration rather than development. A small one means you are funding the build.
This varies enormously and it is the question most likely to surprise you after signing. Ask how many hours a typical new retailer takes, who does that work, whether it is billable, and what happens when the retailer revises its specification six months later. Ask for a written estimate on one retailer you have not yet onboarded.
Ask whether EDI implementation is handled by a dedicated team or by generalists who also configure the rest of the system. Ask how many apparel brands that team has taken live in the last year, and whether they are employees or subcontractors. Then ask to speak to one of those brands.
A vendor confident in its answers will give you all four without hesitation. Hesitation on any of them is itself information.