Storage

Status: documented baseline requirements. Implementation in development, not production-ready. This page describes intended behavior, not a live service.

Short-term luggage storage at partner locations such as hotels, hostels, and shops. Travelers book by the half or full day. Staff verify bags at drop-off and return them at pick-up.

Related: Delivery is a separate, proposed service. Platform explains where storage actions happen. Business requirements hold the full rules.

Customer flow

1. Search nearby locations and compare availability.
2. Choose bags, drop-off time, and pick-up time.
3. Pay for the booking.
4. Show the claim code at the location.
5. Staff check bags in, with photo and tag.
6. Return with the claim code for check-out.
7. Optionally leave a review.

Staff handoff

• Verify the customer claim before handling bags.
• Photograph and tag bags at check-in.
• Verify the claim again at check-out.
• The staff workflow must keep working during connectivity loss and reconcile on reconnect.

A staff web surface is proposed to replace the current in-app staff route. The current route stays until the replacement reaches parity on a phone, including offline recovery. See Roadmap.

Booking rules (planned)

• 1–20 bags per booking.
• Drop-off is scheduled in the future, with a short grace window.
• Maximum stay of 30 days.
• Half-day rate applies up to 6 hours; longer stays price by full days, bag count, and stay length, plus any service fee.
• Availability is enforced per location and time window.
• Unpaid bookings expire after a short hold. Paid bookings past pick-up enter a no-show path. Customers are notified on each status change.

These are requirements under implementation. They are not proof the flow is live or audited.

Payments (planned approach)

• Market: United States. Currency: USD. Language: English-first.
• Card and mobile-pay top-up is processed through Stripe.
• Bookings are paid from an in-app wallet balance funded through Stripe. A shortfall at checkout is resolved with a top-up in the same flow.
• Credits and refunds return to the wallet under the cancellation policy.
• Receipts are provided through Stripe, email, and an in-app transaction record.

Wallet, payout, and insurance availability depend on release decisions and store and payment enablement. Do not treat this section as a live payment claim.

Baseline scope

In scope for the storage baseline: search and filters, location detail, bag sizes, wallet checkout, claim code, staff scan with offline queue, operations administration with settlement reporting, push notifications, help center, and notification preferences.

Proposed for later, not in the baseline: expiring claim codes, promos and coupons, store messaging, partner self-service, automatic payouts, chat, property-system sync, and additional login methods.

Decisions still needed

Launch locations, service policies, support number, and store and payment enablement must be confirmed before public bookings. See Release decisions.