Integrating Truck Stock with Warehouse Inventory and Replenishment

What the talk covered (business execution focus)

Nemo (Sedexus) demonstrated how to use ODU inventory + replenishment routes to manage truck/technician-owned stock without the full fleet/field-service complexity. The approach uses:

• Multiple “warehouses” (one per truck)
• Internal transfers
• Automated replenishment rules

Core use case

A plumbing company with technicians who are on call / no fixed schedule, where:

• Each technician must have a standard set of parts in their truck every morning
• Daily workflow:
  1. Nightly job runs reordering rules
  2. Technician validates an internal transfer to restock the truck
  3. Technician creates sales orders for emergency jobs (consumes truck stock)
  4. Next morning, replenishment reflects what was used

Edge case: a special order part (not in truck or main stock) triggers:

• Vendor purchase → receipt → transfer to truck → delivery

---

Frameworks / playbooks / process patterns highlighted

• Replenishment playbook (truck stocking loop)

  • Model each truck as a separate warehouse
  • Create an ODU route that performs internal transfers from main warehouse stock → truck warehouse
  • Use reordering rules to maintain target quantities
  • Use scheduler/automation overnight to generate the next replenishment transfers

• Document chain automation (end-to-end “demand → supply”)

  • Sales order confirmation for an emergency generates demand
  • Demand flows to purchase draft(s) when items are configured for “on demand”
  • Purchase order → receipt → internal transfer → delivery/order completion

• Standardization to reduce ad-hoc errors

  • Technician “restocking” becomes rule-based (min/max or on-demand) rather than personal judgment

---

Concrete configuration elements (how it works in ODU)

Warehouse + route setup

• Main warehouse: where the company keeps inventory for resupply
• Truck warehouses: e.g., Mark’s truck is configured as “Warehouse 3”
• Route modified for simplified transfer:
  • Instead of multi-step “outgoing delivers / incoming receives” validation, use a one-step internal transfer rule
  • Goal: only one document to validate for moving stock Main → Truck

Product reordering rules (3-product demo)

• Part 1 and Part 2

  • Rule: when truck on-hand drops below 10, reorder up to 10
  • Objective: each morning technician should have exactly 10 units of each part

• Part 3 (specialty edge case)

  • Configured for “on demand” replenishment
  • No safety stock maintained in main warehouse or truck

User-defined defaults (technician sells from their truck)

A setting (“user-defined default”) ties each technician user to their truck warehouse:

• For Mark’s sales orders, default Warehouse = Mark’s truck (Warehouse 3)

Result: when Mark creates sales orders, stock consumption automatically comes from the truck warehouse.

Scheduler behavior

The overnight scheduler runs automatically:

• Executes replenishment rules
• Creates internal transfers for the next day

Technician sees a “to process” count (e.g., 1 internal transfer ready each morning).

---

Daily operating workflow (end-to-end)

1. Technician logs into the Inventory app
2. Technician runs/observes the procurement replenishment rule (overnight action)
3. Technician processes the generated internal transfer:
   • Restocks truck to targets (e.g., 10 part1 + 10 part2)
4. Technician handles emergencies in Sales:
   • Confirms sales orders for multiple customers
   • Validates deliveries tied to parts actually used
5. Next morning:
   • Replenishment recalculates needs based on stock consumed

Example consumption math from the demo

• Day usage:
  • Customer Abigail: 6 units part1, 2 units part2
  • Customer Audrey: additional consumption leads to totals shown:
    • After both, truck stock usage totals: 6 part1 and 4 part2 remaining to restore (because objective is 10 each)

---

Edge case: specialty part ordering (Part 3)

When Mark needs a specialty part not stocked:

• Delivery/order state becomes “waiting” because item isn’t available in the truck warehouse
• Admin runs replenishment action:
  • Scheduler creates a draft purchase order from vendor (example shown: Anita Oliver)
• Purchase manager:
  • Confirms purchase order and unit pricing (added in demo)
• Receiving team:
  • Validates receipt
• Then:
  • Internal transfer replenishment creates the missing Main → Truck stock movement
  • Technician validates transfer and completes delivery to finalize installation

---

Key metrics / KPIs mentioned (quantitative targets)

No business KPIs like CAC/LTV/margins/revenue were provided. The demo focused on inventory target quantities:

• Safety/target stock per morning
  • Part 1: maintain 10 units
  • Part 2: maintain 10 units
• Reorder trigger
  • When on-hand < 10, replenish back to 10
• Edge case behavior
  • Part 3 maintained 0 on-hand; replenished only when demanded

---

Actionable recommendations implied by the talk

• Use one warehouse per truck (truck “warehouses”) instead of custom fleet logic when work is unpredictable
• Standardize technician stock levels with simple min-threshold replenishment rules
• Set user-defined defaults so each technician’s sales orders automatically consume from their truck warehouse
• Rely on the ODU overnight scheduler + routes to remove manual restocking planning
• Configure an on-demand purchasing path for specialty parts to ensure the system can execute:
  • Sales demand → PO draft → confirmation/receipt → internal transfer → delivery completion
• Reduce operational risk by preventing technicians from manually “improvising” truck stocking

---

High-level fit / audience guidance

Best for businesses with:

• Small number of trucks/technicians (e.g., ~5)
• No fixed schedule and more reactive dispatch
• Need for standard daily truck readiness to handle emergencies

Avoids complexity when you don’t need:

• Full fleet optimization
• Full field service setup

---

Presenters / sources

• Nemo — Director of Operations, Sedexus (co-leads global business analyst team; presented the demo and configurations)
• Cesley Berto — credited as helping prepare the presentation and demo setup
• Dua — credited as helping prepare the presentation and demo setup
• Q&A speaker (as moderator / questioner) referenced “Miss Keller” (appears to be a mis-subtitle); content indicates Nemo is the main presenter.