Go back
Retail
Store stock check + transfer coordination
Best for:
Store Operations
Supply Chain
Replenishment
Outcome
Fewer lost sales in understocked locations, fewer write‑offs in overstocked ones, less central chasing.
Case type (unit of work)
Store Transfer Coordination Case = (1 case = 1 store stock check completed via voice + transfer agreed (or ruled out) + system updated with evidence
What DUVO delivers
When system stock is wrong or transfers require human agreement, work stops. Duvo’s voice agent calls stores with a short script, confirms physical stock, proposes a compliant transfer, and creates the transfer order - with audit evidence.
01
Flags imbalance: understock vs overstock across stores/hubs (by SKU/location)
02
Builds a short call pack per store: SKUs, expected stock, urgency, and transfer options
03
Calls store contacts (voice agent) to confirm physical stock and constraints
04
Proposes transfer options within policy (distance, minimum volume, timing windows)
05
Confirms acceptance + timing, then creates transfer orders in the right system
06
Logs outcomes (incl. “stock mismatch”) and escalates repeated mismatches to ops
Definition of done
Stock confirmed
Transfer created (or rejected with reason)
System updated
Evidence stored (call outcome + transfer ID)
Transfers executed:
More transfers completed (including long-tail SKUs that rarely get worked
Phantom stock loops:
Fewer back-and-forth cycles between central and stores
Central team time:
Meaningfully less time on manual store calls and coordination
Sell-through:
Better movement of overstock; fewer lost sales where stock is short
Cases by status: proposed / confirmed / transferred / blocked (with reasons)
Call logs + transcripts per store
Transfer orders created + write‑back verification
Stock mismatch report (where system stock diverges from physical)
Rollout requirements
System access
Store contact list + calling rules (hours, languages, escalation); transfer order creation in ERP/WMS/store tool
Rules
Transfer policies (distance, urgency tiers, approval thresholds)
Timeline
Live in ~2–3 weeks for one region/cluster
