A first wholesale purchase order feels like a win right up to the moment the attachments arrive. There is the PO itself, and then there is a routing guide that runs forty pages, an EDI specification, a carton labelling appendix, and a vendor compliance schedule that reads like a price list for your own mistakes. Each rule in that packet has a dollar figure attached to it.
This guide walks through what actually sits inside that packet: the EDI documents you will be asked to exchange, how to read a routing guide before you commit, how carton and pallet labelling works, how advance ship notices and delivery appointments interlock, and which chargebacks show up most often. It is written for a brand approaching its first retail PO, not for an enterprise supply chain team.
In short
- Routing guides are contracts. Accepting a PO usually means accepting the current version of the retailer’s vendor and routing requirements, including deduction schedules you did not negotiate.
- EDI is the entry ticket. Most national retailers expect electronic exchange of the purchase order, acknowledgement, advance ship notice and invoice before the first load moves.
- The ASN is the single highest-risk document. A late, missing or mismatched advance ship notice is one of the most commonly cited deduction triggers across retailer vendor programs.
- Labelling failures are cheap to prevent and expensive to eat. GS1-128 carton labels and SSCC pallet hierarchy follow published GS1 standards, so there is no guessing involved.
- Chargebacks are disputable, but only with evidence. Timestamped proof of delivery, carrier records and label images are what win claims, and dispute windows are short.
Why wholesale fulfillment is not scaled up parcel picking
Direct to consumer fulfillment optimises for one thing: get a small parcel to a residential address fast. The unit of work is an order of one to three items, the carrier picks the label format, and the customer is the only party inspecting the package. Mistakes cost you a replacement and a refund.
Wholesale inverts almost every assumption. The unit of work is a carton or a pallet, the destination is a distribution center with a receiving dock and a schedule, and the inspecting party is a receiving clerk working from a compliance checklist. Mistakes cost you a deduction that is calculated by formula and applied without a conversation.
The second inversion is who controls the format. In parcel, you choose the box, the label and the carrier. In wholesale, the retailer specifies the carton dimensions you may use, the exact label content and placement, the pallet height, the stretch wrap, the carrier or carrier selection rules, and the hour at which the trailer may arrive. Your operation has to become configurable in ways a D2C pick line never needs to be.
Third, the money moves differently. A consumer pays before the parcel ships. A retailer pays on terms, after receipt, net of deductions, and the deductions are applied by a compliance team that is measured on recovery. If you have not yet mapped out how purchase orders, payment terms and buyer relationships work on the retail side, the wholesale operations guide for consumer brands covers that commercial groundwork before any of the fulfillment mechanics matter.
The operational capabilities you need before the first load
There is a short list of things that have to exist before you accept a retail PO. You need the ability to receive and respond to structured electronic documents, not just read a PDF. You need a labelling setup that can print a compliant carton label with a unique serial number per carton.
You also need inventory accuracy good enough that a committed ship quantity is real. Retailers measure fill rate against the PO, and short shipments draw deductions in many vendor programs. If your on-hand counts drift, the warehousing basics for brands that just outgrew the garage walk through the location and counting discipline that makes a committed quantity trustworthy.
Finally, you need someone who owns compliance. Not as a side task. The job is reading routing guide updates, tracking deductions by reason code, filing disputes inside the window, and feeding root causes back into the warehouse. At small scale that person is often the founder, and that is fine, but the role has to be named.
Which EDI documents will you be asked to support?
EDI stands for electronic data interchange. In practice it means exchanging business documents in a standardised, machine readable format instead of by email attachment. In North America the dominant standard is maintained by ANSI ASC X12, which assigns each document type a three digit transaction set number. International trading partners often use UN/EDIFACT instead, with different document names for the same concepts.
You do not need to learn the whole standard. For a first retail relationship, the working set is small and the retailer will tell you exactly which transactions they require in their EDI specification document.
The core transaction set
Five documents cover the majority of first wholesale programs. The purchase order comes in, you acknowledge it, you tell the retailer what is on the truck, you invoice, and you reconcile the payment. Everything else is an extension of that loop.
| Document | X12 code | EDIFACT equivalent | Direction | What breaks without it |
|---|---|---|---|---|
| Purchase order | 850 | ORDERS | Retailer to you | You are re-keying orders by hand, which is where quantity and date errors enter |
| PO acknowledgement | 855 | ORDRSP | You to retailer | The buyer has no confirmation of what you will actually ship, so shorts surface at receiving |
| Advance ship notice | 856 | DESADV | You to retailer | Receiving cannot pre-stage the load; this is a frequent deduction trigger |
| Invoice | 810 | INVOIC | You to retailer | Manual invoicing slows payment and creates matching exceptions |
| Remittance advice | 820 | REMADV | Retailer to you | You cannot see which deductions were applied against which invoice |
| Inventory advice | 846 | INVRPT | You to retailer | Optional for many programs; required for some drop ship and vendor managed setups |
| Functional acknowledgement | 997 | CONTRL | Both ways | Neither side knows whether a transmission was received and parsed |
Two of these deserve extra attention. The 855 acknowledgement is where you commit to quantities and dates, and a sloppy acknowledgement creates a paper trail that works against you later. The 856 advance ship notice is the one that carries carton and pallet structure, which means it has to agree exactly with the physical labels on the freight.
Who sits between you and the retailer
Very few brands connect their own servers directly to a retailer’s. The usual arrangement involves an intermediary, and the choice of intermediary drives both your monthly cost and how much engineering time the setup consumes.
| Option | How it works | Typical effort to launch | Best fit | Main drawback |
|---|---|---|---|---|
| Retailer web portal | You log in and type orders and ASNs into the retailer’s own site | Days | A single account at low volume | Fully manual; does not scale past a handful of POs per week |
| Managed EDI provider | A vendor maps your data, hosts the connection and gives you a dashboard | 2–8 weeks | Most first-time wholesale brands | Per-document and per-partner fees accumulate as you add accounts |
| EDI module in your ERP or 3PL platform | Your existing system ships a retailer connector you configure | 2–6 weeks | Brands already on an ERP with retail connectors | Connector coverage is uneven; your retailer may not be supported |
| Value added network plus in-house mapping | You own the maps and translation, the network handles transport | Months | High volume, many partners, in-house technical team | Real engineering and ongoing maintenance burden |
| Direct AS2 connection | Point to point encrypted transfer with no network in the middle | Months | Large suppliers to a small number of very large retailers | You own certificates, uptime and retries |
Most brands should start with a managed provider or their 3PL’s module and revisit the question at the third or fourth retail account. The reason is simple: the expensive part of EDI is not the transport, it is the mapping of your product and order data to each retailer’s particular interpretation of the standard.
How do you read a routing guide before you accept the PO?
A routing guide is the retailer’s operating manual for suppliers. It specifies how goods must be packed, labelled, documented, routed and delivered, and it almost always incorporates a compliance or deduction schedule by reference. Retailers publish and revise these documents on their own vendor portals, and the version in force is usually whichever one is current on the ship date rather than the one you read when you signed.
The five pages that matter most
Routing guides are long, but the operational risk concentrates in a few places. Find these sections first and extract the specifics into your summary.
- Carton and pallet specification. Maximum and minimum carton dimensions and weight, pallet type, maximum pallet height, overhang rules, stretch wrap and corner board requirements, and whether mixed-SKU cartons are permitted.
- Label specification. Label size, symbology, data content, placement on the carton, placement on the pallet, and whether a separate retailer-specific label is required alongside the GS1 label.
- Routing and carrier rules. Whether the retailer controls carrier selection above a weight or pallet threshold, how you request routing, lead times for routing requests, and freight terms.
- Delivery window and appointment rules. The must-arrive-by date convention, how far in advance appointments must be booked, what counts as on time, and the consequence of a missed window.
- Compliance and deduction schedule. The list of violation reason codes with how each penalty is calculated, plus the dispute process and the window for filing.
The deduction schedule is the one brands skip and should read first. It tells you precisely which failure modes the retailer cares about and how much each one costs, which is the only sensible basis for deciding where to invest in process control.
Questions to send back to the buyer
Buyers expect questions from new vendors, and asking them signals competence rather than inexperience. Keep the list short and operational.
Ask which distribution centers this PO ships to and whether each has different receiving hours. Ask whether the retailer routes the freight or you do, and at what threshold that flips. Ask whether a test or pilot shipment is available so a labelling error on the first load does not carry a penalty.
Finally, ask what fill rate and on time performance thresholds apply, and over what measurement period. Those two numbers determine whether you are a vendor in good standing or a vendor on a corrective action plan, and they are rarely stated in the PO itself.
What do cartons, pallets and GS1 labelling actually require?
Carton labelling is the most standardised part of retail compliance, which makes it the least excusable place to fail. The relevant standards come from GS1 US and the global GS1 organisation, and retailer routing guides overwhelmingly reference them rather than inventing a private format. Confirm the exact requirement in your retailer’s guide, since retailers do add their own fields on top.
The GS1-128 carton label
The shipping label most retailers expect is built on the GS1-128 barcode symbology, carrying data elements identified by application identifiers. The label is conventionally laid out in zones, with human readable text paired with each barcode so a receiving clerk can verify by eye when a scan fails.
The anchor data element is the SSCC, the serial shipping container code. It is an 18 digit number that uniquely identifies one logistics unit, meaning one carton or one pallet, and it must not repeat. GS1 guidance is that an SSCC should not be reused for an extended period, so build your numbering with plenty of headroom rather than cycling through a short range.
Other elements commonly required include the GTIN of the item inside, the quantity, the PO number, the ship-to location code, and sometimes a lot or date code. The retailer’s guide dictates which are mandatory. Getting a label vendor or your EDI provider to generate these is normal practice; hand-building barcode output is a false economy.
Pallet build and SSCC hierarchy
A pallet of labelled cartons gets its own SSCC and its own label, and the relationship between the pallet SSCC and the carton SSCCs inside it is what the advance ship notice describes. Receiving scans the pallet label, the system expands it to the expected cartons, and any mismatch is an exception.
This is why pallet building is a data operation as much as a physical one. If a carton is pulled off a pallet at the last minute and not reflected in the ASN, the scan fails even though the physical freight is fine. Train the floor that changing the pallet means changing the file.
Physical rules are more mundane but equally enforced. Expect specifications on pallet type and condition, maximum height including the pallet, no overhang, stretch wrap turns and tension, label placement on two adjacent sides, and a requirement that pallet labels are not wrapped under film where they cannot be scanned.
Mixed cartons and the single SKU preference
Many retailer guides strongly prefer single-SKU cartons and single-SKU pallets, because they move faster through a cross dock. Mixed cartons are often permitted but carry additional labelling requirements, and in some programs they attract a handling fee or are restricted to specific order types.
For a brand with a wide catalogue and small per-SKU volumes, this constraint shapes your assortment strategy. It is usually cheaper to pitch a tighter assortment at higher depth than to build a compliant mixed-carton process for twenty slow movers. Understanding which SKUs actually earn their shelf space is the point of the inventory turnover metric that retailers obsess over, and it is the same analysis that tells you what to offer wholesale.
How do ASNs, appointments and delivery windows fit together?
These three mechanisms are the heart of retail receiving, and they fail together. The advance ship notice tells the distribution center what is coming and in what structure. The appointment tells them when a door will be free. The delivery window defines whether that timing counts as on time.
The ordering matters. In a typical flow you finish picking and packing, generate SSCCs and print labels, transmit the 856 ASN, request routing or book an appointment, tender the freight to the carrier, and then invoice. Transmitting the ASN after the truck has already arrived is a classic and expensive sequencing error.
Why the ASN is the highest-risk document
The ASN is risky because it has to be both timely and exactly accurate. Timeliness is specified in the routing guide, commonly as a fixed interval before delivery or before the freight is tendered. Accuracy means the hierarchy, the SSCCs, the GTINs and the quantities match the physical freight item for item.
The practical control is a hard gate in your process: no freight leaves the dock until the ASN has been transmitted and a 997 functional acknowledgement has come back clean. That single rule removes a large share of the risk, and it costs nothing but discipline.
Must arrive by dates and the on time definition
Retailers increasingly measure on time delivery against a must-arrive-by date or window rather than a ship date, which shifts transit risk onto the supplier. Some programs score both early and late arrivals as failures, because an early trailer occupies a door that was allocated to someone else.
Read the precise definition in your retailer’s guide. The variables are whether the window is a single day or a range, whether arrival means gate-in or dock-in, whether the measurement is per PO or per load, and what tolerance applies. Two retailers can both say “on time” and mean materially different things.
Appointment scheduling is the mechanism that converts your plan into a slot. Expect a portal, a lead time requirement, limited capacity at peak, and a reschedule process that may itself carry a penalty. During peak retail season, appointment availability rather than your warehouse is often the binding constraint, which is an argument for building ship plans from a forecast rather than reacting to each PO. If your planning is still spreadsheet-driven, the walkthrough on forecasting demand without an enterprise tool is a reasonable place to start.
Which chargebacks are most common, and how do disputes work?
Chargeback is the everyday term; retailer documentation often uses “deduction”, “expense offset”, “compliance claim” or “vendor violation”. Whatever the label, the mechanism is the same: the retailer reduces payment on an invoice and cites a reason code. The amount is usually formula-driven, commonly a flat fee per occurrence, a per-carton or per-pallet charge, or a percentage of the affected invoice value.
Deduction schedules are retailer-specific and change, so the figures in your guide are the only authoritative ones. What follows is a map of the categories you are most likely to meet, not a rate table.
The deduction categories you will see
| Category | Typical trigger | How it is usually charged | Dispute difficulty |
|---|---|---|---|
| ASN failure | Missing, late, or mismatched advance ship notice | Flat fee per PO or per carton affected | Hard; the transmission timestamp is the evidence and it is on their side too |
| Label non-compliance | Wrong format, unscannable barcode, wrong placement, duplicate SSCC | Per carton or per pallet | Moderate; a dated photo of the label as shipped is the key document |
| Late or early delivery | Arrival outside the must-arrive-by window | Percentage of PO value, or flat fee per late load | Moderate; carrier records and appointment confirmations can shift fault |
| Fill rate shortfall | Shipped quantity below the PO or the acknowledged quantity | Percentage of the shortfall value | Moderate; a clean 855 acknowledgement is your main defence |
| Carton or pallet construction | Overhang, over-height pallets, damaged pallets, wrap failures | Per pallet rework fee | Hard without pre-shipment photos |
| Routing violation | You selected a carrier when the retailer controlled routing | Freight cost difference plus a fee | Low difficulty if you hold a routing instruction that says otherwise |
| Document error | Invoice does not match PO pricing or terms, missing references | Flat administrative fee, or the price difference | Low; this is a data argument and data wins |
| Unsaleable or damaged goods | Product arrives damaged or fails inspection | Cost of goods plus handling | Varies; packaging test records and photos matter |
Notice the pattern. The deductions that are hardest to dispute are the ones where the retailer holds the only timestamp, and the ones easiest to dispute are the ones where you hold a document that contradicts them. That asymmetry is the whole argument for building an evidence trail as a routine part of shipping rather than as a reaction to a claim.
Building a dispute that gets paid
Disputes are won on documents, filed inside a window, through the channel the retailer specifies. Miss the window and the merits stop mattering, so the first operational step is knowing the deadline, which is typically stated in the compliance section of the routing guide and is often measured in weeks rather than months.
The evidence pack that resolves most claims is short. You want the transmission log showing the ASN sent and acknowledged with timestamps, a photograph of a representative carton label and the pallet as shipped, the bill of lading, the carrier’s proof of delivery with time, the appointment confirmation, and the 855 acknowledgement if quantity is at issue.
Write the dispute narrowly. State the claim number and reason code, state the specific fact that contradicts it, attach the document that proves that fact, and stop. Long explanatory emails about how hard the week was do not move a compliance analyst working a queue.
Track every deduction by reason code in a simple ledger, even the ones you choose not to dispute. The value is diagnostic: three label claims in a month is a printer or process problem to fix, while one late delivery in a quarter during a snowstorm is noise. Department store programs add further layers such as markdown allowances and co-op charges on top of compliance deductions, and the breakdown of vendor terms inside department stores shows how those stack against the same invoice.
How do you choose a 3PL that can handle retail compliance?
Many brands enter wholesale with a 3PL that has only ever done parcel. That gap, not the retailer, is the usual source of a first-load failure. Retail compliance is a distinct capability and you should interview for it explicitly.
Ask which retailers the 3PL already ships to and request a reference from a brand of similar size in that program. “We can do EDI” is not an answer; “we ship to that specific chain weekly for four clients” is. Retailer-specific experience compresses your launch timeline more than any other factor.
Ask who owns the ASN. Some 3PLs transmit it, some expect your EDI provider to, and the handoff between warehouse scan data and the 856 file is exactly where accuracy is lost. Get the data flow drawn out, with the system of record for SSCCs named.
Ask how deductions are allocated. If the 3PL mislabels a pallet and the retailer deducts, does the 3PL absorb it? Credible retail 3PLs will discuss a compliance guarantee with caps and exclusions. Vague reassurance means you are carrying the risk.
Questions that separate retail-ready from parcel-only
A handful of concrete questions sort providers quickly. Which EDI transaction sets do you transmit directly, and which do you hand to a provider? Can you print GS1-128 labels with SSCC serialisation, and who controls the number range? Do you photograph outbound retail pallets as standard, and how long are images retained?
Taken together, the fulfillment questions and the commercial ones are a single decision. Terms, buyer expectations and channel economics shape what your operation has to support, and the wholesale operations groundwork for consumer brands is worth revisiting alongside any 3PL shortlist so you are not solving for the wrong volume.
General information, not compliance or legal advice
This article explains how retail vendor compliance mechanisms generally work. It is general information for context and education, not legal, tax, customs or regulatory advice, and it does not describe the terms of any specific agreement you may have signed.
Standards and retailer requirements change. Barcode and identification standards are published and revised by GS1, and EDI transaction set definitions are maintained by ANSI ASC X12 and UN/EDIFACT, so the authoritative current specification is always the one on the standards body’s own site. Deduction schedules, dispute windows and routing rules are set by each retailer individually and are revised without notice to the wider market.
Before you accept a purchase order or sign a vendor agreement, verify the current requirements in the retailer’s own published routing guide and vendor manual, and have the agreement reviewed by a qualified attorney, trade or customs professional, or accountant familiar with your circumstances. Nothing here substitutes for that review.
FAQ on wholesale fulfillment
Do I need EDI for my first wholesale account?
Not always. Smaller independent retailers and some regional chains will accept email purchase orders and PDF invoices, and several large retailers offer a web portal where a low volume vendor can enter documents manually. National chains with distribution center receiving generally expect electronic exchange, and the requirement will be stated in the vendor packet. Check the specific retailer’s vendor requirements rather than assuming either way.
What is the difference between a routing guide and a vendor manual?
The terms overlap and some retailers publish one combined document. Broadly, a vendor manual covers the whole relationship including onboarding, product data, pricing administration and compliance policy, while a routing guide focuses on how freight must be packed, labelled, routed and delivered. Both are typically incorporated into the supply agreement by reference, which is why the version in force on the ship date is the one that governs.
Can I reuse SSCC numbers once a shipment is received?
GS1 guidance is that an SSCC should not be reused for an extended period after it has been assigned, so treat reuse as something to avoid rather than optimise. Practically, allocate a number range with far more capacity than you expect to need and let your label or EDI system serialise it. Duplicate SSCCs inside a retailer’s window of record cause receiving exceptions and are a recognised compliance violation in many programs. Confirm the current rule with GS1 directly.
Who pays the freight on a wholesale order?
It depends on the freight terms in the PO, and the common arrangements are collect, where the retailer’s account and carrier are used, and prepaid, where you arrange and pay for transport and the cost is reflected in your pricing. Many retailers also control carrier selection above a weight or pallet threshold even on prepaid terms. The routing section of the guide states the threshold and the request process, and ignoring it is itself a deduction category.
How long do I have to dispute a chargeback?
Dispute windows are set by each retailer and are often measured in weeks from the deduction date rather than months. Some programs also require that disputes go through a specific portal or form and reject anything sent by email. Find the window and the channel in the compliance section of your routing guide at onboarding, and diary the deadline the day a deduction appears on a remittance advice.
Will a 3PL cover deductions that were their fault?
Some will, within limits. Experienced retail 3PLs may offer a compliance guarantee covering errors clearly attributable to their operation, such as a mislabelled carton, usually with a per-claim cap and exclusions for data they received from you. Providers without retail experience typically offer nothing. Raise the question during selection and get the allocation written into the agreement rather than discovering it after the first claim.
Does fill rate measure against the purchase order or my acknowledgement?
It varies by program, and the distinction is financially significant. Some retailers score against the original PO quantity, which means a short acknowledgement does not protect you, while others score against the quantity you confirmed. The measurement basis and the threshold should be in the vendor manual, and it is a fair question to put to the buyer directly because it changes how conservatively you should acknowledge.
Is drop ship easier than distribution center wholesale?
It is different rather than easier. Drop ship removes the pallet, appointment and dock compliance layer, since you ship parcels to consumers on the retailer’s behalf. In exchange it adds order-level service metrics such as ship-within time and cancellation rate, often requires inventory feeds, and usually comes with its own deduction schedule for late shipments. Brands with strong parcel operations frequently find drop ship a gentler entry point.
What is the single highest value control to put in place first?
A hard rule that no retail freight leaves the dock until the advance ship notice has been transmitted and acknowledged clean. ASN problems are among the most commonly cited deduction triggers across vendor programs, the fix requires no capital investment, and the same gate forces the label and pallet data to be correct because the file has to match the freight. Everything else is a refinement on top of that.