TrailDrop NL — the spec

A client portal for solo operators running outdoor-gear delivery services in Newfoundland. Visitors upload their Airbnb booking confirmation, answer a short fit and trip questionnaire, pick a curated gear bundle, and schedule a delivery to their accommodation — all without the operator touching the order. Built for one-person businesses that need bookings to run themselves.

---

Decisions locked

---

The core loop

1. Visitor receives a booking link and logs into the portal.
2. They upload or paste their Airbnb confirmation; the portal extracts the property address and arrival/departure dates automatically.
3. They complete the size-and-fit questionnaire; local weather for their travel dates loads in the background and flags gear adjustments.
4. They browse trip-type bundles (hiking, kayaking, camping) with weather-informed recommendations surfaced at the top.
5. They select bundle items, choose a delivery window tied to their arrival date, and pay.
6. The operator receives a formatted order summary; no manual back-and-forth required.

---

v1 scope

Airbnb Address Auto-Sync
Parses an uploaded booking confirmation (PDF or forwarded email) or a pasted confirmation number to extract the property address and stay dates. Lives on the onboarding screen immediately after login.

Delivery Window Scheduling
Lets the visitor pick a delivery slot anchored to their confirmed arrival date, with the operator's available windows as constraints. Lives on the checkout screen.

Size and Fit Questionnaire
A short form (clothing sizes, shoe size, height, weight) completed before the bundle browser loads. Results are stored against the booking and used to pre-filter gear options. Lives between address sync and the bundle browser.

Local Weather Integration
Pulls a forecast for the stay location and dates; surfaces a warning banner and reorders bundle recommendations when conditions call for rain gear, extra layers, or similar. Lives on the bundle browser screen.

Trip-Type Gear Bundles
Pre-built bundles (hiking, kayaking, camping) displayed as cards with itemised contents and a single add-to-cart action. Individual items within a bundle can be swapped. Lives on the bundle browser screen.

---

Deliberately later

• Rental vs. purchase toggle — requires inventory-state logic and a returns workflow; adds operational complexity before the base order flow is proven.
• Pre-trip packing checklist with photos — high content-production effort; more valuable once repeat customers exist and retention matters.
• Host notes field — useful coordination feature, but operator-free bookings come first; add once the core handoff is stable and edge cases are understood.

---

Data model sketch

• booking — id, visitor_id, airbnb_confirmation_ref, property_address, check_in_date, check_out_date, status
• visitor — id, email, phone, created_at
• fit_profile — id, visitor_id, booking_id, clothing_size, shoe_size, height_cm, weight_kg
• weather_snapshot — id, booking_id, location_coords, forecast_json, fetched_at
• bundle — id, trip_type (hiking/kayaking/camping), name, description, base_price
• bundle_item — id, bundle_id, product_id, quantity, swappable
• order — id, booking_id, bundle_id, delivery_window_start, delivery_window_end, total_amount, payment_status
• order_item — id, order_id, product_id, quantity, size_variant

---

Screens

• Login / Link Entry — visitor authenticates via the operator-issued booking link.
• Confirmation Upload — paste confirmation number or upload PDF; address and dates extract automatically.
• Fit Questionnaire — collects sizing data before the visitor reaches any gear.
• Bundle Browser — trip-type bundle cards with weather-informed recommendations and item-level swaps.
• Cart and Delivery Scheduling — review selected items, pick a delivery window, apply any discount codes.
• Checkout and Payment — payment capture with email/SMS confirmation sent to visitor and operator.
• Operator Order Dashboard — read-only summary of all incoming orders, formatted for fulfilment with no manual data entry required.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the portal with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are all here.
• Keep it as the single source of truth while you build, so every feature decision has a reference point and scope stays contained.