Template agreement
A sample file is reconciled before the operating period so unexpected fields or identifiers do not arrive at month-end.
Reconciling the market…
Cova and Greenline already support important store operations. BC Direct Delivery is not trying to replace them. The pilot focuses on supplier ordering, shipment expectation, receiving exceptions, credits, and evidence that crosses the supplier-store boundary.
THE GAP SITS BETWEEN SYSTEMS
The store system knows what reached inventory. The supplier knows what was accepted, allocated, packed, invoiced, returned, or credited. Direct Delivery needs a controlled bridge between those two accounts of the transaction.
The first pilot uses approved file templates and operator-assisted handoffs because a reliable export is more useful than an uncertified connection that appears finished but cannot be reconciled.
THE CONTROLLED HANDOFF
Map location, supplier, SKU, quantity, dates, and approved sales or receiving fields from a sample export.
Check headers, types, dates, limits, duplicates, retailer binding, supplier codes, and canonical product matches.
Keep file identity, validation outcome, row counts, period, locations, and matched suppliers for review and safe retry.
Sell-through and reorder evidence is derived only when the file, location, supplier, and SKU can be tied to approved records.
Partner approval, credentials, sandbox contract tests, mapping, reconciliation, and a signed scope are required before enabling provider operations.
WHAT WORKS TODAY
The current pilot capability validates an approved SKU-level sales format, rejects malformed or wrongly bound files, prevents duplicate replay, stores an import receipt, and exposes retry-safe status.
A sample file is reconciled before the operating period so unexpected fields or identifiers do not arrive at month-end.
Wrong organization, malformed headers, invalid values, conflicting data, or duplicate identity produces a visible failure instead of partial success.
Matched sales can support a reorder review. Unmatched or missing facts remain explicit and do not become invented velocity.
WHAT IS NOT CLAIMED
BC Direct Delivery is not represented as affiliated with, endorsed by, or currently approved by either provider. Direct read or write operations remain unavailable until the full certification boundary is complete.
A reviewed Direct Delivery record does not automatically alter the store's inventory system.
Technical adapter contracts do not substitute for partner access, tenant credentials, or an approved commercial relationship.
Every retailer location, supplier code, SKU, tax treatment, and operational event requires an accepted mapping and reconciliation procedure.
OPERATING BOUNDARY
This page describes an independent CSV and operator-assisted workflow intended to sit alongside existing store systems. It does not state or imply a provider partnership, endorsement, certification, or direct connection.
PLAIN ANSWERS
No direct provider operation is publicly claimed. The current pilot uses approved CSV or operator-assisted procedures while certification prerequisites remain incomplete.
No direct provider operation is publicly claimed. A production connection would require partner approval where applicable, credentials, mapping, sandbox tests, reconciliation, and signed certification.
It can validate an approved SKU-level sales file, reject malformed or wrongly scoped data, prevent duplicate replay, keep an immutable receipt, and use matched facts for reviewable sell-through signals.
PROVE THE WEDGE BEFORE THE MIGRATION
The founding audit covers a bounded supplier workflow, approved business records, explicit unsupported connections, and a written proceed, narrow, or stop recommendation.