Store Movement Control Tower — Owning a Date You Do Not Control
Inbound from suppliers and outbound to customers in one control tower, with partial receipts, rejections, inventory, sales, purchase and HR in the same system.
Client
[CONFIRM: GSP — confirm the entity name and written permission before publishing]
Industry
Trading, Distribution & Supply Chain
Timeline
[CONFIRM: build duration]
Services
Product Design, Custom ERP/CRM Development, Inventory & Movement Tracking, Sales & Purchase Modules, HR Module
The Challenge
You own the promise. You do not own the warehouse.
A trading and distribution desk sits between a supplier it cannot control and a customer it cannot disappoint. It buys against a date the supplier gives, sells against a date the customer accepts, and is accountable for the gap between them.
That gap is where the business actually lives, and in most desks of this size it is the least instrumented part of the operation.
The shape of the problem
A purchase order goes to a supplier. The supplier confirms a date. The customer is quoted a date derived from it. Then the supplier ships part of the order, or ships late, or ships something that fails inspection — and the customer’s clock keeps running regardless.
Each of those three events is normal. None of them is an exception. Together they mean the honest status of any given line is rarely “ordered” or “delivered” but something in between, and a sheet with those two columns cannot represent it.
Partial receipts are the normal case
Twelve of thirty arrives. The order is not open and it is not closed. The customer can be partly served, which means a decision has to be made about whether to dispatch what is here or hold for the balance — and that decision needs to be visible to whoever is answering the customer’s call.
In a spreadsheet, partial receipt is represented by somebody editing a quantity and remembering why. The memory is the system, and the memory belongs to one person.
Rejections disappear into email
Material arrives damaged, short, or wrong. It has to go back, be replaced, be credited. Meanwhile the committed delivery date does not move. Without a dedicated place for it, a rejection becomes an email thread, and an email thread is not something you can count, age, or chase systematically.
What needed to be solved
Every movement line sitting in exactly one clearly-named state, with no ambiguity about what it means.
Partial receipt treated as a real state rather than an edited number.
Lateness measured against the customer’s expected date, not an internal one.
A rejection register so returns can be counted and chased rather than remembered.
Inventory that reflects what is actually on hand, not what was ordered.
Sales and purchase in the same system as the movement, so the commercial document and the physical reality are not two different records.
The answer to the one question that matters on a Monday: which customer commitments are going to be missed this week, and because of which supplier?
What We Did
We built a control tower — one screen that knows where every line is and which promise is about to break.
Our approach
We modelled the states first and built the screens second. Most operations software gets this backwards, which is why the resulting tool can display the easy cases and needs a person for the hard ones.
01 — Four movement states, and a line is always in one
Inbound Pending — supplier delivery not complete.
Inbound Overdue — past the expected delivery date.
Ready to Dispatch — supplier has shipped, customer still pending.
Dispatched — already moved to the customer.
The value is in the fourth one being separate from the third. “Supplier shipped” and “customer received” are two different facts, and collapsing them is how a desk ends up telling a customer that something is on its way when it is sitting in its own store.
02 — Partial receipt as a first-class state
A dedicated Partially Received count tracks orders still waiting on balance quantity, separate from fully received and from pending.
This is the state a spreadsheet cannot hold honestly, and it is the one most likely to cause a missed commitment — because a half-delivered order looks like progress and behaves like a problem.
03 — Lateness measured against the customer
Dispatch Due / Overdue counts lines where the customer’s expected date has been crossed.
Measuring against the customer’s date rather than an internal target is the difference between a report that makes the team feel efficient and one that predicts the next difficult phone call.
04 — A Rejection Register
Returns and rejected material get their own register rather than living in an email thread, so they can be counted, aged and chased like any other open item.
05 — Monitoring and OPS
Monitoring holds shipment tracking entries — the live record of where things are between the two ends. OPS is the day-to-day operations desk where the work gets actioned rather than only observed.
06 — Inventory
What is physically on hand, kept separate from what has been ordered and what has been promised. Three different numbers that are routinely treated as one.
07 — Sales and purchase in the same system
Customer orders and supplier purchase orders sit alongside the movement they create, so the commercial document and the physical movement are two views of one record rather than two systems that have to be reconciled.
08 — HR module
The system also carries an HR module for the team side of the operation, so people are managed in the same place as the work rather than in a separate tool.
[CONFIRM: the HR module’s screens were not included in the material provided. Add the specifics — attendance, payroll, leave, roles — before publishing this section, or trim it to one line.]
Delivered
Four-state inbound and outbound movement tracking
Partial receipt handling
Dispatch due / overdue against customer dates
Rejection register
Shipment monitoring and operations desk
Inventory
Sales and purchase modules
HR module
The Outcome
One screen that knows which promise is about to break, and why.
Inbound from suppliers and outbound to customers sit in a single movement snapshot, with every line in a named state and lateness measured against the date the customer was actually given.
The half-finished cases stopped being invisible
Partial receipts and rejections — the two situations a purchase sheet cannot represent honestly — each have their own place in the system, which means they can be counted and chased instead of remembered.
Supplier failure and customer impact sit next to each other
Because inbound and outbound are tracked in one tower rather than two sheets, a late supplier and the customer commitment it threatens are visible in the same view at the same time.
Commercial and physical in one record
Sales, purchase and inventory in the same system as the movement removes the reconciliation step that normally consumes the start of every week.
What this unlocked
A desk that can answer a customer’s “where is my order” from the screen rather than from a phone call to a supplier — and can see the problem before the customer does.
Movement states — Inbound Pending, Inbound Overdue, Ready to Dispatch and Dispatched — so every line sits in exactly one unambiguous place.
Operational modules in one system: Monitoring, OPS, Rejection Register, Inventory and the movement dashboard, plus sales, purchase and HR.
[CONFIRM: a real figure — e.g. purchase orders tracked, lines monitored per month, or reduction in missed dispatch dates. Do not publish an invented number.]
