Integrations get declared live at the first successful message. They are only working when the numbers match — five weekly numbers tell you the truth.
PONTURA INSIGHTS · 5 AUGUST 2026
Most 3PL integrations are declared "live" at the first successful message. That is like declaring a bridge open because one car made it across. An integration is live when the numbers on both sides agree — and keep agreeing under load, through peak, through exceptions, through the invoice run at month-end.
You don't need a dashboard project to know whether your 3PL integration works. You need five numbers, pulled weekly, compared honestly.
1. Orders sent versus orders confirmed. Count the orders that left your ERP and the confirmations that came back and matched, per day. The gap between the two is your silent failure rate — the orders someone repaired by phone, or worse, nobody did.
2. Confirmation lines that match without manual repair. Not order headers — lines. Quantity, unit, item. Every line that needed a human touch before it booked is integration debt paying negative interest.
3. Stock at the 3PL versus stock in the ERP, same timestamp. One number or two? If the answer is "it depends when you look", the answer is two. A daily snapshot comparison, item-level, tells you in a week what a workshop won't tell you in a month.
4. Inventory corrections per week, tagged by cause. Corrections are where integration failures go to hide. If nobody tags them by cause, they read as "warehouse noise" — pull a month of them and count how many trace back to messages that didn't reconcile.
5. 3PL invoice lines that reconcile to confirmed movements. The final exam, and the one most integrations fail. If your 3PL's invoice can't be matched line-by-line to movements both systems agree on, you are paying for activity you cannot verify.
When the test fails, the instinct is to fix messages one by one. The pattern underneath is almost always a contract problem: two systems with different ideas about who owns the truth, in which direction it flows, and what happens when they disagree. That is repairable — we do it message by message, count by count — and it starts, as always, with an honest picture of where the integration actually stands.
Pontura designs and repairs warehouse and 3PL/EDI integrations inside distribution-heavy ERP landscapes. How we work the execution layer →