erp for retail in Kenya is tested at 8:40 on a Saturday, when a branch in Ruiru sells the last unit of a promoted item and three numbers disagree.
The shelf label says one price, the till charges another, and the stock report still shows four units in the back store.
erp for retail in Kenya is the work of making those three numbers agree before the customer reaches the counter.
One Stock Ledger, Six Branches, One Truth
A six-branch retailer usually keeps six stock figures, each maintained by a different person with a different idea of what stock means.
Head office adds them together and calls the total company stock. It is an estimate wearing a balance sheet’s clothes.
erp for retail in Kenya starts by replacing those six figures with one ledger keyed on item and location.
That looks like reporting. It behaves like control, because a shared ledger exposes every movement to people who did not create it.
Build the locations first: shop floor, back store, damaged cage, quarantine and in-transit. Stock in the damaged cage is not sellable.
Then fix the item master. One code per sellable unit, one base unit, one barcode, one tax treatment, one named owner.
A carton and a single bottle are two SKUs joined by a conversion factor, never one item and an educated guess.
erp for retail in Kenya holds only when the till cannot invent items. New lines are requested, priced centrally and released on a stated date.
Refuse negative balances without a reason code. Negative stock is usually a missing document, not a rounding error.
A hard block on unexplained negatives exposes more process failures in month one than a full internal audit.
erp for retail in Kenya gives the branch a figure it can defend at the morning meeting, and gives finance a figure it can post at month end.
Transfers and the Stock That Lives in a Lorry
Between the Nairobi warehouse and a branch in Nakuru, stock exists in a place no shelf can hold: a lorry on the A104.
Most retail systems treat that stock as either sent or received, and the gap becomes a mystery in the closing week.
erp for retail in Kenya gives the gap a name. The quantity leaves the warehouse and lands in a location belonging to neither end.
The transfer order carries the dispatch note number, the vehicle, the driver and the expected arrival date. The branch scans against it.
If the branch counts eleven cartons against twelve dispatched, the system raises a shortage on that transfer, not on the whole branch.
That distinction makes the driver conversation possible on Monday, long before an auditor’s question in March.
Route schedules belong in the model. Mombasa on Tuesday, Kisumu on Thursday, and a cut-off time after which the order waits a week.
erp for retail in Kenya should refuse to release a transfer after the cut-off, rather than let a branch promise stock it will not have.
Transfer pricing matters for branch profitability. Cost plus a fixed mark-up works until a branch is taxed on stock it never sold.
Use one transfer price for internal reporting and any inter-branch recharge, and document the choice once.
erp for retail in Kenya closes the loop when the receiving branch confirms, so the warehouse knows what arrived rather than what left.
How Shrinkage Hides in a Retail P&L
Shrinkage in Kenyan retail is usually reported as one number at month end, and that number is a plug.
It equals opening stock plus purchases minus sales minus closing stock. Everything the business cannot explain lands in it.
The plug hides theft, damage, supplier shortfalls, unrecorded transfers and keying errors in the same line.
erp for retail in Kenya splits it into known loss and unknown loss, by location, category and reason.
Known loss includes expired goods, breakages, markdowns taken after damage and write-offs signed by a manager.
Unknown loss is what remains after counts, and it should be reported per category rather than per company.
A supermarket’s shrink in dry groceries behaves nothing like shrink in fresh produce, and the controls differ.
Count high-risk lines weekly: spirits, cosmetics, phone accessories, infant formula, razor blades and cheese.
erp for retail in Kenya makes count frequency a property of the item class, so the schedule survives the departure of whoever designed it.
Watch receiving. A supplier who delivers nine cartons and signs for ten creates shrink before the goods reach a shelf.
Weigh in and scan in at the door, then match the goods received note to the invoice before the driver leaves the yard.
erp for retail in Kenya posts the difference to a supplier claim, which is recoverable, instead of to shrinkage, which is not.
Price Changes, Promotions and the Margin Leak
A promotion running for fourteen days needs at least four price states: before, at the till during, on the shelf during, and after.
Most margin leaks happen at the fourth state, when the till still sells at the promo price a week after the banner came down.
erp for retail in Kenya stores price records with effective dates rather than editing a single price field, so the end date is part of the change.
Shelf-edge labels, the price file and the till draw from one record. If a branch can override, the override must expire.
Multibuy rules are where honesty gets expensive. Buy two get one free must not apply to a single unit scanned twice.
Test every promotion on the till, with the scanner, before it goes live. A printed memo is not a test.
Markdowns on fresh produce deserve their own approval. A branch that can mark down at will can also sell to a friend at will.
erp for retail in Kenya should route markdowns above a threshold to a category manager, with reason and quantity recorded.
Loyalty and staff discounts must post separately from promotional discounts, or nobody can price the next campaign.
After the promotion, compare margin by item against the plan. Volume bought at a discount without margin is a donation.
Supplier Terms, Landed Cost and the Real Cost of a Carton
A carton of imported goods lands in Nairobi with a cost that is not the supplier’s invoice value.
Freight, insurance, duty, the 3.5 per cent import declaration fee, the 2 per cent railway levy and clearing charges all attach to it.
erp for retail in Kenya records those as landed cost components on the receipt, not as a general expense at month end.
If the cost sits in expenses, gross margin looks healthy while the business loses money on every case sold.
The three-way match is the control: purchase order, goods received note, supplier invoice. Pay only where all three agree.
Differences go to a hold queue with a reason: short delivery, price variance, damaged cartons, wrong item.
erp for retail in Kenya keeps the delivered-not-invoiced balance visible, so finance knows what it owes before the invoice arrives.
Payment terms belong on the supplier record: thirty days from invoice, sixty from statement, or cash on delivery.
Rebates and settlement discounts need their own ledger. Two per cent for payment in seven days is real income.
Consignment stock and sale-or-return goods must sit outside owned inventory, or the balance sheet overstates what the business holds.
erp for retail in Kenya flags stock you hold but do not own, and reports it separately at every count.
eTIMS Invoicing at the Till
Every VAT-registered retailer in Kenya now issues invoices through eTIMS, and the till is where that obligation meets a queue.
A supermarket cannot ask forty customers to wait while someone types a buyer PIN. The integration has to be invisible.
erp for retail in Kenya transmits invoice lines, tax treatment and totals to KRA, then prints the verification details on the receipt.
Tax treatment per item is not optional. Zero-rated flour, exempt agricultural produce and standard-rated soap cannot share a default.
Get that wrong and the return is wrong, even if the shop collected the right money from the customer.
Credit notes need the same discipline as invoices. A refund without a linked credit note leaves the VAT return overstated.
Connectivity fails. The till must keep trading offline, queue the invoices and transmit in order when the link returns.
erp for retail in Kenya should show queue depth on a dashboard, because a silent backlog is a penalty waiting for a date.
Test the reversal path before you need it. A cancelled sale at seven on a Saturday is not the moment to find the gap.
Document the control unit, its serial number and who holds the keys, in case an inspection arrives without warning.
Staff should know which receipt the customer keeps and which copy the branch files, because both are asked for during a check.
Reconciling M-PESA, Card and Cash Every Night
At nine at night a branch manager counts cash, prints the M-PESA statement and totals the card slips. Three numbers, one day’s trade.
M-PESA arrives as a settlement, not as a sale. The paybill statement shows gross collections, charges and the net credited the next day.
erp for retail in Kenya stores the transaction reference from the customer confirmation, so the sale matches the settlement line.
Card settlements behave the same way, with a merchant fee and a T+1 credit that never equals the day’s slips.
The reconciliation is three-way: till total, payment provider report, bank credit. Every shortfall has a name once you look.
Cash adds a physical step. The float, the pickup, the banking slip and the variance are four separate records.
erp for retail in Kenya separates over and short from sales, so a branch cannot hide a shortfall inside a busy Saturday.
Count cash in front of two people, sign the sheet, and bank the same day where the branch sits in a risky location.
Set a tolerance in shillings, not a percentage. A busy branch should not be allowed a larger absolute gap than a quiet one.
erp for retail in Kenya posts the variance to the branch, and the pattern over three weeks says more than any single day.
Watch the settlement lag around public holidays. Money collected on Friday can land on Tuesday, and the cash flow plan must know.
Replenishment Rules That Respect Shelf Space
A reorder point calculated from lead time, average sales and safety stock will still fail if the shelf holds only twelve units.
Ordering forty means twenty-eight sit in the back store, invisible, while the shelf looks empty at five in the evening.
erp for retail in Kenya should know shelf capacity per item per branch and cap the suggestion at what the branch can display and store.
Lead time in Kenya is not one number. Nairobi deliveries take a day; Kisumu or Malindi can take three, and the ferry adds more.
Set lead time per route, then let the system recalculate the reorder point whenever a route changes.
Push allocation beats pull ordering when supply is short. A central planner decides who gets the twenty cartons, not the loudest branch.
Dead stock needs a review date. Every item should show days since last sale, and a category manager should act at ninety.
erp for retail in Kenya can automate the seasonal part: school opening, December, Easter, and the rains that change what a kiosk sells.
Replenishment without a forecast is guesswork with better formatting. Even a simple twelve-week average improves the order.
Check the suggestion against the promotion calendar. Ordering to the base rate during a two-for-one week guarantees an empty shelf.
Agree who may change a reorder point. If every branch manager can edit it, the parameter becomes a mood rather than a policy.
Returns, Exchanges and the Reverse Supply Chain
A return is a sale running backwards, and most retailers only build the forward direction.
The customer arrives with a receipt, a faulty kettle and a reasonable expectation of a refund on the tender used to pay.
erp for retail in Kenya should force the refund to the original tender. Cash back for an M-PESA sale is how refund fraud starts.
Every return needs a reason code: faulty, wrong item, changed mind, damaged in transit, warranty.
The code drives the accounting. A faulty item goes to quarantine and then to the supplier, never back to the shelf.
erp for retail in Kenya links the customer return to a supplier return, so the credit note is claimed inside the contractual window.
Warranty claims need a serial number or an invoice reference, or the shop absorbs the cost of goods it did not sell badly.
Exchanges should create a new sale and a new eTIMS invoice, with the return documented separately against the original.
Track return rates by item and by branch. A spike is usually a supplier problem, a pricing error or internal fraud.
Publish the policy at the till in plain language. A customer who understands the rule argues less, and staff stop improvising.
Keep the returned goods physically separated until they are inspected. A carton that goes straight back to the shelf will be sold twice.
Reconcile the returns account monthly against the supplier credits received. An unclaimed credit is a donation with paperwork.
Month-End Close Without a Warehouse Freeze
Month end in retail should not require a warehouse freeze, yet many finance teams still stop dispatch for two days to count.
A better close is a calendar: cut-off at six on the last day, counts on agreed lines, and a five-day timetable everyone has seen.
erp for retail in Kenya holds what makes a fast close possible: accruals, stock valuation, cash in transit and wastage, all from one ledger.
Goods received but not invoiced is the accrual that keeps supplier balances honest and margin correct in the closing month.
Valuation must use a stated method, weighted average or FIFO, applied to every location without exception.
erp for retail in Kenya should produce the valuation by location on demand, so the count team and the accountant read one report.
Cash in transit is the M-PESA settlement not yet banked. It belongs on the balance sheet, not in a suspense account.
Close the subledgers in order: sales, stock, purchases, payments, then the general ledger. Out of order, every difference doubles.
erp for retail in Kenya keeps an audit trail of who posted what after cut-off, which is the first question any auditor asks.
Review the variance report before the ledger locks. Adjustments signed after the numbers are published undermine the whole control.
Barcodes, Variants and the Item Master Nobody Owns
The item master is the least glamorous part of retail and the one that decides whether the rest works.
A barcode is a promise: this code, this product, this price, this tax treatment, every time it is scanned.
erp for retail in Kenya should own one code per sellable unit, whether it comes from a supplier or from your own butchery scale.
Variable-weight items need weighed labels with a PLU, not a handwritten price on cling film.
Fashion and electronics bring variants. Size, colour and model are attributes of one style, not three unrelated items.
erp for retail in Kenya handles that with a parent item and a variant matrix, so replenishment and reporting roll up without duplication.
Tax class, unit of measure and pack size belong in the master. A branch should never guess whether an item is zero-rated.
Duplicates multiply during busy openings. Two codes for the same soap means two stock figures and one empty shelf.
Give the master a named owner in head office and a weekly merge report, or entropy wins within a year.
erp for retail in Kenya with a controlled request form and an approval step stops the till becoming an item creation tool.
Photograph the product and record the supplier against every new line. Six months later that image settles an argument at the counter.
Counting Stock Without Closing the Shop
A full stock take on a trading Saturday costs more in lost sales than it recovers in accuracy.
Cycle counting avoids that: a slice of the range every day, chosen by value and risk rather than convenience.
erp for retail in Kenya classifies items by annual value and movement, then schedules counts accordingly.
A items weekly, B monthly and C quarterly is a workable default for a supermarket of four hundred square metres.
Count blind. The counter should not see the expected quantity, or the count becomes a confirmation exercise.
Count by location, not by item. The same product in the back store and on the shelf are two counts and two numbers.
erp for retail in Kenya posts the variance only after a recount and a manager’s approval, with a reason code attached.
Small variances should be tolerated and watched. A branch with a 0.1 per cent gap every week has a control problem, not a counting problem.
Report the count result against the category, then let the trend decide where the next audit goes.
Never let the person who owns the stock approve their own adjustment. That single rule prevents most quiet losses.
The Branch Manager’s Daily Report
A branch manager opens the day with five questions: what sold, what did not, what is missing, who was on shift and what is in the drawer.
erp for retail in Kenya answers them on one screen at seven, before the first customer and before the excuses.
Sales against the same weekday last month matters more than yesterday, because Saturday is not Tuesday.
Voids, no-sales, refunds and price overrides are the four lines that reveal a till problem before it becomes a loss.
Stock-outs on the top fifty lines should be listed by name, not as a percentage, so somebody can act on them.
erp for retail in Kenya shows the cash position including M-PESA settlement due, which is often larger than the notes in the drawer.
Basket size and items per basket tell a manager whether the promotion changed behaviour or only discounted it.
The report should end with three actions and an owner, otherwise it is a dashboard and not a management tool.
erp for retail in Kenya emails it at six, so the meeting starts with decisions instead of data collection.
Keep the format stable for a year. A manager who learns the report in January reads it properly by March.
Credit Customers and the Ledger Beside the Till
Half the customers at a hardware branch are on account: contractors, estates, schools and small developers.
Their ledger does not belong in a book beside the till, where one person can read it and nobody can age it.
erp for retail in Kenya keeps credit customers in the same system as cash sales, with limits, terms and statements generated on a date.
A credit limit is only real if the till enforces it. A warning that can be clicked past is a suggestion.
Statements should go out on the first of the month, and the ageing should be visible to the salesperson who owns the account.
erp for retail in Kenya links the invoice to the delivery note, so a dispute about what arrived is settled from one document.
Cheques and post-dated instruments need a register. A cheque in a drawer is not cash and should not reduce the balance.
Stop-supply rules should trigger at a set number of days overdue, not at the finance officer’s discretion.
erp for retail in Kenya flags accounts that exceed both their limit and their terms, which is where the real exposure sits.
Agree the collection sequence in writing: call at seven days, letter at fourteen, stop supply at thirty. Then follow it without exception.
Loss Prevention Beyond the Camera
Cameras record what happened. They rarely tell you where the money went.
The till produces a better trail, if anyone reads it: voids by cashier, refunds without a receipt, discounts by hour.
erp for retail in Kenya should flag a refund above a threshold, a void after tender and a price override below cost, in real time.
Sweethearting is the common pattern: a cashier scans three items, charges for two, and a friend walks out with the third.
Only an exception report catches that, because the till total still matches the drawer at the end of the day.
erp for retail in Kenya ties every transaction to a cashier, a shift and a terminal, so a pattern has a name attached.
Receiving is the other soft spot. Collusion between a driver and a store clerk inflates quantity on the goods received note.
Weigh, scan and photograph high-value deliveries, and rotate the receiving staff every quarter.
erp for retail in Kenya compares delivered quantity with the supplier invoice and the branch’s sales, which closes the loop.
Investigate patterns, not people. An accusation without a report damages a branch more than the loss did.
When the POS and the ERP Disagree
By ten at night the till and the ledger should agree. When they do not, the difference is usually one of five things.
The price file did not sync, the offline queue replayed a sale twice, or the day boundary fell between two clocks.
erp for retail in Kenya should reconcile at transaction level, not just totals, so a mismatch becomes a list of receipts.
Offline trading is necessary in Kenya. A fibre cut or a power outage should not stop a supermarket.
But offline sales need a sequence number and a timestamp, and the system must reject duplicates on upload.
erp for retail in Kenya with an offline mode that posts to a queue will still lose data if the terminal is wiped before sync.
Check the sync dashboard every morning. A branch that has not synced since Friday is trading blind.
Price file mismatches usually come from a manual till edit. Remove the ability and the whole class of error disappears.
erp for retail in Kenya should own the price, the tax and the promotion, and the till should display that decision rather than make it.
Log every override with a user, a time and a reason. The log is the only defence when a customer disputes a charge.
Rolling Out Branch by Branch
A retail rollout fails for boring reasons: opening stock nobody counted and a printer that cannot reach the network.
Start with one branch, preferably the messiest, because a clean pilot teaches nothing about a real one.
erp for retail in Kenya needs a counted opening balance, signed by the branch manager and the count team, before the first sale.
Clean the item master before the pilot, not during it. Merging duplicates later costs far more than a week of preparation.
Hardware is part of the project: scanner, till, drawer, thermal printer, UPS and a second network path.
erp for retail in Kenya on a single Safaricom line is a single point of failure. Add a second provider or a 4G router.
Train by role, not by module. A cashier needs forty minutes on returns and tenders, not a day on general ledger.
Run parallel for two weeks at most. Longer and the branch keeps two habits, and the old one wins.
erp for retail in Kenya cut-over should happen on a Monday, after a weekend count, with a super-user on the floor for five days.
Then roll in order of complexity, and let the first branch’s super-user train the second.
What to Fix Before the Next Peak Season
December and the school opening in January will find every weakness in the system and hold it up in public.
Start in October. Load-test the tills, confirm supplier lead times and freeze the price file a week before the rush.
erp for retail in Kenya should handle the volume, but only if the stock build is real and the transfers dispatch on time.
Temporary staff need a thirty-minute session on the till and a named supervisor, or the voids report will look like theft.
Agree a support rota in writing, including who answers at nine at night on 24 December when a printer fails.
erp for retail in Kenya with a tested backup and a spare terminal turns a bad evening into a slow one, not a closed shop.
Book the stock count for early January, after the returns settle and before the new season’s deliveries land.
Review the season by category in February, using sell-through and stock turn rather than impressions.
The same ledger that ran the season also explains it, which is why the review takes an afternoon instead of a fortnight.
Write down what broke, with dates and names, and fix three items before Easter. That habit is worth more than any upgrade.
