Short answer. Convenience store software in Algeria in 2027 holds five things. A catalogue: one reference per product with its EAN, selling price, last purchase price, department, and for fresh goods its lot and expiry date; quick keys for bread and loose goods; weighed items whose line comes from the scale. A till that sells without a server: the database of prices, promotions and stock is on each till, the ticket is numbered by the till’s sequence, and what must go to the server waits in a queue, with a unique id per ticket, without duplicate or loss. Stock that is a journal of movements, per ticket and per receipt, with lots and expiry dates, and a supplier receipt validated before new purchase prices enter the margin. A closing blind-counted, till by till, with a named gap, QR and cards matched, the credit book, the deposit prepared. And a management view that reads per department the sales, the margin on the last purchase price, close expiry dates, stock-outs, and gets an order proposal, not a guess.
This guide is for the manager of a one-hundred to four-hundred-square-metre store with one or several tills, the group opening a second one, the wholesaler equipping its retailers, and the owner living in France who follows the store from afar. In the common description, a convenience store is a neighbourhood shop selling mainly food, usually self-service, of the order of one hundred to four hundred square metres depending on the country; an EAN-13 is a thirteen-digit barcode, prefix, company, article, check digit, read by the till’s scanner; for weighed items, scales generally print a store-specific code the till can read, and the exact format depends on the scale installed. This guide builds the application around those three objects, the reference, the ticket and the lot, with what is specific to Algeria: cash collection, the neighbour’s credit book, the network that drops, and the remote manager. It does not cover invoicing, labelling or hygiene rules: the application applies what the manager writes, and the expiry and margin thresholds in the example are theirs.
One till ticket with the network down: scan, scale, promotion, total, sync
The figure follows a seven-line ticket during a twenty-eight-minute network outage, from the first scan to the sync.
The scan: the barcode is read, the price is found in the till’s local database, twelve thousand four hundred references, in forty milliseconds; there is no server call to sell, and there never is, network or not, per the offline application guide. The scale: the tomatoes are weighed, the scale prints its code, the till reads it and creates the line, one kilo two hundred and forty grams at one hundred and eighty per kilo. The promotion: six yoghurts, six-for-five rule, evaluated in fifteen milliseconds by the engine of the promotions guide, with the margin guard computed on the last purchase price; the cashier sees the final price, the manager sees in the evening what the promotion cost. Stock: each line reserves locally, with lot and expiry when the reference has them. The ticket: numbered by the till’s sequence, T-0417-C1, printed, drawer opened, one point eight seconds in all; payment in cash, by QR, by card or on the credit book follows the same rules as the till payments guide.
The sync: thirty-one tickets were queued between 10:52 and 11:20; at 11:21 the network returns and they leave, all of them, once, because each ticket carries a unique id and the server ignores what it has already received; if the till restarts during the outage, the queue is on its disk. Central stock is up to date at 11:21, and the manager in Lyon sees the whole morning, not a twenty-eight-minute hole. Products, prices and figures are a constructed example.
«The till sells without a server: prices, promotions, scale and stock are decided locally, the ticket is numbered on the spot; the network only carries what was sold, and it can wait.»
Convenience store software, in five layers
The till is the accented layer: it carries a local database, numbers on the spot and queues; everything else is only a reading.
Catalogue. One reference per product: EAN, selling price, last validated purchase price, department, VAT as written by the manager, lot and expiry for fresh goods, quick keys for what has no code, weighed items; a changed price is logged, who and when, per the roles guide. Till. The local database is copied to each till at opening, prices, the day’s promotions, stock; the till sells, numbers, prints, and queues; QR, card, cash, credit book with a ceiling per the customer credit guide, loyalty points per the loyalty guide; nothing waits for the server. Stock and receipt. Stock is the journal of the false stock guide: every ticket and every receipt are movements, with lot and expiry; the supplier receipt is validated line by line, and a changed purchase price is flagged before entering the margin; the cycle count counts one department a day.
Closing. As in the till sessions guide: float, blind count per till, named gap against a written threshold, QR and cards matched, credit book, bank deposit prepared. Management. The board of the dashboard guide: sales and margin per department, close expiry dates, stock-outs, order proposal per the replenishment guide, WhatsApp alerts; export to the accountant per the integration guide; and for the manager in Lyon, everything the running your store from France guide describes, read from the same tickets.
The manager’s board: departments, margin, expiry, stock-outs, till closing
The figure is what the manager reads at 21:10, on site or from Lyon: five departments, two tills, one receipt waiting.
Departments: one million one hundred and eighty-four thousand dinars of sales on six hundred and forty tickets, average basket one thousand eight hundred and fifty; grocery makes thirty-six percent of sales at twelve percent margin, fresh twenty-six percent at eighteen, bakery and snacks ten percent at twenty-eight; margin is computed on the last validated purchase price, not on a January price. Expiry: thirty-four fresh items, eight lots, expire within three days; the application proposes a promotion with the margin guard, the manager accepts or not; twelve same-day bakery items are expected, not an alert. Stock-outs: thirteen references, seven in grocery, to order tonight; the order proposal is ready at 21:15 with supplier lead times.
Closing: till 1 blind-counts five hundred and twelve thousand against five hundred and twelve thousand three hundred expected, a three-hundred-dinar gap, named, under the written threshold; till 2 balances; one hundred and eighty-three thousand of QR and cards matched; fifty-six thousand on the credit book of twenty-three customers, with their ceilings; nine hundred and forty thousand prepared for the bank. The receipt: forty-eight lines delivered in the morning, three purchase prices changed, two lines missing; until it is validated, the new prices do not enter the margin and the missing lines are not in stock. Departments and figures are a constructed example.
«The manager reads per department the sales, the margin on the last purchase price, the close expiry dates and the stock-outs; the till is blind-counted, the gap is named, and the evening order is proposed, not guessed.»
Putting a convenience store under software, in six beats
Installing the tills is the accented beat: the first day sold without a server is what makes the rest accepted.
Take over the catalogue: existing references, often a till file or an Excel sheet, with EAN, price, department; quick keys; weighed items with the scale’s code format; opening stock counted department by department. Write the rules: promotions and margin guard, credit book and ceilings, tolerated till gap, expiry threshold, minimum margin per department, who may change a price; with the manager, without code. Install the tills: local database, scanner, scale, printer, drawer, and one day of dry-run sales alongside the old till.
Receive and count: receipt validated line by line, lots and expiry, cycle count of one department a day. Close: blind count, gap per till, QR and card matching, deposit. Read the board: departments, margin, expiry, stock-outs, proposed order, WhatsApp alerts to the manager, Saturday review.
Six real situations, and what the application does
Each row is a sentence heard in a convenience store, and the answer is a local database, a validated receipt or a named closing, not a more attentive cashier.
The network drops mid-morning: the till does not notice; prices, promotions, stock and ticket number are local; the queue leaves on return. The supplier changed its prices: the receipt is validated line by line, the changed price is flagged, and the department’s margin is recomputed the same day, not discovered at year end. Yoghurts expire on the shelf: lot and expiry were entered at receipt; the alert goes out three days before; a promotion is proposed with the margin guard; what remains is written off with a reason.
The till does not balance: each till has its session and its blind count; the gap is named, till and cashier, and compared with the written threshold. The neighbour pays at month end: the credit book is in the application, per customer, with a ceiling, each ticket linked, and a WhatsApp reminder before month end. The manager is in Lyon: they read the day’s board per department and till, and get a WhatsApp alert on gap, expiry and stock-out; they no longer call in the evening to ask for the figure.
Convenience store software in 2027, in weeks
Six weeks, the first without code, and two for the tills, because stock, closing and the board are only readings of what the tills and the receipt write.
- What the manager sees: in the evening, sales and margin per department, the gap per till, items expiring within three days and stock-outs; in the morning, the receipt to validate; on their phone in Lyon, the same.
- What the store stops doing: stopping sales when the network drops, discovering a changed purchase price at year end, letting goods expire on the shelf, looking for which till is short, keeping the credit book on paper.
- What is measured: sales and margin per department on the last purchase price, tickets and average basket, gap per till and cashier, items written off for expiry, stock-outs, receipt lead time, queued tickets per till.
Week 1, catalogue and rules: references taken over, EAN, prices, departments, quick keys, weighed items; promotions, credit, tolerated gap, expiry and margin thresholds. Weeks 2 and 3, tills: local database, scanner, scale, printer, drawer; queue, unique id, promotions, credit book, QR and card; dry-run day then switch-over. Week 4, stock and receipt: movement journal, lots and expiry, validated receipt, cycle count.
Week 5, closing: blind count, gap per till, matching, deposit. Week 6, management: board per department, expiry, stock-outs, order proposal, alerts, accounting export. A store opening a second shop keeps the catalogue and rules, adds tills and a board per shop; a pharmacy follows the same path with its lots, described in the pharmacy software guide.
- Does convenience store software in Algeria start with stock?
- No, with the till. If the till does not sell when the network drops, nothing else will be accepted; and if the ticket is not numbered on the spot with a unique id, stock will be wrong. The local database on each till, prices, promotions, stock, and the queue to the server are the first thing built; stock, receipt and the board read what the tills write.
- What does the till do when the network is down for two hours?
- It sells as usual: prices and the day’s promotions were copied at opening, stock is reserved locally, the ticket is numbered by the till’s sequence. Tickets wait in a queue on the till’s disk; when the network returns they leave once each, and the server ignores what it has already received. If the outage lasts until evening, closing happens anyway, and the sync the next day.
- How do weighed items go through the till?
- The scale prints a label with a code the till can read, carrying the reference and the weight or price; the exact format depends on the scale installed, and it is configured once at set-up. The till creates the line at the catalogue’s price per kilo, and the stock movement is in kilos.
- How is the margin computed?
- On the last purchase price validated at receipt, reference by reference; a receipt with a changed price is flagged, and the price enters the margin only once validated by the manager. The evening board shows margin per department on the day’s sales, and the promotion engine’s margin guard uses the same price. Margin is not a percentage typed in January.
- And lots and expiry dates?
- Entered at receipt for references that have them, fresh goods above all; the till notes the lot sold when known; the alert goes out at a number of days written by the manager, three in the example; a promotion is proposed with the margin guard, and what remains at the date is written off with a reason. Labelling and hygiene rules are for the manager and counsel, not for the application.
- Does the neighbour’s credit book fit in the application?
- Yes: one customer, a written ceiling, each ticket put on the book linked to the customer, a WhatsApp reminder before month end, and the settlement collected like any other payment with a receipt. The book is in the evening closing, apart from cash, and the manager sees balances per customer.
- How long to put this in place?
- Six weeks in the standard calendar, the first without code and two for the tills. A one-till store with a clean catalogue takes less; a ten-till shop with several scales, a lot of fresh goods and a second site takes more, the time to take over the catalogue and write each department’s rules.