The quick read
  • PromoStandards is a free, open, industry-governed set of web-service specifications that standardizes how supplier systems answer questions about products, inventory, pricing, order status, and shipping.
  • It is plumbing, not a platform. You don't log into PromoStandards — your tools use it behind the scenes so that "where is my order" stops being an email.
  • It is not the same thing as the major distributor product-search platforms. Those are search-and-research platforms; PromoStandards is the live data connection underneath modern distributor workflows.
  • A supplier's PromoStandards support is a reliable proxy for how seriously they take distributor operations generally.
  • Ask suppliers which services they support and which versions — "we support PromoStandards" can mean anything from product data only to full order lifecycle.

The problem it solves

Picture the ordinary life of a promo order without any system integration. A distributor sells a client five hundred branded notebooks. The order goes to the supplier by email or a portal form. The confirmation comes back by email. The proof goes out by email, comes back by email. When the client asks "where are we on the notebooks," the distributor's account manager emails the supplier's customer service team, who checks an internal system and replies — hours or a day later. Multiply by every order, every change, every shipment, every distributor, every supplier, and the industry's answer to "what's the status" has historically been: a human reads a screen and types what it says to another human.

Every maturing industry eventually builds a shared language so its systems can skip the humans for routine questions. Finance built one. Travel built one. Retail built EDI. The promotional products industry's answer is PromoStandards.

What PromoStandards actually is

PromoStandards is a set of open web-service specifications — concretely, defined request-and-response formats a supplier's system agrees to answer — maintained by a nonprofit industry organization whose members are the suppliers, distributors, and service providers who use it. The standards are free to download and free to implement. There is no per-transaction toll, no gatekeeper platform in the middle. A supplier implements the services on their side; a distributor's software — their order management system, their shop platform, their ERP — calls those services directly.

That architecture is the point. PromoStandards is deliberately boring infrastructure: it does not try to be a marketplace, does not own the relationship, does not insert itself into the money. It defines the questions and the shape of the answers, and gets out of the way.

It's a vocabulary, not a product

The practical consequence: you will never "log in to PromoStandards." If you are a distributor, you experience it indirectly — as the reason your order system shows live inventory for one supplier and a three-day-old spreadsheet for another; as the reason one supplier's order status appears automatically in your dashboard while another's requires an email.

The services, in plain language

The standard is organized as a family of services, each answering one category of question. The names are dry; the questions are the ones every distributor asks daily.

Product data — "what do you sell?"

Product information as structured data: names, descriptions, categories, colors, sizes, imprint methods and areas. This is what lets a supplier's catalog appear inside distributor-facing tools accurately and automatically, instead of being re-keyed from a PDF catalog and drifting out of date.

Media content — "what does it look like?"

Product images and related assets, addressable by product and variant, so the right photo lands next to the right SKU in whatever system is displaying it.

Inventory — "do you have it, right now?"

Live availability by SKU and variant. This single service eliminates the most expensive email in promo — the one where the client has approved the order and then everyone discovers the navy version is backordered six weeks. Systems that check inventory at quote time prevent the problem from existing.

Pricing and configuration — "what does it cost, configured this way?"

Quantity-break pricing including decoration charges, setup fees, and the rest, as data. This is what turns quoting from a lookup-and-arithmetic exercise into something a system does instantly and consistently.

Purchase order — "here is the order, formally"

Submitting the order itself as structured data rather than a portal form or an email: products, quantities, decoration details, artwork references, ship-to addresses. Fewer re-keyings means fewer of the transcription errors that become expensive reprints.

Order status and shipment — "where is it?"

The status of an in-flight order, and shipment details with tracking once it ships, as queryable data. The account manager stops being a human proxy for a supplier's order screen; the distributor's own system answers the client's question.

Invoice — "what do I owe?"

Invoices as data, flowing into the distributor's accounting instead of arriving as PDF attachments to be re-keyed.

Why distributors should care

If you are a one-person distributorship doing a handful of orders a month, you can run on email and goodwill. The case for caring grows with volume, and it compounds:

The hours come back

Status-checking, re-keying, and inventory surprises are the three great time sinks of promo operations, and they are precisely the three things the standard automates. The question to ask about any supplier is not "is their portal nice" but "does my system have to involve a human to know what theirs knows."

Errors drop at the re-keying points

Every manual transcription — catalog to quote, quote to order form, order confirmation to client email — is a place a digit can flip or a color code can drift. Structured data passes through unchanged. In an industry where the product is customized and errors become physical objects with logos on them, removing transcription points is quality control.

Your tools get better for free

Because the standard is open, the ecosystem of distributor software — order management, online stores, ERP connectors — builds against it once and works with every compliant supplier. When you choose suppliers who speak the standard, you inherit that entire tool ecosystem. When you choose suppliers who don't, every integration is a custom project or a manual process.

PromoStandards vs distributor search platforms

These get conflated constantly, so here is the clean separation.

The major distributor product-search platforms are research and workflow platforms. They are where distributors search products across thousands of suppliers, build presentations, and manage parts of their workflow. They are commercial products with subscriptions, run by companies, and a supplier "being on" one of them means having a listing presence there.

PromoStandards is the data standard underneath. It is not a destination and sells nothing. Notably, the platforms themselves consume it — live inventory or order status shown inside a platform is frequently arriving over PromoStandards services from the supplier's systems.

The practical takeaway for choosing suppliers: platform presence and standards support answer different questions. A listing tells you a supplier wants to be found. Standards support tells you their operations can talk to yours. A supplier with both is set up for distributors end to end — which is exactly why operational details such as blind shipping and data standards belong on the same checklist when you evaluate a new supply partner.

What to ask a supplier

"Do you support PromoStandards?" is too easy to say yes to, because supporting one read-only service technically counts. The questions that produce useful answers:

"Which services, and which versions?"

Product data only is a catalog feed. Inventory and pricing is quoting without surprises. Purchase order, order status, and shipment notification is the full operational loop. A supplier who can name their supported services and versions without checking has an engineering team that owns this; a supplier who has to ask around has a checkbox.

"Is the data live?"

An inventory endpoint that serves yesterday's batch export passes the compliance test and fails the actual purpose. Ask how fresh inventory and status data is — the honest answers are specific.

"How do I get credentials, and is there a cost?"

The standard is free; a supplier's implementation choices vary. Suppliers who treat integration access as a premium gate are telling you where distributor automation sits on their priority list.

"What happens when it breaks?"

Integrations are software; software has incidents. A supplier with a real integration program has a support path for it. A supplier whose endpoint can be down for a week without anyone noticing does not actually run their business on it — and neither should you.

Where Inkgility stands

We will keep this short, because the article is about the standard, not about us. Inkgility's distributor platform is API-first: pricing, order submission, and status webhooks are part of the trade program at the Pro and Enterprise tiers, with PromoStandards-compliant endpoints so our catalog and order data work inside the platforms and tools distributors already use. Documented publicly, not sales-call-gated — because we would rather be evaluated by the four questions above than exempted from them.