A storefront that also books the trip.
A rental shop and guide service was selling gear on one platform and taking trip bookings by email on another. We rebuilt both into a single storefront that checks availability across equipment, guides and dates.
- Client
- Aurora Ridge Outfitters
- Industry
- Outdoor retail & tourism
- Location
- Jasper, Alberta
- Timeline
- 10 weeks
- Team
- 2 engineers, 1 designer
Rent the gear. Book the guide.
Plan a tripE-commerce & Guided-Trip Booking Platform
Gear and trips lived on separate systems. A customer could book a canoe trip for a date when every canoe was already rented, and staff would find out the morning of.
The old storefront took four seconds to become interactive on a phone, which is where 78% of the traffic came from.
- Next.js
- Shopify
- Sanity
- Vercel
What it looks like in use.
Booking pipeline
4 rowsRevenue by channel
BeforeAfterFour decisions that made it work.
-
01
One availability model
Guides, permits and equipment share a single calendar, so a booking can never double-allocate a canoe.
-
02
Books first, sells second
The homepage leads with the trip, and gear bundles attach to the booking at checkout.
-
03
Rebuilt for a phone on LTE
Server components, image budgets and an 18KB first-load bundle brought LCP under a second.
-
04
Editors, not developers
Trips, journal posts and seasonal promos are managed in a headless CMS the team actually enjoys.
“We stopped double-booking canoes, and the site finally loads on the road to the trailhead.”