One calendar for every source
Channel reservations and direct bookings share a calendar instead of two systems that disagree.
Boris reads your properties and reservations from Beds24 and maps them onto your own resources, so channel bookings sit in the same calendar, customer record and payment history as the ones you take directly.
Available Running against the providerβs production API.
Channel reservations and direct bookings share a calendar instead of two systems that disagree.
Each Beds24 property is matched to the resource it corresponds to, once.
Channel bookings keep what the channel actually pays out, so revenue is not overstated.
Connect your Beds24 account in Integrations.
Refresh properties and map each one to a Boris resource.
Sync reservations and let new ones arrive as they are created.
No. Beds24 keeps distributing to the channels; Boris runs the operation around the reservation once it exists.
Yes, if Beds24 already receives them: Boris imports what Beds24 holds.
Create a workspace, add your resources and connect the tools you already pay for. No credit card required.
Create your workspace