1. 17% state tax plus local
What OR requires: Oregon imposes a 17% state retail tax on recreational cannabis, administered by the Department of Revenue, and local governments may add up to 3% for a combined 17 to 20%. Retailers collect at the point of sale and remit to the state, which also administers the local portion, and roughly 109 jurisdictions levy the optional 3%.
What SellStack does natively: SellStack's native tax engine handles the 17% state tax and the applicable local add-on out of the box, configured once per location and applied automatically at the point of sale.
What this means for your operations: You stop tracking which jurisdictions levy the local add-on by hand, and a rate change is a configuration update, not a spreadsheet project.
Request a demo for Oregon operations →
2. Metrc reconciliation
What OR requires: Every OLCC licensee must operate in Metrc, which Oregon runs as its Cannabis Tracking System. Plants and packages carry unique RFID tags, all movement between licensed facilities requires a Metrc transfer manifest, and lab results and recalls run through the system. A 2026 bulletin changed how secondary and composite lab-test results are entered, effective September 1, 2026.
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 Metrc. Records reconcile against the ledger you already run on.
What this means for your operations: When Oregon changes how the tracking system works, your inventory logic does not have to be rebuilt. You adapt the reconciliation, not your whole operation.
Request a demo for Oregon operations →
3. Transfers in a capped market
What OR requires: All transfers between licensed facilities must be recorded in Metrc with an electronic manifest before transport. HB 4121 replaced blanket moratoria with permanent per-capita license caps, so OLCC cannot accept new applications in a category until active licenses fall below the cap. Growth effectively happens by acquiring existing licenses, and the wholesale category is reopening under the caps.
What SellStack does natively: SellStack runs facility-to-facility transfers and their manifests from one ledger, and because multi-entity operations live in one system of record, folding an acquired license or facility into your operation is a configuration change rather than a migration project.
What this means for your operations: Transfers stay manifest-ready, and when you grow by acquisition, the new facility joins one ledger instead of becoming another system to reconcile.
Request a demo for Oregon operations →
4. Delivery within the lines
What OR requires: OLCC-licensed retailers that register for delivery may deliver only within the same city or unincorporated county, or into an adjacent jurisdiction that has opted in. Drivers must be tracking-system-registered employees on the manifest, no more than 10,000 dollars of retail value may be in a vehicle at once, product must ride in a secured lock-box, the vehicle must be GPS-equipped, and no more than one delivery per address per day is allowed.
What SellStack does natively: SellStack owns the delivery order and integrates with your delivery platform as the operations layer; SmartRoutes is already fully supported, so the order carries into vehicle, driver, and routing logic, with the service-area geography and the vehicle-value cap enforced on the delivery side.
What this means for your operations: You get one order-to-doorstep flow instead of re-keying orders into a separate dispatch tool, and the geography and value limits are enforced where delivery actually happens.
Request a demo for Oregon operations →
5. Lot-aware traceability
What OR requires: Both Metrc on the state side and federal GMP, which has been live for Oregon 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 Oregon operations →
6. ERP integration
What OR requires: A Oregon 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 Oregon operations →
7. Schedule III GMP readiness
What OR requires: Medical cannabis moved to Schedule III federally, effective April 28, 2026, and it is in effect now for Oregon 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 Oregon medical operations build GMP-grade records now, on a clock that already started, without a parallel compliance system bolted on beside your commerce stack.