POS Setup for 7-OH Retailers: Locked SKUs, Lot Tracking, Limits
A POS system for a 7-OH store should lock SKUs instantly, track lots for recalls and enforce per-sale caps. Here's how to set up and test each one.
Photo: Pixabay
On this page 7 sections
- POS System Features a 7-OH Store Can't Skip
- Locking 7-OH SKUs Instantly When a Local Ban Passes
- Lot Tracking in Your POS for 7-OH Recalls
- Restricted Product POS Controls: Quantity and Mg-Per-Sale Limits
- Keeping 7-OH Sales on a Separate Merchant Account
- POS Providers That Prohibit 7-OH
- Run This Test Before You Sign
Key takeaways
- Put every 7-OH item in one dedicated category so a single action takes all of it off sale, and lock down open-price keys that bypass the lock.
- Record the lot at receiving even if your POS can't capture it at checkout. Received dates and sell-through still narrow a recall to a date range.
- Item-count limits don't enforce milligram caps across mixed products. Store mg per unit as an item attribute or the cap exists on paper only.
- Before buying hardware, get written confirmation that the processor behind the POS has approved 7-OH and that the terminals can move with you if it drops you.
A POS system for a 7-OH store has to stop a sale the moment the law stops it. When a local ban takes effect, one action should pull every 7-OH product off sale at every register. Each unit sold should trace back to a lot, so a recall has an answer. And the register should refuse any basket that goes over a per-sale cap. The terminal on the counter matters less than the software behind it and the merchant account it runs on. Settle those two before you buy hardware, because state and local governments are changing 7-OH rules on short notice, and a register that can't keep up turns a rule change into a compliance problem.
7-OH law differs from one jurisdiction to the next, and its federal status has been in motion. What follows is operational guidance for the counter and the back office, not legal advice. Confirm the rules for each location with a qualified attorney.
POS System Features a 7-OH Store Can't Skip
7-OH sells from behind the counter in smoke shops and convenience stores. Tickets are small, and regulars come back weekly or more. Tablets and shots from a handful of brands share the shelf, and their potencies differ widely. That pattern sets the requirements: speed at the register, precision in the back office.
| Feature | Why a 7-OH shop needs it | What to test in a demo |
|---|---|---|
| Category-level lockout | A ban takes effect on a set date, and every location has to stop selling at once | Disable a whole category from the back office, then scan a locked item at a register |
| Open-price key controls | A "misc" key lets a cashier ring a locked product anyway | Restrict open-price items to manager PINs, or turn them off |
| Lot or batch capture | Recalls and lab questions are asked by lot, not by brand | Receive stock by lot, sell it, run a report of units sold per lot |
| Item attributes (mg per unit) | Potency caps written in milligrams can't be enforced with item counts | Add a custom field and check whether the cap logic reads it |
| Per-transaction limits | Local rules that cap the amount per sale need a hard stop | Try to ring one unit over the limit |
| Role permissions | Overrides need an audit trail | Check who can override and whether the override is logged |
| Data export | A processor or a new provider will ask for your records | Export sales by SKU and lot to CSV |
Take this table with you when you compare POS systems built for counter retail, and ask the vendor to run each test live instead of describing it.
Locking 7-OH SKUs Instantly When a Local Ban Passes
A county can vote on a ban one night and enforce it days later. Our coverage of Franklin County, Georgia's proposed kratom and 7-OH ban shows how fast that path from discussion to vote runs. On the effective date, every register in the affected area has to refuse the sale, including the one your newest part-timer runs on Saturday.
Good 7-OH SKU setup starts at item creation. Give every 7-OH product its own category, separate from kratom leaf, because a ban that names one does not automatically cover the other. Processors draw the same line; see why 7-OH and kratom leaf are underwritten differently. Tag product form as well, so a rule aimed at shots alone doesn't force you to pull your tablets. With that structure, a lockout is one action on one category. Without it, you're scrolling through a few hundred items at 11 p.m., hoping you didn't miss a flavor variant.
Then close the gaps. Use the manufacturer's barcode as the item code so a scan always lands on the right record. Turn off the open-price or "miscellaneous" button, or put it behind a manager PIN, because a cashier who hits "misc $24.99" has just sold a locked product with no record of what it was. Set locked items to display a message at scan, such as "Not for sale at this location," so staff aren't guessing. If you run more than one store and the ban covers only some of them, confirm that the POS locks a category per location rather than chain-wide.
Run a drill once a quarter. Lock the category, try to sell, then unlock it. Ten minutes of testing beats finding out during an inspection that the lock never synced to the backup register.
Locking the SKUs is half of a ban response. Prepaid orders and stock on hand still need decisions, and our guide on handling refunds and pulled stock when a 7-OH ban hits walks through them. Don't rename or recode the product to keep selling it. That is a legal problem and a card-network problem at once, as explained in the miscoding risk of ringing 7-OH as herbal supplements.
Lot Tracking in Your POS for 7-OH Recalls
Lot tracking tells you which units from which batch went out the door and on what dates. You need that record when a manufacturer recalls a batch, and you need it when your processor's underwriting team asks for the lab results behind what's on your shelf. Underwriters read certificates of analysis closely, as we cover in what underwriters check on a 7-OH COA. A COA only helps you if you can tie it to the lot you actually sold.
The catch is that the barcode on a 7-OH package identifies the product, not the lot. Two cartons of the same tablet from different batches scan identically. POS systems deal with this in one of three ways:
- Native lot tracking. You receive stock by lot, and the register either prompts the cashier to pick the lot or assumes first-in, first-out. It's the cleanest option, and you'll find it more in pharmacy and grocery software than in general retail POS.
- One item variant per lot. The product is the parent item and each lot is a variant. It works, but cashiers have to choose the variant, and under pressure they'll pick the wrong one unless the shelf is labeled clearly.
- Receiving records only. The POS tracks the product, and you log each lot number and received date at intake alongside its COA. You won't know which customer got which lot, but you can bracket it by date.
Even the third method is far better than nothing. Here is 7-OH recall tracking with receiving records alone. Say you received Lot A on March 3 and Lot B on March 24, and you sell first-in, first-out. Your sales report shows Lot A's quantity sold through by March 26. A recall of Lot A then covers sales from March 3 through about March 26, and you can keep selling the remaining Lot B units knowing they aren't affected. (These dates are illustrative.)
Whatever method you use, file the COA for every lot against the lot number printed on the package, and keep it as long as you keep sales records. Store the receiving log where your processor or attorney can reach it without you digging through a back-room filing cabinet.
Restricted Product POS Controls: Quantity and Mg-Per-Sale Limits
Where a state or local rule caps how much 7-OH one customer buys per transaction, the register has to enforce it, not the cashier's memory. Unit limits per item are a standard POS feature. Milligram limits summed across a mixed basket are not, and caps written in milligrams are exactly where item limits fail.
Here's a worked example with illustrative numbers. It isn't any jurisdiction's actual rule.
Assumptions: A hypothetical rule caps 7-OH at 200 mg per transaction. Product A is a 3-tablet pack at 15 mg per tablet (45 mg per pack). Product B is a 2-tablet pack at 30 mg per tablet (60 mg per pack).
A customer buys 3 packs of A (135 mg) and 1 pack of B (60 mg), for 195 mg total. That's under the cap. Add a fourth pack of A and the total is 240 mg, which is 40 mg over.
An item-count limit misses this. A limit of "4 per item" allows four packs of A plus four packs of B, which comes to 420 mg.
To enforce a milligram cap, each item needs its total milligram content stored as an attribute, and the POS needs logic that sums that attribute across the basket. Ask the vendor whether it does this natively or through an add-on. If the answer is neither, build a fallback: a laminated chart at the register listing mg per package for every SKU, plus a shift-lead sign-off on any basket near the limit. That approach is slower and easier to get wrong, which is the argument for paying for software that does the math.
Two related controls belong in the same setup. Where age verification is required, an ID scanner integrated with the POS logs each check instead of leaving it to a glance at a license. And staff training has to cover what not to do: never split one customer's purchase into two transactions to get under a cap. That defeats the rule the cap exists to enforce, and splitting a single sale into several card transactions also breaks card network rules and your merchant agreement.
Keeping 7-OH Sales on a Separate Merchant Account
A convenience store that sells 7-OH next to fuel and snacks has to decide whether 7-OH runs on its own merchant account. The answer depends on what each processor has approved, and the only legitimate version of this setup is one where every processor knows exactly what you sell.
Start with the fixed rule. If your current processor hasn't approved 7-OH in writing, you can't ring 7-OH on that account. Not under another product name, and not "just until the new account opens." That is transaction laundering, and it leads to termination and a MATCH listing. If it has already happened, start with our guide to getting approved for a 7-OH merchant account and tell the new underwriter the truth.
From there, you have two honest options:
- One account for everything. A high-risk merchant account underwrites your whole store, 7-OH included. You run one terminal and get one statement, and the register never sends a sale to the wrong account. Pricing and reserve terms will reflect the riskiest thing you sell, which our article on 7-OH processing rates, reserves and holds explains.
- Two disclosed accounts. A low-risk account handles general merchandise and a separately approved account handles 7-OH. Each processor must know about the other account and the products on it, and you want that acknowledgment in writing. In practice this means a dedicated terminal or lane for 7-OH, because few POS systems route individual items to different merchant IDs inside one basket.
Most single-location shops are better off with the first option. The second fits a large convenience operation where 7-OH is a small share of sales, and only after both underwriters sign off. Ask before you build it.
POS Providers That Prohibit 7-OH
Before you buy hardware or sign a software contract, read the provider's acceptable use or prohibited business policy. Many mainstream POS platforms run on a payment facilitator model: the POS company is also your processor, and you're a sub-merchant under its master account. Those platforms write their own restricted-product lists. Check them for botanical extracts and anything tied to controlled substances before you assume 7-OH is allowed. Our article on whether the major payment facilitator platforms allow 7-OH covers what happens when sellers try anyway. Held funds and a closed account cost far more than the hardware.
A POS that runs on a dedicated merchant account works differently. The underwriting decision belongs to the processor and its sponsor bank, and that approval should name 7-OH. Get answers to these before you commit:
- Has the processor approved 7-OH for my business, in writing?
- If the processor ends the relationship, can my terminals be reprogrammed for a new processor?
- Will I get my item, sales and lot data in a usable export if I leave?
- What happens to my reserve if the account is terminated?
The second question matters more than it looks. A terminal locked to the processor that sold it becomes dead hardware the week that processor shuts you down, which is the same week you're scrambling for a new account. Our guide to reserve and termination terms in 7-OH processor contracts covers the contract side of that risk.
Run This Test Before You Sign
Ask any POS vendor for a 20-minute live demo and have them do six things while you watch. Create a 7-OH category and lock it. Scan a locked item. Try the open-price key from a cashier login. Receive two lots of the same product and sell from one. Ring a basket that exceeds a milligram cap. Export the results to a spreadsheet. A system that fails two of these will fail you the day a county rule takes effect.
MannyPay sells smart terminals from brands including Clover and Valor and offers high-risk merchant accounts. See how we approach the category on our 7-OH payment processing page. To talk through hardware and a high-risk merchant account for your store, request a free quote, and a MannyPay specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
