PromoStandards, PDX, and the work that still falls to a human

The promotional products industry has done something genuinely hard: it built data standards for one of the most fragmented supply chains in B2B. More than 500 suppliers now expose at least one PromoStandards endpoint: product data, inventory, pricing, order status, shipping notifications. PPAI runs a parallel effort, PDX, whose SAGE Connect implementation reached 130 suppliers and 212,000+ products after growing 73% in six months.

This is real progress, and worth applauding. It's also worth being precise about what it hasn't solved, because that's the part still sitting on your team's desks.

The three gaps

Gap one: consistency. The standards' own ecosystem says it plainest. As one integration provider puts it, every supplier implements PromoStandards a little differently: inconsistent part IDs, partial implementations, undocumented rate limits. eXtendTech's State of PromoStandards in 2026 frames the industry's current question exactly: "The question isn't whether PromoStandards works. It does. The real question is whether it's implemented consistently."

Gap two: reach. Two overlapping standards, neither universal, and an in-house distributor-side integration still takes three to six months of developer time for the SOAP/XML plumbing alone, before the supplier quirks. Most of the 20,000+ mostly small distributors in North America don't have a developer, let alone six months of one.

Gap three: the customer side. The standards connect distributors to suppliers. Your customers, the ones emailing POs in whatever format their purchasing system exports, aren't on any standard and never will be. PPAI built PDX explicitly to "eliminate unnecessary phone calls and emails" for status and inventory, which is also the frankest official admission of how the industry actually communicates today.

Standards automate the middle of the workflow. The edges still belong to a person: the customer's PO coming in, the supplier's exception coming back, the portal that half-implements the spec.

What the last mile looks like

Walk any distributorship and the leftover work is the same list: the PO from the customer keyed into the ERP by hand. The order status pulled from the one supplier whose endpoint is down, or wrong, or was never built. The proof chased by email. The invoice that doesn't match the PO reconciled line by line. None of it is beneath a standard. It's beyond one, because it involves reading, judgment, and systems that will never share an API.

Complements, not competitors

This is why we built AltOps to work at the screen level rather than the API level. An agent taught from a screen recording doesn't care whether a supplier implemented Order Status 2.0.0 correctly. It checks the portal the way your team does, and uses the endpoint's data when your systems surface it. Where the standards reach, wonderful: cleaner data, fewer screens. Where they don't, the agent covers the gap instead of your CSR.

The right mental model is a spectrum. EDI and PromoStandards automate the structured core; agents automate the ragged edge; people keep the judgment calls. The industry spent a decade wiring the middle. The edge is where the hours still are, and at 34–40% gross margins it's where the profit is hiding too.