Returns & virtual warehouses
Two physical warehouses, multiple virtual ones — exactly the model Ray described on the call.
Phase 2 · scoping in proposal
Mirrors how your warehouse actually works.
You told us product doesn't physically move during a return — the virtual warehouse assignment changes as condition is assessed. We'll model exactly that: scanner-driven transitions between virtual warehouses, with audit trail per unit. Your Zebra scanners drive every move — same workflow your team already knows.
Warehouse map
2 physical · 5 virtual (example)| Code | Warehouse | Type | Units | Notes |
|---|---|---|---|---|
| PHY-NG | North Geelong (physical) | physical | 28,430 | Main distribution centre |
| PHY-WH2 | Secondary warehouse (physical) | physical | 12,860 | Overflow + B2B prep |
| VW-RTN | Returns inbox (virtual) | virtual | 142 | Incoming returns awaiting inspection |
| VW-INSP | Inspection (virtual) | virtual | 38 | Being assessed for condition |
| VW-RST | Restockable (virtual) | virtual | 64 | Passed inspection · ready to merge back |
| VW-DMG | Damaged / scrap (virtual) | virtual | 19 | Beyond repair · write-off pending |
| VW-QUR | Quarantine (virtual) | virtual | 12 | Suspected contamination · 14-day hold |
Returns lifecycle
Every transition is one scanner action — picked up exactly as today, just unified.
Customer ships return VW-RTN
Receive + scan barcode
VW-RTN VW-INSP
Open + visually inspect
VW-INSP VW-RST
Condition passed → restock
VW-INSP VW-DMG
Condition failed → scrap
VW-RST PHY-NG
Merge back to sellable stock
Phase 1 includes
- Unlimited virtual warehouses with custom transition rules
- Zebra scanner integration for every move
- Per-unit audit trail (who moved it, when, why)
- Condition tags per unit (new / repackaged / damaged / scrap)
Phase 2 add-ons
- Return-reason analytics ("why" most returns happen)
- Photo capture at inspection (scanner-triggered)
- Automated refund triggering when condition is set
- NDIS-compliant disposal certification for damaged stock