Connecting Isn't the Work

Someone will tell you they can connect a new trading partner in two days.

They're probably telling the truth. And the date you promise off the back of it will still be wrong.

Connecting is solved. Reconciling is not.

Two systems agreeing to exchange files stopped being hard a long time ago. Connectivity is cheap now, whether you go direct, through a network, or over an API. That part genuinely has collapsed from weeks to days, and the people selling it are not lying to you.

What hasn't moved is working out what the partner actually wants inside those files. That's the work, and it doesn't appear anywhere in a connection-time estimate.

The same standard, different rules

Two partners can sit on the same X12 version and still need completely separate mapping, because each one publishes its own implementation guide on top of the standard.

Segments the standard calls optional become mandatory. Code lists shrink to the handful that partner actually uses. Conditional rules appear, so one field being present makes another one required. And they disagree about how to identify your item, whether that's a UPC, your vendor number, a GTIN, or two of them in a particular order.

None of that is in the two days. Two days is real when it's a spec you have mapped before. The long ones are where it isn't.

The queue nobody plans for

Then there's the part that never makes it into the plan at all.

Once your maps are built you go into the partner's certification testing, and that runs on their calendar rather than yours. Large retailers and 3PLs commonly have long testing queues or limited testing windows, which is a scheduling problem rather than a technical one. No tooling on your side moves it.

The numbers are public if you go looking. EDI data testing averages around two weeks and can stretch to six. Walmart Marketplace quotes an onboarding window of four to ten weeks. On the traditional path, certification testing alone accounts for two to four weeks of an eight to fourteen week project.

So the honest shape is setup in days, testing in weeks. Being ready isn't the same as being live, and only one of those is yours to control.

Which half are you waiting on

When someone asks how long a new partner takes, ask which half they mean.

The half you control is your side of the mapping, and that genuinely has got faster. The half you queue for is the partner's testing slot, and it moves at their pace regardless of what you bought.

Put both numbers in the plan separately and the date you promise stops being a guess. Put one number in and you will be explaining a slip to somebody in six weeks.

Shortening the mapping half is roughly what we do. The queue half you just have to plan around, and telling the two apart costs nothing.