Inventory · worked example
Receive stock once. Keep the balance clear.
An approved order requests 10 units. Six arrive first, then four. A repeated receipt must not increase the stock a second time.
This is an ETD demonstration using sample records. It runs in this page and resets when you reload. No customer system or external service is connected.
Try the receipt rules
- Approved order
- 10
- Received
- 0
- Outstanding
- 10
Ready. Receive six units, then press the same button again to test a repeated receipt.
Six checks you can reproduce
| Case | Starting quantity | Incoming | Decision | Received after |
|---|---|---|---|---|
| Awaiting approval | 0 | 6 | review | 0 |
| Partial delivery | 0 | 6 | recorded | 6 |
| Repeated receipt | 6 | 6 | duplicate | 6 |
| Over-delivery | 6 | 5 | review | 6 |
| Final delivery | 6 | 4 | recorded | 10 |
| Zero quantity | 0 | 0 | review | 0 |
Download the six cases · Download the rules
What changes in a real system?
The duplicate check here lasts only while this page is open. A production system needs persistent receipt IDs, transactional updates, user permissions, a reconciliation process and a recovery path when an integration fails. Agree the source of truth for reservations, returns and stock adjustments as well.
Before migration, bring item codes, opening balances by location, units of measure, outstanding orders and any supported accounting or warehouse APIs. Test with a small reconciled set before importing the full record history.
Compare inventory options · Scope a custom stock system · Discuss your workflow