Supplier order
Dairy Farm Co → Station Road
6
Lines running out before delivery
- 2 860 €
- Order cost
- 410 €
- Margin at risk during delivery
Every morning at 06:00 it reads stock and sales in each store, finds the lines that run out before the next delivery and prepares the supplier order. You accept it and place the order as usual; marql checks the receipts. It answers for shelf availability.
Today
Thu, 5 Nov · demo chain · 6 stores
Proven, 30 days
4 120 €
Waiting for you
1
Revenue, 7 days
182 400 €
↗ 3.1 % vs prior 7 days
Week goal
Not set
Revenue by day, 14 days
Decisions · 1
AI Inventory Manager · AI
Supplier order
Dairy Farm Co → Station Road
Waiting since 06:00
Cost: purchase 2 860 €
ReviewDairy Farm Co → Station Road
6
Lines running out before delivery
The stores keep their POS and the ERP keeps the stock. marql reads both, makes the chain comparable, and brings you what is worth acting on.
Cloud POS, accounting and the web shop connect over their own APIs; an ERP inside your network is read by a small on-prem agent. Sales and stock arrive per store, per product.
Two spellings of the same yoghurt become one SKU, categories and VAT are mapped, and every store becomes a row in one table.
gate · reporting: A store that sent nothing is named as not reporting, not counted as a zero
Products about to run out, categories losing margin and stock that stopped selling are ranked by what each is worth, so the first line is the one to fix first.
The supply desk prepares a store order or a move between stores from demand and stock. Nothing is placed until someone approves it.
gate · approval: Not approved — nothing is ordered and nothing is written
The format in numbers
89.7%
2.8%
8%
Which store runs out first, which category is slipping, and where the money sits on the shelf.
What runs out next
Revenue at risk on products with less than a week of supply, store by store, and each product's days of supply grouped into low, dead and fine.
Out of stock, next to what it sells
A product with nothing left is marked out of stock beside its normal sales, for one store or the chain.
Category margin by store
Margin per SKU and per category, for one store and the chain, wherever a cost price exists.
Dead and excess stock
Stock with no sale in 30 days is priced as frozen capital; stock with more than 60 days of cover is marked as excess.
Stores against stores like them
Each store is compared with the stores of its own format, and once five or more compare, the gap to their median is priced per month.
Pace against plan, today
Set a target per store, and the day's view shows how many stores are behind pace and by how much at this hour.
Stock · demo grocery chain
data as of 07:50 · 6 of 6 stores reporting
| product · store | days of supply | sold / day | status |
|---|---|---|---|
| Semi-skimmed milk 1 LStation Road | 0.6 | 142 | low |
| Sliced rye breadRiverside | 0 | 38 | out |
| Olive oil 1 LOld Town | 214 | 0.4 | excess |
| Sparkling wine 0.75 LRetail Park | — | 0 | dead |
| revenue at riskproducts with less than 7 days of supply | 1 860 € / week | ||
a store with no stock is read on its own, never averaged into the chain total
Grocery runs on systems that already work. marql sits on top of them and says plainly what it does not see.
marql has read-only access to your POS and accounting and does not change a price, a stock level or an order there.
With e:corg 2.0, e:corg creates an approved order or transfer as its own draft.
marql reads system stock, not the shelf.
A product the books say is in the back room but nobody has put out is not flagged as out of stock: there is no shelf camera and no planogram audit.
Expiry dates and batches are not tracked.
Fresh lines are read by their sales and stock, not by their use-by date.
Margin needs a cost price.
Where neither the POS nor the accounting carries one, the product keeps its revenue and units and its margin is left empty rather than estimated.
Replenishment is a recommendation.
An order is placed only when someone approves it.
No. Every store keeps the system it runs. marql reads it — over the vendor's API for cloud systems, or through a small on-prem agent for an ERP inside your network — and changes nothing there: no prices, no stock levels, no orders. 151 connectors are live today, and a system without one is mapped from a REST API or a scheduled CSV export.
No. Stock is read per product and per store, and the lists you see are ranked by money, so a long assortment produces a longer tail at the bottom of the list, not a longer morning.
Not directly. marql reads the stock your system holds, not the shelf. What it does see is a product that should be selling and is not: a sale that breaks its own pattern in one store is flagged with the money behind it.
Yes. Products sold by weight are counted in kilograms against what the POS sells, which is how the candy chain in our success stories reads its pick-and-mix.
Yes. Where one store holds excess of a product another is running out of, the move is listed with quantities. It is prepared for approval and carried out in your own system.
Per store, on a graduated ladder: €200 a month for each of the first nine, €185 for stores 10 to 29 and €160 for 30 to 49. Each rate applies only to the stores inside its band, so twelve stores are €2,355 a month. The first month is free. The calculator is on /pricing.
Other retail formats
Retail chains
The overview: every store compared on one page.
Fresh food
Bakery, butcher, produce and confectionery: margin per product and stock that will not sell.
Convenience stores
Small shelves, frequent deliveries: every gap costs a sale the next store gets.
Health & beauty
Drugstores, cosmetics and parapharmacy: long assortments, category margin and slow lines.
Specialty retail
Pet, toys, books and gifts: a long tail of slow stock and staples that must not run out.
Franchise
Shared scorecards across franchisees' own systems.
The walkthrough is built around the POS and accounting you already run. Leave your details and pick a time.