Product
Table Bookings
Integrations
Summarygenerating…
Overview
Because Stampede modules share a data layer, turning on Bookings immediately feeds every other connected module. Deposit payments flow through PayOS; bookers appear in Marketing audiences; reservations attribute to campaigns.
How it works
Shared data layer. No separate API integration between modules — connections are enabled with a switch.
Core concepts
Native integration
one data layer across modules.
PayOS
processes deposits and pre-orders via Square.
Usage & workflows
Turn on the modules you use; Bookings lights up correspondingly.
Example
Enabling PayOS on an existing Bookings deployment immediately unlocks deposit taking and in-venue payment links to reservations.
Note
Where to find it
Configure this in the Stampede admin app under Admin → Bookings. Permissions are role-gated — contact your account owner to request access if you don't see it.
Tip
API reference
The Stampede API exposes guest, booking, and campaign data programmatically. See developer.stampede.ai for authentication, base URL, rate limits, and endpoint reference.
Note
Need help?
Contact support via the Stampede admin app or your account manager. The knowledge base at help.stampede.ai has guided walkthroughs for common tasks.
Want to see it live?
Book a 20-minute walkthrough and we'll show you the feature in your own admin.