Your Customer Requires EDI. Here’s What Happens Next.

A letter arrives: your largest customer wants orders, ship notices, and invoices sent by EDI, usually by a date that feels too close. You don’t need to become an EDI shop to meet it. Send us their requirements and we’ll come back with a scoped plan and a flat setup quote within 2 business days.

The 2-business-day offer
Send us the mandate letter or the customer’s EDI implementation guide, plus your ERP and deadline. Within 2 business days you get back the document list, the connection method, a realistic go-live plan, and a flat one-time setup fee, quoted before any work begins.
F
Foundational e-Business Services
Managed EDI since 2000

Most mandates boil down to the same handful of documents

Retailers, OEMs, distributors, and large manufacturers word their EDI requirements differently, but the core request is usually the same: receive purchase orders electronically, confirm them, tell the customer exactly what is shipping before it arrives, and invoice without paper.

Alongside the documents, the customer’s guide will specify how files travel (AS2, SFTP, or a VAN), which identifiers and labels to use, and a testing window you have to pass before going live. Missing any of those is what turns a mandate into chargebacks.

Documents Most Mandates Require

850 Purchase Order
855 PO Acknowledgment
856 Advance Ship Notice
810 Invoice
997 Functional Acknowledgment
860 PO Change
830 Planning Schedule (OEM)
862 Shipping Schedule (OEM)
Retail programs often add GS1-128 carton labels and routing documents; OEM programs often add release schedules. We read the customer’s guide and tell you exactly which apply.

Three ways companies meet a mandate

🖥

A web portal

Type orders and invoices into a browser screen the provider hosts. Cheapest to start and fine for a handful of orders a month.

  • No ERP integration, so data gets keyed twice
  • Labels and ASNs are manual and error-prone
  • Breaks down as order volume grows
⚙

Software you run

License EDI translation software and have your own team build maps, test with the customer, and monitor every day.

  • Full control if you have EDI skills in-house
  • Your team owns every spec change and failed file
  • Knowledge often sits with one person
🤝

A managed service

A team like ours builds the integration to your ERP, handles testing and certification with your customer, and runs it from then on.

  • Documents flow in and out of your ERP
  • We monitor, fix, and apply spec changes
  • Flat monthly rate, no per-transaction fees

From the letter to your first live order

Most customers are live within two weeks of kickoff. The pace usually depends on how quickly the customer schedules testing, not on the mapping.

1

Spec review

You send the mandate and the customer’s implementation guide. Within 2 business days you have a scoped plan and a flat setup quote.

→
2

Mapping and connection

We build the maps between your ERP and the customer’s format and set up the AS2, SFTP, or VAN connection they require.

→
3

Testing and certification

We run the customer’s test cycle and fix what they flag. Here’s how certification works.

→
4

Live and monitored

Production orders start flowing. We watch every transaction and handle the customer’s future spec changes.

Two fees and one pass-through, all quoted upfront

Connecting a new customer is a one-time flat setup fee that covers all mapping and testing, quoted for your approval before any work begins. After go-live, a fixed monthly rate covers operating the connection: data processing, EDI staff and helpdesk, and map fixes and changes.

The only usage-based charge is network (VAN) traffic, billed by data volume rather than per document, and quoted upfront too. There are no per-transaction fees. For typical ranges, try the quick estimate on our pricing page or read what managed EDI actually costs.

Four things get you an exact plan

  • The mandate letter or the customer’s EDI implementation guide
  • Which ERP or order system you run, and its version if you know it
  • Your go-live deadline
  • Any other customers who have asked about EDI

Don’t have the guide yet? Send what you have. Most customers will share their EDI specs with a supplier on request, and we can tell you what to ask for.

Send the spec. Get a plan in 2 business days.

No software to buy, no EDI staff to hire. Tell us who is asking and what they want, and we’ll scope it and quote it before you commit to anything.

Or call: 888-728-4030

Questions suppliers ask when the letter arrives

How long do I have to get EDI working?
The customer’s letter sets the date. Most of our customers are live within two weeks of kickoff, and the biggest variable is how quickly your customer schedules testing. If your deadline is close, tell us when you send the spec and we’ll say plainly whether it’s achievable.
Do I need to buy EDI software?
No. With a managed service there’s nothing to install or license. We receive and send the files, translate them, and connect them to your ERP.
Will it work with our ERP?
Almost certainly. We integrate with SAP, NetSuite, Microsoft Dynamics, Infor, JD Edwards, IBM i systems, and custom or legacy ERPs through APIs, database access, or file exchange. See EDI integration by ERP platform.
What happens if we get it wrong?
Many customers deduct chargebacks for late, missing, or inaccurate documents, especially ship notices. Getting the setup and monitoring right sharply reduces that risk. DF Stauffer cut chargebacks by 85% after handing EDI operations to us.
We’re using the customer’s web portal now. Can we switch?
Yes. Portals are a common first step. Moving to an integrated setup removes the double keying, and the customer’s testing process is usually lighter the second time around.
What if more customers ask for EDI later?
Each new trading partner is its own flat setup fee, quoted upfront, and then runs under the same monthly service. Herr’s Foods grew from 24 to 130 trading partners this way.