Appearance
Luggage MNStorage and delivery, proposed for the US
Short-term storage at partner locations, plus independently bookable luggage delivery. Review scope, sequence, and approvals.
Skip to content
Two separate bookings. Storage can be linked to delivery, but delivery never depends on it.
Status at a glance
This site describes a proposal, not a shipped service.
- Storage baseline: requirements are documented. Implementation is in development and is not production-ready.
- Delivery, courier app, organization administration, and staff web cutover: proposed. Not released.
- Roadmap: defines build order and evidence gates. It does not commit to dates or cost.
No bookings, payments, or payouts can be taken from these pages.
Two services
Storage — travelers book short-term storage at partner locations by the half or full day, drop off bags with staff verification, and pick them up later with a claim code.
Delivery — travelers book luggage transport as a standalone order. Delivery does not require a storage booking. An optional link to a storage booking is allowed when a customer uses both. A return trip is a second delivery order.
Delivery has exactly two models: point handoff and driver collection. Both are described in Delivery.
How the product is organized
Two apps plus one website:
- Traveler app — storage and delivery booking, claim code, order milestones.
- Courier app (proposed) — assigned delivery jobs only, with custody proof.
- Website (proposed org split) — oversight, organization operations, and staff handoffs.
Roles, access boundaries, and surfaces are summarized in Platform.
What to read next
- Roadmap — Phases 0–5, in order, with entry and exit gates.
- Business requirements — market, payments approach, booking rules, scope, and client-owned inputs.
- Release decisions — launch city and partners, custody proof, commercial terms, service policies, and store and payment enablement.