Seed to sale POS reporting and METRC integration
A seed to sale POS is a register that reports every tagged package to the state system your license runs on, which in most regulated states is METRC. The tag on the jar and the sale on the screen have to stay tied together. Integration is simply the wiring that keeps those two records agreeing without hand entry.
What does a seed to sale POS actually track?
The name is literal. Traceability starts at the plant and ends at the customer, and every step in between leaves a record the state can pull. The chain looks like this:
- Every plant and package carries a state-issued tag with its own identifier
- The tag follows the product through growing, processing, transfer and sale
- The register records which tagged package each sale came out of
- Those sales are reported back to the state system on the schedule your state sets
- Your inventory in the POS and your inventory in the state system have to agree
Nothing in that chain is optional in a regulated state, and none of it is something a general retail register knows how to do. This is the reason dedicated cannabis POS platforms exist and why we say plainly on dispensary POS that a licensed shop should buy compliance software from a company whose whole product is compliance software.
The details differ by state. Most regulated states contract with the same traceability system, a few run their own, and the tag formats, transfer manifests and reporting deadlines are set by each regulator rather than by the software. That is why a vendor demo in another state proves very little. Ask to see yours, with your product categories loaded and your reporting schedule in place.
Why does a state require this at all?
Traceability exists so a regulator can follow a product from where it was grown to who bought it, without taking anyone's word for it. In the states that require it, that reporting is a condition of holding the licence rather than a feature you opt into. The obligation belongs to you, not to your software vendor, and it does not scale down because your shop is small.
What each state actually asks for varies, and it moves. Tag formats, transfer paperwork, reporting deadlines and how corrections are handled are set by each regulator. Some states contract the same traceability system, some run their own, and rules get amended between licence renewals. That is why the only useful source on your obligations is your own regulator, read directly.
The practical version for an owner is simple. Someone in your building has to know what your state expects this month, not last year. Give that job a name. A vendor's release notes are not a substitute for reading the rule that applies to your licence.
Which counter tasks sit next to the reporting?
The reporting is only one thing the register is doing. Every applicable sale still needs an ID check that runs as part of the sale rather than as a step a staff member remembers. Purchase limits still have to be checked against the person standing there. The tag on the package still has to be scanned, not typed from memory at the end of a shift.
Then the ordinary retail mechanics that traceability quietly depends on. Case and unit handling for anything bought by the box and sold one at a time. A return routed back to the package it came from. A discount or a void recorded against the person who ran it. Every one of those is a place where the shelf and the state record can separate if the software makes the right action harder than the wrong one.
Staff accounts are part of the compliance story, not an admin nicety. Individual logins, permissions set so a clerk sells and returns with a reason attached, a shift lead voids and discounts, and only an owner edits items or exports data. When an auditor asks who made an adjustment, you want a name on the record rather than a shared code.
What breaks when the integration is weak?
Drift. Your shelf count and your state count separate by a little, then by more, and the gap is what an audit finds. It usually starts somewhere ordinary: a manual adjustment nobody logged, a package split at the counter, a return that went back into stock without a tag, or a sync that failed quietly overnight and nobody checked the log.
So the question to ask a vendor is not whether they integrate. Almost everyone says yes. Ask what happens when a sync fails, who sees the error, how a mismatch gets reconciled, and whether the fix is a support ticket or a screen you can use yourself at closing time. Ask them to show it with your state selected.
The habits matter as much as the software. Reconcile daily rather than monthly, because a one-day gap is a memory and a thirty-day gap is an investigation. Give one person the job of reading the sync log, and make manual adjustments require a reason on the record. None of that is glamorous, and all of it is what a clean audit actually looks like from the inside.
Does traceability reporting help with payments?
No, and it is worth being clear about why. Traceability satisfies your state regulator. It says nothing to a card network or a sponsor bank, because their objection is federal. Cannabis remains a federally scheduled substance, so the major card networks do not process plant-touching sales in most states no matter how clean your reporting is. A perfect audit trail does not open a merchant account for a licensed dispensary.
We lay out what a licensed shop can and cannot accept on dispensary payments and can dispensaries take credit cards. If someone offers you a workaround that leans on a miscoded transaction, read cashless ATM risks first. Card networks have taken enforcement action against that misrepresentation, and the shop carries the fallout.
What still gets done by hand?
More than the word integration suggests. An integration moves specific fields between two systems in a specific direction on a specific schedule. Here that is mostly sales recorded against tagged packages, plus inventory adjustments the software knows how to describe. That is a narrow job, done well.
Everything requiring a judgment call stays human. Receiving a transfer and checking it against the manifest. Splitting a package. Logging waste. Correcting a mistake somebody made yesterday. Deciding whether the shelf or the system is right when they disagree. None of that is a failure of the software, it is what the software was never going to decide for you.
So when a vendor says they integrate, ask the unglamorous questions. Which fields move, in which direction, how often, who sees the error when a sync fails, and whether a mismatch is fixed on a screen your manager can use at closing or through a support ticket that waits until morning. Ask it with your state selected.
How do you change platforms without losing the trail?
By reconciling before you migrate, not after. Your item library, supplier list and much of your operating data can move to a new platform. Your history inside the state system does not move, because it belongs to the state rather than to your software. Carrying a discrepancy into a new system only relocates a problem you will then have to explain twice.
Keep read access to the old platform for a stretch after go live rather than switching it off the day the new one starts. When a question comes up about a transaction from before the change, you want to answer it from the record instead of from memory.
Time it around your reporting rather than your calendar. Not mid reporting period, not the week of a full stock count, not during your busiest stretch. A quiet weekday costs almost nothing. A convenient-looking date at month end costs you the reconciliation, and that is the one thing this whole system exists to protect.
Do hemp and CBD sellers need this at all?
Generally not. Hemp has been federally legal since the 2018 Farm Bill, which defines it as cannabis containing no more than 0.3% delta-9 THC on a dry weight basis, and hemp products are not tracked in METRC the way licensed cannabis is. Your obligations there are testing, labelling and the rules your own state layers on top, which vary and are worth checking rather than assuming.
What hemp and CBD sellers do need is a processor that will keep the account open. That path is real and open, and it starts at hemp merchant accounts or CBD merchant accounts. If you sell online as well, CBD payment gateways covers the checkout side. And if you are not sure which side of the line your products fall on, tell us what you carry and we will give you a straight read.
What do owners ask about state reporting?
Is traceability reporting optional if my volume is small?
No. In states that require it, it is a condition of the licence rather than a feature you opt into, and it applies whatever your volume is. What differs by state is the tag format, the transfer paperwork and how often you report. Confirm those with your own regulator rather than with a vendor in another state.
Does an integration mean I stop entering anything by hand?
It does not. An integration moves specific fields between your register and the state system, mostly sales against tagged packages. Receiving a transfer, splitting a package, logging waste and correcting a mistake usually still involve a person making a decision. Any vendor implying full automation has not worked a counter.
What happens at the counter when the state system is unreachable?
That is the question to press a vendor on, because it happens and your line does not stop. Ask which functions keep working, where the queued records go, who is alerted, and how the backlog gets submitted once the connection returns. Then ask to see the screen where you would check that yourself at closing.
Who is responsible if my numbers and the state numbers disagree?
You are. The licence is yours, so a mismatch is your problem even when the software caused it. That is the practical reason to reconcile daily and to have one named person reading the sync log. A one-day gap is a memory you can explain. A month-long gap becomes an investigation.
If I switch POS platforms, does my reporting history move with me?
Your item library and much of your operating data can move. Your history inside the state system stays where it is, because it belongs to the state rather than to your software. Reconcile before you migrate, keep read access to the old platform for a while, and do not switch mid reporting period.
Do hemp and CBD retailers report into a traceability system?
Generally no. Hemp has been federally legal since the 2018 Farm Bill, which defines it as cannabis containing no more than 0.3% delta-9 THC on a dry weight basis, and hemp products are not tracked the way licensed cannabis is. Your obligations there are testing, labelling and whatever your own state layers on top.
Get a straight read on your setup
Tell us how your shop is licensed and what you carry, and a Rooted Payments specialist explains what your POS has to report and what your payments can realistically look like.