Business requirements

Storage requirements below are the documented baseline; implementation is in development and not production-ready. Delivery items are marked proposed and are not released.

This page summarizes market, payments, booking rules, scope, and client-owned inputs for review. It is a planning document, not a live-service claim.

Market

• Service style: short-term luggage storage at partner locations, plus proposed standalone luggage delivery.
• Launch market: United States.
• Currency: USD.
• Language: English-first.

Payments (storage baseline)

• Payments are processed through Stripe, including cards and mobile-pay options enabled through Stripe.
• The in-app wallet is the planned primary rail: customers fund the wallet through Stripe, then bookings are paid by wallet debit.
• 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: unpaid holds release with no charge; paid bookings canceled before check-in are credited per policy; no-show and expired bookings receive no credit.
• Receipts are provided through Stripe, email, and an in-app transaction record. No fiscal-receipt integration is planned.
• Money is tracked in integer cents with a currency marker. A configurable service fee applies (default zero).

Proposed delivery payments follow the same wallet-primary approach: a server quote bound to route, bag count, window, currency, and expiry; payment completes before dispatch; duplicate payment attempts cannot double-charge; delivery credits and refunds use a traceable reference under a written cancellation policy. Courier compensation and organization settlement reconcile to the paid order. Automated courier payouts are outside the first release.

Wallet, payout, and insurance availability still require release decisions and store and payment enablement.

Booking rules (storage baseline)

• 1–20 bags per booking.
• Drop-off is scheduled in the future with a short grace window; maximum stay 30 days.
• Pricing: half-day rate 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.
• Booking states cover unpaid holds, paid, checked-in, checked-out, canceled, no-show, and expired bookings, with a manual-review path for disputed paid cancellations.
• Unpaid bookings expire after a short hold; paid bookings past pick-up enter a no-show path. Customers are notified on each transition.

Related custody detail for delivery is in Delivery; access boundaries are in Platform.

Scope

Storage baseline — in scope: search and filters, location detail, bag sizes, wallet checkout, customer claim code, staff scan with offline queue, operations administration with settlement reporting, push notifications on status changes, static help center, and notification preferences.

Not in the baseline: expiring claim codes, promos and coupon ledgers, store messaging, partner self-service, automatic payouts, chat, property-system sync, and additional login methods.

Delivery — proposed, not in the baseline: the two delivery models in Delivery, the courier app, organization administration, manual dispatch, custody events, and the staff web cutover. Each is gated in Roadmap.

Client-owned inputs

Quoted work excludes the following client responsibilities. Public bookings cannot start until they are in place:

• US Stripe account plus mobile-pay merchant enablement.
• Apple Developer membership and Google Play registration for the apps.
• Maps SDK keys and billing for both mobile platforms.
• Ownership of hosting and backend accounts, plus production secrets for scheduled jobs.
• A US support number.
• Launch location data and participating organizations.
• Release configuration, project records, and secrets for app builds.

Commercial terms, service policies, and launch approvals are tracked separately in Release decisions.