Simon G. / Fields / Retail & distribution
The right stock in every location, credit under control.
For distributors and retail chains with many locations and thousands of products: the forecast and order proposals per supplier, transfers before a branch runs out, price corridors that stop discount leakage, and credit limits per customer. Every night, signed by the people you name, on your own server.
The demo shows a fictional parts distributor with forty branches, a central warehouse and 12,000 products.
The network this morning
What the head of supply chain sees first. Coverage, orders, transfers, credit.
Figures from the demo company, fictional. Every tile opens the decisions behind it.
Forecast and order proposals
An order per supplier, every night, with the reasoning beside it.
The demand of every product in every location is forecast from its own history; slow movers get their own method. Orders respect pack sizes, minimums and lead times, and say which stockout they avoid and what it would have cost.
- Forecast error shown per product, weekly
- Safety stock where it belongs in the network
- Orders inside the signed limit go through; the rest wait for a signature
Stock across locations
Moved before a branch runs out and before a warehouse sits on excess.
Days of stock per location and product, transfers proposed with their cost, excess named with its value. A gap in the data is drawn as a gap, never as zero.
- Transfers proposed with cost and effect
- Excess stock with the money it ties up
- A gap in the data drawn as a gap
Price corridors
The list price inside a signed corridor, and the discounts that leak.
Each price change is proposed inside the corridor the commercial director signed. Discounts given outside the rules are listed by salesperson and customer, with the money, every month.
- Price changes proposed inside the corridor
- Discount leakage by customer and salesperson
- Margin by product family, monthly
Credit per customer
A limit and a risk class from each customer's own payment record.
How well and how late each customer pays, turned into a limit and a class the credit controller signs. The weekly overdue list says what to do, customer by customer.
- Limits proposed, signed by the credit controller
- Overdue list with the action for the week
- Payment behaviour trend per customer
What we read, so you prepare nothing
Files you already have. We take them ourselves.
- SalesTransactions by product and location, from your ERP or point of sale.
- Stock and movementsStock, receipts, transfers and returns per location.
- PurchasingOpen purchase orders, supplier lead times, pack sizes and minimums.
- Prices and paymentsPrice lists, invoices with discounts, customer payments.
No implementation project on your side. We read these with your IT beside us, set Simon G. up for your activity, and it runs on your server with no internet connection. Your data is shared with no one, not even through a chatbot.
What it does not do
Plainly.
- It is not a point of sale or a web shop.It reads what they record.
- It does not plan promotions or expiry in the first release.It reads their effect and says so.
- It does not send the order to the supplier.It proposes; a person sends it.
- It does not post to the ERP.Nothing is written back.
See the demo distributor
Thirty days of access to the demo network, then a conversation on yours.
A fictional forty-branch distributor, every screen live: orders, transfers, corridors, credit. Ask for access and we send an account within one working day, with a ten-task script that takes forty minutes.
Fees are said in the first conversation. How the pilot works.