Grocery Store POS Systems

Why grocery is its own problem

Two numbers explain most of what follows. A grocery basket has far more lines in it than almost any other retail sale, and the net margin left at the end of the year is thinner than in almost any other retail trade. Everything a grocery POS has to be good at comes out of those two facts.

More lines per basket means scanning speed is not a convenience, it is the checkout. A thin margin means a cost you would shrug at in a gift shop is a cost that shows up in your year here. And on top of both sits a set of things other shops simply never deal with: produce sold by weight, food benefits tendered at the register, a stock list where some of it goes off, and a legal obligation at the till on beer, wine and tobacco.

So a grocery store POS system is judged on different ground from a boutique one. The rest of this page goes through that ground in the order it actually hits you.

A catalog in the thousands, scanned fast

A small independent grocer can carry several thousand distinct items. A convenience store carries fewer but turns them faster. Either way the catalog is the part of the system you touch constantly, and the things that matter are unglamorous.

• Scanning has to be the default, not a fallback. Every item that can carry a barcode should ring by barcode. Anything staff have to look up by name is a bottleneck that only shows up at the busiest moment.
• Bulk price changes. Prices move constantly on grocery lines, and they move in batches when a supplier changes cost. Changing a hundred prices should be an import, not a hundred edits. Ask exactly how that is done before you buy.
• Shelf labels that match the system. A price on the shelf that disagrees with the price at the till is an argument at the register and, in most states, a weights-and-measures problem. Being able to print shelf labels from the same catalog the register uses closes that gap.
• Case, pack and each. You buy a case of twenty-four and sell singles. The system has to hold that relationship, or your stock count is wrong from the first delivery.
• Departments that mean something. Grocery, beer and wine, deli, produce, tobacco, household. Department-level reporting is how you find out which part of the shop is actually carrying the others.

Weighed items, scales and PLU codes

The moment you sell anything by weight, you are running equipment that the state inspects and a set of codes that most POS salespeople have never had to think about.

• PLU codes on produce. Loose produce is rung by a four-digit price look-up code, the same codes you see on the little stickers, assigned internationally rather than by you. A five-digit code beginning with 9 marks the organic version of the same item. A register that knows those codes, and a cashier-facing screen with pictures for the ones nobody remembers, is the difference between a fast produce lane and a slow one.
• By weight against by each. Some items sell both ways in the same shop. The catalog has to carry which is which, and the register has to prompt for a weight only when it should.
• Legal for trade. A scale used to price goods for sale is a regulated instrument. It has to be an approved type, it has to be installed so the customer can see the display, and it is subject to inspection. This is not a POS feature, it is a legal requirement, and a scale that merely connects to your POS is not automatically one that satisfies it.
• Tare. The container does not get sold as product. Tare has to be handled at the scale, consistently, or you are giving away weight on every salad bar and deli tub.
• Deli labels with the price inside the barcode. A deli or meat counter weighs, prices and prints a label, and the barcode on that label carries the price so the front register just scans it. These price-embedded barcodes are their own format, and whether your register reads them properly is a question to ask with the specific scale you intend to use.

EBT and SNAP at the register

If you sell staple food, accepting SNAP is often a significant share of your takings, and it is the part of grocery payments with the most rules attached. None of it is difficult once it is set up. All of it is worth understanding before you pick a system.

• You have to be authorized. Accepting SNAP is not something your processor can switch on. The store is authorized by the USDA's Food and Nutrition Service and issued its own FNS number. That application is yours to make, and the timing of it is worth building into any plan to open or to change hands.
• It is a separate rail. EBT transactions are PIN based and routed through the state EBT processor rather than through the card networks. That means the setup involves your state as well as your POS, and it is a question to ask early rather than at go-live.
• Eligibility lives at the item level. SNAP covers staple foods. It does not cover alcohol, tobacco, hot prepared food, or non-food household items. Your catalog has to carry that flag on every item, because the register has to work out what is eligible in a mixed basket without the cashier deciding.
• Split tender is the normal case. A real basket has eligible and ineligible items in it. The register applies benefits to the eligible portion, then takes the rest on card or cash, in one transaction, without anyone unpacking the bags. A system that cannot do that cleanly will slow every lane you have.
• No fees on the benefit portion. You cannot surcharge or add a fee to a SNAP purchase, and you cannot give cash back on SNAP food benefits. Cash back rules on an EBT cash benefit account are a separate matter and vary by state.
• WIC is a different program again. WIC works against an approved product list, item by item, with its own rules and its own certification. If you intend to accept it, say so up front when you are choosing a system. It is a bigger ask of a POS than SNAP is.

Age-restricted items at the till

Beer, wine, spirits and tobacco are a meaningful part of most convenience and many grocery baskets, and they are the part where a mistake at the register is a license problem rather than a money problem.

• Prompts on the item, not on the cashier. The restriction belongs on the product record, so every restricted line stops the sale and asks, regardless of who is on the register or how busy it is.
• ID scanning. Most US driver licenses carry the date of birth and the expiry date in a barcode on the back. Scanning does the arithmetic and flags an expired license, which removes the two errors people make under pressure. It does not confirm the person is the one on the license, so it sits on top of looking properly rather than replacing it.
• Different ages, different products. The minimum age is not the same for every restricted category, and the rules differ by state and sometimes by county. The system should hold the age against the product rather than relying on anyone to remember.
• Hours and days. Plenty of states restrict when alcohol may be sold. A register that can refuse a sale outside those hours takes a real risk off the shop floor.
• What you may keep. Rules on retaining scanned ID data vary by state. Check yours before switching on anything that stores it.

Why processing cost bites harder here

This is the part of grocery payments that is genuinely different in kind, not just in degree. On a thin net margin, the difference between two processing arrangements can be a visible share of what you keep, and there are a few structural reasons it lands harder on this trade than on others.

• Debit is a large share of the mix. Grocery skews heavily to debit, and debit is priced differently from credit. How your transactions are routed across debit networks is a real lever, and it is one most merchants never hear about. It is a fair question to put to anyone quoting you.
• Small baskets magnify fixed fees. A convenience store selling a coffee and a paper is paying a per-transaction component on a very small sale. The percentage matters less than people assume and the flat piece matters much more, which is exactly the opposite of a shop selling one expensive item a day.
• Volume multiplies everything. A small difference per transaction is a small number. Multiplied by a grocery transaction count, it stops being small. That is the whole argument for reading the statement properly rather than comparing headline rates.
• Surcharging is not a simple answer. You cannot surcharge debit, you cannot add a fee to a SNAP purchase, and the rules on surcharging credit differ by state and card brand and carry disclosure requirements. Anyone pitching a grocery store free processing should be asked, immediately, exactly which program they mean and what it would require you to post at the register.

Volume: lanes, uptime and Saturday

1. Count lanes against your busiest hour, not your average day. The average day never queues.
2. Ask what happens when the connection drops mid-shift: what the register can still do, what it stores, and what the limits are. A grocery store that cannot take a payment for twenty minutes has a line to the back of the shop.
3. A drawer per cashier if the layout allows it. A shared drawer makes a shortfall nobody can account for.
4. Receipt printers and scanners are consumables with a duty cycle. At grocery volume, specify equipment for the volume rather than for the price.
5. Settle daily, and reconcile daily. At this transaction count, a discrepancy found a week later is no longer traceable to anything.

Self-checkout, honestly

Self-checkout is the question every grocer gets asked about and the one with the least honest coverage, because it is sold on the labour saving alone.

• What it actually does. It moves the scanning work to the customer and lets one member of staff oversee several lanes. That is a real gain at peak, in a shop where baskets are small and mostly barcoded.
• What it costs you. Shrink goes up. That is not a rumour, it is the trade-off, and it needs to be set against the labour saved rather than ignored. Loose produce and anything sold by weight is where most of it happens.
• Age-restricted items still stop. Every beer and every packet of cigarettes pulls a member of staff over to the lane. In a shop where a large share of baskets contain one, the saving is smaller than the sales pitch suggests.
• Produce is the hard part. A customer looking up loose chard on a touchscreen is slower than a cashier who knows the code. A good produce lookup screen with images helps a great deal, and it is worth testing with real items before you buy.
• Floor space is not free. Units take the space of a staffed lane and change how people move through the front of the shop. Worth drawing before buying.

The honest summary: self-checkout suits high-volume, small-basket, mostly-barcoded shops, and suits a produce-heavy or alcohol-heavy independent much less. It is a question worth answering with your own basket data rather than with a general argument.

Stock that goes off

Perishables are the part of grocery inventory that behaves unlike any other retail stock, and the part most systems handle only partly.

• Shrink is a category, not an accident. Waste, spoilage, damage, staff use and theft are five different things. Recorded as one number they tell you nothing. Recorded separately, by department, they tell you where the money is going.
• Count what moves, often. A full count of several thousand lines is a project nobody does regularly. Counting the fast and the perishable lines on a short cycle is something you can actually keep up, and it catches the problems that matter.
• Margin by department, not just sales. Produce and deli turn over well and carry waste. Grocery lines carry less waste and thinner margin. Sales by department alone will mislead you about which is carrying the shop.
• Ordering from real movement. The reason to keep the catalog accurate is that it turns into an order. A system whose stock figures nobody trusts is a system where ordering goes back to walking the aisle with a clipboard.

What to ask before you sign

1. Is my exact scale model supported, in writing, including price-embedded labels from the deli counter?
2. How does the system handle SNAP eligibility at item level and split tender in a mixed basket?
3. If I want WIC, is it supported, and what does certification involve?
4. How do I change a hundred prices at once, and how do shelf labels stay in step with the register?
5. How are age restrictions held, and do hour-of-day restrictions work in my state?
6. What happens to the lanes when the internet drops, and for how long?
7. How is my debit traffic routed, and what choice do I have about it?
8. What am I paying, every line of it explained, including the lines that are not processing at all?