When a warehouse or 3PL serves delivery networks, inventory cannot live in a silo. If reserved units do not match what shipping will attempt, you get oversell, empty runs, and merchant disputes.
This guide explains a practical stock-state model (available / reserved / defective), how expeditions connect to last-mile, and what to demand from software — without fake “full WMS” claims. Speedliv by Storeino links inventory (product types, stock states, expeditions, sourcing) to the shipping stack. COD remains optional on parcels.
The problem: two truths (WMS sheet vs courier sheet)
Common pattern:
- Warehouse Excel says 40 units available
- Confirmation team confirms 25 orders
- Shipping dispatches 25
- Nobody decremented reserved stock in the same system
- Returns arrive to a different sheet
- Defective units still look sellable
Multi-merchant 3PL makes this worse: ownership of stock, SLA, and who pays for mis-picks must be explicit.
Stock states that ops can run
Keep three states that map to decisions:
| State | Meaning | Who cares |
|---|---|---|
| Available | Can be promised / reserved | Confirmation + sourcing |
| Reserved | Promised to confirmed / allocated orders | Warehouse pick + shipping |
| Defective | Not sellable until disposition | QA / merchant rules |
You can add location bins later. If you cannot run these three cleanly across expeditions, bin-level sophistication will not save you.
Expeditions linked to shipping
An expedition should:
- Pull from reserved (or explicitly allocate then reserve)
- Produce parcels / slips the hub and drivers already understand
- Update stock as goods leave
- Accept returns into the correct state (available vs defective)
The parcel ID after expedition must be the same ID last-mile scans. That is the “one parcel truth” rule.
Process SOP (3PL / warehouse serving couriers)
- Receive goods → count → available (or quarantine → defective)
- Confirmation / order allocation → reserve
- Pick / pack → expedition linked to shipping parcels
- Hub scan / distribution slips
- Deliver / collect (COD amount optional on parcel)
- Returns → scan → available or defective + reason
- Weekly: available vs reserved vs open parcels reconciliation
KPIs
| KPI | Why |
|---|---|
| Reserved vs open confirmed parcels | Prevent silent oversell |
| Pick-to-dispatch time | SLA |
| Return-to-shelve time | Cash and stock accuracy |
| Defective rate by merchant/SKU | Sourcing quality |
| Expedition mismatch errors | Integration / process holes |
What to ask vendors (honest scope)
Ask for a live path: reserve → expedition → parcel scan → return to defective. Ask whether inventory is a bolted spreadsheet export or a module on the same platform as settlements and driver app.
Speedliv inventory covers product types, warehouse stock states (available / reserved / defective), expeditions, and sourcing — alongside parcels, slips, finance, confirmation, and the driver app. It is a shipping ops platform with inventory, not a claim to replace every enterprise WMS feature set.
Maghreb / MENA multi-site note
Upload cities/zones for every country you deliver into. Warehouse location and delivery coverage are related but not the same list — keep both explicit. Demo MAD data is sample only.
Checklist
- Available / reserved / defective states
- Expeditions create shipping parcels (same IDs)
- Returns path with reason codes
- Roles for warehouse vs hub vs finance
- Optional COD on parcels without forcing COD workflow
- Multi-country city/zone upload for the delivery side
FAQ
Do we need Speedliv if we already have a WMS?
Maybe as the shipping / confirmation / settlements layer with a clear integration boundary — evaluate based on whether parcel truth is shared.
Is inventory mandatory?
Only if you operate warehouse / 3PL flows. Pure line-haul / last-mile networks may start with parcels, slips, driver app, and finance.
CTA
Book a meeting on speedliv.com for warehouse / 3PL + shipping mapping. Demo: https://demo.speedliv.com/en/auth/login · WhatsApp +212 661-962932 · Warehouse solution
Reservation timing: confirm first or allocate first?
Two valid patterns:
A — Confirm then reserve: Call center confirms, then warehouse reserves. Lower dead reservations; risk of stock-out after confirm.
B — Soft allocate then confirm: Stock held briefly during confirmation SLA. Higher protection for VIP SKUs; needs automatic release on cancel/no-answer rules.
Pick one per merchant contract. Mixed rules without system support create tribal knowledge.
Multi-merchant 3PL realities
- Label ownership of stock by merchant
- SLA for pick/pack cutoffs tied to delivery waves
- Billing for storage vs outbound vs returns (even if invoicing sits partly outside)
- Defective disposition rules differ by merchant
The shipping platform should at least keep stock states and expeditions honest so last-mile is not guessing.
Returns quality loop
Returns are where 3PL and courier fight:
- Driver scans return reason
- Hub receives and sorts
- Warehouse books available vs defective
- Merchant sees the same final state
If step 3 is a weekend Excel paste, Monday’s available stock is fiction.
Space, waves, and delivery cuts
Align warehouse waves with distribution slips:
- Morning wave → morning distribution slip → driver app assignments
- Late cutoffs need explicit “next wave” status — not silent parking on a desk
Security & roles
Separate:
- Receivers (to available)
- Pickers / expedition operators
- QA (to defective)
- Finance (settlements, not stock invent)
Audit logs matter when merchants dispute shrinkage.
Extended FAQ
Can Speedliv replace our entire WMS?
Treat it as inventory + shipping ops for networks that need available/reserved/defective and expeditions linked to parcels. Complex yard/bin robotics may stay specialized — do not claim otherwise.
What if we only store cross-dock?
You may emphasize slips and scans with light stock states. Still keep defective/quarantine explicit.
Merchant onboarding checklist (inventory)
- Product types created with units
- Opening stock counted into available
- Defective quarantine location agreed
- Reservation rule (A or B) documented
- Expedition cutoff times aligned to delivery waves
- Return reason codes shared with courier
- Who pays for mis-picks defined in contract language outside the tool if needed
Example weekly recon
Compare:
- Sum(available + reserved + defective) vs last physical count adjusted for receipts/shipments
- Reserved vs confirmed-not-yet-shipped parcels
- Expeditions without hub inbound scans (leak indicator)
Publish the recon every week even when green — silence breeds shadow sheets.
Cross-dock vs storage
Cross-dock emphasizes slips and scan timing; storage emphasizes reserved accuracy over days. Either way, defective must never look available. Document which merchants are cross-dock only so confirmation SLAs match physical reality.
CTA reminder
Book a meeting on speedliv.com with a sample stock snapshot and expedition wave times. Demo: https://demo.speedliv.com/en/auth/login · WhatsApp +212 661-962932.
Wave example
Wave 1 (07:30): yesterday’s confirmed expeditions → distribution slips 09:00.
Wave 2 (13:00): morning confirms → afternoon distribution.
Cutoffs belong in the system, not on a sticky note.
