METRC · Part 3 of 7 · 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 set up against the wrong Metrc item can look alike on a report, but they call for different checks. The labels below are our own shorthand for sorting problems. Metrc does not define them.
| What differs | Check first | What to keep |
|---|---|---|
| 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 that the POS product name and unit match the Metrc item before retrying the import or upload. | Product identifier, package identifier, unit, and the source record. |
| Your POS or inventory software and Metrc | Check whether the sale, transfer, or adjustment reached Metrc, failed, or is still waiting to upload before retrying it. | Source transaction ID, timestamp, response or error, and any retry. |
| Harvest or processing history | Follow the input package or harvest to the packages made from it and the waste logged against it. | Input and output IDs (packages or harvests), amounts, units, and the history for each one in Metrc. |
A category is a place to start, not proof of cause. Keep the original export or screenshot and note what was counted. For a large or repeating gap, find the event where the two records first split. Metrc's Oregon guidance describes a separate procedure for each of a receipt, a void, a package adjustment, and a rejected transfer, and other states' setups can differ; using one to compensate for another can leave the history harder to explain.
When you pass a gap to someone else, write down what you saw, the change you suggest, and who will check it afterward. If the source event is unclear, leave the record as it is, flag it for the owner, and settle it at the next count or before the state's reporting deadline for that event, whichever comes first.
- 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.