Skip to main content
Retail

A shelf is run by the number not by instinct

We implement retail systems from the till through stock, pricing, promotions and channels — sized to your store: a single shop starts with a clean catalogue and a till that reconciles, a chain needs unified pricing and per-branch reporting, and a multi-channel retailer needs one stock serving the shelf and the website together. What they share: a shelf whose number cannot be read is either bought twice or never bought at all.

Request a store assessmentSee the store formats
  • Four store formats, four scopes
  • A plain word on what does not fit your size
  • One stock for shelf and website
  • We store no card data
  • Durations are planning ranges, not commitments

Direct answers

The questions asked first

How do you treat a single shop, a chain and a multi-channel retailer differently?

By fit rather than price: a single shop suffers because everything lives in the owner’s head — so it starts with a clean catalogue with barcodes and units, a till that reconciles daily, a known cost, and installing loyalty or multi-warehouse transfers is waste. A chain suffers from disunity: different prices per branch, undocumented transfers, and reports collected into a spreadsheet at month-end. A multi-channel retailer suffers because shelf and website do not know each other: an item sold twice because stock lives in two systems, and an online return never entered against the shelf. In the assessment we tell you which of these you are.

Do you guarantee higher sales or more footfall?

No, and no system can: sales follow location, price, offer, competition, season and shopper behaviour, and retail shifts for reasons a program does not own. What we do commit to is that your decisions rest on correct figures: a balance that matches physically, a margin computed on real cost, returns whose cause is known, and a per-branch report with one definition. The system removes the reasons you lose money without noticing — selling from a phantom balance, pricing below cost, invisible shrinkage — but it does not create demand.

Do you handle or store payment card data?

No. Card data never passes through our systems, is never stored and is never processed; the payment happens on the licensed payment provider’s terminal or gateway, and we connect only the result of that transaction to the system (amount, status, reference). That reduces your compliance scope, and you should ask your provider about its certification and level of compliance. We claim no compliance we do not hold, and we give no legal advice on data protection.

What usually stops retail projects?

Three things we see repeatedly, none of them technical: an unclean catalogue — duplicated or missing barcodes, mixed units and conflicting categories — which makes every report suspect; an uncounted opening balance, so the system is built on a quantity nobody trusts and it gets hand-adjusted from week one; and the absence of a decision owner for pricing and discounts — who approves an item price per branch, and who can stop a promotion? That is why we start with the catalogue, the count and a written assignment of permissions, before any promise about a report or a season.

Formats

Four store formats — and four different scopes

The same sector does not mean the same project. Read your format first, then what fits you — and, plainly, what does not.

Single shop or grocery

One or two tills · owner-run · hundreds to thousands of items

What it suffers from
Everything sits in the owner’s head: prices are memorised or written on the shelf, stock is judged by eye, purchasing happens when something runs out, and the till is reconciled at day’s end “if time allows”.
What fits it
A clean catalogue with barcodes, units and cost; tills that reconcile daily; pricing managed from the system rather than from a shelf label; an alert when an item runs out; and a simple daily report the owner reads on a phone.

What does not fit you: A loyalty programme, multiple warehouses with transfers, several price lists and complex seasonal planning: each adds setup and entry burden a single-till shop cannot carry, and gets abandoned after months so everything returns to the label and memory.

Branch chain

Several branches · transfers between them · dozens of users

What it suffers from
Unity is missing: an item’s price differs from branch to branch, transfers are recorded on paper or not at all, and branch reports are collected into a spreadsheet at month-end so the error appears after a full month of repetition.
What fits it
One price list with clear rules on who may change it; stock per branch with documented transfers; a count per branch with a named owner; daily branch reporting on one definition of sales, margin and returns; and till reconciliation per shift.

What does not fit you: Switching all branches on in one day, patching the system core instead of using the standard extension path, and building complex executive dashboards before branch balances actually match.

Multi-channel retailer

Shelf, branches and a website · the same items across channels

What it suffers from
Shelf and website do not know each other: an item sells twice because stock lives in two systems, online orders are prepared by hand, an online return is never entered against the shelf so differences swell, and promotions are run in two places.
What fits it
One stock serving shelf and website, quantity reserved at order time to prevent overselling, documented picking and shipping from the branch, returns entered against the same balance, pricing and promotions from one source, and a sales report combining channels without double counting.

What does not fit you: Keeping separate stock per channel (which is the root of overselling), launching loyalty before the customer is unified across channels, and opening a new channel before the existing channel’s balances match.

Serialised retail (durable goods)

Electronics, appliances or furniture · high-ticket sales · warranties and service

What it suffers from
The item is not just a number: it has a serial or IMEI, a warranty, a supplier and a date, it goes for service and comes back, and it may be replaced. Without tracking, warranty and replacement become a paper chase, and the true cost of the unit is unknown.
What fits it
Serial-level tracking of every unit from receipt to sale, a warranty and replacement record tied to the invoice, actual cost per unit, fault and return-rate reporting by supplier and item, and service linked to spare-parts stock.

What does not fit you: Starting with a loyalty programme before warranty is tracked, relying on the item code alone without a serial, and managing service in a file separate from stock so parts go missing with no cause.

The bands here are indicative guidance rather than an official classification, and the criterion is operational complexity: number of branches, number of items, number of selling channels, and whether transfers between locations are managed. A single store with thousands of items can be more complex than three branches with a hundred.

Symptoms

What usually shows up in retail

Eight recurring symptoms, each with a different root cause — which is why the treatment differs even when the complaint sounds the same.

A price that differs branch to branch

A price is updated in one branch and forgotten in another, the customer complains, and the difference surfaces on comparison rather than at the till.

Cause: no unified price list

The sheet balance does not match the shelf

The balance is hand-adjusted without a document, the difference appears at count time, and the buyer loses trust and measures by eye.

Cause: adjustments without documents

Shrinkage with no known cause

Everyone says there is shrinkage, but no record shows whether the cause is damage, entry error, theft or an unrecorded return — so the complaint is treated, not the cause.

Cause: movements not recorded

A till that does not reconcile daily

Reconciliation is postponed to week’s end, differences accumulate, and it becomes impossible to know which shift caused them.

Cause: deferred reconciliation

A catalogue with duplicated items

The same item under three codes, so stock is split between them and purchasing repeats because each record looks short.

Cause: an unclean catalogue

Selling from a balance that is not there

The website sells a quantity that physically sits in another branch, the shortage appears at picking time, and the order is cancelled.

Cause: two balances, one channel

Returns with no recorded reason

A return goes back to stock with no reason, so the same problem repeats without knowing whether it is sizing, a defect or a wrong online description.

Cause: reason not captured

Seasonal buying by estimate

Seasonal buying is built on last season as the team remembers it, so some items pile up while others run out at their peak.

Cause: no measured sell-through

Components

What we implement in the store

Eight components built in order according to your format; we do not implement all of them for a store that does not need them all.

A clean catalogue with barcodes and units

Merging duplicated items, correcting barcodes, units and categories, and loading cost — the base every later report rests on.

The base

Tills and daily reconciliation

Fast selling screens, several payment methods, shift close with documented cash reconciliation per user, and shift reports.

A till that reconciles

Pricing and promotions from one source

A price list with published rules on who may change it, and promotions scoped by date and branch that apply at every till with no manual update.

One decision

Branch stock and transfers

A balance per location, transfers between branches with a documented order and a named owner, and a reorder point for critical items.

Documented movement

Counting and the adjustment cycle

An opening count through system documents, periodic counting of sensitive items, and documented correction with a cause for each difference.

A difference with its cause

An online channel on the same stock

Connecting the website or marketplace to the same stock, reserving quantity at order time, picking from the branch, and returns entered against the balance.

No overselling

Customer and loyalty — after the base

One customer across channels with purchase history, then a loyalty programme and points rules — implemented after balances are correct, not before.

After balances are right

E-invoicing and management reporting

Issuing invoices through the statutory integration with a submission and response log, plus branch, margin, return and shrinkage reporting on one definition.

Documented compliance

Method

The method: from the catalogue to operation

Eight stages, each with a published output, starting with the catalogue and the count rather than with configuration — because a report on a corrupt catalogue multiplies the error.

  1. 01

    Assessment and format

    A visit covering branches, tills and items, establishing the real operating format, what runs on spreadsheets today, and where the largest financial risk sits.

    Output: an assessment naming your format
  2. 02

    Catalogue and cost cleanup

    Merging duplicates, correcting barcodes, units and categories, and loading real cost — because a margin without correct cost is a misleading number.

    Output: a trusted catalogue
  3. 03

    Opening count

    A physical count through system documents per location, with documented correction of differences before go-live rather than after.

    Output: a documented opening balance
  4. 04

    Configuration and testing

    Configuring tills, prices, taxes and payment methods, and running a full cycle on real data — sale, return, transfer and shift close.

    Output: one complete tested cycle
  5. 05

    Training on the process

    Training each role on its own process: the cashier on an error, the supervisor on reconciliation, the buyer on the reorder point — with illustrated guides left with you.

    Output: a guide per role
  6. 06

    Phased go-live per branch

    Going live on one branch first (or one shift), then expanding — not switching the whole chain on in a single day.

    Output: one branch running, then expansion
  7. 07

    Connecting channels and reconciling

    Connecting the online channel, payments and e-invoicing, reconciling stock balances with accounting, and closing a first full period.

    Output: a documented close with its differences
  8. 08

    Periodic improvement

    A periodic review: which items are slow, where shrinkage recurs, which promotion showed no readable effect, and which report nobody uses and should be dropped.

    Output: a periodic improvement report

The durations shown are planning ranges to help you build your schedule, not contractual commitments: the actual duration depends on how clean your catalogue is, how fast the count proceeds and how quickly your team approves adjustments, and can be affected by peak season.

Measurement

What we measure in a retail project

Indicators about data and daily operations, not a promise about market outcomes.

Balance accuracy

The gap between the physical count and the system balance, because every report after it — margin, purchasing, availability — rests on that figure.

Daily till reconciliation

The share of shifts closed with documented cash reconciliation, because deferred reconciliation hides a difference until its cause can no longer be found.

Item-data completeness

The share of items with a barcode, unit, category and correct cost, because an item without cost silently corrupts its own margin.

Recorded return reasons

The share of returns recorded with a specific reason, because an unknown cause repeats season after season.

E-invoice accuracy

The share of invoices accepted on first submission, and what was rejected with its reason from the log — because a rejected invoice is not a completed sale.

We announce no sales increase, footfall, basket size, shrinkage percentage or saving: those follow location, price, offer, competition and buying behaviour. What we measure is what belongs to our work: balance accuracy, daily till reconciliation, item-data completeness, recorded return reasons, and e-invoice accuracy.

Integration

Where the system lives in your store

We connect what you have instead of forcing its replacement, and we inspect every interface before promising it.

Odoo (tills, stock and accounting)

A till sale deducts from the same stock and creates the invoice and the accounting entry, so the work is not run in two systems.

The primary integration

The payment provider — with no card data

We connect the transaction result (amount, status, reference) to the system; the card is read on the provider’s terminal and never passes through our systems or gets stored.

An explicit boundary

Website and marketplaces

Connecting the store or marketplace to stock, prices and orders after inspecting its interface; if it has none we say so and promise no integration.

After the interface check

E-invoicing

Connecting invoice issuance to the statutory integration with a log of every submission and response, and reports for anything failed or rejected.

With a documented log

Suppliers and purchasing

Purchase orders, supplier lead times and prices, and a reorder point built on measured sell-through rather than an estimate.

Buying on a figure

Boundaries

Where our scope stops — written before you ask

In retail, a management system gets conflated with hardware, security and payments, so the separation is written out plainly.

Payment card data

We do not store, process or pass card data through our systems; payment happens on a licensed provider’s terminal or gateway, and we connect only the result.

Security systems and loss prevention

We supply no cameras, security gates or alarm devices and offer no guarding services; our role is to surface shrinkage in the numbers, not to prevent it physically.

Tills, printers and label equipment

We supply no devices, receipt printers, label printers or barcode scanners; we connect what you have after confirming compatibility.

Marketing and media buying

We run no campaigns, buy no advertising and guarantee no footfall or sales increase; we set up the measurement and present the figures as they are.

When what is needed falls outside our scope we say so in the assessment and refer a specialist instead of accepting it and learning at your season’s expense. That is written in the contract, not left to courtesy.

FAQ

Questions specific to retail

Direct answers on formats, scope, payments and what we do not guarantee.

How do you treat a single shop, a chain and a multi-channel retailer differently?

By fit rather than price: a single shop suffers because everything lives in the owner’s head — so it starts with a clean catalogue with barcodes and units, a till that reconciles daily, a known cost, and installing loyalty or multi-warehouse transfers is waste. A chain suffers from disunity: different prices per branch, undocumented transfers, and reports collected into a spreadsheet at month-end. A multi-channel retailer suffers because shelf and website do not know each other: an item sold twice because stock lives in two systems, and an online return never entered against the shelf. In the assessment we tell you which of these you are.

Do you guarantee higher sales or more footfall?

No, and no system can: sales follow location, price, offer, competition, season and shopper behaviour, and retail shifts for reasons a program does not own. What we do commit to is that your decisions rest on correct figures: a balance that matches physically, a margin computed on real cost, returns whose cause is known, and a per-branch report with one definition. The system removes the reasons you lose money without noticing — selling from a phantom balance, pricing below cost, invisible shrinkage — but it does not create demand.

Do you handle or store payment card data?

No. Card data never passes through our systems, is never stored and is never processed; the payment happens on the licensed payment provider’s terminal or gateway, and we connect only the result of that transaction to the system (amount, status, reference). That reduces your compliance scope, and you should ask your provider about its certification and level of compliance. We claim no compliance we do not hold, and we give no legal advice on data protection.

What usually stops retail projects?

Three things we see repeatedly, none of them technical: an unclean catalogue — duplicated or missing barcodes, mixed units and conflicting categories — which makes every report suspect; an uncounted opening balance, so the system is built on a quantity nobody trusts and it gets hand-adjusted from week one; and the absence of a decision owner for pricing and discounts — who approves an item price per branch, and who can stop a promotion? That is why we start with the catalogue, the count and a written assignment of permissions, before any promise about a report or a season.

Does a grocery or single shop need a full retail system?

No. It needs three things done well: a clean catalogue with barcodes and cost, a till that reconciles daily, and pricing managed from the system. Loyalty programmes, multiple warehouses and several price lists add setup and entry a single-till shop cannot carry and get abandoned after months. An abandoned project is worse than a small successful one — and we say so at assessment stage even when it means a smaller scope for us.

Do you work with our existing tills and printers?

Yes, where they are compatible: we inspect the devices, scanners and printers and how they connect before promising anything, and we say plainly if a device will not work with the proposed system. We neither sell devices nor maintain them — supply and maintenance come from a hardware vendor, which separates responsibility and speeds up repairs when a device fails.

What is out of scope?

Payment card data; security systems, cameras and loss prevention; supplying and maintaining tills, printers, label printers and scanners; running advertising campaigns and buying media; guaranteeing sales or footfall; system and cloud licences (contracted in your name); store fit-out and shelving; and legal advice on data protection. We say all of this at assessment stage, before the contract.

Which store format are you?

Tell us your branches, items and selling channels, and what is run on spreadsheets today, and we will come back with an assessment naming your format, the fitting scope — and what does not fit you.

  • An assessment that names your format
  • A written scope before any commitment
  • A plain statement of what is outside our scope
Request a proposal

Related topics

We are a systems implementation and integration company: we do not store, process or transmit payment card data (payment runs through a licensed provider), we supply no tills, printers or equipment, we provide no security systems, cameras or loss-prevention tooling, and we guarantee no sales increase, footfall, basket size, shrinkage percentage or saving. Commercial results depend on location, price, offer, competition, season and buying behaviour. Durations are shown as planning ranges rather than commitments, and the scope of work is written into the contract.