By E-commerce 4 Internet Marketers Editorial
National hemp and CBD storefronts that only encode binary “ship / do not ship” flags miss the milligram caps already live in several states. Virginia’s two-milligram per-package ceiling and Minnesota’s five-milligram per-serving lower-potency hemp edible (LPHE) limits are concrete examples. Federal dual deadlines under Public Law 119-103 do not rewrite those state numbers.
This explainer shows how destination-aware cart rules have to version product attributes (per serving, per package, beverage versus non-beverage) rather than only ZIP ban lists.
Virginia’s 2 mg per-package ceiling
Virginia Code § 3.2-5145.4, effective August 15, 2026, requires that an industrial hemp extract offered for retail sale contain a total tetrahydrocannabinol concentration of no greater than 0.3 percent and contain no more than two milligrams of total tetrahydrocannabinol per package. The prior 25:1 cannabidiol-to-THC exception that allowed higher milligram packages is removed in the August 15, 2026 version of the statute.
A Western District of Virginia memorandum opinion in Northern Virginia Hemp & Agriculture, LLC v. Spanberger describes House Bill 30 (signed June 29, 2026) as eliminating that 25:1 ratio and limiting retail hemp extract products to no more than two milligrams of total THC per package beginning August 15, 2026. For cart systems, the practical attribute is total THC milligrams per retail package against a Virginia ship-to address, not only percent THC on a COA.
Minnesota’s 5 mg serving and package structure
Minnesota Statutes § 342.01, subdivision 50, defines a lower-potency hemp edible in part by serving and container caps. For products not intended to be consumed as a beverage, servings may contain no more than five milligrams of delta-9 tetrahydrocannabinol. Beverage products in a single container may contain no more than ten milligrams of delta-9 tetrahydrocannabinol. Related packaging rules in § 342.62 limit multi-serving non-beverage LPHE packages to no more than 50 milligrams of delta-9 tetrahydrocannabinol per package, with a separate ten-milligram container limit for beverages.
Those figures are not interchangeable with Virginia’s per-package total THC rule. A SKU that is legal in Minnesota at five milligrams per serving and fifty milligrams per package can still fail Virginia’s two-milligram per-package ceiling. Cart logic that only stores one “THC_mg” field without distinguishing serving, package, isomer basis, and beverage flags will mis-block or under-block.
Federal dates do not flatten state matrices
Congress and subsequent appropriations timing around the hemp definition rewrite (including Public Law 119-103 timing discussed in industry legal analyses) create November 12 and December 11, 2026 federal checkpoints for certain container and cannabinoid limits. Those federal calendars matter for interstate hemp status and processor appetite. They do not automatically raise Virginia’s two-milligram package cap or Minnesota’s five-milligram serving cap. Destination law can be stricter than the federal hemp definition a brand is watching on the national news cycle.
FDA’s cannabis and cannabis-derived products pages remain relevant for claims and federal food/drug framing, but state milligram caps for retail hemp still have to be encoded as first-class cart constraints.
How to encode milligram caps in cart rules
- Store verified attributes per SKU: total THC mg per package, delta-9 THC mg per serving, beverage flag, COA date, and isomer notes your counsel requires.
- Maintain a versioned destination rules table keyed by state (and locality when needed) with operators such as max_mg_per_package, max_mg_per_serving, and ban_entire_category.
- Evaluate rules at address entry and again before payment authorize, not only at shipping-rate quote.
- Prefer hard blocks with plain-language messages over silent SKU drops that create support tickets.
- Diff and retest the matrix when a state amends definitions (Virginia’s August 15, 2026 change is the template for why versioning matters).
- Keep evidence packs (COAs, labels, rule-version IDs) aligned with what specialty processors ask when reviewing CBD or hemp acquiring. Operators comparing gateway options for compliant hemp catalogs often review contextual resources such as CBD payment gateways alongside counsel-approved matrices. This explainer does not endorse any processor.
Other states continue to diverge on intoxicating hemp. Missouri, Illinois, Texas, and peers appear in many operator matrices for bans or potency rules that change on their own calendars. Treat each as a separate versioned row rather than a single “Midwest” bucket.
Closing
Virginia’s two-milligram per-package industrial hemp extract rule (effective August 15, 2026) and Minnesota’s five-milligram per-serving LPHE structure show why national hemp carts need destination-aware milligram logic, not only ship-or-ban ZIP lists. Federal hemp deadline headlines do not override those state caps. Version the attributes, block before authorize, and keep the rule IDs that underwriters and regulators will ask for later.