1. The 15% gross receipts tax, raised and layered
What MN requires: Minnesota's cannabis gross receipts tax is 15%, raised from the original 10% for sales after June 30, 2025. That sits on top of the 6.875% state sales tax plus any local sales tax, so most adult-use product carries an effective rate in the rough range of 22% to 30%. Registry patients buying from a business with a medical retail endorsement are exempt from both taxes, while the tribal-program and visiting patients are not. The rate moved once already, early in the market's life, so the tax layer is something that changes rather than something you set once.
What SellStack does natively: SellStack's tax engine calculates the 15% gross receipts tax, the 6.875% state sales tax, and local sales tax from one configuration, each applied where it is owed, and the medical exemption applies to registry sales through an endorsed retailer without a parallel setup. When the rate moves again, it moves in configuration, not in your inventory logic.
What this means for your operations: You stop hand-building a multi-layer tax calculation that already changed inside the first year, and the medical exemption is part of the same ledger rather than a separate carve-out you reconcile by hand.
Request a demo for Minnesota operations →
2. Metrc under OCM, unifying to one instance
What MN requires: Minnesota's state track-and-trace system is Metrc, contracted by the Office of Cannabis Management as the sole state regulator, covering both medical and adult-use with serialized plant and package tags. Credentials are issued on license approval and tracking is real time. SF 4401, signed in May 2026, moves the state toward unifying medical and adult-use onto a single Metrc instance, so the track-and-trace surface is itself consolidating as the market matures.
What SellStack does natively: SellStack Cannabis ERP-Commerce ships with native Metrc integration and treats its own ledger as the source of truth, reconciling Metrc from it rather than building inventory logic on top of it. Every tag, transfer, and sale ties back to the lot record you already run on, so a move to a single Metrc instance is an integration-side change, not a rebuild of how you track inventory.
What this means for your operations: Metrc reconciliation is a byproduct of operating, not a separate end-of-day exercise, and as OCM unifies the track-and-trace surface the record the state sees already matches the record you run your business on.
Request a demo for Minnesota operations →
3. Many license tiers, one ledger
What MN requires: Minnesota's framework runs a wide range of license types. Four are capped and awarded by lottery: cultivator, manufacturer, retailer, and mezzobusiness. Others are uncapped, including microbusiness, wholesaler, transporter, testing, delivery service, and the medical combination business. Microbusinesses and the vertically integrated mezzobusiness can span cultivation, manufacturing, and retail inside one license, and SF 4401 now lets hemp operators concurrently hold adult-use licenses, so a single operator often runs several tiers and channels at once.
What SellStack does natively: SellStack runs every license tier you hold from one lot-aware ledger. A lot's genealogy, its tax treatment, and its channel are the same record, so cultivation, manufacturing, wholesale, and retail reconcile to each other instead of living in separate systems per license.
What this means for your operations: You run a microbusiness or mezzobusiness that spans the whole chain without maintaining a separate inventory per function, and as you add a license tier the new channel joins the same ledger rather than becoming another system to reconcile.
Request a demo for Minnesota operations →
4. Delivery, by endorsement or license
What MN requires: Minnesota handles delivery two ways. A retailer with a delivery endorsement may deliver directly or through a licensed partner, and there is a standalone Cannabis Delivery Service license, which is uncapped and was not issued in the first cycle. Drivers must be 21 or older, and a vehicle may carry no more than $5,000 of regulated cannabis product per route. The order, the manifest, and the lot record all have to stay tied together regardless of which path the delivery runs through.
What SellStack does natively: SellStack owns the delivery order and carries it into the delivery workflow with the $5,000 per-route cap enforced on the delivery side. The order, the manifest, and the lot record are one flow, whether you deliver under a retailer endorsement or hand off to a licensed delivery service, not a re-keyed hand-off into a separate dispatch tool.
What this means for your operations: Your delivery runs inside the same system as the rest of the operation, and the per-route cap is enforced where delivery actually happens, not tracked on a spreadsheet, no matter which delivery path a route uses.
Request a demo for Minnesota operations →
5. Lot-aware traceability
What MN requires: Both Metrc on the state side and federal GMP, which has been live for Minnesota medical operations since April 28, 2026, require lot-level records throughout the chain. A lot has to stay identifiable from receipt, through processing, to the point of sale, and the records have to hold up to a traceback.
What SellStack does natively: SellStack delivers lot-aware commerce from receipt through sale. Every inventory record, sales record, and test result carries the lot identifier, and the lot genealogy is the ledger itself, not something reconstructed from reports later.
What this means for your operations: The lot story is the audit story. Metrc reconciliation and the records half of GMP both come out as byproducts of operating normally, rather than as separate projects.
Request a demo for Minnesota operations →
6. ERP integration
What MN requires: A Minnesota operation has to keep financials, inventory, and commerce in agreement, and reconcile all of it to Metrc. Operators running a separate ERP and a separate commerce system carry a standing reconciliation burden between the two.
What SellStack does natively: SellStack Cannabis ERP-Commerce backs onto your ERP or warehouse platform as the system of record, and Microsoft Dynamics 365 Cannabis on Business Central is already fully supported. Financials, inventory, and commerce run from the same ledger, so the lot record, the financial record, and the inventory movement are the same record.
No ERP in place yet: You do not need an ERP to run SellStack. SellStack Cannabis E-Commerce Edition operates standalone, with no ERP underneath it, so an operation can stand up a GMP-ready sales model now and work out which ERP or warehouse platform to connect later, or whether to add one at all. Even standalone, it is lab-results compliant out of the box: because it ingests lab data, a no-ERP operation still meets Metrc, BioTrack, and other state lab-results requirements from day one. The lot-aware ledger, the commerce layer, and the records are the same with or without an ERP, so nothing has to be rebuilt when one is connected down the road. That makes it a fit for operations mid-transition, and for startups that need to be selling on a compliant, GMP-ready footing before the deeper infrastructure is in place.
What this means for your operations: There is no reconciliation project between the ERP and the commerce layer. One ledger means your books, your inventory, and your storefront never drift apart.
Request a demo for Minnesota operations →
7. Schedule III GMP readiness
What MN requires: Medical cannabis moved to Schedule III federally, effective April 28, 2026, and it is in effect now for Minnesota medical operations. Adult-use rescheduling is still pending; the DEA proceeding was stayed September 29, 2026 awaiting a GAO report, with a decision expected late 2026 or early 2027. For medical operators, GMP-grade records start to matter.
What SellStack does natively: The records half of GMP, immutable and lot-level, is built into how SellStack operates, so the audit trail is a byproduct of running on one lot-level ledger rather than a separate project.
What this means for your operations: Your Minnesota medical operations build GMP-grade records now, on a clock that already started, without a parallel compliance system bolted on beside your commerce stack.