Applying retailer requirements isn’t a one-size-fits-all project. Nor is it static. Retailers can dictate what information they need and how they need to receive it — and everything is subject to change at the retailer’s discretion. That being said, a supplier serving 20 retailers shouldn't need 20 fundamentally different ways to receive an order, release it to the warehouse, generate shipping documentation, invoice the customer, and resolve exceptions.
In other words, what changes from retailer to retailer usually sits at the edges, not the core. Retailers set the external rules, but the internal operating model is up to the supplier, and it can hold steady no matter how many retailers sit on the other side of it. Once a supplier knows which pieces are retailer-specific (external) and which pieces belong to its own operation (internal), keeping up with a growing retailer list is far less daunting.
In this article, you will learn:
Where retailer requirements tend to vary
How to categorize what suppliers can standardize and what needs to be configured by retailer
Tips for keeping requirements from piling up as you scale
What Varies Between Retailers
Knowing where to expect variations is the first step in managing them. Luckily, retailer requirements differ in a few predictable places.
Fulfillment Model
A retailer that ships from its own distribution centers (DCs) has different documentation needs than one running dropship, vendor-managed inventory, or a marketplace model. Dropship retailers usually want faster acknowledgments and more frequent inventory updates since they're depending on the supplier for real-time availability. DC-fed retailers care more about case pack accuracy and inbound appointment windows.
Transaction Sets and Data Elements
Every retailer draws from the same general pool of electronic data interchange (EDI) documents, including purchase orders (EDI 850s), purchase order acknowledgments (EDI 855s), advance ship notices (EDI 856s), invoices (EDI 810s), and so on. But each retailer picks and chooses which EDI document transaction sets are required, as well as specifics around which fields, qualifiers, and code values are mandatory.
Physical Compliance
Retailers build their own compliance guides according to how their own docks and putaway processes function. These guides outline details like label formatting, label placement, carton making, and pallet configuration.
Chargeback, Deduction, and Scorecard Criteria
Fill-rate thresholds, on-time delivery windows, and the dollar penalties attached to missing them are set independently by each retailer. A shipment that's fine for one retailer can trigger a chargeback with another.
Related Reading: Vendor Compliance Checklist
What Doesn't Have to Change
Beneath all of this variation is a general workflow that’s the same for every retailer: Receive a purchase order, acknowledge it, ship the product, send the invoice, and get paid. That overarching sequence, and the systems behind it, don't need a retailer-specific version.
Furthermore, a supplier's item master, pricing data, and accounting close don't change based on who placed the order. Neither does its EDI connectivity itself. The way documents get sent, received, and translated is a capability the supplier owns.
Related Reading: Repeatable Supplier Onboarding Process: A Two-Layer Framework
How to Split What You Standardize From What You Configure
Every supplier must consider where to draw the line between "We do this the same way every time," and "We adjust this per retailer." Getting that split wrong in either direction creates problems. If you standardize too much, you risk compliance failures piling up. But if you configure too much, you risk creating unwieldy workflows that hinder growth.
Follow this general rule of thumb: Standardize what you control, configure what the retailer controls, and manage the exceptions between them. The following table helps illustrate this concept:
Operational Area | Standardize | Configure by Retailer |
Order processing | – ERP workflow – Ownership – Exception path | – PO mapping – Required fields |
Shipping | – Pick and pack process – Internal quality assurance | – Routing, labelling, carton, and pallet specifications |
Advance ship notice | – Trigger – Internal source data | – Required fields – Hierarchy – Timing |
Invoicing | – ERP billing workflow | – Required fields – Allowances – References |
Exceptions | – Ownership – Escalation process | – Retailer-specific error rules – Deduction rules |
Here’s another way of thinking about where to draw the line:
If a rule exists to protect a particular retailer’s receiving dock or compliance program, it belongs in the configure category.
If a rule exists because it’s how the business is run regardless of who’s on the other end of the order, it should be standardized.
Keep Requirements From Piling Up as You Scale
Once you draw the line between what should be standardized and what should be configured, keeping that split intact as the retailer count grows and as retailers change their own rules is an ongoing effort.
Keep Each Retailer-Specific Reference in One Place
Compliance guides, label specs, and scorecard thresholds should live and be updated as needed in one place, not scattered across whichever team last touched them. When the reference is fragmented, the same rule change gets discovered and subsequently fixed more than once.
Assign Ownership for Compliance Guide Changes
Retailers update their requirements on their own schedule. Someone needs to own watching for those updates. Without a named owner, a guide update can turn into chargeback.
Related Reading: Understanding Retailer Deductions, Chargebacks, and Fines
Let SPS Commerce Absorb the Repetitive Parts
Retailer requirements will keep varying. The businesses that scale past 20, 50, or 100 retailers don't rebuild their operation for each new addition. They start managing complexity instead.
The SPS Commerce network understands how each retailer works and applies compliance updates across its network of 300,000-plus trading relationships. A change one retailer makes to its requirements gets caught and reflected for every supplier connected to that retailer. The network handles the complexity so you don’t have to.