If your hotel already uses a property-management system (PMS) and sells rooms through Booking.com or other online travel agencies, connecting your website to the existing booking infrastructure is usually better than building a new reservation system. The price depends on whether you are configuring a supported connection or commissioning software that must reliably synchronize inventory and reservations between systems.
For a Nigerian hotel planning a project in 2026, I would use these illustrative development allowances before seeing the existing software:
| What you actually need | Initial project allowance | What you are buying |
|---|---|---|
| Existing booking engine connected to a hotel website | Provider subscription and setup, plus separately scoped website work | A supported booking flow, room pages, tracking and testing |
| Supported website and booking-engine integration with custom front-end work | ₦500,000–₦1.5 million | A coherent direct-booking journey, configuration, mobile testing and handover |
| Custom PMS-to-channel-manager or booking-engine integration | ₦1.5 million–₦4 million | API work, room/rate mapping, sync, failure recovery and acceptance testing |
| Multi-property or unusual inventory workflows | ₦4 million+ | Property-level rules, deeper reconciliation, monitoring and ongoing support |
These are my scoping allowances, not independently surveyed Nigerian market averages, vendor quotations or guarantees. A vendor may include standard setup in its subscription; a complex custom connector can cost more. The cheapest responsible solution is often to use an integration your current providers already support.
First, identify the three systems
These products do different jobs:
| System | Its responsibility |
|---|---|
| Hotel website | Helps guests compare rooms and decide to book directly |
| Booking engine | Presents bookable rates and completes a direct reservation |
| PMS | Keeps the hotel’s operational room and reservation records |
| Channel manager | Exchanges availability, rates, restrictions and reservations with connected distribution channels |
A hotel might buy the last three as one suite or from different vendors. The architecture matters more than the product names.
If a guest books the last available room on an OTA, the other sales channels should not continue advertising that same room as available. If staff close a room for maintenance, the relevant availability should change everywhere that sells it. If a guest cancels, the inventory and reservation state need to be reconciled correctly.
That is why a booking widget is not the same thing as an integration.
What does a channel manager actually cost?
Separate three kinds of spending rather than asking for one number.
Software subscription. A channel manager or bundled PMS may charge per property, per room, by plan or through a negotiated contract. Booking engines, extra channels, payments and support may or may not be included. For an example of a published vendor model, HotelSync’s pricing page shows per-unit plans, monthly minimums and different booking-engine commission terms. It is one vendor’s offer, not a market average or a recommendation.
Configuration and onboarding. This includes connecting the hotel to supported channels, mapping room types and rate plans, configuring restrictions, importing or checking data, training staff and testing reservations. A vendor may handle some of it.
Custom development. This is justified when your website, existing PMS or business workflow cannot use a supported connector. It may involve API authentication, event processing, state mapping, monitoring, recovery procedures and continued maintenance.
Ask each provider for a written breakdown of all three. A cheap subscription does not help if your current PMS cannot exchange the data you need.
Before hiring a developer, check whether the API is actually available
A hotel owner should not assume that a developer can connect directly to every OTA by obtaining an API key.
Booking.com’s official Connectivity API documentation describes a partner model with onboarding expectations for companies managing property availability, rates and reservations. Its Connections API guidance also explains property permissions and connection types.
Similarly, SiteMinder’s developer guide describes distinct APIs for booking channels, PMS/RMS providers and other applications. Access and integration scope depend on the relationship and product.
This changes the buying decision. A hotel wanting its own website to accept direct reservations is not necessarily a candidate to become an OTA connectivity partner. It may simply need to embed or integrate the booking engine supplied by an approved provider.
Before paying for custom API development, ask:
- Which exact provider and product are we connecting?
- Is there an existing certified or supported connector?
- Who can grant the necessary access, and on what terms?
- Which system owns room inventory, prices and reservations?
- Can the proposed integration write changes, or only read data?
- Who maintains the connector when the provider changes its API?
A developer cannot responsibly promise access that the provider has not approved.
The difficult work is room and rate mapping
Imagine a hotel that calls a room “Executive Deluxe” in its PMS but “Deluxe Double” on an OTA. The two labels might refer to the same physical inventory. Another channel might sell that room with breakfast included, while the direct site offers room-only and flexible-cancellation rates.
The integration must know what each room type and rate plan means. A wrong mapping can create overbooking, incorrect prices or unexpected cancellation terms.
The same applies to minimum stays, closed dates, occupancy rules and taxes. Booking.com’s availability documentation distinguishes room inventory, rate-level pricing and booking restrictions. Treat those as business rules to verify, not just fields to copy.
A good implementation records the mapping and gives staff a way to spot exceptions.
Test the failures, not just a successful reservation
A demonstration where one guest books one room is not an adequate acceptance test. Ask for evidence of what happens when:
- The last room is booked on an OTA while another guest is viewing it on your website.
- Staff manually block a room in the PMS.
- A guest changes dates or cancels after confirmation.
- A reservation notification arrives twice or arrives late.
- One provider is temporarily unavailable or rate-limits requests.
- A room or rate plan is unmapped after staff change the setup.
- A guest pays a deposit but the booking confirmation is delayed.
For paid direct bookings, a browser success screen should not be the only evidence of payment. The booking and payment records need an explicit reconciliation process. My payment gateway integration cost guide explains why payment verification, retries and duplicate events change the development scope.
For operational reliability, define who gets an alert when synchronization fails and what the front desk should do while the issue is being resolved.
A practical buy-versus-build decision
Use a bundled PMS, channel manager and booking engine when your hotel has standard room inventory, the vendor supports your important channels, and your team wants one accountable provider. That is often the sensible choice for an independent hotel.
Connect an existing booking engine to your website when your reservation software already works but the public site loses guests through weak room pages, confusing mobile booking or a poor handoff. Your investment should improve the guest journey, not duplicate the inventory system. See my hotel website cost guide and direct-booking website guide.
Commission custom integration when you have a genuine gap: an existing PMS with a supported API but no suitable connector, multiple properties with special rules, or operational data that must flow into another system. Commission the smallest integration that solves that gap.
Consider replacing the existing software when the current vendor cannot provide reliable access, cannot support required channels or creates more operational risk than a controlled migration. Do not rebuild an entire PMS merely because a website booking button looks dated.
What should a hotel integration quotation include?
The proposal should identify the exact systems and approved access, supported channels, room/rate mapping, booking and cancellation flows, payment boundaries, data ownership, monitoring, exception handling, test cases, deployment sequence, staff training and support terms.
It should also say what happens if a provider refuses access or a required integration proves unavailable. That dependency should be discovered before a large implementation payment.
For hotels considering Google’s booking surfaces, Google’s official connectivity partner directory explains that approved partners send hotel rates to support free booking links. This is another reason to assess existing providers before inventing a new integration.
When to bring in a developer
If your hotel already has a PMS, OTA listings and a website but the systems do not agree—or guests abandon the direct-booking process—start with an integration and booking-flow audit. Identify which system owns the reservation, where information stops moving and whether a supported connector already exists.
I work on websites and product workflows where ownership, permissions, payments and reliable state changes matter. I would not recommend writing a custom channel manager as the default. If you need help defining the right integration or improving the booking journey, contact me with your existing PMS, booking provider, hotel size and the exact failure you want to fix. We can scope the smallest responsible project before discussing a build.
