Availability and inventory

OutwardOps counts seats, and the boats, guides and gear a trip needs, in one inventory engine. A departure sells out at its real limit instead of overselling. Online, phone and affiliate bookings all draw from the same pool, and any change that would break a limit is checked and refused before it is saved.

Last updated ยท By OutwardOps team

How does OutwardOps avoid overbooking?

Every departure has a seat capacity. When a guest starts checkout the engine places a hold on those seats, and the hold expires on its own if the guest walks away. Staff bookings, affiliate bookings and online bookings all go through the same engine, so two people cannot take the last seat at once.

Moving a booking or changing a party size reserves the new seats first and releases the old ones second. Closing a departure, changing its capacity and cancelling a booking free or protect seats the same way.

OutwardOps calendar showing departures for the month, each with seats booked out of capacity, colored by trip
The calendar shows booked seats against capacity for every departure. Sample data.

Can it track boats, guides and gear, not just seats?

Yes. Boats, guides and gear are resources with a capacity. Each trip says what a party needs, and the engine reserves it for every departure:

  • One boat per departure, one guide for every six guests, or one kayak per guest.
  • A list of resources in order of preference, so the second boat is used when the first is taken.
  • Time before and after the trip that a resource stays reserved, for loading or clean-up.
  • An option to keep a party together on one resource rather than split across several.

What happens when I change the rules?

If a new requirement would leave a booked departure without enough boats or guides, the change is refused and the departure is named, so nothing is silently oversold. A resource that a trip still needs cannot be archived.

A trip's Resources tab: one boat per departure, with a fallback resource option and before and after windows
What a trip needs, set per trip. Sample data.

How do I control what can be booked?

  • Per-trip limits: minimum and maximum party size and a booking cutoff in hours, with separate limits for empty, partly booked and full departures.
  • Per-departure status: open, hidden from the booking page, call to book, or cancelled, plus an unlisted flag for link-only trips.
  • Seat capacity can be changed on any departure, singly or in bulk with a preview, and never below the seats already booked.
  • Affiliate seat blocks and booking rules limit what a reseller can take. Overbooking is a permission that owners and admins hold, so a deliberate overbook is a choice, not an accident.

Ask about this in a demo

Related

Frequently asked questions

Can two bookings take the last seat at the same time?

No. Seats are reserved inside the inventory engine with locks, so simultaneous bookings are serialized and the second one is told the seats are gone.

Does a boat shared by two trips get double-booked?

No. Resources are reserved across every trip that uses them, so a boat used by a morning charter and an afternoon charter is only taken once per time window.

Can staff book past the limit?

Only members with the Overbook permission, which owners and admins have by default. Other staff are stopped at the limit.

Does it handle lodging by the night?

Lodging inventory is built for staff, with units and nightly stays. Guest booking of stays is coming. The departures engine covers seats, boats, guides and gear.

See it with your own trips

Book a demo