Customer Tabs and Staff Discount Limits: The Two POS Features Nobody Explains

By Grace Wanjiru · Updated July 21, 2026 · 11 min read · Independent guide for shop and restaurant owners

Ask ten shop owners in Manila, Nairobi or Lagos what actually worries them about a new till, and almost none of them will say "the checkout screen." They'll tell you about the notebook under the counter, the regular who still owes for last week's rice, or the new cashier who gave a friend 30% off a full basket that nobody approved. Two features decide whether a POS actually helps with problems like that, or just ignores them: whether it can run a real customer tab, and whether it can cap exactly what each employee is allowed to discount. Almost no POS website explains either one clearly. Here's what to actually check before you sign up.

"Store credit" and "a customer tab" are not the same thing

These two words get used interchangeably in POS marketing, and it causes real confusion. Store credit means your shop owes the customer something. A customer tab, a credit book by another name, means the customer owes your shop.

Store credit usually comes from a prepaid balance, a returned item, or a voucher. The money already moved from the customer to you, or you owe them for something returned, so you're the one holding the debt. That's a nice feature, but it solves a completely different problem from the one most shop owners in busy trading streets actually have.

One more distinction worth being precise about: an open table or a running bar tab during a single visit is not a customer tab either, because it closes out before the customer walks out the door. A real customer tab survives the visit. It's a balance carried on the books until the customer comes back, sometimes days or weeks later, to pay it down.

Utang, deni, fiado, ardoise: same idea, different word

Whatever you call it, letting a trusted customer walk out owing you money is one of the oldest habits in small retail, and it's very much alive today. In the Philippines, sari-sari store owners call it utang, and it's common enough that several dedicated apps, SariTrack and Zobaze POS among them, exist mainly to replace the thick notebook owners used to keep a running utang balance under each customer's name.

In Kenya, shopkeepers running a duka call the same problem deni. It's common enough that a Kenyan developer built an app specifically so shopkeepers could track who owes what, reported by The Standard under the headline "No deni in my duka." A handful of Kenyan duka-management apps, including Duka Digital, now build the credit-customer list in as a core screen, not an afterthought.

Nigerian shop owners describe the same need in plainer terms, tracking "credit customers," and it's popular enough that standalone ledger apps like CreditBook and ShopCredit exist purely to replace the paper debt book, alongside POS-adjacent tools like MarketBook that create a debt record automatically when a sale is marked as credit and can send a payment reminder by SMS or WhatsApp.

The pattern repeats well beyond these three markets. Brazilian small shops call it fiado, common enough that apps like Cadê Fiado and Fiado Digital exist to replace the caderninho, the little notebook, with automatic WhatsApp reminders. In francophone West and Central Africa, shopkeepers call the same running tab an ardoise, literally "the slate," a phrase that comes straight from writing a customer's debt on a chalkboard by the till.

How an unmanaged tab quietly eats your margin

A tab isn't dangerous by itself. It becomes dangerous the moment nobody can see the total, and nobody set a limit before the first sale went on it.

The pattern is always the same. A regular customer asks for "just this once," you say yes because saying no to a loyal customer feels wrong, and there's no system stopping a second, third or tenth "just this once" from stacking up. Weeks later you're staring at a number you didn't track in real time, spread across a notebook, a few sticky notes and your memory, and a chunk of it is now genuinely hard to collect without an awkward conversation.

What actually fixes this isn't refusing to extend credit, plenty of shops depend on loyal credit customers to survive a slow week. It's visibility: one screen that shows every customer's current balance, updated the moment a credit sale happens, the way Kenyan duka apps show "everyone who owes you in one place" or Philippine utang trackers keep a running balance under each customer rather than a total buried in daily sales. Without that single view, you're not managing credit, you're hoping.

The other leak: staff giving away discounts nobody signed off on

An untracked discount button is a hole in your till that looks completely legitimate on the receipt, because technically, it is one. Nobody stole cash out of the drawer. They just quietly gave away margin you never agreed to give.

This isn't a theoretical risk. US grocery chain Hy-Vee temporarily shut down its own employee discount program after finding what it called fraud and abuse, including one employee's discount account being used across five states in a single hour. On Square's own community forum, a merchant asked how to restrict an employee discount to specific items, a plain sign that the default setup let staff apply it more broadly than the owner wanted. On the salon-industry forum Salon Geek, an owner asked whether a staff member giving an unauthorized discount to a friend, after being told not to, counted as grounds for dismissal, and other salon owners in the thread called it a form of stealing.

The fix isn't trusting staff less. It's giving each employee their own login with a discount ceiling tied to their role, so a junior cashier simply cannot apply a discount past what you've decided, and a report exists afterward showing exactly who applied what. That turns an invisible habit into a visible, correctable one.

How to test both features before you sign anything

A features page telling you a POS "supports credit" or "has permissions" doesn't tell you enough. Test both, live, during a free trial, before you commit a single customer's real tab to it.

For customer tabs, check:

• Create a test customer, put a sale on their tab, and confirm you can see their exact running balance on demand, not buried in a general sales report.
• Record a partial payment against that balance and confirm it updates correctly, not just to zero or nothing.
• Turn off your phone's data or wifi and repeat the test. A tab that only works online is a tab you can't trust during a power cut or a weak-signal afternoon.
• Ask for a single report listing every customer who currently owes you money, sorted by amount or by how long it's been outstanding. If that report doesn't exist, you'll be back to mental math.

For staff discount limits, check:

• Create two staff logins with different permission levels, then try to apply a large discount from the lower one. It should be blocked or capped, not just discouraged by policy.
• Ask specifically: is the limit enforced by the system at the point of sale, or is it just something written in an employee handbook? Those are very different guarantees.
• Ask for a report showing every discount applied, by which employee, and over what period. If a vendor can't show you that report in the demo, ask them to, that's a fair question and a serious one.

Where digabloPos actually fits

A simple system to run tabs without losing money

The tool only helps if a few habits sit around it. None of these take long, and all of them are worth deciding on day one, before your first customer asks for credit.

• Set a per-customer ceiling before you extend any credit, a number you'd be comfortable never seeing back, and stick to it even for regulars.
• Record a name and phone number the first time someone goes on the tab, not just "the lady from down the street."
• Review every outstanding balance weekly, not monthly. A balance that's been sitting for three weeks is far easier to collect than one that's been sitting for three months.
• Decide upfront who can put a sale on a tab. If any cashier can do it without asking, you've effectively handed out unlimited credit approval to your newest hire.
• Set discount limits by role on day one, before there's a specific incident to react to, and glance at the by-employee discount report on the same weekly schedule as your tab review.

Neither of these problems is really about software. They're about visibility and a limit you decided on in advance, instead of finding out the size of the problem after it's already happened. A POS that shows you both clearly just makes the habit easier to keep.

FAQ