How to reconcile Metrc with your POS inventory

Reconciling Metrc with your POS means making every package's quantity agree in both systems, and explaining every package where it does not. Do it in a fixed order: clear the sales that failed to reach Metrc first, then compare package quantities, then correct each difference with a reason code in whichever system is wrong. Correcting quantities before clearing failed sales hides the sales, because a quantity fix does not report them.

In Massachusetts, Metrc is the seed-to-sale system every licensee must use, and 935 CMR 500.105(8) requires inventory kept in real time with a documented count every month. The Commission's seed-to-sale FAQ adds that a sale posted twice or from the wrong package is voided or edited receipt by receipt and reconciled in Metrc and the POS within 24 hours, and that waste is accounted for by the end of the business day.

Why the two systems drift

• Sales that never posted. A key expired, Metrc was down, or the budtender's own key lacked a permission. The POS sold the product; Metrc still shows it on hand.
• Adjustments made in one place only. A count correction entered in the POS with the state system bypassed, or made directly in the Metrc portal.
• Units. A package held in grams in Metrc and as eaches in the POS, or a product weight that does not match the package's unit weight, turns every sale into the wrong quantity.
• Receiving. A manifest accepted in Metrc but not received into the POS, or received against the wrong product.
• Room moves. Moving stock between rooms is not always sent to Metrc (see Treez below).

The routine

1. Every day, clear failed submissions. Resend or fix each sale and adjustment your POS could not post.
2. Every day, record waste before close.
3. Weekly, compare quantities package by package with your POS's reconciliation report, largest difference first.
4. For each difference, decide which system is right from the physical count, not from either screen, and adjust the wrong one with a reason.
5. Monthly, run the documented inventory count 500.105(8) requires, and keep the record.

By POS

Dutchie POS

• Failed sales: Traceability, Logs, Batch Mode filtered to Error, and the Receipt Audit, which lists Dutchie sales missing from Metrc and Metrc sales missing from Dutchie.
• Compare: Traceability, Integration Audit shows each package's Dutchie and Metrc quantities side by side. Sync Levels pushes one side's number to the other with a reason. Dutchie says to refresh packages and check the receipt audit first.
• Adjust: Products, Inventory, Adjust, with a required reason; it goes to Metrc unless "Bypass state system" is ticked. Destroy does not go to Metrc, so Dutchie advises adjusting the package to zero instead.
• Units: the error "Error calculating equivalent quantity" means the package's unit differs between the two systems.

Flowhub

• Failed sales: the Sales tab filters by reporting status, and failed sales can be pushed again. Sending the same sales by API and by CSV creates duplicates in Metrc.
• Compare: Inventory, Metrc, Discrepancies, with flags for quantity, packages missing from either system, finished packages still active, and unit weight mismatch. Fix Metrc or Fix Flowhub adjusts the chosen side. It only sees packages modified in Metrc in the last 90 days.
• Adjust: a discrepancy with a reason, approved in Flowhub and Metrc or in Flowhub only.
• Units: the unit weight mismatch flag compares the Flowhub product weight with the Metrc package's unit weight.

Treez

• Failed sales: Compliance Management, Metrc Control, To Do tab, with the error Metrc returned. Treez recommends working it daily; a dismissed item cannot be restored.
• Compare: the Metrc True Up tab lists every package whose counts differ and adjusts Metrc to match Treez. Treez warns that a true-up adjusts packages and does not report sales, so clear Metrc Control first.
• Massachusetts: moving a package from a not-for-sale room to a for-sale room must also be done by hand in Metrc.

Cova

• Failed sales: Operations, Traceability Dashboard, with the reason, a suggested fix and the next retry.
• Compare: Reports, Metrc Reconciliation exports every package sorted by largest difference; blank columns mean the package is missing from one system. Cova says to clear failed sales and unreceived manifests first.
• Adjust: a quantity adjustment carries both a Cova reason and a Metrc reason, and updates Metrc unless "Only Adjust in Cova" is chosen.
• Units: a manifest can show grams expected and units received, for example three units of 3.5g.

Blaze

• Failed sales: no screen is documented publicly; Blaze documents what Metrc's 401, 500 and 503 errors mean.
• Compare: no reconciliation report is documented publicly. Blaze says to cross-check against Metrc often.
• Adjust: the Inventory Reconciliation form, by batch, with a reason per line, sent to Metrc in real time. Packages are closed in Metrc itself.
• Units: a product's weight per unit must match how Metrc holds the package, each or a weight.

BioTrack

BioTrack's public help center has no articles on its POS and Metrc. Ask BioTrack support where failed submissions and package comparisons live.

Where BudLogix fits

BudLogix reads incoming transfers from Metrc, and receivers scan each package off the manifest at the dock and count what is inside. It writes nothing to Metrc; adjustments stay in your POS or in Metrc. About Purchasing.

For the rest of what an inspector checks, see the Massachusetts CCC inspection checklist.