Skip to content

Module 04 · Compliance plan and up

Receive against the manifest. Deliver with your own drivers.

Manifests, delivery trip ledgers and receipts are built from your state's rule pack, so a missing field blocks departure instead of turning up later as a finding. Drivers work from a mobile app that checks ID, purchase limits and vehicle caps at every stop. Metrc writes run under the approving person's own key.

By BudAlly

Published

Run the free auditSee pricing

  • 01 · MANIFEST READINESS

    Every manifest is checked against a readiness list before anything leaves.

    The list covers licenses that are active and eligible, current driver and vehicle credentials, every package lab-passed with its COA attached, no duplicate tags, the vehicle value cap, route and times, and every field your state's pack requires, with missing fields listed by name. Contents and destination lock at departure. Voids are versioned, with a reason and the approver's own key.

  • 02 · RECEIVING

    Receive package by package, and return rejects on the same manifest.

    Receiving records the counted quantity per tag, with photos of any exceptions, before the driver leaves. Rejected packages go back on the same manifest through return transit to the shipper, and inventory is restored only when they are received back. The invoice then bills the accepted quantity, and any short or reject creates a linked credit memo.

  • 03 · TRIP LEDGER

    The delivery trip ledger is built before the vehicle departs.

    Drivers scan packages onto the vehicle, and the ledger separates product already tied to orders from unordered stock. A cap meter tracks total value and, where a state sets one, a separate cap on unordered product. Depart stays disabled until the ledger exists and the caps pass. Each stop records time, customer type, price and signature, and any stop without a delivery goes in a stop log with its reason.

  • 04 · DRIVER APP

    The driver app gates the shift and every stop.

    A shift can't start until the driver's age, employment, license, badge, training and vehicle credentials check out. Each stop needs a geofenced arrival, an ID scan matched to the name on the order, a purchase-limit check covering that day's in-store and delivery purchases, a signature and payment. A refused order is scanned back onto the trip ledger, and a missing signature blocks shift close.

  • 05 · DISPATCH RULES

    Dispatch applies your state's delivery rules from the rule pack.

    The dispatcher's rules engine applies vehicle value caps, agent counts, one retailer per trip, premises-to-stops-to-premises routing, GPS requirements and municipal opt-out geofences. Where a state requires one customer per delivery record or one order per trip, a load that breaks it is blocked. A rule the pack doesn't hold returns UNKNOWN and fails closed.

  • 06 · CUSTOMER ORDERING

    Shoppers order with ID and limits checked before the van loads.

    The customer flow covers the age gate, ID capture, residence check, a medical card where one applies, a limit check at checkout, payment rules by state and a delivery slot inside store hours. Tracking shows status and an ETA, with no live map of the driver. A refused or partial delivery shows its refund timeline and a revised receipt.

  • 07 · CASH HANDLING

    Driver cash is capped during the shift and counted at the end of it.

    The driver app keeps a running cash total against the vehicle cap and a drop threshold. Cash tips are counted separately from sale cash, and refunds go to the original tender, never as cash at the door. Shift close is a blind cash count reconciled to what the trip was expected to bring back.

  • 08 · RECORDS

    Manifests and receipts come out as signed, hashed PDFs.

    Each manifest renders as a PDF/A with a QR code, manifest number, page count and a SHA-256 footer. Every signature stores name, role, time, location and device. If paper has to be used, a photo of it is attached to the record.

What it never does

  • Nothing departs until every field your state's pack requires is filled and the vehicle caps pass.
  • Manifest contents and destination never change after departure.
  • A stop never completes without an ID scan, a name match, the age or medical check, a limit check and a signature.
  • A rule that hasn't been verified from a primary source returns UNKNOWN and routes to a person; it is never guessed.
  • Metrc writes run only under the approving person's own key.
  • Document numbers are sequential and gap-checked; records are voided, never deleted.

BUILT TO CONNECT WITH

  • Metrc
  • Onfleet
  • Aeropay

Questions

Do we need a third-party delivery service to use this?
No. The module gives you dispatch, the delivery rules engine and a driver app, so delivery runs on your own staff and vehicles.
What happens when a package is rejected at receiving?
It goes back on the same manifest, through return transit to the shipper. Inventory is restored only when the shipper receives it, and the invoice bills only what was accepted, with a credit memo for the difference.
How does it know my state's manifest and delivery rules?
The field sets, caps and stop rules come from your state's rule pack, versioned and shown on the manifest. Where the pack has no verified value, such as a delivery hour or a signature rule, the check returns UNKNOWN, blocks, and goes to a person instead of guessing.
Which plan includes manifests and delivery?
Manifests, transfers and mobile receiving are in the Compliance plan and up. Self-delivery dispatch and the driver app are in the Close plan and Chain Ops.