METRC · 3 min read
Name the METRC Discrepancy Before You Fix It
Before changing a Metrc record, name the record that differs. A quantity gap, an incorrect receipt, a transfer mismatch, and a product-mapping issue can look alike on a report, but they call for different checks. The labels below are an internal triage aid, not Metrc-defined discrepancy classes.
Start with the record that differs
| What differs | Check first | Keep with the exception |
|---|---|---|
| Package quantity and physical count | Recount the identified package; review its last receipt, transfer, sale, and adjustment. | Package ID, count, unit, time, and the package-history entry. |
| Sales receipt and POS transaction | Compare the receipt and line items with the register transaction before editing or voiding. | Receipt ID, package, quantity, sale time, and the correction history. |
| Manifest and delivered package | Compare the manifest, package label, and received or rejected status. | Manifest ID, sender and receiver, package, and the quantity that arrived. |
| Product setup and package record | Check the product/item mapping and unit before retrying an import or sync. | Product identifier, package identifier, unit, and the source record. |
| Internal system and Metrc record | Check whether the source event posted, failed, or is still pending before retrying it. | Source transaction ID, timestamp, response or error, and any retry. |
| Harvest or processing lineage | Trace the input package or harvest through the recorded output and waste. | Parent and child IDs, input and output amounts, units, and the event history. |
Separate diagnosis from correction
A class is a starting point, not proof of cause. Keep the original export or screenshot, record what was counted or observed, and identify the event that first diverged. Then choose the correction that matches that event. Metrc documents distinct receipt, void, package-adjustment, and transfer-rejection workflows; using one to compensate for another can leave the history harder to explain.
For a team queue, require four fields before approval: discrepancy class, source evidence, proposed record to change, and the person who will verify the result. If the source event is unclear, leave the record unchanged while the owner investigates.
Sources:
- Metrc Oregon Wiki: Sales — receipt edits, voids, returns, and package history.
- Metrc Oregon Wiki: Correcting Errors — package-adjustment and rejection reason examples.
- Metrc Oregon Wiki: Frequently Asked Questions — reconciliation and data-format checks.