Your scan-data week, already formatted
Every tobacco sale recorded with the discounts your manufacturer programme needs, exported as the weekly file. Clean rows, fewer rejections, under your own programme agreement. US stores.
- Transaction-level detail
- Multipack and loyalty discounts on their own lines
- Full Shift and Multi-Store
What is tobacco scan data, and why does it pay?
Tobacco scan data is the weekly, transaction-level file of every tobacco sale a store makes, including each discount, sent to a manufacturer programme the store chose to join. Programmes use it to fund promotions at the counter and to pay incentives. Data that is late, incomplete or folds discounts into prices gets rejected, and rejected rows do not pay.
The work is not the selling; it is the data. Stores lose incentive money to a register that cannot separate a multipack discount from a price change, or that sells cartons as packs. That is a software problem, so it is ours to fix.
Programme rules, rates and file formats are set by each manufacturer and change. We build exports from your programme's current requirements; your agreement governs payment.
From the counter to the incentive payment
- Salecounter
A tobacco item is sold
The cashier scans a pack. The POS records the UPC, quantity, price, time and register, and any multipack or loyalty discount on that line.
- Promoauto
The programme discount applies itself
Buy-two or loyalty-price promotions set up from your manufacturer agreement apply automatically and are recorded as their own discount, not mixed into the price.
- Weekexport
Export the weekly file
Pick the week and the programme. The POS builds the transaction-level file with store details and the fields your programme lists.
- Submitportal
Send it the way your programme asks
Upload it to the manufacturer's data collector or let your scan-data partner pick it up. The POS keeps a copy of every file you sent.
- Monthpayment
Incentives arrive, rejected rows are rare
Programmes validate data before they pay. Clean, complete rows are what keep incentive payments coming.
The fields a weekly file usually needs
Your programme's requirements document is the authority. This is the usual shape.
| Group | Fields |
|---|---|
| Store profile | Store name, address, account number you were given |
| Transaction | Date, time, transaction ID, register |
| Item | UPC, description, quantity, unit of measure |
| Price | Selling price, final price after discounts |
| Promotions | Multipack discount, manufacturer discount, retailer discount, loyalty ID if used |
| Category | Cigarettes, smokeless, cigars, vapor, as your programme groups them |
Read the scan-data guide
How programmes work, the data-quality checklist, and the questions to ask before you enrol.
Related
- Age verification for the same tobacco sales
- Inventory: cartons in, packs out
- Full Shift plan
Scan data questions
What is tobacco scan data?
Tobacco scan data is the transaction-level record of every tobacco sale in your store (product, quantity, price, discounts, date and time) that you send to a manufacturer programme, usually weekly. In return, enrolled stores can receive promotional funding and incentive payments under their agreement.
Do I have to send scan data?
No. Manufacturer scan-data programmes are optional. Stores enrol to get access to promotions and incentives. Each programme sets its own rules, file format and payment terms in its agreement.
What does the weekly file contain?
Typically store details, transaction date and time, UPC, quantity, selling price, and each discount separately: multipack, manufacturer, retailer and loyalty. Exact fields and formats change, so we build the export from your programme's current requirements document.
Why do scan-data rows get rejected?
The usual reasons are missing store details, discounts folded into the price instead of recorded separately, wrong units (packs vs cartons), unknown UPCs and late files. The POS records discounts on their own lines and checks UPCs and units before export.
Can the POS submit the file for me?
The POS builds and stores the file. Delivery depends on your programme: some want an upload to their data collector, others work through a scan-data provider. We set up the route you use on onboarding.
Does scan data cover vapes and cigars?
If your programme includes those categories, yes. You map your POS categories to the programme's categories once.
Can I run multipack promotions?
Yes. Buy-two, buy-three and loyalty-price promotions are set up as automatic discounts with start and end dates, and recorded as their own discount type for reporting.
Is scan data available outside the US?
No. Scan-data programmes are a US manufacturer arrangement. The feature is off for UAE and Pakistan stores.
Which plan includes scan data?
Scan-data exports are in Full Shift and Multi-Store for US stores.
Clean scan data from the first week
Start the trial, map your tobacco categories, and export a test file to check against your programme.
