Skip to content
EnovveEnovve home
How it works

A scan becomes a fact. The fact never gets overwritten.

The Enovve mechanism end to end: a scan becomes an event, the event survives bad signal in a local queue, the ledger appends it, and every surface reads the same projection.

How it works

One scan, five stops, no second set of books.

This is the whole mechanism. Select any stage to see what it does and why it is built that way.

3 · The ledger is append-only

Events replay into the ledger in order. Because it only ever appends, the current stock position is a computed view rather than a number somebody overwrote — which is what makes an audit trail possible at all.

The reasoning

Four decisions that shape everything else.

Each of these is a trade-off we made deliberately. Here is what we chose and what it costs.

Why offline-first is the whole design, not a feature

Retail software fails in stockrooms. Not dramatically — it just hangs on a write, the associate taps again, and now the count is wrong. Every subsequent decision inherits that error.

Enovve inverts the order of operations. A scan is written to a durable on-device queue and acknowledged to the user in the same frame. The network is never in the critical path of the interaction.

Each queued event carries an idempotency key, so when the queue drains — after a reconnect, a retry or a crash — the ledger applies it exactly once. That single property is what allows the app to promise both 'never blocks' and 'never double-counts', which are usually in tension.

Why the ledger only ever appends

Most retail systems store a stock number and overwrite it. When the number is wrong, the evidence of how it got wrong has already been destroyed.

Enovve stores the events instead. Current stock on hand is a projection computed from the event stream, not a field somebody updated. Nothing is overwritten, so nothing is lost.

The practical payoff shows up during a shrinkage investigation. Instead of reconstructing a quarter from receipts, you query: who scanned this EPC, on which device, at which second, and what did the position look like immediately before and after.

Why the dashboard and the assistant can't disagree

A familiar failure: the dashboard says one number, the BI tool says another, and the meeting becomes an argument about data rather than a decision.

That happens when surfaces read different copies. In Enovve the dashboard tile, the assistant's answer and the public API response are three readers of the same projection.

It also means the assistant is not doing anything magical. It translates a question into a query against the same view you are already looking at, and reports the figures it used so you can check it rather than trust it.

Why Enovve does not want to be your ERP

Replacing an ERP is a multi-year programme with a real chance of failure. Almost nobody who needs better tooling on the shop floor also needs that.

So Enovve takes the other half of the problem. Your ERP stays the system of record for finance; Enovve is the system of engagement the floor actually touches, and writes back to it.

Integration is bidirectional: Enovve pushes transactions and adjustments outward, and subscribes to catalogue, price and purchase-order changes inward. Everything the app does is also available over the public API and as webhooks.

A day on the floor

What actually changes, hour by hour.

The clearest way to explain an operations platform is to follow one shift through it.

  1. Delivery lands at the back door

    Products

    The associate walks the pallet with the reader running. UHF picks up the whole cage in one pass; the receipt reconciles against the purchase order before the driver has left.

  2. A customer asks for a size 42

    Products

    One scan of the shelf label shows on-hand across every store and the reserved pool. No walk to the terminal, no phone call to the other branch.

  3. Sale closes in the aisle

    Sell

    Card is taken on the device beside the fitting room. The line writes to the ledger as it is paid, so the dashboard's revenue tile moves before the customer reaches the door.

  4. Cycle count on Zone B, store still open

    Products

    Forty minutes of counting during a quiet period. Two variances surface immediately — socks are four short, daypacks are four short — instead of appearing in a quarterly stocktake.

  5. Signal drops in the stockroom

    Offline queue

    Nothing changes for the associate. Scans acknowledge locally and queue. When the device rejoins the network four minutes later, the queue drains in order and nothing double-counts.

  6. Manager asks what to reorder

    Ask Enovve

    Rather than building a report, they ask. The assistant reads the same ledger the dashboard does and names three lines with the velocity behind each.

  7. The day closes itself

    Ledger

    There is no end-of-day reconciliation, because there was never a second set of books to reconcile. The ERP already has every line.

Boundaries

What the platform will and won't do.

The limits are as much a part of the design as the features.

Role-scoped access

A seasonal associate, a store manager and a regional director see three different applications on identical hardware. Scope is enforced server-side, not by hiding buttons.

Audit trail on every write

Who, which device, which second — for every event in the ledger. Retained and queryable rather than rotated out of a log file.

Assistant boundaries

The assistant reads only the tenant's own operational data, scoped to the asking user. It answers; it does not take actions without an explicit confirmation step.

Device management

Zero-touch enrolment, remote configuration and remote wipe. A lost handheld is a hardware cost, not a data incident.

Rollout

Live in the aisle, not in a steering committee.

Enovve sits on top of the systems you already run, so going live is a configuration exercise rather than a migration.

  1. 01

    Plug into your stack

    Enovve connects to the ERP, e-commerce platform and payment provider you already run. No migration, no freeze window.

  2. 02

    Hand out the devices

    Rugged handhelds arrive configured and enrolled. An associate is productive after one shift, not one training week.

  3. 03

    Work the floor

    Selling, counting and fulfilment happen in the aisle. Every scan updates the same ledger the dashboard reads.

  4. 04

    Close on real numbers

    Revenue, ticket, stock position and exceptions are current to the last scan — not to last night's batch.

See it running on a real shop floor.

30 minutes, your catalogue, your questions. We will show you the handheld, the ledger behind it and exactly what it takes to connect your stack.

Book a demo