1
Create your site
Account → site → basics. You’ll get IDs and secrets for any connector you add later.
Outfitter operating system
First Wave Logic is the native-first system for outfitters who need direct booking, payment clarity, manifest, check-in, and AI guest help without living in a pile of spreadsheets, missed calls, and brittle plugins. Already on WooCommerce? Connect easily with the plugin—orders land in the same calendar and manifest as native bookings. WordPress and outside channels can stay in the loop without being the operating brain.
Software you run to sell direct, run the day, and keep guest, payment, and field reality aligned. Not a generic scheduler. Not a marketplace skin. The product is built for outfitters who need one calm operating brain.
Capacity-aware scheduling so direct bookings and ingested orders land in one truth.
Share links for your site; guests book against real availability.
Built-in checkout when you configure Stripe and native capture—fees are visible at pay time, per your setup.
Run-of-show and guest status for crew and dock—not a PDF scavenger hunt.
Handoffs, units, and timing built for rental ops—not squeezed into tour-only widgets.
Assistant answers from your content; staff can take over when it matters.
Incoming bookings and refunds from supported channels—including WooCommerce via a simple plugin when you keep WordPress checkout. Idempotent patterns.
Booking data in CSV from the operator app when you need a copy.
Straightforward
What ships today, why it matters, and where the leverage shows up in a small operation.
| Feature | Advantage | Benefit |
|---|---|---|
| One calendar | Every channel feeds the same schedule. | Fewer double-books and “which spreadsheet is right?” moments. |
| Native Stripe path | Guests pay in Stripe Checkout when you enable it; splits follow your Connect rules. | Transparent totals at checkout; less manual payout chasing for that volume. |
| Manifest + check-in | One run sheet, mobile-friendly. | Guides and desk share the same picture under pressure. |
| Rental workflows | Inventory and timing tied to bookings. | Dock and office stop arguing about what went out the door. |
| Guest chat (KB) | Repeat questions answered from your docs; escalation to humans. | Less inbox noise without pretending AI replaces judgment. |
Big listing and legacy res systems often bundle their margin and rules. Here you run your site and schedule; on direct checkout, Stripe shows the full total before pay. We’re not claiming we beat every competitor on every metric—we’re built for operators who want control, clarity, and modern UI without the marketplace tax on every ticket.
| Area | Typical legacy / marketplace | First Wave Logic |
|---|---|---|
| Who owns the guest relationship | Often the portal’s brand first | Your booking links, your comms, your KB |
| Fees on direct sales | Opaque bundles, surprise line items | Stripe shows what the guest pays when you use native checkout—configured per site |
| Calendar & rentals | Ticket mindset; rental often bolted on | Calendar, check-in, rental-oriented workflows together |
| After the sale | Sheets and side channels | Manifest + check-in in one app |
| Your data | Export varies; lock-in pressure | CSV export from the operator app for bookings |
Exact fees and legal merchant-of-record depend on your Stripe setup and contracts—configure with counsel as needed.
Small crew, big-house execution
You don’t need a stadium crew to run a tight show. You need one schedule everyone trusts, guest answers that don’t all land in your inbox, and check-in that works on the dock—not a metaphor for fame or guaranteed revenue, just the same people sounding like a much larger outfit because the system carries the admin weight.
Simple path
No maze—create a site, add what you sell, share your booking link. Connectors are optional.
1
Account → site → basics. You’ll get IDs and secrets for any connector you add later.
2
Tours, packages, rentals—capacity and pricing live where bookings pull from.
3
When you’re ready, enable native checkout and Connect per your deployment. Or keep payment external and still run calendar and manifest.
4
WooCommerce first: plugin-based connection—minimal setup, same operator calendar. Shopify, Square, Wix, and API paths also let bookings land in one place if you still sell there.
Migration without surrender
The point is not to become another patchwork integration project. The point is to let operators keep selling where they need to while moving the operating brain into First Wave Logic.
Default
Products, availability, checkout, manifest, and guest self-service live here first.
Shipping now
Keep the site and storefront; install the plugin, paste your connection details, and Woo orders sync into the same calendar and manifest—no custom REST project for a standard shop.
Next priority
High-value migration connectors for operators who want better economics and a sharper operations desktop.
Channel layer
Build outward from a clean ingest contract instead of rewriting the product for every platform.
These are the surfaces that make the product useful: schedule, day-of execution, and guest communication. Capture live product screenshots before production launch, but sell the workflow now.
One calendar for native and connector bookings, weather changes, and staffing decisions.
Capacity, status, and timeslot control at a glance.
Manifest, check-in, alerts, and the operator brief for crews under real pressure.
The day-of source of truth for crew and office.
Booking pages, weather-flex logic, and AI guest help that reduce missed calls.
Direct booking and support without funnel leakage.
Day-of
Bookings carry product and guest context into the calendar your team already uses. Check-in updates reality for office and field. Guest chat and reminders knock down repeat questions—your people handle exceptions.
When you use native Stripe
With Stripe Connect configured, application fees and transfers follow rules you set—so you spend less time on manual payout admin for that volume. Roles (platform vs connected account) must match your legal setup.
Straight answers—no hype.
No. The default story is your booking pages on this platform. Connectors exist if you still sell elsewhere and want those bookings in the same calendar and manifest.
For built-in checkout, yes—it’s Stripe. If guests pay elsewhere (PayPal, in-person, another gateway), set payment capture accordingly and use booking ingest or manual payment state; we don’t run PayPal inside FWL checkout today.
Money routes through Stripe Connect per your configuration—application fees and transfers at checkout when that path is enabled. Your merchant-of-record and agreements still need to match how Stripe is set up.
Same job—schedule, sell, run the day—but with a different center of gravity. You keep direct booking control, get a sharper operator UI, optional AI guest handling, rentals alongside tours, and migration paths from legacy platforms without making connector sprawl the whole product. See fees & how it works for checkout fees and support expectations.
That is the plan. The product direction is native-first with connectors where they actually help: WooCommerce first, then high-value migration paths like FareHarbor and Rezdy. The goal is one operator desktop, not a permanent patchwork.
Yes—CSV from the operator app for site booking lists.
Create an account and step through setup—no inflated promises, just the product as it runs today.