Glossary
Transfer
Movement of packages between licensees (or between an operator's own licenses), documented by a manifest in the state system and received tag by tag.
For a store, receiving a transfer is where an inventory discrepancy usually enters. The receiver records the accepted quantity per package, and the invoice should match it: invoice quantity equals accepted quantity, or a credit memo.
BudAlly's mobile receiving goes tag by tag: scan the tag, count, and record the accepted quantity. Short or damaged lines produce a credit-memo draft, and a tag that isn't on the manifest holds the invoice line rather than being received against the wrong tag. Metrc's API has no receive-transfer endpoint, so BudAlly prepares the accepted list, hands the user a task with the Metrc screen linked, and the ledger records what Metrc shows after.
Between an operator's own stores, BudAlly shows stock across them and drafts transfer manifests from the supply plan, so stock can move where it sells.
Where this comes up on budally.com
- Metrc for dispensaries: what it records, and how a store reconciles against it
- Metrc in California: what a dispensary has to report, reconcile and keep — the operations view
- Metrc in Michigan: what a dispensary has to report, reconcile and keep — the operations view
- Metrc reconciliation for dispensaries: the daily, weekly and 30-day procedure
- NMS2S explained: New Mexico's seed-to-sale system, what its API does, and what your store still has to do by hand
- How to get NMS2S expanded API access: CCD's validation process, step by step
- NMS2S vs BioTrack vs Metrc: what changed for New Mexico operators
- The NMS2S API for dispensary software: what exists, what it supports, how access works
Related terms
- Manifest
The state-system transport document for a transfer between licensees: packages, quantities, driver, vehicle, route, departure time. Received tag by tag with accepted quantities. In NMS2S: Sent → Ready to Receive → Fully / Partially Received.