Why connectivity matters
Section titled “Why connectivity matters”Every booking path depends on accurate hotel supply. If the rate is wrong, the guest loses trust; if availability is wrong, the hotel risks a failed booking; if inventory is stale, no route behaves reliably. Wink powers more than a website booking button — the same hotel data supports website paths, shareable links, QR codes, web components, WinkLinks storefronts, partner links, Traveliko listings, social booking routes, Agentic AI handoffs and developer flows. All of them need the same foundation: accurate ARI — Availability, Rate and Inventory.
The two setup paths
Section titled “The two setup paths”Path 1 — Connect a supported provider. Use this when the hotel already manages rates in a channel manager, PMS, CRS or rate provider that Wink supports. The hotel selects the provider in Extranet, activates Wink as a channel in the provider dashboard, maps room types and rate plans, and the provider sends ARI to Wink — filling the Master Rate Calendar automatically. Best for multi-channel hotels, frequent rate changes, live inventory needs and lower manual workload.
Path 2 — Load rates manually in Extranet. Use this when the hotel doesn’t use a supported provider or wants to operate Wink manually, via Distribution > Master rate calendar — single-date and bulk updates across date ranges. Best for small inventory, early setup or testing. It requires discipline: if rates change in the operation, someone must update Wink. And if a provider is connected, a manual change can be overwritten when the provider sends its next update for the same dates.
Connected provider vs manual loading
Section titled “Connected provider vs manual loading”| Question | Connected provider | Manual loading in Extranet |
|---|---|---|
| Who updates ARI? | The supported provider sends updates to Wink. | The hotel updates rates and availability manually. |
| Best for | Multi-channel hotels, frequent changes, live inventory. | Small inventory, limited use, no connected provider. |
| Workload | Lower daily workload after setup. | Ongoing manual maintenance. |
| Real-time behavior | ARI updates automatically from the provider. | Only as current as the last manual update. |
| Risk | Mapping or provider setup must be correct. | Stale rates or availability if not maintained. |
| Booking notification | Channel manager / CRS / PMS notified where configured. | Hotel receives booking notifications through Wink. |
Supported providers
Section titled “Supported providers”Wink supports a range of channel managers, plus PMS connections directly or through Channex as a proxy. Confirm your specific provider version, setup path and mapping requirements with the Wink team before going live.
| Provider | Type | Notes |
|---|---|---|
| SiteMinder | Channel manager | Direct integration |
| Cloudbeds | Channel manager | Direct integration |
| Travelclick | Channel manager | Direct integration |
| RateGain | Channel manager | Direct integration |
| D-EDGE | Channel manager | Direct integration |
| YieldPlanet | Channel manager | Direct integration |
| Rate Tiger | Channel manager | Direct integration |
| Hotel Link | Channel manager | Direct integration |
| Channex | Channel manager + PMS proxy | Direct, plus a proxy for many PMS providers |
| SynXis | CRS | Extra setup via SynXis Channel Connect Express may be required |
Many PMS systems — for example Mews, Apaleo, Opera Cloud and OTA Sync — can route ARI to Wink through Channex as a proxy. If your PMS connects to Channex, it can reach Wink; confirm your PMS version and Channex setup before going live. (This is a representative list — confirm your provider with the Wink team.)
Provider setup, in brief
Section titled “Provider setup, in brief”In Extranet, go to Distribution > Channel manager, select your rate provider and save. In the provider dashboard, add the Wink channel and map the room types and rate plans created in Wink. Initiate a full rate push if the provider doesn’t do it automatically, then check the Master Rate Calendar — it may update within a few minutes (timing varies by provider and mapping). Use the Verifier to simulate a traveler price request and test availability, currency, discounts and rate display before sending live demand. Create a test booking only once the team understands notification behavior.
Booking notifications
Section titled “Booking notifications”Connectivity isn’t only about sending rates to Wink — it’s also how bookings flow back. When a booking is made, the channel manager, CRS or PMS can be notified where configured; the hotel and traveler receive confirmation emails; partners receive booking and attribution confirmation on partner routes; and developers can listen to a booking.created webhook for real-time detail.
Where Wink fits
Section titled “Where Wink fits”Connectivity sits between Extranet and Booking Engine. Extranet is the hotel-side control layer for content, rooms, rate plans, restrictions, availability, policies and Booking Engine settings; a supported provider feeds ARI into it, or the hotel maintains the Master Rate Calendar manually; and Booking Engine uses that approved data to fulfill bookings from direct, Social, WinkLinks, partner, Traveliko, Agentic AI and developer routes. The simple rule: the stronger the connectivity, the more reliable the booking path.
Common mistakes
Section titled “Common mistakes”- Assuming Wink can sell without current availability. It needs ARI from a provider or manual Extranet updates first.
- Connecting a provider but not mapping rooms and rate plans. Setup isn’t complete until mapping is correct.
- Manually editing rates while a provider is connected. Manual changes can be overwritten by the next provider update.
- Forgetting to verify. Test rate display, availability and discount logic before sending live demand.
- Treating connectivity as only a technical task. It affects revenue, marketing, partner routes, conversion and guest trust.