Skip to content
Iterna
Retail & multi-branch

Retail and multi-branch management software

Retail gets hard at the second branch. One shop can run on a POS and a stock sheet. Two shops introduce transfers, branch-level reporting, and the question nobody can answer confidently — how much of this do we actually have, and where is it?

Tell us your problem

How this usually runs today

  • Each branch reporting in its own format, consolidated manually
  • Stock counts that never quite reconcile
  • Transfers between branches recorded in a chat and forgotten
  • Loyalty on a card the customer has lost
  • Online and offline inventory treated as two separate businesses
  • Staff performance measured by whoever shouts loudest

What we’d build

  • Inventory

    One truth across branches and channels, by variant.

  • Transfers

    Requested, approved, in transit, received, with the discrepancy recorded.

  • Stock takes

    Cycle counts that produce a variance report, not an argument.

  • Multi-branch reporting

    The same numbers, the same way, every branch.

  • Loyalty

    Points or stored value that works at any branch and online.

  • Staff

    Rosters, attendance, and sales attribution that survives scrutiny.

  • Purchasing

    Reorder points based on what actually sells where.

The parts that are harder than they look

  1. 01

    Variants multiply faster than anyone plans for.

    Size, colour, pack size, bundle. Get the variant model wrong at the start and every report downstream is wrong in a way that’s expensive to unpick.

  2. 02

    Transfers are a state machine, not a form.

    Requested, approved, dispatched, in transit, received, short. Most systems model the request and the receipt and lose everything in between, which is exactly where stock goes missing.

  3. 03

    Online and offline stock allocation is a business decision the software has to express.

    Do you ring-fence stock for the webstore, share it, or allocate by branch? All three are valid, and the system has to support the one you chose without a rebuild when you change your mind.

  4. 04

    Loyalty across branches means one customer identity.

    That sounds obvious and it’s the reason most loyalty programmes stay per-branch. Merging duplicate customers created at three counters is real work.

Proof

We haven’t published a project in this sector yet.

What we have done is build an operations platform that handles rosters, attendance, commission and statutory payroll for a real business — the same problems in a different setting.

That case study is here.

See the Operiq case study

FAQ

Questions we get asked

  1. 01

    Can it work with our existing POS or e-commerce platform?

    Usually, where those platforms offer a way in and out. Keeping the till your staff know and building the inventory, transfers and reporting around it is often the cheaper path.

  2. 02

    How does stock stay accurate across branches?

    By modelling the movement rather than the count. Every sale, transfer, receipt and adjustment changes the number, so a stock take produces a variance you can investigate instead of a new figure that overwrites the old one.

  3. 03

    Can loyalty points be used at any branch?

    Yes, and that depends on one customer identity across branches rather than a card per counter. Merging the duplicates that already exist is part of the work.

  4. 04

    Can head office see everything while each branch sees only itself?

    Yes. Access by role and by branch is part of the data model from the start, not a filter added to a report later.

  5. 05

    What if we add branches later?

    A new branch should be configuration, not a project. That is largely decided by choices made in the first version, which is why we ask early how many branches you expect rather than how many you have.

Tell us how many branches and how stock moves between them.

Where the counts disagree, what a transfer looks like today, and what head office cannot see. We will tell you what to build first.

Tell us your problem