CBD / Hemp

Encoding State Hemp Caps Like Virginia 2 mg and Minnesota 5 mg in Cart Rules

Federal hemp deadlines do not erase stricter state milligram caps. Virginia's 2 mg per-package rule and Minnesota's 5 mg per-serving LPHE limits show why zip-to-SKU cart matrices need versioning.

E-commerce 4 Internet Marketers Editorial

Illustration of two developers in a bright late-September office at midday, mapping state hemp milligram caps on a whiteboard beside open laptops.

By E-commerce 4 Internet Marketers Editorial

Virginia now caps retail industrial hemp extract at two milligrams of total tetrahydrocannabinol (THC) per package, and Minnesota still structures lower-potency hemp edibles (LPHE) around five milligrams of delta-9 THC per non-beverage serving. National stores that only keep binary ship-or-ban ZIP lists will mis-sell into both markets.

This explainer walks through those two statutes, why federal hemp deadline headlines do not rewrite the numbers, and how cart systems can store destination milligram rules as versioned product attributes.

Virginia hard-codes 2 mg per package

Virginia Code § 3.2-5145.4, effective August 15, 2026, requires that an industrial hemp extract offered for retail sale contain a total THC concentration of no greater than 0.3 percent and contain no more than two milligrams of total THC per package. The earlier alternative that allowed higher milligram packages when cannabidiol was at least 25 times the total THC is gone from the August 15 text.

That change arrived through House Bill 30, signed June 29, 2026. On August 14, 2026, U.S. District Judge Robert S. Ballou denied a temporary restraining order and preliminary injunction in Northern Virginia Hemp & Agriculture, LLC v. Spanberger (W.D. Va., No. 7:26-cv-00615), so the two-milligram package ceiling took effect on schedule the next day. For a cart, the decisive field against a Virginia ship-to address is total THC milligrams on the retail package, not only percent THC printed on a certificate of analysis (COA).

Minnesota splits serving, beverage, and package caps

Minnesota Statutes § 342.01, subdivision 50, defines an LPHE in part by those serving and container limits. For products not intended to be consumed as a beverage, servings may contain no more than five milligrams of delta-9 THC. A beverage in a single container may contain no more than ten milligrams of delta-9 THC.

Section 342.62 then caps packaging. A multi-serving non-beverage LPHE package must not contain more than 50 milligrams of delta-9 THC. A single beverage container must not contain more than ten milligrams of delta-9 THC. Those figures are not interchangeable with Virginia’s per-package total THC rule. A SKU that clears Minnesota at five milligrams per serving and 50 milligrams per package can still fail Virginia’s two-milligram package ceiling.

Cart logic that stores one generic “THC_mg” field, without serving versus package, isomer basis, and beverage flags, will over-block one state and under-block the other.

Federal checkpoints leave state caps alone

Public Law 119-103 and related industry legal analyses describe November 12 and December 11, 2026 federal checkpoints around the hemp definition rewrite, including a 0.4 milligram total THC per-container threshold for many products once the broader rewrite applies. Those dates matter for interstate hemp status and for how processors price residual risk. They do not raise Virginia’s two-milligram package cap or Minnesota’s five-milligram serving cap. Destination law can be stricter than the federal definition a brand is watching on the national news cycle.

The U.S. Food and Drug Administration’s cannabis and cannabis-derived products pages still matter for claims and federal food or drug framing. State milligram caps for retail hemp nonetheless have to sit in the cart as first-class constraints, not footnotes.

Encoding the caps before payment authorize

Build the matrix around attributes counsel will defend, then evaluate it twice in checkout.

  • Store verified SKU fields: total THC milligrams per package, delta-9 THC milligrams per serving, beverage flag, COA date, and any isomer notes your counsel requires.
  • Keep 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.
  • Run the rules when the customer enters a ship-to address and again before payment authorize, not only when shipping rates are quoted.
  • Prefer a hard block with a plain-language message over a silent SKU drop that creates a support ticket later.
  • Diff and retest the matrix whenever a state amends definitions. Virginia’s August 15, 2026 change is a live example of why rule-version IDs matter.

Hold COAs, label photos, and rule-version IDs with the same boarding file specialty processors request for CBD and hemp acquiring. After Virginia’s August 15 package ceiling took effect, shops refreshing those files for milligram-capped SKUs may also open Organic Payment Gateways for CBD-friendly acquiring options while they match questionnaire answers to destination attributes. This explainer does not endorse any processor.

Other states keep writing their own intoxicating-hemp calendars. Illinois, Texas, and several peers appear in operator matrices with bans or potency rules that move on state timelines. Treat each jurisdiction as its own versioned row. Do not collapse them into a single regional bucket.

Why milligram fields beat ZIP flags

Virginia’s two-milligram per-package industrial hemp extract rule and Minnesota’s five-milligram per-serving LPHE structure make the same operational point for national catalogs: destination milligram logic has to travel with the SKU. Federal hemp deadline headlines do not override those state caps. Version the attributes, block before authorize, and keep the rule IDs underwriters and regulators will ask for later.

Sources