What to order, and where it's short.Ready before the stores open.
Every morning your AI supply employee and AI buyer read forecast demand, stock and lead times, and prepare store orders, vendor orders and transfers between stores. Each line shows the numbers it came from. A person approves every order.
Order proposals
Current proposals are grouped by supplier and urgency; they are not orders yet. Create a draft to move it to Orders, where you can follow its status, receipt and observed result.
Rows needing data review: 3. Open products to investigate.
Mediterra Foods → Store order · Westside, North Park
Items: 8 · Stock may run out before replenishment
1 284 €
Preliminary total · verify prices and currency
- On hand
- 12
- Daily demand (forecast)
- 6.0
- Lead time
- 3 d
- 7-day risk
- 213 €
Supplier not identified → Store order · Harbour
Items: 3
Ordering calendar missing or invalid — check ordering days
Review productsMove stock between stores
2 moves · 96 € of margin at stake
Pasta 500 g · 30 units · Old Town → North Park
From a forecast to goods on the shelf.
The arithmetic is on every line, so an order can be checked before anyone approves it.
Forecast
Each night, in your local night, demand is rebuilt for every product in every store: weekday and holiday patterns for steady sellers, a separate method for items that sell now and then. Each line gets a typical day (P50) and a busy one (P90).
Propose
In the morning, stock on hand and on the way is set against demand over the lead time and the wait to the next order day. Short lines are grouped by supplier and urgency, and a move from a store with too much comes before buying more.
Approve
A proposal is not an order. A person creates the draft, checks quantities, prices and currency, and approves it.
Receive and check
The approved order goes to your ERP. When the goods arrive, the receipt records what came, and the order shows what changed on the shelf afterwards.
Olive oil 1 L · Westside · this morning's line
- Busy-day demand, P90 forecast8.0 a day
- Lead time 3 d + 4 d to the next order day× 7 d
- Needed until the delivery after this one56
- On hand−12
- On the way−0
- Short44
- Rounded up to packs of 1248 units
Cover today: 12 on hand ÷ 6.0 a day = 2 days, under the 3-day lead time. Stock may run out before replenishment.
Stock moved first, every order followed.
Supply is its own section in marql: Replenishment, Orders, Transfers, Suppliers and Monitor.
Move stock before buying more
When one store holds weeks of an item that another store is about to run out of, a transfer is proposed: the quantity, both stores' cover before and after, and the margin at stake. Accept records your decision; the move is made the way you always make it.
Stock you have already paid for goes where it sells, before a new order is placed.
Move stock between stores
2 moves · 96 € of margin at stake
Old Town
cover 38d → 26d
North Park
cover 1d → 8d
Harbour
cover 30d → 20d
Westside
cover 1d → 8d
An order you can follow to the shelf
A draft order is a document. Once approved, it goes out as an e:corg draft that a person posts, or as a document for any other ERP. The receipt records what actually arrived, and lines that fall short keep the order open. After delivery, the order shows what changed on the shelf.
Every order has a status, a receipt and an observed result, in one place.
Mediterra Foods → Store order · Westside, North Park
8 items · 1 284 € · Prepared by marql's AI supply employee
Created
Tue 06:04
Confirmed
Tue 09:12
Sent
Tue 09:20
Received
Fri 08:40
After delivery
7 days
Sent as
- e:corg 2.0 · an e:corg draft; a person posts it
- Any other ERP · a document to export; a person enters it
Receipt
Ordered 156 · received 156
8 of 8 order lines with goods recorded
After delivery
On shelf · 6 SKU–store positions with higher observed stock · 2 back from zero
Monitor: every step, and a hand on the brake
Supply › Monitor is the AI supply employee's work log: what it read, what it assembled, what it held and why. Any order can be taken over, so the AI stops changing it, or stopped; Pause everyone halts all the AI employees at once.
You see why an order was held: not its order day, no supplier chosen, or an item with no sale for three days while stock says it is there.
Supply monitor
Now
AI supply employee · morning pass: 5 of 7 orders
Work log
- 06:00Supplymorning pass started
- 06:01Supplysnapshot read: data as of 05:40 · orders to work through: 7
- 06:03SupplyCentral warehouse → Westside: draft ready, 14 items · 612 €
- 06:04SupplyFresh Dairy Co. → North Park held: not its order day
- 06:05SupplySupplier not identified → Harbour held: needs a supplier chosen
- 06:05SupplyChickpeas 400 g · Harbour: no sale for 3 days with stock on the books — held, shelf check requested
- 09:12YouMediterra Foods → Westside, North Park approved, 1 284 €
Exactly where the line is.
Ordering is where a wrong number costs real money. This is how far the AI supply employee and the AI buyer go, and no further.
A person approves every order.
The AI employees prepare drafts; approving and posting stay with your team.
marql never sends an order to a vendor.
Placing it with the supplier stays with your team.
With e:corg 2.0 as your ERP, an approved order or transfer becomes e:corg's own draft, and a person posts it.
With any other ERP it goes out as a document, and a person enters it. Your POS is only read.
Data gaps are shown, not guessed: a missing ordering calendar, an unidentified supplier or a stock row that needs review appears as a row to check.
The supply desk is switched on per organisation.
The questions buyers ask first.
From three things per product and store: stock on hand and on the way, forecast daily demand, and the lead time. Demand is forecast every night; the busy-day figure (P90) sets how much to hold over the lead time plus the wait to the next order day, so the order matches your service level. Stock already there is taken off, the rest is rounded up to the pack, and every line shows the figures it came from.
Ordering needs stock and purchase cost, which usually live in the ERP or the accounting system rather than the till. Some POS systems connected through partners send sales only; then your stock source is connected as well. Until it is, a product without a stock record is set aside rather than ordered on a guess.
No. With e:corg 2.0 an approved order lands in e:corg as a draft, ready to post. With any other ERP the order goes out as a document that a person enters. The calculation is the same either way.
Your team. The AI buyer prepares vendor orders on each vendor's order days, the AI supply employee prepares store orders from the warehouse and transfers between stores, and a person approves every order. marql never sends an order to a supplier.
Yes. Proposals are computed wherever there is stock data, and you choose which ones become drafts. Start with one store, one supplier or one category, and leave the rest as reading until you trust the numbers.
By the AI supply employee's KPI, shelf availability, against control stores: about one store in five, where the employee only advises. Each order also shows what changed on the shelf after its delivery.
Ready to see
the euros it found?
The walkthrough is built around the POS and accounting you already run. Leave your details and pick a time.