A useful Metrc receiving workflow brings the state manifest beside the buyer's order and the receiver's physical observations. It should reduce transcription while keeping package identity, quantities, permitted state actions and supplier disputes distinct.
Start with one licensed facility and a supported transfer type. Confirm state availability, credentials, user permissions, item mapping and recovery procedures before processing a live delivery. A Metrc integration does not establish that a POS, payment provider or product category is approved for your business.
Prepare the connection and receiving responsibility
For LineNow, Metrc connectivity depends on the configured market, facility license, operator credentials and vendor integration configuration. Have the authorized account owner connect through the product's connection flow. Confirm the intended facility and environment before testing. Never put API keys in supplier emails or order notes.
Assign one owner to submit the state receipt. If a POS or another integration already submits it, determine which system will perform each action so the same transfer is not received twice.
Also establish what remains manual: physical inspection, package identity checks, interpretation of regulatory requirements, unsupported corrections, and any reporting outside the supported receipt integration.
Pull the manifest, then verify it
LineNow's State Pull can retrieve supported manifest and package context into the compliance workflow. Returned information depends on the state API, available records and permissions; do not assume every request includes prices, complete lab reports or every document needed for release.
The receiver should check:
- The receiving license and source license match the actual transfer.
- Package identifiers and units match the labels and paperwork.