Direct answer: A reliable DTC inventory allocation for 3PL receiving starts with approved SKU quantities by channel, then links each unit to a physical carton or handling unit, receiving order, destination and usable-stock outcome. Freeze the allocation before origin release, send the receiver an accurate pre-alert, control every late change, and reconcile shipped, delivered, received, quarantined and available quantities.
This guide is for DTC brand, importer and operations teams moving China-origin inventory into a US or Canadian third-party logistics warehouse. It addresses the handoff between a commercial channel-allocation decision and a warehouse receiving process. It does not choose demand forecasts, define a universal routing guide, approve product identifiers or determine the 3PL’s inventory-accounting rules.
Reviewed: September 5, 2026. Recheck the cited standards and the receiver’s current agreement, routing guide and system specification whenever the destination, inventory platform, label method, product attributes or receiving process changes.
Key facts for DTC inventory allocation
| Control | Required evidence | Release question |
|---|---|---|
| Channel decision | Approved SKU quantity by DTC pool, launch, region or other real stock purpose | Does every unit have one intended allocation? |
| Physical load | Item-to-carton-to-handling-unit ledger | Can each released carton be traced to the allocation? |
| Receiver setup | Open receiving order, current routing guide and accepted destination identity | Can the 3PL recognize and process the load? |
| Pre-alert | Submitted shipment notice and receiver acknowledgement where required | Does the accepted data represent the physical cargo? |
| Receipt | 3PL receipt, exception states and inventory availability record | Do shipped, received and usable quantities reconcile? |
A channel allocation is not complete because a planning spreadsheet totals correctly. The physical cartons, receiving order and warehouse system must preserve the same decision. A DTC launch pool, general replenishment pool and marketplace pool can travel together only when the warehouse can distinguish them without guessing. Start with the DTC brand receiving path to define the commercial handoff and the date the relevant stock must become usable.
Define the usable-stock outcome before allocating units
Name the outcome the inbound is supposed to create. Examples include 2,400 units available to a DTC launch pool, 600 units held as safety stock, or a regional allocation available for orders after a specified receiving event. Use a stock state that the 3PL or inventory system actually reports. Vessel arrival, customs release and carrier delivery are important milestones, but none proves that units are available for fulfillment.
Give every allocation a purpose, owner, approval time and change condition. The commercial owner may decide how many units protect a launch or replenishment window; the operations owner must translate that decision into cartons, receiving references and a dispatch gate. Avoid percentages without unit totals. A statement such as 40 percent to DTC becomes ambiguous when suppliers short ship, cartons are rebuilt or inspection removes units.
Record the inventory date and the latest safe decision time. Work backward through 3PL processing, delivery, import release and transport availability. If the required quantity or date cannot be supported, escalate the gap before origin release. The inbound readiness checker helps expose missing importer, cargo, label, receiver and deadline inputs without treating a completed checklist as warehouse approval.
Build one SKU-to-carton allocation ledger
Create one controlled row for every materially different SKU and allocation. Include the brand’s item identifier, product description, approved units, stock pool, destination, purchase or transfer reference, lot or expiry attributes when required, and the person who approved the row. If the same SKU serves two channels, use two allocation lines rather than one total followed by an informal note.
Connect the data to the physical load. Each carton row should show its outer identifier, SKU contents, unit quantity, destination allocation, finished dimensions, gross weight, label version and exception status. A mixed-SKU carton needs item-level quantities. A rebuilt carton receives an updated relationship and evidence; it must not retain an obsolete allocation merely because the outer box looks unchanged.
Use the carton-to-shipment reconciliation method for the common origin controls, even when the receiving channel is DTC rather than FBA. The value is the comparison among physical units, cartons, commercial documents and receiving references. Marketplace-specific labels are not required for a DTC allocation, but the need for one approved physical and data state remains.
Identify parties, locations and handling units precisely
Separate the brand, legal importer, supplier, consolidator, carrier, 3PL customer account, physical receiving location and inventory owner. A familiar warehouse name or street address may still be insufficient when the provider operates several accounts, buildings or receiving systems. GS1 US guidance on the Global Location Number is one reference for standardized party and location identification. Use a GLN only when the parties’ implementation calls for it; do not invent or borrow an identifier.
The same discipline applies to pallets and other logistics units. GS1 US describes the Serial Shipping Container Code as a globally unique identifier for a logistic unit that can connect the physical unit with electronic information. That does not mean every DTC pallet must carry an SSCC. The active 3PL routing guide decides whether it requires an SSCC, a proprietary license plate, carton identifiers or another method, and who is authorized to create them.
Freeze the receiver’s current instructions in the shipment file: document name, version, effective date, account, destination and confirming contact. Extract the required label, pallet, notice, appointment and paperwork controls. The North America 3PL receiving path is the appropriate commercial page for clarifying these account-specific requirements.
Translate the allocation into a receiving order and pre-alert
Confirm that the 3PL has an open receiving order, purchase order, transfer order or equivalent record for the intended stock. Its reference, account, destination and expected quantities should agree with the allocation ledger. A valid transport booking cannot compensate for an unknown warehouse order, and an open order does not authorize cargo whose physical quantities or labels differ from the accepted file.
Prepare the pre-alert or advance ship notice from the final physical hierarchy. The X12 856 Ship Notice/Manifest definition explains that the transaction can list shipment contents and configuration with order, product, physical, packaging, marking and carrier information. It is a standards reference, not the 3PL’s implementation map. Follow the receiver’s required format, fields, channel, cutoff and acknowledgement.
Save the submitted version, time, control number or portal reference, plus the technical and business response. A successful upload can prove transmission without proving that the warehouse accepted the content. If the notice is rejected, correct the source data and preserve the new version. Repeatedly sending an unchanged file risks duplicates and leaves the physical discrepancy unresolved.
Control changes after origin release
Late allocation changes are operational changes, not spreadsheet edits. Moving 200 units from launch stock to general stock may require new carton relationships, receiving-order quantities, labels, commercial records or system reservations. Record the original value, revised value, reason, approver, affected cartons, documents changed, receiver response and time the physical change was completed.
Use a stop condition when the physical and electronic states differ. Hold the affected cargo when practical for an unknown receiving order, duplicate handling-unit identifier, unresolved quantity difference, wrong destination, unreadable label, unapproved lot substitution or rejected pre-alert. The origin release gate provides a place to isolate and correct these exceptions while the supplier or preparation team can still act.
For several factories, maintain supplier traceability after consolidation. The allocation ledger should show which purchase order and supplier produced each SKU even when cartons share a final load. The multi-supplier intake service and the supplier release board help keep factory cutoffs, discrepancies and destination allocations visible through the dispatch decision.
Book delivery around receiving readiness
Treat the delivery appointment as a separate control from the pre-alert. Confirm who requests it, which cargo-availability event permits booking, the required lead time, destination, time zone, vehicle and unload constraints, order references, pallet and carton totals, and contact path. Compare the accepted appointment with the final physical load before dispatch.
Do not build the slot solely from an estimated port, airport or terminal arrival. Allow for import release, deconsolidation or transload, local availability and the final-mile provider’s capability. If delivery timing moves, assess whether the 3PL order, ASN and allocation reservation need updates. Name who may change the appointment and who can approve waiting, storage or redelivery.
Reconcile receipt to usable DTC inventory
Track at least five states: shipped from origin, delivered by the carrier, received by the 3PL, held in an exception state, and released as usable inventory. A signed proof of delivery supports the carrier handoff, but the 3PL may later report shortage, damage, unidentified stock, lot conflict, quarantine or put-away delay. None of those units should be silently counted as available DTC stock.
Open one exception record for each discrepancy. Include the receiving order, notice and carton or handling-unit references; affected SKU and allocation; quantity; timestamps; condition evidence; 3PL response; origin evidence; owner; and expected closure. Keep inventory correction distinct from any freight or damage claim so a financial discussion does not hide the current stock state.
Close the file only at the agreed completion signal. Reconcile the approved allocation with the final usable quantities, document any approved reallocation, and update the demand plan with the actual availability date. Preserve the result as shipment evidence, but do not turn one successful receipt into a universal 3PL processing-time promise.
Pre-release checklist
- Approve exact SKU units for each DTC stock pool and destination.
- Confirm the current 3PL order, account, location and routing-guide version.
- Reconcile items to cartons and required handling units.
- Verify identifiers and labels against the receiver’s implementation.
- Generate the pre-alert from the final physical hierarchy.
- Retain the receiver’s acknowledgement and resolve every rejection.
- Freeze or formally amend the allocation before dispatch.
- Confirm delivery timing, vehicle constraints and exception contacts.
- Reconcile shipped, delivered, received, held and usable quantities.
What this guide cannot determine
This guide cannot determine the correct demand forecast, identifier license, barcode symbology, label layout, EDI mapping, receiving-order type, notice deadline, warehouse tolerance, appointment rule, inventory ownership, reservation method, processing service level, chargeback or liability for a specific account. Confirm those points in the current 3PL agreement and implementation material with the brand’s inventory owner, 3PL, systems provider and other qualified advisers.
Review the process again when a SKU, supplier, inventory channel, 3PL, facility, account, routing guide, integration, label rule or receiving status changes. Standards help parties structure identifiers and messages; they do not replace the bilateral operating instructions for the shipment.
Frequently asked questions
What belongs in a DTC inventory allocation file?
Include approved SKU quantities by channel or stock pool, destination and receiving order, item identifiers, carton or handling-unit relationships, required lot or expiry data, arrival plan, reservation state, exception owner and final usable-stock result. Add only fields required by the product, receiver and inventory system.
Should DTC and marketplace inventory share the same inbound shipment?
They can when cartons, commercial records, destination rules and allocations remain unambiguous. Show which units belong to each stock pool and how the 3PL will receive them. Split the load when shared handling would create label, routing, timing or ownership conflicts.
Is an ASN enough to reserve DTC stock?
No. An ASN describes an expected shipment under the receiver’s implementation, while reservation is an inventory-system state. The notice, receiving order and physical load should agree, but the brand or 3PL must confirm when received units become available to the intended pool.
When should a DTC allocation be frozen?
Freeze it before origin release, after final quantities and receiving instructions are known and while cartons and data can still be corrected. Use a later amendment cutoff only when the 3PL, carrier and systems can accept changes without creating different physical and electronic states.
What closes the 3PL receiving handoff?
Use the completion state defined in the service agreement, such as receipt posted with discrepancies accepted or inventory released as available. Carrier proof of delivery is not enough. Reconcile shipped, delivered, received, quarantined, damaged, unidentified and usable quantities.
Build the shipment-specific handoff
For a shipment review, send the SKU allocation, supplier and carton counts, finished dimensions and weight, cargo-ready date, 3PL receiving order, destination instructions, importer status and required usable-stock date. Use the inbound quote brief to ask Forest Leopard North America Inbound Desk for an origin-to-receiving plan with the open allocation and exception controls identified.
Change log
2026-09-05 Asia/Shanghai: Re-opened the X12 856 definition plus current GS1 US SSCC and GLN guidance; all three authoritative sources returned HTTP 200. Rechecked static guides, queued content, the public article inventory, sitemap and cross-site ownership. Receiver-specific identifiers, notices, tolerances and completion states still require the current 3PL documents.