1. Federal registration, on top of state rules
What FL requires: Marijuana covered by a state medical licence moved to Schedule III federally on April 28, 2026. On October 30, DEA issued its first registrations, to more than 900 dispensaries in seven medical-only states including Florida, and Florida manufacturer and distributor applications are still listed as pending. Registrants keep federal records under 21 CFR Part 1304, take an initial inventory and then a biennial one, and may deal only with other registrants or timely applicants, with documented due diligence on each trading partner; DEA guidance calls for compliant supply chains by November 29, 2026. State security, labeling, and records are accepted to the extent permitted. Schedule III does not itself impose GMP rules, but GMP-grade records are how operators get ready for federal scrutiny.
What SellStack does natively: The records half of GMP, immutable and lot-level, is built into how SellStack operates. Every order, lot, and counterparty sits on one ledger, so a federal inventory, a state request, and a trading-partner file all draw on the same record rather than a separate compliance project.
What this means for your operations: You meet federal registration and records scrutiny with the record you already run on, not a parallel system assembled after the fact.
Request a demo for Florida operations →
2. Patient supply limits, enforced at checkout
What FL requires: Every order is recorded and dispensed through the Medical Marijuana Use Registry, and each dispensation records the date, time, quantity, form, delivery device, and dispensing employee. Rule 64-4.224, effective August 24, 2026, sets a 70-day supply per 70-day look-back and one 35-day smokable supply, capped at 2.5 ounces, per 35-day look-back, with daily and 70-day limits by route, for example 4,200 mg of THC in edibles and 24,500 mg across non-smokable routes. The amount a patient can receive is the smaller of the remaining limit and what is left on the physician's order. Edibles are capped at 10 mg of THC per serving and 200 mg per package.
What SellStack does natively: SellStack's medical patient channel tracks each patient's eligibility and remaining allowance and applies the configured limits at checkout, with the registry as the authority, so the counter and the delivery van work from the same numbers.
What this means for your operations: Your staff stop doing look-back arithmetic by hand at every sale, and an over-limit order is caught before it is dispensed, not after.
Request a demo for Florida operations →
3. Two systems, one record
What FL requires: The Department of Health maintains a state seed-to-sale system covering planting, harvest, destruction, transport, sale, theft, diversion, and loss. Under Rule 64-4.221, each treatment center runs its own internal tracking system, fully integrated with the state system in real time by API, after training and an approved, validated integration plan. Under Rule 64-4.222, a disconnection longer than two hours must be reported within three hours, dispensing during an outage requires registry checks, outage sales must be filed within 24 hours of restoration, and unexplained inventory adjustments must be justified within 12 hours.
What SellStack does natively: SellStack treats its own lot-aware ledger as the source of truth and reconciles to the state system, so the dispensing record, the state record, and your inventory agree, and an outage or an adjustment leaves a clean trail instead of a reconciliation project.
What this means for your operations: When a connection drops or a count is off, the hours-long deadlines are met from records you already have, not rebuilt from receipts.
Request a demo for Florida operations →
4. Hundreds of doors, one inventory
What FL requires: Florida is vertically integrated: each Medical Marijuana Treatment Center must cultivate, process, transport, and dispense itself, and one person or entity may hold only one licence. There is no cap in current statute on dispensing locations; local governments may ban dispensaries but may not cap their number. 789 locations are open statewide, the largest operator running 170. Transfers between treatment centers are prohibited except after a state-certified harvest failure, in bulk, capped, re-tested, and tracked in both centers' systems.
What SellStack does natively: SellStack runs multi-location, multi-channel operations from one ledger, so cultivation, processing, and every dispensing location share one inventory and one product record, and a certified harvest-failure transfer is a documented transaction with its lot record intact.
What this means for your operations: You see stock, movement, and lot history across every storefront from one place, instead of reconciling location by location.
Request a demo for Florida operations →
5. Delivery, around the clock
What FL requires: Treatment centers may deliver 24 hours a day, while in-store dispensing is closed from 9 p.m. to 7 a.m. Each delivery vehicle carries a transport manifest generated from the tracking system and is staffed by two people, and the same patient registry checks and supply limits apply to a delivered order as to one picked up in store.
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 patient's limits already applied.
What this means for your operations: Delivered and in-store orders run on one flow and one set of limits, so overnight delivery does not become a separate, manual operation.
Request a demo for Florida operations →
6. Lot-aware traceability
What FL requires: Both the state seed-to-sale system on the state side and federal GMP, which has been live for Florida 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. the state seed-to-sale system reconciliation and the records half of GMP both come out as byproducts of operating normally, rather than as separate projects.
Request a demo for Florida operations →
7. ERP integration
What FL requires: A Florida operation has to keep financials, inventory, and commerce in agreement, and reconcile all of it to the state seed-to-sale system. 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. The 365 Cannabis integration on Microsoft Dynamics Business Central is deep and native, one of several supported ERPs, not the only option. 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.