Inspections

OMMA inspection checklist for cannabis dispensaries

An inspection goes best when your records already agree with each other. This checklist is about the records and routines you control, so you can walk in with nothing to explain.

Last reviewed October 2026 · For licensed Oklahoma dispensary owners and managers

The right approach

We do not list what OMMA inspects; that is set by OMMA, and the current rules and any notice you received are the authority. What we can say is that an inspector compares what you say happened with what the records show, and Metrc is the state's record. So the most useful preparation is making sure your shelf, your point of sale and Metrc tell the same story, and that every exception has a reason written down.

Use this as a working list. Tick items off, and keep a note of anything you could not close and why.

Two to four weeks before

Licenses and paperwork

• Confirm your facility license and any other required documents are current, and know where they are. Check current OMMA rules for what must be displayed or available.
• Confirm the license number in your POS and Metrc connection matches your current license.
• Collect your written procedures: patient check-in, overrides, voids, waste, recalls and inventory counts.

Metrc and inventory

• Run a full inventory comparison against Metrc and work the mismatch list down. See inventory reconciliation.
• Clear all failed or pending Metrc sales. See Metrc reporting.
• Resolve negative balances in Metrc and packages that are empty but not finished.
• Close out incoming transfers that are overdue or only partly checked in.
• Do a full physical count, blind if you can, and investigate variances rather than overwriting them.

Patients and sales

• Review medical customers with expired cards or missing license details. See license verification.
• Review the last 30 days of over-limit sales, by your numbers and by Metrc's. See purchase limits.
• Review the overrides list. Every override should have a manager and a reason that makes sense.
• Review voids, especially any that never reached Metrc.

Lab testing and holds

• Confirm nothing on the sales floor is lab-failed, untested or on a Metrc hold.
• Check rooms marked not for sale or quarantine hold only what they should.
• Check for packages past their expiration date that are still on the floor.

The week before

• Re-run the inventory comparison and the failed-sales list. Anything new since the big clean-up?
• Make sure at least two people on every shift can pull up a sale, a package history and a customer record quickly.
• Check that staff Metrc keys still work, if your store uses them.
• Brief the team: who greets the inspector, who answers record questions, and who calls the owner.

On the day

• Run a final Metrc sync and confirm no sales are waiting to report.
• Have the compliance dashboard open, so you can explain any open item and show the fix in progress.
• Answer what is asked, show the record, and write down anything you were asked to follow up.

Afterwards

• Write up findings and follow-ups the same day, with an owner and a date for each.
• Turn anything that surprised you into a step in your daily routine. See the daily compliance dashboard guide.

Where GreenPOS helps

• Compliance score: Compliance → Compliance Score lists every open issue with a Go to fix link, and a Why is your score…? card shows each deduction.
• Records on hand: Overrides, Purchase Limits, Metrc Sync History and Audit Trail are tabs on the Compliance page, and each package has its own History.
• Counts: inventory counts can be blind, scheduled, limited to one room, and compared with Metrc, with Update Metrc for managers whose role allows Metrc adjustments.
• Recall Assist (Professional plan) walks through a recall, embargo or lab-failure pull: find affected packages, see affected customers, optionally place packages on hold and notify customers, with a manager PIN to confirm.
• Lab and holds at the register: a Metrc-tagged package sells only when Metrc shows its lab testing as Test passed or Retest passed, and packages on a Metrc hold are blocked with no override.