BC DIRECT DELIVERYOrder visibility
The store can review what was approved and what the supplier says was fulfilled before receiving starts.
FREE PARTICIPATION FOR LICENSED B.C. RETAILERS
A clean Direct Delivery handoff, without another retail software bill.
Your supplier invites the store. Your team sees the approved order, receives against what was promised, records the exception, and carries the clean result back to the system you already use.
THE RETAILER SHOULD NOT PAY TWICE
The store already pays for retail operations. Direct Delivery creates a different handoff problem.
A store may receive supplier menus through several channels, place orders in different formats, then re-enter the result during receiving. When a shortage or credit appears, the evidence often leaves the original purchase order and becomes an inbox task.
The free retailer workspace is deliberately narrow. It helps the store complete a supplier transaction without pretending to replace its existing buying, inventory, or accounting controls.
THE CONTROLLED HANDOFF
What the operating record does, step by step.
- 01
Accept the supplier invitation
A licensed store joins a specific supplier relationship. Access is invitation-only during the pilot.
- 02
Review the approved facts
See the SKU, case configuration, price, quantity, terms, and destination that the supplier has recorded.
- 03
Receive against the order
Record accepted quantities and identify shortage, damage, overage, or another discrepancy at the handoff.
- 04
Keep the resolution attached
A return authorization, replacement, accepted variance, or credit stays connected to the affected line.
- 05
Export the clean result
Use an approved CSV handoff for the store system while direct provider operations remain closed pending certification.
WHAT THE STORE GETS
Less re-entry, a better receipt, and one place to finish the exception.
The retailer view exists to make supplier participation easier, not to turn the store into the payer for a second general-purpose platform.
Receiving evidence
Quantities, reasons, photos or documents approved for the pilot, and operator decisions can stay on the same record.
Credit follow-through
The issue remains visible until the supplier records the agreed operational or financial resolution.
WHAT STAYS OUTSIDE
The free workspace has a clear boundary.
Consumer transactions, loyalty activity, payment-card data, employee scheduling, store-wide purchasing, and general inventory management do not belong in the supplier-led pilot.
No consumer records
The workflow uses business transaction records and SKU-level sales files approved for the pilot.
No surprise write-back
Provider operations remain disabled until partner approval, credentials, mapping, contract tests, and reconciliation are complete.
No forced migration
The store can evaluate the shared handoff while its normal operating systems continue unchanged.
OPERATING BOUNDARY
Free means no retailer platform subscription in the current pilot model.
It does not mean every future retailer feature is permanently free. Any later premium retailer product would be separately scoped, priced, and accepted. A supplier cannot enroll a store without the store's participation.
- Supplier-led invitation
- Business records only
- Store approval remains required
PLAIN ANSWERS
Questions operators ask before a pilot.
Why is retailer participation free?
The supplier is the initial payer because the supplier owns the Direct Delivery transaction and benefits when its retailer accounts can receive and resolve orders consistently.
Does the store have to replace Cova or Greenline?
No. The pilot uses approved CSV or operator-assisted handoffs. Direct provider connections are not represented as available until they are configured and certified.
Can any store create an account?
Not during the current pilot. Participation is invitation-only and limited to licensed organizations accepted into a bounded supplier workflow.
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.