The Discount Nobody Approved: Where Retail Margin Actually Goes
Discounting is the fastest way to give away a year of margin without a single missing item. Every shilling comes straight off profit, none of it touches your stock count, and in most Kenyan shops nobody can tell you who authorised any of it.
Shrinkage gets the attention. A missing carton is visible, countable, investigable — and it makes people angry. Discounting takes more money out of more Kenyan retailers than shrinkage does, and it does it in the open, one small kindness at a time, with a cashier's hand on the keyboard and nobody's name against the decision.
This is not an argument against discounting. Discounts move slow stock, keep good customers, and close a sale that would otherwise walk. It is an argument against untracked discounting, because the arithmetic is unforgiving in a way that most owners have never actually done on paper.
Do the arithmetic once and you never forget it
A discount is not a percentage off the price. It is a percentage off the margin, and those two numbers are very far apart on a retail item.
A 10% discount on an item with a 25% gross margin
A tenth off the price is two fifths off the profit. To earn back that one discount at full price you need to sell the item roughly another two thirds of a time over. The cost figure never moves, which is exactly why the damage is invisible in a stock report: nothing is missing, the shelf is right, the count is right, and the profit is gone.
Shrinkage shows up as a hole in your stock. Discounting shows up as nothing at all.
Why one gets investigated and the other does not
How a discount is actually recorded at our till
Precision here matters, because the shape of the field determines the shape of the control.
- The discount is entered per line, as an amount per unit, and it is multiplied by the quantity on that line.
- It is capped at the line subtotal, so a line can never go negative no matter what is typed.
- The line is pre-filled from the item itself: an item can carry a configured discount value, or a discount percentage applied to its selling price. The value wins where both are set.
- Above the item's own discount, a cashier may add a manual discount only up to the workspace maximum discount percentage set in Settings › Sales. It defaults to zero, so out of the box the till applies the item's discount and nothing more.
- Above that limit the sale needs a reason and a second name: either the cashier holds the discount override permission, or a supervisor who holds it types their personal approval PIN at the till.
- Every discounted line writes a discount record — cashier, approver and how they approved, percentage, the limit in force and the reason — and the sale shows it.
- The discount reduces the taxable base — tax is computed on the discounted amount, which is correct, and means a discount also reduces the VAT you charge and remit.
- The cost of the item does not change, so the entire discount lands on margin.
- Every line discount is stored on the sale line, summed onto the sale, and totalled in the POS sales summary report.
So the catalogue-level discount is a genuine control: set a promotional price on the item once and every counter applies it consistently. What happens when someone goes past that figure at the counter is a control too.
Where the trail goes
A discount that reaches the sale as a bare number, with no reason and no second name, is a figure nobody can be asked about. So every discounted line here also writes a discount record — against the sale and the line — carrying the cashier, the approver, the percentage, the limit in force and the reason. The reason is free text rather than a code.
Discount controls: what exists, what does not
| Control | Available today |
|---|---|
| A promotional price or percentage set once on the item and applied at every till | Yes |
| A per-line discount amount recorded on the sale and visible on the receipt | Yes |
| Discount totals per period in the sales summary report | Yes |
| A hard cap so a line cannot be discounted below zero | Yes |
| Correct tax treatment — tax charged on the discounted amount | Yes |
| The sale, cashier and counter attached to every discount, since it lives on the sale | Yes |
| A workspace-wide maximum discount percentage for manual discounts | Yes |
| A reason required on a discount above the limit | Yes |
| A supervisor approval step above the limit, by personal PIN | Yes |
| A fixed list of reason codes rather than a typed reason | No |
| A maximum discount percentage per item, category or role | No |
| A whole-sale discount as its own recorded object rather than spread across lines | No |
| A separate permission for discounting above the limit, distinct from the permission to sell | Yes |
| Discount included in the POS sales CSV and PDF export columns | No |
Built and maintained Configurable by you, not maintained by us Not built
The last row is the smallest and most annoying gap: discounts are totalled in the on-screen summary, but the sales export columns run subtotal, tax, total, paid and balance — so a discount analysis today means the summary screen rather than a spreadsheet.
What to do alongside the limit
The limit and the approval PIN stop a discount nobody authorised. They do not tell you whether the discounts somebody did authorise were sensible, and that part is still policy and reading. The controls that actually work in Kenyan retail are boring and cheap.
-
Move real discounts into the item, not the counter
If a product is on promotion, set its discount value or percentage on the item. Every till then applies the same figure automatically, the promotion ends when you clear the field, and no cashier has to remember anything. This single move removes the majority of legitimate counter discounting.
-
Set the ceiling in Settings and make it specific
Settings › Sales holds the most a cashier may give above the item's own discount. Zero is the default and a sound start; raise it only to a figure you can defend, and decide deliberately who holds the override permission and which supervisors set an approval PIN. A rule like "use your judgement" is not a rule.
-
Read discount totals per cashier, weekly
Absolute totals mislead — a busy till discounts more. Read discount as a percentage of that cashier's sales. One cashier at 4% against a floor average of 0.9% is the whole finding, and it takes two minutes to see.
-
Ask about the outliers without accusing anyone
Most of what you find is not theft. It is a cashier who has been told to keep customers happy, or one who does not know a promotion ended, or a damaged-stock workaround nobody documented. All three are fixable once visible.
-
Stop using discounts as a workaround for something else
Damaged goods, price errors and goodwill on a faulty item are three different events with three different correct records. Pushing all of them through the discount field destroys your ability to see any of them.
Rating your own discount exposure
Five questions, weighted by how much money hangs on the answer
Answer honestly rather than aspirationally. The purpose is to find where your money is going, not to score well.
Can you state your total discount as a percentage of sales for last month?
Make them prove it: Open the sales summary for the period and read the discount total against total sales. If nobody has ever looked, that is the answer.
Are your promotional prices held on the items, or typed at the counter?
Make them prove it: Pick three items currently on promotion and check whether the discount is configured on the item record.
Do you know which cashier discounts the most, adjusted for their sales volume?
Make them prove it: Compare discount as a share of sales, per cashier, over four weeks — not the raw totals.
Is there a stated ceiling above which a cashier must ask?
Make them prove it: Read the maximum discount in Settings › Sales, then ask two cashiers separately what the limit is. Different answers mean the limit is enforced but not understood.
Are damaged goods and price corrections handled as discounts?
Make them prove it: Ask what a cashier does when an item is dented. If the answer involves the discount field, your discount figure is measuring three things at once.
What we do and do not do
What AWRA OpsHub does today
- A discount value or percentage configurable on each item, pre-filled automatically at the counter.
- Per-line discounts recorded on the sale line and summed onto the sale.
- A hard cap preventing a line from being discounted below zero.
- Tax computed on the discounted amount, so VAT charged reflects what the customer actually paid.
- Discount totals for any period in the POS sales summary, filterable alongside subtotal, tax and total.
- Every discount inherently attributable to a sale, a cashier and a counter, because it is stored on the sale.
- A workspace maximum discount percentage for manual discounts above the item's own, set in Settings › Sales and defaulting to zero.
- Above the limit, a required reason and either the cashier's own override permission or a supervisor's personal approval PIN, which locks for fifteen minutes after five wrong entries.
- A discount record on every discounted line — cashier, approver and approval method, percentage, limit in force and reason — shown on the sale.
- An over-limit discount on a sale queued offline in the mobile app kept and flagged for review, rather than refused after the goods have left.
More we can add to your workspace
- A fixed list of discount reason codes, so reasons can be counted rather than read one by one.
- Discount limits per role, item or category, on top of the workspace-wide maximum.
- The same discount authority on quotes, sales orders and invoices.
- Pattern alerts on discounting — one cashier, customer or item drawing an unusual share.
- A sale-level discount recorded as its own object rather than distributed across lines.
- Discount columns in the POS sales CSV and PDF exports.
- Automatic margin alerts when a discount pushes a line below cost — the cap stops a negative price, not a below-cost one.
Coded reasons and limits per role are the next smallest changes on this list. If discount leakage is your live problem, say so and they move up the queue rather than sitting behind features nobody has asked for.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsOur take
Discounting is the leak that never triggers an investigation, because nothing goes missing. Put your real promotions on the item records where they apply themselves, set a ceiling in Settings that people can repeat back to you, and read discount as a percentage of sales per cashier once a week. The till holds every cashier to that ceiling and asks for a supervisor's PIN above it; the weekly reading is what tells you whether the approved discounts were worth giving.
The neighbouring mechanics are worth reading alongside this: tax-inclusive pricing at the till explains why the discount changes your VAT, returns and exchanges covers the damaged-goods route that discounting is often standing in for, and counters, cashiers and the handover explains why every discount already has a name attached to it.
See where the margin actually went
Promotional prices held on the item, a discount limit with a supervisor PIN above it, every line discount recorded against a named cashier and approver, and discount totals for any period you care to look at.
See POS in AWRAFrequently asked questions
Can we stop cashiers giving discounts altogether?
Yes, and it is the default. Above the item's own discount, a cashier may give only up to the workspace maximum set in Settings › Sales, which starts at zero — so out of the box the till applies the item's discount and nothing more. Above the limit, the sale needs a reason and either a cashier who holds the discount override permission or a supervisor who types their approval PIN. Setting your genuine promotional prices on the item records is still the best first move, because those apply automatically and need nobody's approval.
Is the discount a percentage or an amount?
At the counter it is an amount per unit, multiplied by the line quantity and capped at the line subtotal so a line cannot go negative. On the item record you can configure either a discount value or a discount percentage of the selling price — the value takes precedence where both are set. The percentage is resolved to an amount when it pre-fills the line.
Does a discount reduce the VAT we charge?
Yes, and that is correct. Tax is computed on the line amount after the discount, so a discounted sale charges proportionally less VAT. It also means a large volume of untracked discounting quietly reduces your output VAT, which is another reason the total is worth reading rather than ignoring — your tax figures and your margin figures are moving together.
Where do I see how much we discounted last month?
In the POS sales summary report, which totals discounts for the period alongside subtotal, tax, total sales and average sale, and can be filtered. What it will not do yet is put a discount column in the CSV or PDF export of sales, so per-cashier analysis over a long period is on-screen work rather than spreadsheet work. That export column is a small gap and a fair thing to ask us for.
Can a discount push an item below its cost?
Yes, within the limit you allow. The cap stops a line going below zero and the workspace maximum stops a cashier going past your percentage without a second name, but neither reads the item's cost. Because the cost never changes, the whole discount lands on margin. If you sell items with thin margins, set the workspace maximum with your thinnest line in mind rather than your fattest.
Is there any record of who authorised a discount?
Yes. Every discounted line writes a discount record carrying the cashier, the approver and how they approved — their own override permission or a supervisor's PIN — the percentage, the limit in force and the reason, and the sale shows it. The reason is typed text; a fixed list of reason codes is something we can add.
