Library · 01.01 · Plan & Enter Markets

Define distribution requirements before choosing a 3PL

Physical Goods Editorial · Last reviewed October 9, 2026

Build a useful distribution brief before choosing a 3PL. Define product data, order flows, inventory authority, unresolved assumptions and acceptance evidence.

A useful distribution brief states what must physically happen, what information must agree, who decides when work departs from plan, and which evidence will prove the operation is ready. It should be complete enough that a warehouse, carrier, systems integrator or operating partner can identify the work, price the same scope and expose what remains unresolved.

This is a method for the company designing or changing its distribution operation. It is not a request-for-proposal template, warehouse operating procedure or universal service-level agreement. Use a working brief with a one-page cover sheet and only the supporting annexes your product and channels require. Do not send an unfilled master template and expect a provider to infer the missing operating decisions.

A conflicting case pack must be visible on the first-page inquiry, not hidden in an annex. Example: a retailer order for 15 cases is 90 units under a six-pack master and 120 under an eight-pack supplier record. Neither quantity should be promised before the merchant resolves the conflict with evidence. A provider capability inquiry may continue with both assumptions explicitly marked; retail commitment and release remain held.

At a glance: what must be in a distribution operating brief?

Short answer: Before asking a warehouse or 3PL for a quote, provide the product and packaging data, expected inbound loads, order mix by channel, storage and special handling, returns, system handoffs, and decision owners. Mark actual records separately from planning assumptions. An unresolved field can be shown honestly; it must not be silently priced as though known.

One-page brief example — fictional, not a client operation

This is an illustrative first-page extract, not a complete approved brief. Its quantities are hypothetical inputs for learning the method, not market averages or forecasts for any real brand.

How to read the example: The company can ask candidates whether they support the proposed channels and processes, but cannot yet demand a complete comparable final quote for storage, fragile handling or parcel transport. Unknown dimensions and an untested pack-out may alter feasibility and cost. They are visible requirements, not harmless blanks.

Minimum viable brief versus deeper annexes

The first column must distinguish confirmed inputs from planning assumptions. Use it to start a capability discussion, not to declare that two firm provider bids are comparable. A definitive quotation requires the providers to accept sufficiently complete and consistent specifications; launch approval also requires separately documented operating tests. A brief defines required tests; it never proves a live operation has passed them.

Three decision stages: do not require a launch file just to ask a question

1. Capability inquiry: send the one-page cover and named unknowns. A brand without historical orders can state a labeled scenario instead of inventing actual demand. A provider can describe constraints and indicative ranges; no firm comparison or launch approval follows.
2. Comparable proposal: issue one dated operating-brief revision, requirement IDs and a written change log to every candidate. Confirm SKU/UOM and retailer-specific requirements to the level needed for a reliable price, or require each quote to identify a conditional exclusion. The 03.02 comparison references this exact revision rather than retyping the SKU and demand tables.
3. Operational acceptance: require physical scans/measurements, configured-system evidence, named financial and stock authorizations, validated routing requirements where relevant, and accepted exception tests before receiving/releasing affected stock. These proofs are not prerequisites to initial exploratory conversation.

If you do not know a field: mark UNKNOWN, say what decision it blocks, name the person who can provide evidence, and set a follow-up. Unknown is not zero, a market benchmark, or a failed qualification by itself.

Pack conflict example (fictional): A merchant master says CH-101 has 12 each per case and a supplier document says 10. Twenty cases could imply 240 or 200 each. Do not commit either quantity to a retailer or convert them into available stock. Obtain the actual packing sample/scan and approve a single effective master revision; record both competing sources, the supplier deviation, an interim quoting assumption, decision authority and affected commitments. If a retailer purchase order is involved, obtain the current trading-partner routing guide, pack/label and ASN instructions, appointment requirements, claim owner and evidence of any applicable label scan. No universal SSCC label is presumed.

When to prepare one

Prepare or revise the brief when opening a new distribution channel or geography; appointing or replacing a third-party logistics (3PL) provider; combining warehouses, freight and returns providers; moving from founder-run fulfillment into managed operations; or diagnosing persistent defects that appear to sit between organizations.

Do not begin with a full network redesign if the only change is a documented, bounded task that the current operation can already support—for example, introducing one confirmed carton label with no effect on other handoffs. Record the narrow change, impacted owner and acceptance test instead. Conversely, if goods are subject to special handling, regulated storage, hazardous-material controls, food or product safety, import requirements, or retailer-specific routing rules, the operating brief identifies those dependencies but does not replace qualified specialist review.

The brief is not a way to make a forecast look certain. It is a controlled account of known facts, planning assumptions and unresolved decisions.

What the finished brief must establish

A completed brief gives five things to five groups of people:

Physical Goods recommended method: no requirement is 'complete' merely because a field is populated. It is complete when the evidence source, approver, exception rule and testable result are understood at the right level for the decision.

1. State the operating decision before listing capabilities

Write one paragraph identifying the business event and the decision required: We need to place approved inventory in a defined operating network to serve these channels, starting under these conditions. Name the person who can authorize changes to channel scope, launch date, operating spend and inventory release.

Record three distinct categories:

• Non-negotiable: a condition without which the operation cannot proceed (for example, validated temperature control, if the product and specialist review require it).
• Preference: a valuable condition that can be traded off if its cost or operational consequence is explicit.
• Open decision: something the company has not yet decided, with owner and decision deadline.

Do not put an unverified target under 'non-negotiable' simply because it looks familiar. A service promise needs an operational event definition, measurement method, feasible provider capability, and contractual agreement where applicable.

Output: one-page operating objective, scope exclusions, decision authority and change-control rule. Acceptance: each business-critical condition is classed and has an owner; unresolved blockers are visible rather than disguised as assumptions.

2. Define the physical product and its handling units

Start at the sellable unit, then document the shipping carton, inner pack and pallet / transport unit where used. These are different operational objects. A provider may receive cases, store individual units, pick single pieces and dispatch parcels; a wholesale order may require full cases or mixed pallets. The brief must say which conversion is allowed and how its quantities are counted.

Minimum product record:

GS1 distinguishes trade items (identifiable by GTIN) from logistics units (which may be identified with a Serial Shipping Container Code, or SSCC). Their functions are not interchangeable. Whether GS1 identifiers and particular label fields are required depends on the channel, trading relationship and chosen standard; the brief should record that decision explicitly rather than presuming every parcel needs an SSCC. [1][2] GS1 US also distinguishes dimensions and weights for consumer units from non-consumer shipping units; record the packaging level and units of measure with the figure. [3]

For U.S. warehousing, material handling and storage also raise facility-level safety considerations. OSHA identifies warehouse storage and handling hazards; whether any particular control or legal standard applies needs qualified review in the actual operation. [6]

Exception rule: if the physical sample, supplier specification and product master disagree, do not silently choose one. Quarantine the affected data record for approval; prevent distribution based on an untested substitution where it would change handling or channel compliance.

Output: approved SKU and pack-level master, with unknowns and evidence provenance. Acceptance: receiving, storage and outbound personnel can identify and count the same product at the same packaging level.

3. Describe actual demand, not an attractive average

A monthly order total does not describe warehouse work. Separate observed history, committed events, forecasts and unquantified possibilities. Describe each sales channel independently where fulfillment rules differ, without assuming that e-commerce, wholesale and samples can use the same handling process.

Request order-line data sufficient to inspect:

• order count and units/lines per order, not just revenue;
• single-item, multi-line, kit and case-order prevalence;
• destinations and service promises, including any remote, cross-border or appointment work;
• daily or weekly surges linked to launches, replenishment or wholesale windows;
• cancellations, split orders, exchanges and special packing requests;
• historical returns and causes, if reliable records exist.

If history is absent, build explicit scenarios. For example, a base order, a mixed order, a wholesale shipment and a launch surge may be priced and tested separately. Record the scenario source, assumption owner, date, and sensitivity range; invite providers to explain what changes their commercial basis. Do not attach a probability or benchmark to these scenarios unless it has a defensible basis. A quote based on uncertain demand is a conditional model, not a commitment or a forecast endorsed by Physical Goods.

Record what the company can control (launch communication and order holds) separately from uncertain demand. Determine who is permitted to release bulk campaigns or exceptional large orders into the warehouse queue.

Output: versioned demand and order-profile appendix. Acceptance: the operations team can select representative test transactions and providers can identify which work is excluded from standard handling.

Inbound data to provide alongside the SKU master

Give candidate providers a compact shipment profile: origin and ship-from party; expected receipts by period; mode and delivery type (parcel, floor-loaded container, pallets or full truckload where relevant); expected pallet/carton count and packaging configuration; ASN/PO/packing-list availability; labeling and scan identifiers where required; receipt inspection and quarantine rules; appointment constraints; and who investigates a shortage. Mark every estimated field. This is information needed to scope the work, not a universal list of documents legally required for every shipment.

4. Trace the inbound path until stock is usable

Map each step: origin release → freight booking → delivery notice → delivery appointment (where required) → physical receipt → counting/inspection → discrepancy record → system posting → disposition → release to sell or allocate.

Define what makes an inbound shipment expected. The receiving party may need a purchase order, advance shipping notice (ASN), packing list, expected SKU and quantity data, transport-unit IDs, carrier reference and appointment instructions. The brief should state which records are required for this arrangement, not claim one universal document set.

Specify how the receiver handles differences among expected, delivered and accepted quantities. In particular, record:

• what must be counted (pallets, cartons, eaches, serialized units);
• which images or measurements are taken for damage or mismatch;
• who owns carrier-related evidence or claim preparation;
• who approves a quantity adjustment or quarantine release;
• whether received stock is saleable immediately or only after a defined acceptance event;
• how an inbound failure becomes visible to the person responsible for replenishment and customer commitments.

Do not conflate a truck's arrival with saleable stock. A received but quarantined unit and a received available unit lead to different commitments. Shopify, for example, distinguishes On hand, Available, Committed, Unavailable and Incoming inventory states; these are platform-defined states, not an industry-wide vocabulary. [4]

Output: inbound event map and sample receiving/discrepancy record. Acceptance: a reviewer can reconcile an expected shipment to accepted stock, non-saleable stock and open discrepancies without relying on verbal explanation.

5. Define the outbound promise as observable events

Follow an order through order creation → authorization/release → routing → warehouse acceptance → allocation → picking → packing → carrier tender → tracking confirmation → delivery exception handling. Different organizations may own each transition.

For every transition, state the triggering event, timestamp/system, owner, rejection reason and customer-facing effect. Agree how to handle each of these cases before launch:

A storefront action and warehouse action are not necessarily the same event. In Shopify's app-connected fulfillment flow, a requested fulfillment may be cancelled directly before acceptance, but after a service accepts it, cancellation requires a request that the service can accept or reject. The specific integration and warehouse response still need testing. [5]

Avoid undefined terms such as 'same-day' or 'fast shipping.' If they are operationally necessary, define the eligible order population, the clock start, calendar/cutoff treatment, exclusions, the end event, the measured source and the exception owner. Targets are negotiated business requirements, not numbers adopted from an article.

Output: outbound state-and-owner map, representative test set and written service definitions. Acceptance at the briefing stage: the test cases, required records, intended witness and escalation owner are specified well enough for a candidate to challenge. Actual provider/integration execution is a separate readiness gate before real orders are released; drafting the brief does not demonstrate that the system works.

6. Specify returns as physical inventory decisions

A returns policy written for customers is not enough to instruct a warehouse. Name who authorizes return shipments and who receives, inspects, grades, photographs and disposes of goods. Define what evidence allows an item to be restocked, repaired, reworked, returned to vendor, recycled or destroyed. Distinguish an undeliverable shipment from a customer return, and a commercial refund decision from the physical inventory disposition decision.

Where merchandise includes hygiene, safety, serialized or specially regulated products, send disposition rules for specialist validation. Write whether returns affect the system of record immediately or only on inspected acceptance.

Output: disposition table and exception escalation rule. Acceptance: a returned unit cannot become available to sell solely because a refund or return label exists.

7. Establish records, handoffs and decision authority

List every operating party: product company, supplier, freight coordinator, importer/broker (where relevant), warehouse, commerce platform, marketplace, carrier, returns handler, technology provider and operating partner. Assign one accountable decision owner for each exception even where multiple parties execute tasks.

For each record identify the authoritative source for that decision, not just the software that stores a copy. Inventory on hand might be measured at the warehouse while sellable availability is published through commerce software; the brief must state synchronization rules, latency tolerance, discrepancy detection and authority to adjust. Do not call two independently editable quantity records a single 'source of truth.'

Require sample exports and logs of: shipment receipts, SKU stock states, order exceptions, packing/tracking events, returned stock disposition, adjustment approvals and invoices. Verify whether the company actually has access to the data, whether fields can be exported and whether identifiers reconcile across systems.

Output: responsibility and record-authority matrix. Acceptance: each material event has a record owner, a reconciliation mechanism and an escalation contact; no exception depends on an unnamed 'team.'

8. Capture the cost model and launch conditions

Do not ask providers to 'quote fulfillment' without a complete scenario. Cost categories to expose include implementation and integration, receiving, storage, pick/pack, cartons and consumables, parcel freight, non-parcel freight, returns, special projects, inventory services, software, management, minimums and exceptional charges. Determine who authorizes unscheduled work, how charges are substantiated and how hard costs are funded.

The brief should not imply a binding estimate; it specifies common comparison scenarios and records assumptions so quotes can be compared on scope. Contracts, indemnities, insurance, customs responsibility and other specialist terms require qualified review as applicable.

Before stock is committed, define a launch decision:

1. Ready to test: essential requirements are written; unresolved choices have owners; product data and sample records are available.
2. Ready to receive: location/provider and receiving path are confirmed; supplier, freight and receiver know the same instructions; a discrepancy path exists.
3. Ready to release orders: opening stock is reconciled; actual integration and representative order tests pass; failure recovery and contacts are known.
4. Ready for ongoing control: weekly exception review, inventory reconciliation, cost verification and change approval have assigned owners and agreed cadence.

A company can approve a conditional launch only by naming the exception, its operating containment, person who accepts the exposure and condition that ends the exception. A missing essential safety or regulatory clearance is not something an operating team may waive through a generic conditional approval.

How to validate the brief before inviting proposals

Use an evidence review with the business owner, operations lead, commerce/systems owner and whichever specialists are material to the product. For each critical requirement ask four questions: Can we point to its origin? Can the executing party demonstrate it? Can a named person approve deviations? Can we determine objectively whether it passed?

Mark items Confirmed, Estimated, Unresolved or Not applicable. A 'Confirmed' item needs an artifact or accountable approver; estimated values need their method and review trigger. Separately classify the effect of each gap as Blocking, Conditional with containment, or Non-blocking. Unknown dimensions, for example, may block a provider's final freight and storage design even when order volumes can be scenario-estimated.

Pilot example — hypothetical, not a Physical Goods client: A homeware brand wants parcel fulfillment plus periodic wholesale cases. It has sellable SKUs and projected order totals but no case-pack master, no tested fragile pack-out, and no owner for retailer label exceptions. Its initial statement—'3PL for e-commerce and wholesale'—is not provider-ready. The operating brief instead records the two order types separately, designates fragile pack-out testing and carton labeling as gates, requests supplier case-pack evidence, identifies the wholesale contact who approves deviations, and postpones the final quote comparison until those requirements are known. It does not claim a particular damage rate, cost saving or launch date.

The decision record that closes the brief

Conclude with a short approval block:

The brief should remain under revision control after launch. Update it when a new channel, product characteristic, node, material demand pattern or systems integration changes the agreed work. The approved baseline belongs to the company; provider-specific standard operating procedures and contract schedules can refer to it, but they are separate records.

Information providers need from you — scoping handoff

Use this as the cover message accompanying a written distribution-brief inquiry:

• Product: the SKU/pack-unit file, available dimensions and weights, physical samples, special handling and traceability requirements.
• Inbound: origin, delivery type, shipment frequency, carton/pallet quantities, notices, receiving evidence and short/damaged stock instructions.
• Outbound: example order baskets by channel, destination/service assumptions, pack-out and retailer requirements, surge cases and return dispositions.
• Data and decisions: system ownership, export fields, exception/cancellation procedure, stock-release and spending authority.
• Quote qualification: which figures are historical, committed, scenario-based or unresolved; which conditions prevent a complete quote; whom to contact for clarifications.

Once multiple candidates respond, use 03.02 — Fulfillment Provider Comparison Matrix to normalize their written charges and operational evidence. This chapter does not decide who wins the tender.

Where this chapter stops

This chapter determines the requirements to test. How to evaluate a U.S. 3PL explains how to evaluate a particular provider once those requirements exist. Separate Library chapters cover receiving evidence, ongoing inventory-record authority and cross-party responsibility. Each addresses a different operating decision.

Related Physical Goods capability: Distribution & Operations — operating design and coordination where several specialist functions must work as one.

Source notes

This decision method, its gates, matrices and worksheet structure are Physical Goods editorial recommendations, not a published industry standard, a legal requirement or an assurance of operating results. The sources below support specific facts and terminology only. Selected GS1, Shopify, GS1 US and OSHA source pages were reviewed October 8, 2026; the cited sources apply only to their stated scope. Specific regulatory and contract requirements must be verified for the operation.

1. GS1, What is the Global Trade Item Number (GTIN)? and What is a logistics unit?. Supports the distinct functions of trade-item GTIN and logistic-unit SSCC; specific use depends on the trading relationship.
2. GS1, Logistic Label Guideline. Describes GS1 logistics-unit labeling and SSCC, not a blanket statutory requirement for every parcel.
3. GS1 US, Add Product Dimensions. Supports pack-level dimensions and gross/net weight distinctions; the business must validate its own physical measurements.
4. Shopify Help Center, Understanding inventory states. Supports Shopify-specific On hand / Available / Committed / Unavailable / Incoming definitions.
5. Shopify Help Center, Fulfilling orders using a fulfillment service with an app. Supports accepted-versus-requested cancellation behavior; actual provider and app workflows must be tested.
6. OSHA, Warehousing — Hazards and Solutions. Further safety reference for U.S. warehouse handling; the chapter does not determine the applicable safety standard for a particular product or facility.

When to revisit the method: major changes in relevant standards, commerce systems, warehouse nodes, product handling, sales channels or the accountable parties.