What the PACT Act asks of a distributor
The federal Prevent All Cigarette Trafficking (PACT) Act governs how covered tobacco products move in interstate commerce, and its scope was extended in recent years to reach electronic nicotine delivery systems. That extension is why a lot of vape and e-liquid distributors found themselves inside a statute they had never had reason to read.
For an operator, the obligations come in four buckets:
- Registration — with the federal authority, and with the tobacco tax administrator of each state you ship into.
- Monthly state reporting — a recurring report to each state covering your shipments into it: who received them, where, what was in the box and how much.
- Delivery-sale rules — extra requirements when the recipient is a consumer rather than a business, covering age verification, package labeling and how shipments may be carried.
- Recordkeeping — the ability to produce the underlying records after the fact, on request.
Two things are worth internalising before you design any process around that list. The obligations vary by state and they change. And the questions get asked long after the shipment left, when the only thing left is your record of it.
Filing dates, prescribed formats, and which product categories a given state treats as covered all move, and they differ between states. Build so the underlying data is complete, attributable and provable; treat the exact deadline, format and channel as a per-state setting you confirm with counsel and with the state, and re-confirm.
Why this is an order-entry problem, not an accounting problem
Almost everything written about PACT Act compliance sits at one of two extremes. It either recites the statute — accurate, unusable — or it sells you a tax engine that ingests your data and produces a filing.
The second is closer to useful and still misses the real failure. Whatever you feed a filing tool has to come out of your systems first, and in most distribution businesses that means a person assembles it by hand each month: shipment lines from one export, addresses from another, product descriptions from the catalog, case quantities converted into whatever unit the state counts, invoice numbers matched back by eye. Every one of those joins is a judgement call, made a month late, by someone who was not in the room when the order was taken. That is where the errors come from, and no downstream tool can fix it, because the information was never recorded in the first place.
The alternative is boring and it works. Capture the fields at the moment of the order, on the same screen where the order is taken, in the same database the warehouse picks from and accounting bills from. Then the monthly report is a query over records that were already correct when they were created, and month end changes from rebuilding to reviewing. That is the practical argument for running sales, ordering, warehouse and accounting on one platform instead of three that must be reconciled — the case we make on the Zekal One platform page.
The field-capture checklist: what your order screen has to record
This is not a rendering of any state's report layout — those differ, and you should take the current one from each state. It is the set of things that, if they are missing from the order record, force a human to reconstruct them later.
| What to capture | Where it belongs | Why the filing needs it |
|---|---|---|
| Ship-to name and full delivery address | On the order, from the account's delivery location | Reporting is keyed to where goods arrived. A bill-to address files the shipment in the wrong state. |
| Recipient type — business, retailer, consumer delivery sale | On the account, defaulted onto the order | Delivery sales carry a different set of duties. Decide it once, at the account. |
| Brand and product identity as the state names it | On the item, alongside your internal SKU | Reports want brand-level detail. Your warehouse shorthand is not that. |
| Quantity in the unit the state counts | A conversion stored on the item, applied at entry | Sticks, ounces, millilitres, containers — so nobody re-derives it in a spreadsheet. |
| Covered-product flag | On the item record | Decides whether a line belongs in the filing at all — settled once, by whoever set the item up. |
| Tax status — stamped, unstamped, tax-paid jurisdiction | On the inventory ledger, at stock level | Reporting and your excise position only agree if they read the same ledger. |
| Lot or batch | Recorded at pick and pack, tied to the order line | Traceability in both directions, and the route to that lot's COA. |
| Ship date, carrier and tracking | On the shipment, from the warehouse | Places the movement in a reporting period and evidences that it happened. |
| Order and invoice reference | One thread from order through invoice | Walk from a reported line back to the document behind it, in one step. |
| Who entered it, and any approval on it | On the order, automatically | When counsel or a state asks why this shipped, the answer is on the record. |
Ship-to versus bill-to. A chain buys from head office and receives at four locations in three states. If the order carries only the billing address, two of those states are silently short and the third is overstated — and you will not catch it from your own data, because your own data is what is wrong. Capture the delivery location on the shipment every time, even when it looks identical to the billing address.
Zekal One captures PACT Act fields at order entry for exactly this reason. Nothing above is exotic; it is ordinary order data that most systems never asked for, because the people who designed them were not filing anything.
Stamped vs unstamped inventory, and excise on the same ledger
Here is the version of this problem that costs real money. The same physical product sits in your building in two tax states — stamped and unstamped, or tax-paid for one jurisdiction and not another. In most systems that is one stock number, and the distinction lives on a shelf tag or in a spreadsheet the tax person keeps privately. The arrangement survives until a picker takes the closest carton; after that, physical stock, excise position and reporting quietly diverge, and nobody notices until a count forces the reconciliation.
Zekal One tracks excise and stamped versus unstamped status in the same ledger as the stock itself, not beside it:
- Tax status is an attribute of the stock — a pick moves the tax position the instant it moves the unit
- Locations and bins separate the two — the scanner enforces what a shelf tag only suggested
- Cycle counts cover both — drift is corrected continuously instead of discovered annually
- Excise and stock reconcile by construction — there is only one set of numbers
Lots, COAs and the traceability half
Reporting gets the attention, but recordkeeping is the obligation that arrives as a phone call: a customer, a state, or your own counsel asks what was in a specific lot on an invoice from four months ago, and who else received it.
That question has an answer only if manufacturing, warehouse and sales write to the same database. Zekal One records recipes and bills of materials, production runs that consume inputs and yield finished goods, and lot and batch traceability in both directions — from a finished unit back to its inputs, and forward to every customer who received it. Certificates of analysis attach to the lot and stay retrievable, so producing one is a lookup rather than a search of somebody's email. If you also move hemp-derived or botanical lines, the same discipline carries over unchanged — see kratom and hemp-derived distribution.
A monthly close checklist you can hand to one person
If the fields above are captured at entry, the close is a review rather than a reconstruction — deliberately something one competent person can own.
- 1Close the period on shipments — agree the cut-off and stop back-dating movements into it
- 2Clear shipped-not-invoiced and invoiced-not-shipped — anything in either bucket reports inconsistently
- 3Review exceptions, not everything — missing tracking, a covered item with no unit conversion, a shipment with no lot, a blank recipient type
- 4Verify ship-to addresses on new accounts — first deliveries are where wrong-state errors are born
- 5Reconcile stamped and unstamped movement against the stock ledger for the period
- 6Confirm registrations are current for every state you shipped into, including any state you reached for the first time
- 7Generate the per-state data from the order records, and read it once, by state, before it goes anywhere
- 8File through each state's own channel, in that state's current format and on its current schedule
- 9Archive exactly what you filed, plus the confirmation — so next year's question is answered from the file, not from a rerun
A rep opens an account in a state you have never shipped into. The order is legitimate, the credit is fine, the box goes out — and you have taken on a state-level obligation nobody noticed. That is exactly the class of exception that belongs in front of a person before it ships. Approvals is where new-account and out-of-policy orders route by role, with the decision recorded permanently on the order.
It does not perform age verification of any kind. It does not automatically block a sale or shipment into a jurisdiction where a product is restricted — deciding what may ship where is your compliance call, and the platform's job is to make the record of what shipped complete and attributable. It is not a filing service or a tax engine, and we publish no named integrations with one. What it does is own the order, so the data behind the filing was captured correctly when it was created rather than inferred from exports weeks later.
Frequently asked questions
What does the PACT Act require of a distributor, in plain terms?
In general shape: register federally and with the tobacco tax administrator of each state you ship into; report shipments into each state on a recurring monthly cycle; follow additional rules when delivering to a consumer rather than a business; and keep records that evidence all of it. The specifics — format, timing, and which categories a state treats as covered — vary by state and change, so confirm them with counsel and with the state.
How do I file the monthly state reports?
Through each state's own channel, in that state's current format. There is no single national submission, which is why the sane approach is to keep one clean set of shipment records and produce each state's view from it, rather than running a separate process per state. Take the current format and schedule from each state directly instead of carrying over last year's assumptions.
Does Zekal One file the reports for us?
No — and be sceptical of anyone who says otherwise without naming the states. What Zekal One does is capture the PACT Act fields at order entry, so the filing assembles from data recorded at the time instead of being reconstructed from exports. Submission still happens through each state's channel, by a person who owns it.
Does the platform verify a customer's age?
No. Age verification is not something Zekal One does today, and we will not imply otherwise — where delivery-sale rules require it, that sits with your delivery-sale process and carrier arrangements. What the platform contributes is the surrounding record: the account, the recipient type, the order, who took it, what shipped, when and to where.
Will it stop an order going to a state where the product is not allowed?
No. The platform does not enforce state-by-state product legality, and software that claimed to would be making a legal determination on your behalf that changes faster than software does. The practical control is procedural: route new accounts and out-of-policy orders to a person through Approvals, where the decision is recorded on the order and nothing ships until it clears.
How is stamped versus unstamped inventory tracked?
As part of the same ledger as the stock, not in a parallel spreadsheet. Excise and stamped/unstamped status are attributes of the inventory itself, so a receipt, a pick or a count moves the tax position at the same moment it moves the units — which keeps stock and excise reconciled without a monthly exercise.
This guide describes the general shape of federal and state obligations as they affect distribution operations, and is written to be useful operationally rather than relied on legally. It deliberately states no deadlines, form numbers, penalties or the status of any product in any particular state, because those vary by jurisdiction and change. Verify your obligations with qualified counsel and with the relevant federal and state authorities before acting.
Written by the team at Bitomatic Software Solutions Ltd, from building and running Zekal One inside a working distribution operation.