Order Response
Order Response answers one question: for the items I have on order, how much has the supplier confirmed, and when is it arriving? It returns the confirmed quantity per item per store, broken down by shipment, so a store can see that 100 of the 120 units are due next week and the rest a fortnight later.
🛑 The data is yours, not ours
Order Response owns no database. It stores nothing, and every figure it returns comes from your own system. Each answer is read, at the moment you ask, from a system you operate — an ERP, a purchasing system, whatever holds your supplier confirmations — which you register with Hii Retail once.
That single fact shapes everything else on these pages:
| Where the numbers come from | your system, on every request |
| What Hii Retail stores | nothing |
| The one thing it does derive | a business unit's confirmedQuantity is re-added from the shipments you list, rather than taken from the total you send — see The business-unit total is the sum of its shipments |
| If you have not registered a system | every request returns 404 — there is no fallback |
| How fresh the answer is | exactly as fresh as your system. Hii Retail cannot improve on it |
| Who can change the data | you, in your own system. There is no write endpoint here |
So why route it through Hii Retail at all? Because it puts supplier confirmations in the same place, the same shape and behind the same authentication as the rest of your Hii Retail inventory data — so a caller that already reads stock levels can read what is on order without integrating separately with your ERP, and without you exposing that ERP to every consumer.
If you want to…
| …then read | |
|---|---|
| call the endpoint and understand what comes back | The API |
| connect your own system so there is something to read | Connecting your system |
What this service does not do
Each of these is a real boundary, and each is a different kind:
| No writes. There is no endpoint to create or change an order response. | Structural — Hii Retail is not the owner of the data. Change it in your own system. |
| No events. Nothing is published when a confirmation changes. | Structural — a service that stores nothing has no change to detect. If you need to react to a confirmation, react in your own system. |
| No stock effect. A confirmed quantity does not move stock in Hii Retail. | By design — an order response is a promise, not a movement. Stock changes when goods are received, through Goods Received. |
| No history. You always see what your system says now. | Follows from storing nothing. If you need to know what was confirmed last week, your own system is the only record. |