Take out of the range
Retail Park · Easter egg 250 g
Frees ≈860 €
frozen · estimate
60days checked without sales
Seasonal and slow lines stay on the shelf long after they stop selling. Every morning it reads sales by shop and product, finds lines that stopped selling while the category has substitutes, and proposes taking them out: supply stops reordering, marketing clears what is left.
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 category manager · AI
Take out of the range
Retail Park · Easter egg 250 g
Waiting since 06:00
Frees ≈860 €
ReviewRetail Park · Easter egg 250 g
Frees ≈860 €
frozen · estimate
60days checked without sales
Each shop keeps its POS. marql reads sales and stock, including what is sold by weight, and brings back the products where money moved.
Cloud POS and accounting connect over their own APIs; an ERP in your network is read by an on-prem agent. Products sold by weight are counted in kilograms against what the POS sells.
The same croissant under three names becomes one product, so each shop can be compared with the others on it.
gate · reporting: A shop that sent nothing is named as not reporting, not counted as a zero
When a cost price rises and the shelf price does not, the product's margin drops in the data the next morning, ranked by what it costs per month.
Seasonal lines left after the season, boxes that stopped moving and shops holding months of one product are listed, with moves to the shops that sell it.
gate · approval: Not approved — no move is made and nothing is written
The format in numbers
+17.9%
4.3%
Margin that moves with every invoice, shops that sell the same product very differently, and the season's leftovers.
Margin per product, per shop
Revenue, units and margin for every product, wherever a cost price exists, for one shop or the chain.
When and what each shop sells
Peak hours, the strongest and weakest day, sales by part of the day, and the products growing or falling most in money.
Sold by weight, counted by weight
Trays and unopened boxes are counted in kilograms against what the POS sells.
Seasonal stock after the season
Stock with no sale in 30 days is priced as frozen capital, and dead stock (no sale in 60 days) is set against the month before.
Shop against shop
Each shop is placed against shops of the same format on revenue, average check and margin.
Only what is worth it
Anomalies in sales, stock and margin are ranked by money; only what is worth at least €50 a week reaches you.
Margin · demo confectionery chain
data as of 08:05 · 4 of 4 shops reporting
| product | margin, this month | vs last month | stock, days |
|---|---|---|---|
| Dark chocolate pralines, by kgall shops | 31.2% | −6.4 pts | 22 |
| Pick-and-mix gummies, by kgall shops | 48.9% | +0.3 pts | 9 |
| Gift box 500 gOld Town | 36.0% | −0.8 pts | 171 |
| Easter egg 250 gRetail Park | — | no sale 60 d | dead |
| margin lostpralines, at this month's cost price | 2 140 € / month | ||
margin is read at the cost price the invoices carry, product by product
The kitchen and the bake plan are their own systems. marql reads what the POS and the stock say about them.
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.
There is no production or bake planning: marql does not tell a bakery how many loaves to bake per hour.
Recipes, expiry dates, batches and HACCP records are not tracked.
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.
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. marql does not plan bakes or prep. It shows, per shop and per product, what sold, when, and what is left in stock, which is what a production plan is checked against.
Yes. Products are mapped to one list, so one praline or one loaf can be read shop by shop: units, revenue, margin and days of stock.
With what is left after them. Seasonal lines that stopped selling are priced as frozen capital per shop, and moves to the shops still selling them are listed for approval.
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.
Grocery & supermarkets
Thousands of SKUs on thin margin: stock gaps, dead lines and margin per category.
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.