METRC · 3 min read
Route a METRC Discrepancy to the Right Record Owner
Route a discrepancy to the owner of the record that first diverged. The person who can explain the cause may not be the person authorized to change that record. The map below is a team procedure, not a list of Metrc permissions.
Route by the record that needs changing
| Record or question | Start with | Send with the request |
|---|---|---|
| Physical count or room record | Inventory lead at the facility holding the package. | Package ID, room, count, unit, counter, and time. |
| POS receipt or product mapping | POS administrator or the team responsible for the catalog. | Receipt/transaction ID, package ID, product mapping, and original versus expected value. |
| Metrc receipt, package, or adjustment | The authorized Metrc user for that license; contact Metrc support for a platform or access problem. | License, record ID, action attempted, current state, and relevant history. |
| Transfer data | Receiving and sending inventory leads, then the authorized record owner. | Manifest ID, package labels, delivered quantity, and receive/reject state. |
| Rule meaning, reporting deadline, or product disposition | Compliance lead and the jurisdiction's regulator. | The applicable rule, event date, license, and the decision that needs interpretation. |
Keep the escalation specific
State what happened, which record differs, what evidence you checked, and what correction you are requesting. Do not send credentials or patient information in a support ticket. Preserve the original transaction and package history so the receiving team can inspect the same event.
When two records disagree, do not ask the POS vendor to decide what a state rule requires, or ask the regulator to debug an integration retry. Separate the technical question from the compliance question and route each to the party that owns it.
Sources:
- Metrc Oregon Wiki: Sales — receipt correction and package-history behavior.
- Metrc Oregon Wiki: Correcting Errors — adjustment and transfer-rejection reason examples.
- Metrc Oregon Wiki: Frequently Asked Questions — data and reconciliation checks.