Inventory · Alerts · Ledger

Know what every outlet has on the shelf — before it runs out.

BluYards is a multi-outlet inventory platform with a full double-entry ledger built in. Stock moves, alerts fire, and the books post — from one document, in one transaction, with a trail behind every number.

  • Tally import, two-way safe
  • Open stock pools
  • Append-only stock ledger
  • No Redis, no broker
The BluYards dashboard: network KPIs, a map of outlets coloured by stock health, and a live alert feed
One dashboard for the whole network — health bands on the map, KPI trends from nightly snapshots.
2,000
SKUs per outlet
the scale the inventory matrix and alert sweep are built and tested against
1M+
stock level rows
threshold recomputation stays set-based in SQL at this size
<1s
alert to inbox
alerts are evaluated inside the movement transaction and fan out on commit
500
movements per API call
all-or-nothing batches, idempotent, deduplicated per outlet

Figures describe the platform's tested capacity and the demo dataset that ships with it.

Visibility

Every outlet, every SKU, on one screen

The inventory matrix holds 2,000 SKUs per outlet without paging, and updates live as movements land. Each cell carries on hand, in transit, days of cover and a health band — click one for the ledger behind the number.

  • Virtualised grid that holds 2,000 SKUs per outlet without paging
  • Cells carry on hand, in transit, days of cover and a health band
  • Server-Sent Events push each change; changed cells flash rather than re-render the page
  • Drill into any cell for the movement ledger behind the number
How the matrix works
The inventory matrix: outlets down the side, products across the top, each cell coloured by stock status
The alerts centre listing low, critical and out-of-stock alerts with severity and age

Alerts and books

An alert that reads as a story, and books that already agree

One alert follows an item from low to critical to out and back again, escalating by region and de-escalating in place. Meanwhile every inward and outward document posts its own voucher, so the ledger is never a month behind the shelf.

  • Thresholds resolved global → category → product → outlet, stored in units
  • Hysteresis on resolution, so alerts stop flapping at the reorder point
  • Trial balance, P&L, balance sheet and ageing from posted vouchers only
  • Import masters and the day book from Tally; re-import safely any time
Inside the ledger

Who it is for

Four jobs, one system

Multi-outlet retail

Know which shelf is empty before the customer does

Chains running ten to a few hundred outlets, where head office cannot phone every store and the POS only reports what sold, never what ran out.

Distribution and wholesale

Dispatch against demand, not against a spreadsheet

Warehouses serving outlets or dealers, where the cost of a stockout is a lost order and the cost of overstock is cash on a pallet.

Finance and accounts

The books agree with the shelf, because they come from the same document

Teams who keep their statutory books in Tally and are tired of re-keying the operational side into it.

Operations and audit

Every number has a document behind it

Anyone who has had to explain a variance six weeks later, with nothing to go on but a changed cell.

See it by role

Integrations

It fits the systems you already run

A POS that retries, a Tally company your accountant keeps, spreadsheets that still arrive by email — all of it has a supported path in.

Tally / TallyPrime

Masters and day book, over the HTTP gateway or an XML export

Any POS

REST API with idempotent, deduplicated movement batches

CSV

Sales, stock counts and the product catalogue

Webhooks

Signed, retried, with a circuit breaker

Email / SMS / WhatsApp

One delivery log across every channel

PDF & CSV export

Every report, server-rendered

See it against your own numbers

Bring a product list and a week of sales. We will load it, set thresholds with you, and show you which shelves would have been empty. Built and supported by BluMargins Technologies.