Compliance Field guide
How tobacco scan data works (and how to stop leaving rebates unpaid)
A plain guide to tobacco scan data: what the weekly file contains, why submissions get rejected, and how to track what manufacturers paid you.
If you sell cigarettes, cigars, smokeless or vapor products, there is money sitting in your sales data. Tobacco manufacturers run programs that pay retailers for reporting what they sell, and for running the promotions and pricing the program asks for. That reporting is called scan data.
A lot of stores sign up, submit for a few weeks, then drift. A file fails. Nobody notices. The payout comes in short and nobody checks why. This guide explains how the whole loop works, so you can keep it running without babysitting it every Monday.
Try it: the free scan data payout estimator shows what late or rejected weeks cost at your own units and rates. It runs in your browser.
What scan data actually is
Scan data is a file. Every week, your POS exports the tobacco lines it rang, usually one row per item per transaction, and you send that file to the program. The manufacturer uses it to see real retail sell-through, verify that promotions ran the way they were supposed to, and calculate what they owe you.
A typical row carries things like:
- Your store’s program account number
- Transaction date, time and a transaction ID
- The item’s UPC and description
- Quantity and unit of measure (pack or carton)
- Price paid, and any discount or multi-pack deal applied
- Whether a manufacturer promotion or loyalty offer was used
The exact columns, order, delimiter and file naming are set by each program’s technical specification. Those specs change over time. That is the single most important thing to remember about scan data: the format is not yours to decide, and it is not static.
The weekly cycle
Most programs run on a repeating weekly rhythm. In broad strokes:
- The sales week closes. Programs define their week, often Sunday through Saturday, in store local time.
- You generate the file. Your POS pulls every eligible tobacco line from that week.
- You check it. Unmapped items, odd quantities and missing account numbers get fixed before sending.
- You submit. Usually an upload to an FTP or SFTP server the program gives you, or a portal.
- The program validates it. Files that fail validation are rejected or partly rejected.
- You get paid. Payment arrives later, per the program’s schedule, often as a check or a credit.
The gap between steps 4 and 6 is where stores lose money. If you don’t record what you expected and compare it to what arrived, a rejected week looks exactly like a slow payment.
Where the money comes from
Programs differ, and terms are in your agreement, so treat this as a map rather than a rulebook. Payments generally come from a few sources:
- Reporting incentives for submitting complete, accurate files every week.
- Promotional funding for running specific price buydowns or multi-pack offers.
- Loyalty offers where the program funds a discount for an adult tobacco consumer enrolled in its loyalty program.
Each one has conditions. Some require that the promoted price actually appears on the shelf and at the register. Some require that you didn’t stack the deal with another discount. If your file doesn’t show the deal correctly, the funding doesn’t come.
A worked example
Say a store sells 40 cartons and 300 single packs of one manufacturer’s brands in a week. Here is how unit of measure trips people up.
| What was rung | Rows in file | Units if counted correctly | Units if cartons count as 1 |
|---|---|---|---|
| 40 cartons | 40 | 400 packs | 40 |
| 300 packs | 300 | 300 packs | 300 |
| Total | 340 | 700 packs | 340 |
If the program pays per pack, the second column is what you are owed for. The third column is what a misconfigured pricebook reports. That is less than half the volume. Nothing errors out. The file is valid. You just get paid on the wrong number, every week, until someone checks.
The rebate rate in this example doesn’t matter. Whatever it is, you are collecting it on 340 units instead of 700.
Shop-floor tip: When you add a new carton UPC to the pricebook, set its unit of measure the same day. A carton that sits in the system as “each” will quietly short your file until you catch it.
The five reasons files fail
1. Items not mapped to a manufacturer
Your POS has to know which manufacturer each tobacco item belongs to. New items arrive constantly: new flavors, new pack sizes, new UPCs on the same product. Any item without a manufacturer simply never makes it into that program’s file.
2. Wrong unit of measure
Covered above. A carton is ten packs for most cigarette programs. If the item says otherwise, your volume is wrong.
3. Missing or wrong account number
Each store has its own account number with each program. A new store, a changed account or a typo means the file goes to nobody. Multi-store operators hit this one a lot when they open or buy a location.
4. Wrong week or late file
Files built on the wrong week boundaries, in the wrong time zone, or sent after the deadline can be rejected outright. If your POS closes the week at midnight UTC but the program wants store local time, transactions near midnight Saturday land in the wrong week.
5. Out-of-date layout
When a program updates its spec, old files stop passing. Nobody emails the cashier about it. Someone has to read the notice, compare the layout and update the export.
A weekly scan data routine that takes ten minutes
You don’t need to love scan data. You need a routine.
Monday (or whatever day follows your program week):
- Open the week’s preview before generating the file.
- Look at any warnings: unmapped tobacco items, missing account numbers, items with no unit of measure.
- Map new items to their manufacturer. Most stores get a handful each week.
- Generate and submit, or confirm the automatic upload ran.
When payment arrives:
- Record the amount against the week it covers.
- Compare it to what you expected.
- Flag any week that came in short or never came in, and follow up with your program contact while the week is still recent.
Once a quarter:
- Check each program’s current technical specification against what you send.
- Confirm account numbers for every store.
- Review your top tobacco items for correct manufacturer and unit of measure.
Shop-floor tip: Keep a short list of your program contacts and account numbers per store somewhere the manager can find it. When a file fails on a Tuesday, nobody wants to dig through email.
Promotions have to match what you report
If a program funds a two-pack deal, the register has to actually ring the deal, and the file has to show it. If your cashier keys a manual discount instead of the promotion firing on the lane, the file may show a regular-price sale plus an unexplained discount. That can disqualify the line.
So the order of operations is:
- Set up the promotion in your POS as a real promotion with dates.
- Make sure the shelf tag shows the promoted price.
- Let the register apply it automatically.
- Check that the scan data preview shows the deal on those lines.
This is the same discipline that keeps your pricebook honest in general. There’s more on that in our guide to pricebook hygiene.
Rebates and your real margin
A carton that looks like a thin margin at the register may look better after the rebate. That changes buying and pricing decisions. If you only look at margin at the register, you might drop a brand that actually earns you more than one with a fatter shelf margin.
The useful number is margin after rebate per item: retail minus cost, plus the rebate per unit you expect to collect. Track it, but only count rebates you are actually being paid. An expected rebate on weeks that keep failing is not margin.
How CornerHawk handles scan data
CornerHawk’s scan data module is built around the routine above.
- Products carry a manufacturer and unit of measure. A carton counts as 10 packs. A bulk tool maps unmapped tobacco items in one pass.
- Program setup per store holds each store’s account number and expected rebate per unit for Altria, RJ Reynolds and ITG programs.
- The weekly file previews the Sunday to Saturday week in store time, shows readiness warnings, then generates a pipe-delimited file.
- Automatic submission can upload each store’s file over FTP, FTPS or SFTP after the week closes, retry failed uploads, never send the same week twice unless you choose Resend, and log every file. Failures show in the notification bell.
- History and payouts records what each manufacturer paid against the expected rebate, and the reports center shows outstanding and short-paid weeks plus margin after rebate per item.
One honest note. The column layout CornerHawk generates is a generic one. Before you submit to any program, check it against that program’s current specification and confirm it with your program contact. Programs change their requirements, and they are the only ones who can tell you a file is right.
The short version
- Scan data is a weekly file of your tobacco sales sent to manufacturer programs.
- Most lost money comes from unmapped items, cartons counted as one, bad account numbers and failures nobody noticed.
- Preview before you send, map new items weekly, and compare every payment to what you expected.
- Check each program’s current spec at least once a quarter.
If you’re tightening up the rest of your back office at the same time, the glossary has short definitions of the terms used here, and our guide to age verification compliance covers the other half of selling tobacco responsibly.
Quick answers
What is tobacco scan data?
Scan data is a weekly file of your tobacco sales, item by item and transaction by transaction, that you send to a manufacturer program. In return for accurate, on-time files and meeting the program's terms, the manufacturer pays you rebates or promotional funding.
How often do I have to submit scan data?
Most programs work on a weekly cycle with a fixed week definition and a deadline a few days after the week ends. The exact week, deadline and format are set by each program, so check your agreement and the current technical specification.
Why do scan data files get rejected?
The usual causes are items not mapped to the right manufacturer, cartons counted as one unit instead of ten packs, missing store account numbers, dates outside the program week, and files sent late or in an old layout.
Can my POS submit scan data automatically?
Many can. CornerHawk generates the weekly file per store and can upload it over FTP, FTPS or SFTP on a schedule, with retries and a log. You still need to confirm the layout matches each program's current specification.