Voyage Supply Chain and Procurement for Maritime Hospitality
Control F&B and technical stores from planning to delivery with route-aware demand forecasting, supplier workflow control, and waste analytics.
Status: Pilot-ready for multi-vessel procurement planning, cold-chain controls, and variance close.
Operational scope
Qail Provision replaces chat-and-spreadsheet procurement with one auditable workflow from demand plan to goods receipt.
Voyage demand planning
Build SKU demand from passenger load, route duration, service class, and seasonal menu profile.
Supplier and PO controls
Standardize RFQ, approval matrix, PO issue, and goods receipt with role-based sign-off and evidence.
Cold-chain and shelf-life rules
Tag temperature-sensitive SKUs and block risky dispatch when handling checkpoints are incomplete.
Waste and variance governance
Close weekly against expected consumption to isolate over-issue, spoilage, and pricing drift by supplier.
Core KPIs and formulas
| KPI | Formula | Use |
|---|---|---|
| Provision cost per pax-day | Total provision cost / total served passenger-days | Commercial cost control |
| Procurement cycle time | PO approved to goods received duration | Supplier and internal process speed |
| Supplier on-time rate | On-time deliveries / total deliveries | Vendor reliability signal |
| Waste ratio | Discarded quantity / total issued quantity | Menu planning and handling quality |
| Stockout incidents | Count of out-of-stock events before departure | Dispatch readiness metric |
Recommendation: split KPI boards for hospitality SKUs and technical stores because service behavior differs.
Data contract (minimum fields)
Demand and inventory
- voyage_id, route_id, departure_date, service_tier
- sku_id, unit, par_level, forecast_qty, issued_qty
- shelf_life_days, cold_chain_required
Procurement and receiving
- supplier_id, po_id, ordered_qty, delivered_qty
- unit_price, lead_time_days, delivery_status
- receiving_temp_log, variance_reason
30-60-90 rollout
0-30 days
Onboard top 100 SKUs, define supplier master, and run first route-level demand plan with one vessel class.
31-60 days
Activate approval workflow and variance reason codes; run weekly review on stockout and waste ratios.
61-90 days
Expand across all active routes and compare supplier scorecards for pricing, lead-time, and reliability.
Pilot success thresholds
- Top-SKU stockout incidents trending to zero
- Waste ratio down for two consecutive monthly closes
- PO to receiving cycle time variance shrinking route by route
- Supplier on-time rate stable at agreed SLA level