Buying guide Field guide
Choosing a convenience store POS: the questions that actually matter
A c-store POS buyer's guide: offline mode, pricebook, scan data, EDI, fuel, lottery, end-of-day, contracts and the questions to ask in a demo.
A POS demo is designed to impress. Big screens, smooth animations, a dashboard full of charts. Then you go live, the internet drops on a Friday night, the distributor’s invoices still have to be typed in, and the end-of-day report doesn’t match the drawer.
This guide is a list of questions that separate a good c-store system from a good demo. Use it to plan the conversation, and ask to see each answer live, in the product, not on a slide.
Start with your store, not the feature list
Before you look at any system, write down how your store actually runs:
- How many stores, registers and employees?
- Fuel? Which pump controller and which fuel card settlement?
- Lottery? Which state?
- Tobacco scan data programs you’re in, or want to join?
- Which distributors deliver, and do they offer EDI?
- Deli, roller grill, coffee, pizza?
- Do you do your own books, or does an accountant?
- What’s your card processor, and is your contract with them flexible?
That list is your scorecard. A system that’s brilliant at restaurant table service doesn’t help a store that lives on cigarettes and fountain drinks.
The register
What happens when the internet goes down?
This is the first question, not the last. Ask the salesperson to unplug the network during the demo and ring a sale. Then ask:
- Can it take cash and card while offline? (Card offline depends on your processor and terminal. Ask specifically.)
- Do sales sync automatically when the connection is back?
- What happens if two registers sell the last pack of something while offline?
- How does the back office know a sale happened late?
Shop-floor tip: Ask what happens to a sale if the register’s browser or app is closed while offline. “It’s saved” is the only acceptable answer.
Speed at the counter
Time a basic transaction: scan three items, cash, change. Then a harder one: age-restricted item, split between EBT and cash, a manufacturer coupon, a loyalty member. If the hard one takes a lot of taps, your line will feel it.
Tenders
Make sure it handles what your customers actually pay with: cash, card, EBT (with EBT-eligible items handled correctly in a split), house or charge accounts for regulars and local businesses, manufacturer coupons, and tips if you have a deli or coffee bar.
Age verification
Ask how the register handles a 21+ item. Does it calculate age from the date of birth? Can a cashier skip the prompt? Is the check recorded? See our age verification guide for what good looks like.
The pricebook
The pricebook is where you’ll spend most of your back office time. Ask to see:
- Adding a new item by scanning its barcode.
- Changing a price for one store only, in a multi-store setup.
- Setting a mix and match promotion (2 for $5) and seeing it on the receipt.
- Finding every item whose price changed this week, so you can print shelf tags.
- Who changed a price, and when.
If any of that is slow or confusing in the demo, it’ll be worse at 11pm on a Sunday. Our pricebook hygiene guide explains why these matter.
Buying and receiving
- Invoices. Can you scan a paper invoice, import an EDI 810 file, or both? Can EDI be picked up automatically from your distributor’s FTP folder?
- Costs. Does posting an invoice update item costs and case costs?
- Ordering. Can it build an order sheet from what’s low, and send it to the vendor by email or message?
EDI 810 explained goes into what to ask your distributors.
C-store specifics
These are the modules generic retail systems usually don’t have, or have only as an add-on:
| Area | What to ask |
|---|---|
| Scan data | Which programs? Is the file generated weekly per store? Can it upload automatically? Does it track payouts? |
| Lottery | Pack life cycle, daily counts, settlement, link to end-of-day? |
| Fuel | Prices, deliveries, FIFO cost, taxes per gallon, cash vs credit? |
| Deli | Recipes with food cost, production, hold times, waste? |
| End of day | Does it compute expected cash including fuel cash, paid outs, ATM and lottery? |
| Loss prevention | Voids, no sales and refunds per cashier against the team? |
The back office and the money
- Does closing the day feed the books, or do you type the same numbers again into accounting software?
- Can it import a bank statement and match deposits?
- Can it reconcile card batches with what the processor deposited?
- Does it give you a P&L with fuel and merchandise margins, not just sales?
- Payroll from the time clock, or a CSV your payroll provider can import?
If you have an accountant, ask whether they can get what they need without logging in every week.
Many stores
If you run more than one store, or plan to:
- One login to see all stores, with a filter for one or several.
- Store-level prices where you need them, company-level everywhere else.
- Roles and permissions: a manager who sees one store, a district manager who sees five.
- Comparing stores side by side on the same report.
Contracts, data and hardware
This is where the real cost of a system often hides.
- Term. How long is the contract? What does it cost to leave early?
- Processing. Is card processing bundled? Can you bring your own processor?
- Hardware. Bought, leased, or only usable with this vendor’s software? What standard hardware works?
- Your data. Can you export your pricebook, sales and customers in a normal format, any time, without asking?
- Price per what? Per store, per register, per module? What’s included and what’s extra?
- Support. Hours, how to reach someone, and what happens on a holiday weekend.
Shop-floor tip: Ask for the cancellation terms in writing before the demo ends. A vendor confident in the product won’t mind.
Questions to ask about switching
The best system in the world is a bad choice if moving to it costs you a month of chaos. Ask the vendor:
- Pricebook import. Can they load your current pricebook from an export? Which columns do they need? Who does the cleanup?
- History. Do you need past sales in the new system, or is a cutover date fine? Most stores keep the old reports for history and start fresh.
- Customers and house accounts. Can member lists and house account balances come across?
- Go-live. Will someone be available on your go-live day? On the first weekend?
- Training. Is there training for cashiers as well as managers? How long does a new cashier take to learn the register?
- Parallel running. Can you keep the old system available for a few days in case something goes wrong?
A good answer is specific. “We’ll take care of it” is not specific.
Things that look good in a demo but don’t matter much
Some features sell systems without changing how a store runs. That doesn’t make them bad. It just means they shouldn’t decide the purchase:
- A dashboard with twenty charts you won’t open after the first week.
- Customer-facing screens with animations.
- Integrations with tools you don’t use.
- An app store of add-ons, each with its own monthly fee.
Ask yourself: will my manager use this on a Tuesday? If not, weigh it lightly.
Run a fair trial
If possible, run the new system on one register or one store for a few weeks:
- Import your real pricebook, not a demo one.
- Ring real transactions.
- Close real days and compare them to your current system.
- Have your manager, not you, run the back office for a week.
- Have your accountant look at a month-end.
Where CornerHawk fits
We built CornerHawk for this list. It’s honest to say where it fits and where it may not.
- The POS lane runs in a browser or as an installed app on Windows, Android or iOS and keeps selling with no internet (offline mode); sales queue on the device and sync in order, and anything the server can’t accept is parked for review instead of lost.
- One pricebook drives registers and back office, with store prices, promotions, coupons, Item Logs and shelf labels.
- C-store modules include scan data with automatic submission, lottery, fuel with taxes and FIFO cost, deli, EDI import with automatic pickup, and the Daily Book end-of-day close.
- Accounting, card processor reconciliation, payroll, scheduling and a multi-store dashboard are part of the same system.
- Plans are priced per store per month. See pricing.
Check things against your own setup: card terminal integration, pump controllers and state lottery report formats vary, so ask us about yours specifically. If you’re moving from another system, the switching guide explains the steps.
The short version
- Test offline, live, in the demo.
- Time a hard transaction, not an easy one.
- Spend most of the demo in the pricebook and the end-of-day close.
- Make sure the c-store modules you need are real, not on a roadmap.
- Read the contract, processing terms and data export terms before you sign.
Quick answers
What's the most important feature in a c-store POS?
Reliability at the counter. If the register stops when the internet drops, nothing else matters. After that, a pricebook that's easy to keep clean, and a back office that closes the day accurately.
Do I need separate software for the back office?
Not necessarily. Many stores run a register from one company and back office from another, and spend time moving data between them. A system that does both from one pricebook avoids double entry, but check that the back office covers what you need.
What should I ask about contracts?
Ask about the length of the term, cancellation terms, what happens to your data if you leave, whether payment processing is tied to the software, and whether hardware is leased, bought or locked to the vendor.
How long does it take to switch POS systems?
It depends on the size of your pricebook and how clean it is. The steps are the same: export the pricebook, clean it, import it, set up departments and taxes, test, train, and go live on a quiet day with the old system on standby.