METRC California: Retail vs. Delivery Compliance
California's Department of Cannabis Control (DCC) requires every licensed cannabis business to use the state's track-and-trace system to follow cannabis from seed to sale. That system, Metrc California, requires different records for a retail dispensary than for a delivery operation. The DCC partners with Metrc, the software that runs this tracking program, called the California Cannabis Track-and-Trace (CCTT) system.
Retail staff log incoming packages and check purchase limits before a sale. Delivery staff track inventory and document each order while the product is on the road. Operators who run both a storefront and delivery need to see where these requirements overlap and where they differ.
What Metrc Requires for California Retail Dispensaries at the Counter
Every incoming package carries a Metrc tag, a label that holds a unique identifier, or UID. A UID is an alphanumeric code, as defined in California's cannabis regulations, used to reference a specific plant and any cannabis product made from it. Read the Ins and Outs of METRC in California post for the full tag and UID process.
A cannabis POS built for dispensaries handles compliant checkout, real-time inventory, kiosk mode, customer profiles and METRC integration. Its compliance tools include METRC package intake, which records each tag as inventory arrives, before the product can be sold.
This compliance software also includes purchase limit enforcement, which checks a sale against the customer's limit before checkout is complete. Retail sales also require the customer to be 21 or older with valid ID. California's Business and Professions Code requires a track-and-trace program that uses a unique identifier to report cannabis movement through the distribution chain.
What Metrc Requires for California Cannabis Delivery Operations
Delivery adds a step that counter-only compliance does not cover: tracking the sale and the product while a driver is still on the road. For delivery orders, the same compliance software generates a Metrc sales delivery manifest and syncs inventory adjustments to Metrc.
Cannabis delivery software supports each run with AI route optimization, real-time dispatch, a driver fleet app, delivery zones and inventory kits. Route optimization plans each driver's stops, and the driver fleet app lets dispatch see every vehicle's status. Delivery zones mark the areas a driver can legally serve, and inventory kits group the products a driver carries for a run.
Metrc Retail vs. Delivery Requirements at a Glance
The table below separates what retail and delivery share from what delivery adds on top, so an operator can see both at a glance.
| Workflow step | Shared by retail and delivery | Added for delivery |
|---|---|---|
| Product entry | Metrc package intake logs each tag and UID before a product can be sold. | Inventory adjustments synced to Metrc record stock changes while a product is in transit. |
| Sale documentation | Purchase limit enforcement checks run before checkout completes. | A Metrc sales delivery manifest documents each delivery order. |
Reading the two columns side by side shows where the two operation types share the same goal. Each one needs a record Metrc can match to the product, whether that record starts at the counter or ends at a delivery address.
What Changes When a Business Runs Both a Storefront and Delivery
A multi-location retailer faces the same question at every site: does package intake feed into one Metrc record, or several? A business that runs a storefront and delivery from one license needs its inventory to match in both places.
Point-of-sale software built for dispensaries offers real-time inventory and Metrc integration at the counter. Delivery software can draw from that same inventory, using route optimization, dispatch, delivery zones and inventory kits to move stock out to drivers.
Package intake, purchase limit enforcement and inventory adjustments synced to Metrc can run through one feed instead of two. A single feed lets staff log each product into Metrc once, instead of separately for the storefront and for delivery. See the Metrc compliance page for how these features work together.
Common Metrc Compliance Mistakes by Operator Type
Metrc compliance breaks down differently depending on how a business sells. The mistakes below match the retail, delivery and hybrid operations covered above.
- Retail: logging a package's tag into Metrc after it reaches the shelf, not at intake, puts the system out of step with the floor. Logging intake as each package arrives keeps the two aligned.
- Retail: skipping the purchase limit check at checkout removes the control meant to stop a sale over the state limit. That control only works when checkout runs it on every sale.
- Delivery: closing a sale without generating the trip's Metrc sales delivery manifest or logging the inventory adjustment leaves no record of what left the store. Generating both at dispatch avoids that gap.
- Hybrid: running the storefront and delivery side on separate inventory logs risks the same item being double counted or missed in Metrc. Keeping one feed, instead of two, keeps the counts aligned across both channels.
Each mistake above comes down to the same root cause: a step logged late, skipped or split across two systems instead of one.
Operators stay responsible for keeping their own package intake, purchase limit and delivery records accurate. Software that logs these steps supports that work; it does not replace it.
Keep Retail and Delivery Compliance on One Metrc Feed
WebJoint's dispensary POS logs package intake and enforces purchase limits at checkout. Its compliance features also sync inventory adjustments and delivery manifests back to Metrc. If you run a storefront, a delivery fleet or both, see how these features fit your operation: Book a Demo.