BC DIRECT DELIVERYShared identifiers
Supplier order number, retailer reference when provided, shipment reference, store location, and relevant dates.
DIRECT DELIVERY WITHOUT AN ASN
When no ASN arrives, the order confirmation has to carry more weight.
Central delivery can give the store a standardized electronic shipping reference. Direct Delivery happens between the licensed producer and retailer. Without that shared notice, both parties need a controlled shipment and receiving record.
THE MISSING HANDSHAKE
The store needs to know what is coming before the cases reach the receiving desk.
An advance shipping notice normally carries a predictable shipment identifier and expected contents into the receiving process. In BC Direct Delivery, the supplier and retailer must create that operational handshake themselves.
A portal alone does not solve the problem. The confirmed order, shipment reference, expected lines, actual receipt, and discrepancy outcome must remain linked and usable by both organizations.
THE CONTROLLED HANDOFF
What the operating record does, step by step.
- 01
Confirm before fulfillment
Lock the approved retailer, destination, SKU, price, case count, and terms into a shared order reference.
- 02
Publish expected shipment facts
Record the carrier or hand-delivery reference, shipped cases, and expected date before the handoff.
- 03
Open receiving from the order
The receiver starts with expected lines instead of creating an unrelated receipt from scratch.
- 04
Record the physical result
Accept quantities and identify shortage, overage, damage, wrong item, or another exception line by line.
- 05
Complete the commercial result
Attach replacement, return, accepted variance, or credit evidence to the same order and shipment.
THE MINIMUM SHIPMENT RECORD
Create a small, dependable contract between fulfillment and receiving.
The exact format can vary during a pilot, but the identity and line-level facts should not. Both parties need enough information to know they are discussing the same shipment.
Expected lines
Registered SKU, product description, case configuration, lot reference when approved, and shipped case count.
Decision evidence
Receiver, timestamp, actual quantity, exception reason, supporting record, and authorized resolution.
WHY THE ORIGINAL ORDER MATTERS
Receiving cannot prove a variance if the expectation is missing.
A packing slip can describe what the supplier says was shipped. The accepted order describes what the retailer agreed to buy. Keeping both lets operators see whether the problem began at ordering, fulfillment, transport, or receiving.
Ordering variance
The accepted commercial terms differ from a later fulfillment record.
Shipment variance
The supplier fulfilled a different quantity or item than the approved order.
Receiving variance
The physical handoff differs from the shipment record and requires a documented outcome.
OPERATING BOUNDARY
This page explains an operating gap. It does not replace program instructions.
Suppliers and retailers should confirm current BCLDB requirements, their agreements, licence conditions, record retention duties, and approved delivery procedures before changing a workflow.
- One shared shipment reference
- Line-level receipt
- Human decision on every exception
PLAIN ANSWERS
Questions operators ask before a pilot.
What is an ASN?
An advance shipping notice is a structured message sent before delivery that identifies the shipment and its expected contents so the receiver can prepare and match the arrival.
Does BCLDB provide an ASN for Direct Delivery products?
BCLDB's published Direct Delivery information states that an ASN is not provided for Direct Delivery products. Operators should confirm the latest program materials before relying on a procedure.
Can a packing slip replace the confirmed order?
Not by itself. A packing slip represents what was packed. The accepted order represents what was agreed. Receiving needs both expectations and physical results.
PROVE THE WEDGE BEFORE THE MIGRATION
Put one month of Direct Delivery on one record.
The founding audit covers a bounded supplier workflow, approved business records, explicit unsupported connections, and a written proceed, narrow, or stop recommendation.