Changelog
Every feature, fix, and improvement — shipped fast, documented here.
OTA reservations — cancelled where they were booked, and a payment status that says who collects
Neither Booking.com nor Expedia lets a channel manager cancel a reservation on their behalf. Bridg_ used to let you try anyway: the room went back on sale in Bridg_ while the OTA still held the booking — which is exactly how an overbooking starts. A reservation that came from an OTA now says, on its detail page, to cancel it on the OTA's extranet; the cancellation then comes back to Bridg_ on its own and releases the room at that moment, not before. The payment status follows the same logic: a reservation is only shown as paid when the OTA itself collected the money, and it says so in plain words.
Satisfaction surveys — a questionnaire in three languages, sent at the right moment
The stay questionnaire in Iris was rebuilt around the categories of the satisfaction reports hotels are already measured on — recommendation, cleanliness, staff service, maintenance, food and beverage — and it speaks the guest's language from the first line, the hotel's name included. The invitation reads as a letter from the hotel, not as a system notification. Behind every answer, Iris shows who the guest is and how they booked, with a button to reply to them directly. And the timing was corrected: the invitation now leaves after the guest has actually checked out, and never during the night.
Dashboard by period — performance on nights stayed, activity on bookings taken
The dashboard had been showing everything « since the beginning », for a reason: its figures were all counted on the day a reservation was taken, which made occupancy and RevPAR meaningless over a short window. It now reads by period — today, the last 7 days, this month, the last 90 days — and keeps apart two questions the industry standards keep apart. Performance (occupancy, ADR, RevPAR, room revenue, room nights) is counted on the nights actually stayed; activity (reservations, revenue booked, cancellations received, share of direct, lead time, length of stay) on the day the reservation was taken. Every figure is compared with the previous period of the same length, and the on-the-books view shows what is already sold for the next 7, 30 and 90 nights.
Arrivals sheet — what reception prepares every morning, on one printable page
Reception had the day's arrivals as a number on the dashboard, not as a working document. The arrivals sheet lists who is arriving, at what time they said they would, what they asked for, which room they are in and what is left to collect, sorted by announced arrival time and printable on a single landscape page. To feed it, reservations received from the PMS now follow the PMS: the date the booking was really taken, its remarks, the company, the nationality — updated with every message the PMS sends.
One name per channel — and channel updates sent in the right order
The same source could appear under three different names depending on the screen, and some reports showed raw codes. There is now a single list of sales channels, shared by every screen, report, export and email. Hotelbeds, until now filed under « Autres OTA », is named; reservations received from the PMS are filed under the channel they really came from. Two distribution fixes ship with it: availability now leaves before prices, so stock changes reach the OTAs first even behind a large price update, and a closure set on one room type no longer closes the whole rate.
Iris Insight by Bridg_ — a new name, a fixed overview, and access granted right by right
Iris takes its full name, Iris Insight by Bridg_, logo included, along with an interface pass: denser screens, replies in one click, a readable activity log. The dashboard opens on a fixed overview built on the standard guest-satisfaction indicators — the same charts for every hotel, so a group compares like with like: recommendation and the main service areas over three years, your reviews against the market, and how many reviews were answered in time. Access to Iris is now granted from the Users screen of the Channel Manager, with five separate rights and an « Iris Insight seulement » account for people who need Iris and nothing else.
Booking engine — corporate spaces ready for a hotel's partner companies, and no more fallback rate
The corporate booking engine gives each partner company of a hotel its own private space with its negotiated rates. It was reviewed end to end before a first hotel put it in front of its clients: a multi-room booking is now priced correctly, a space only sells its own corporate rates, the purchase order becomes optional, and the files companies attach survive deployments. The hotel chooses whether a space needs a password, and the page carries the company's name in its header. On the public engine, the audit of October 10 removed the fallback rate: a room with no active booking-engine rate is no longer shown, rather than sold at a price nobody set.
Google and Tripadvisor reviews in Iris
Iris gathered Booking.com and Expedia reviews; Google and Tripadvisor now join them. Google reviews arrive as they are published and are answered from Iris, the reply appearing on the hotel's Google profile. Tripadvisor reviews arrive in their original language, with the management's reply when there is one; since Tripadvisor offers no way to publish a reply from outside, Iris copies your text and opens the review, and you confirm once it is published. Both sources are connected hotel by hotel by the Bridg_ team.
ADR and RevPAR — room revenue only, excluding tax
An average daily rate that includes VAT, tourist tax and breakfast is not comparable from one hotel to the next, nor with the figures an operator reports. ADR and RevPAR now count room revenue only, excluding tax: no VAT, no tourist tax, no breakfast or package, no complimentary stays. The VAT rate and the breakfast price used for the calculation are set in the property sheet. Two OPERA cases were corrected along the way: a day-use now comes in at the price of its day instead of zero, and packages are read where OPERA actually lists them.
OPERA — one reservation per room type
A guest who books a Double and a Suite in one go makes a single reservation in Bridg_, but OPERA holds one reservation per room type. Bridg_ now sends it that way: BK-… for the first type, BK-…-2 for the next, each with its own rooms, occupants and amount. It is on for every OPERA connection, with no setting to forget.
Hotix — a new PMS interface
Hotels running Hotix can now connect it to Bridg_ from the PMS screen. Bridg_ reads the availability Hotix holds, every few minutes and across the whole selling horizon, and sends each reservation into Hotix as it is taken, modified or cancelled. Hotix keeps control of stock only: prices and restrictions stay managed in Bridg_.
Sources report — every reservation, channel by channel
The Sources tab of the reports gave one line per channel. It now details every reservation behind that line, cancellations and modifications included, with a « Toutes sources » total. Revenue stays net of cancellations, and the cancelled amount is shown apart. A reservation now knows it has been modified — when its dates, rooms or amount change after it was taken — and the report counts those modifications.
Guest messages in Iris, and every review read by AI
Messages guests send through Booking.com, Expedia and Airbnb now arrive in Iris, next to their reviews and with the stay they belong to. The team replies from Iris, or writes first — to one reservation or to the day's arrivals — with ready-made replies, translation and attachments, and unread messages are flagged as they come in. On the review side, the analysis now runs entirely on AI: each review and survey answer is read sentence by sentence, every sentence tied to its topic, the guest's sentiment and emotion. Iris turns that into the mood of your guests and flags the dissatisfied ones to call back — including those who gave a good score but wrote a disappointed text.
Team and hotel groups — the owner grants what they hold
An owner could already invite a colleague, but a right ticked outside the colleague's role quietly disappeared. The owner can now grant or withdraw any right they hold themselves, whatever the colleague's role, and a removed collaborator keeps nothing. Properties that belong to the same hotel group are gathered under the group's name in the property selector and in invitations.
Oracle OPERA — a complete two-way interface, in production
Bridg_ now talks to Oracle OPERA through OXI in both directions, and the first hotels run on it in production. OPERA sends its availability by room type, its rates and its restrictions, and Bridg_ passes them on to every channel; Bridg_ sends OPERA the reservations taken on the OTAs and on the hotel's website, and receives those taken at the front desk. The details that make an interface usable day to day came with it: several rooms in one stay, foreign-currency bookings converted to dinars, the right company or agency profile on each reservation, and a PMS screen the property owner can run without calling anyone.
Booking engine and reports — prices that add up
A round of corrections on what the guest pays and what the hotel reads. The tourist tax now applies to every night, including nights whose price comes from the PMS, and the price calendar no longer drops to zero in that case or announces a price the room list then contradicts. Optional extras stay optional, a minimum stay set on a rate is enforced, and a stop sale closes the hotel's own website as well as the OTAs. On the reporting side, the reservation list and the by-rate report show the rate the guest actually booked.
Iris — reviews, surveys and AI insight, in one place
Iris goes into production. It gathers what guests say about a hotel and turns it into work for the team: every Booking.com and Expedia review becomes a ticket with a priority, an owner and a deadline, tied to the guest's stay and answered from Iris. Reviews are read sentence by sentence and sorted by domain, theme and aspect, so a score can always be traced back to what guests actually wrote. Post-stay surveys are sent automatically after departure and read on dashboards built on the standard satisfaction metrics, next to a benchmark against the hotel's competitive set. On top, AI writes insight reports and drafts replies.
Marketplace — every Bridg_ product, and what is already connected here
The Marketplace gathers every Bridg_ product and integration in one catalogue, laid out like an app store: categories with counters, a search, one card per product. Each card reflects the real state of the property being viewed — a PMS interface connected, a module active, Iris switched on — and the product sheet sends an activation request to the Bridg_ team in one gesture. It is open to every user, because knowing what exists should not require a special right.
PMS-connected mode — reservations and stock follow the PMS
When a hotel runs a PMS, the PMS is the reference for what happens at the front desk, and Bridg_ now behaves that way. The Reservations screen shows the day as reception lives it — arrivals, departures, guests in house — with the PMS's own number, status and room on each reservation. Check-in, check-out and no-show come from the PMS rather than from a button in Bridg_. On the stock side, the inventory sent to the channels is the PMS's, and reservations taken at the front desk now decrement it. The same protocol Bridg_ HMS uses is now open to third-party PMS as JSON Connectivity.
Calendar and rate plans — a grid that works like a spreadsheet
The calendar is where a revenue manager spends the day, and it now behaves like the spreadsheet they would otherwise open next to it: a 7, 14 or 30-day horizon, frozen headers, filters and restrictions inside the grid, several cells edited at once, copy, paste and fill. Rate plans were reworked in the same pass: each plan says what it sells and shows the price its settings produce, a rate can be distributed on several channels, and the hotel's own booking engine becomes a channel like the others. When a PMS holds prices and restrictions, the calendar now says so instead of letting a change be silently overwritten.
Payments that didn't go through — never counted as cancellations
With card prepayment came a new kind of reservation: one the guest started but never paid. Counting those as cancellations would have made a hotel's cancellation rate jump for reasons that have nothing to do with its guests. They now live in their own « Paiements non aboutis » area, the dashboard shows what was lost at payment instead of a cancellation rate, and a prepayment still in progress is not counted as sold.
Card prepayment — CIB payments through SATIM, and a booking that only counts once it's paid
Until now every direct booking arrived unpaid, and a hotel with a no-show problem had no way to ask for the money up front. A rate plan can now require prepayment: the guest sees it on the rate card before choosing, pays by CIB card on SATIM's secure platform, and only comes back to a confirmed reservation once the gateway has accepted the payment. That last part is the whole point — the booking is created but held, no confirmation letter goes out, and nothing reaches the PMS until the money is actually authorized. A declined card doesn't destroy the booking either: it stays open for twenty minutes so the guest can retry, then releases the rooms on its own if they don't. Everything the bank needs to identify the payment — transaction number, authorization code, masked card, timestamp — is kept on the reservation and printed on the confirmation letter, the PDF and the hotel's own copy, so a disputed charge can be traced without calling anyone. Merchant credentials live in a new Paiement screen open to the account owner alone: they commit the hotel financially, so no manager, however senior, can read or change them.
Loyalty in the booking engine — members sign in and see their own rates
A hotel with a loyalty program can now connect it to its booking engine. Guests sign in or join from the engine itself — with a password or a one-time code sent by email — and the rates reserved to their tier appear at once, marked « Tarif membre ». A rate can be reserved to one or several tiers of the program, straight from the rate dialog. The engine carries the program's logo and invites members to open or get the program's app. In the same release, « Mes réservations » lets any guest find a booking without the confirmation email — reservation number, arrival date and name — then consult, modify or cancel it.
Price safety — a guard against price collapses, and booking-engine prices checked by the server
One mistyped price can sell a whole season at a loss before anyone notices. Bridg_ now refuses any price drop of more than half unless the user explicitly confirms it. The booking engine got the same kind of protection: the price of a reservation is checked again by the server when it is created, rather than trusted as sent by the browser. A series of silent gaps between Bridg_ and the OTAs was closed in the same round.
Notifications — every new reservation on your phone, and the day's activity every evening
Two ways to know what happened without opening the back-office. The mobile app now sends a notification for every new reservation. And every evening, each hotel receives the Daily Pickup by email: the reservations taken that day, the stays modified and the cancellations, each list on its own date. A day without activity sends nothing.
Top Management — an executive role that sees the numbers, never the guests
Some people on a hotel's team need the performance numbers and nothing else — no reservation list, no guest names, no way to open a booking and see who's staying in room 214. Top Management is a new role built around that boundary: it can see the Dashboard and Rapports, both built entirely from aggregate figures, and every other screen in the app responds with a plain "you don't have permission to view this screen" instead of quietly rendering a stripped-down version. The restriction isn't just a hidden menu — the API itself refuses booking and guest data for this role regardless of which route is used to ask for it, so there's no client-side trick that gets the names back.
Bridg_ Table — social links on the hero, only the ones you set
A restaurant with an Instagram full of plated shots and a WhatsApp line guests actually book through had nowhere to put either on the widget. Image de marque now has a Réseaux sociaux card — Instagram, Facebook, TikTok, WhatsApp, X, each entirely optional and independent — and the hero shows a small icon for exactly the ones filled in, nothing more. Leave all five blank and the row simply doesn't render.
Bridg_ Table — keyboard access, sharing, a proper loading state
The floor plan was the one part of the widget you couldn't reach without a mouse or a finger — tables lived on an SVG canvas with no keyboard path in or out. They're now real focusable, operable controls: tab to one, see a clear copper focus ring, hit Enter or Space to pick it. The same themed focus ring now shows up consistently on every pill-shaped control in the flow — zone chips, occasion tags, time slots, the party counter, the room switcher. Past the accessibility work: a confirmed reservation can now be shared (native share sheet on mobile, a copied link on desktop) instead of only living in an email, a day with nothing free shows "Complet" right on the date field before you even open the calendar, and the first-load skeleton now traces the actual layout — hero, stepper, fields — instead of two grey rectangles.
Bridg_ Table — availability dots, a photo carousel, and social proof
A round of the kind of small conveniences that separate a booking form from a booking experience. The calendar now shows a dot under any day with at least one open table, instead of making guests click through each date blind; picking a fully-booked day surfaces the next open one with a single tap instead of a dead end. The hero band got a real photo carousel when a restaurant has more than one image, plus an optional rating-and-review-count line next to the star classification — self-reported by the property, since Bridg_ doesn't aggregate reviews itself. And the guest form picked up quick occasion tags (birthday, date night, business dinner, family celebration) that write themselves into the special-requests field instead of asking every guest to type it out.
Bridg_ Table — one floor plan per room, and a wider stage on desktop
Two rounds of feedback on the 2.11.0 redesign, both addressed. First: a restaurant with several physical rooms was getting one combined floor plan, which made no sense — two rooms don't share a coordinate space. There's now a room switcher, in the back-office editor and on the public widget alike, so each room gets its own plan; if a guest already picked a room at the reservation step, the table step locks straight to it instead of showing tables from rooms they didn't choose. Second: the reservation card was quietly narrower than the hero band sitting above it, which is what made everything feel cramped once the stepper grew to four steps — widths now match, the card no longer crowds the hero above it, and the stepper's longest label got trimmed so its rhythm holds at any step count.
Bridg_ Table — a visual pass worthy of the category leaders
A craft pass across the entire public reservation engine, end to end, with the category's best (Resy, Tock, SevenRooms) as the bar rather than a checklist. Nothing about how the widget behaves changed — every screen, transition, and micro-interaction got more considered instead: bolder hero typography, a stepper that actually fills as you progress, warmer floor-plan tables that cast a real shadow and glow softly when picked, icon-led form fields, and a confirmation ticket with a small pulse of its own when your table is booked. It reads as one deliberate product now, not a form with steps.
Bridg_ Table — the floor plan, properly sized for a phone
A floor plan drawn in virtual coordinates has an obvious failure mode on a small screen: shrink it to fit and the table labels and resize handle shrink right along with it, past the point of being readable or tappable. The floor-plan canvas now measures its own real rendered size and keeps labels, the resize handle, and each table's touch target above a readable/tappable floor regardless of screen size — desktop is untouched, since it never needed the floor. The back-office editor's headers and tab list, which used to compress awkwardly next to a button on a narrow phone, now stack and scroll properly instead.
Bridg_ Table — draw your floor plan, let guests pick their table
Table assignment stops being invisible. A new floor-plan designer in Bridg_ Table lets a property draw its dining room exactly as it really is — drag tables into place, resize and rotate them freely, color-code them by zone — and, once it's arranged, choose to let guests pick their own table from that same plan on the public widget instead of getting a silent auto-assignment. Every table shows live, per-slot availability, and the chosen table follows through to the confirmation ticket. Left off by default until a property has actually drawn its plan, so nobody sees a pile of overlapping default tables by accident.
Bridg_ Table — make the booking engine your own
A hotel restaurant is its own brand, not just a room-service line item — so Bridg_ Table now lets it look like one. A new "Image de marque" tab gives the restaurant its own name, description, logo and photo gallery, separate from the property that hosts it, plus six color pickers for the public widget's palette. Nothing is mandatory: every field falls back cleanly to the property's own identity and to the existing Encre & Cuivre theme, so a restaurant nobody has touched looks exactly as it did yesterday.
Bridg_ Table — a booking engine that looks the part
The public reservation widget is rebuilt end to end: a guided flow instead of a dense one-page form, time slots grouped by service the way the category leaders do it, a tactile party-size counter, a real calendar picker, and a confirmation screen designed like a keepsake rather than a receipt — complete with a working "add to calendar" file. It's built entirely in the visual language already established across the marketing site and dashboard, so it reads as one product, not a bolted-on widget.
Bridg_ Table — an activatable module, not a plan tier
Restaurant reservations (introduced in 2.6.0 as a plan-tier feature) are now a module activated per client from a dedicated admin screen, independently of their subscription plan — the same idea as the loyalty program, but for the whole feature. A client without it doesn't see it: no menu entry, no access, not even by typing the URL directly. Testing this surfaced a real gap — the module's read routes weren't checking entitlement at all, only the write ones — now closed.
Restaurant reservations — a new module for in-house dining
A property can now open table reservations for its restaurant, activated per plan the same way the loyalty program is. Guests book through a public widget with no login and no payment step, get an instant confirmation with a self-service link to change or cancel, and the property receives a printable back-office letter for every new, modified or cancelled reservation. The allocation engine assigns the best-fitting table on its own, and falls back to combining two adjacent tables when no single one is free.
House rules on children — adults-only properties, adult age threshold
Two rules that belong to the house rather than to a rate plan. A property can now declare that it does not accommodate children at all, and can set the age from which an occupant counts as an adult. Above that age they enter the room price through the occupancy tier instead of being billed as a child — previously a teenager came out cheaper than an adult even where the property treated them as one.
Dashboard focus — revenue and average rate first
The dashboard now opens on the two figures a hotelier actually reads first. Revenue and average rate get a full-width row of their own instead of being buried among ten identical tiles; occupancy rate and tonight's occupancy are gone from that view. The channel-level sales switch introduced in 2.3.0 has been withdrawn.
Cancellations reach the hotel, marketing references appear within the minute
A cancellation coming from an OTA released the inventory without a word to the property — staff discovered the departure by reading their calendar, or never did. Every cancellation path now notifies the hotel. Separately, opting a property into the marketing references took up to 24 hours to show, and the screen never explained why nothing happened.
Daily production report, property activation, disabled rooms kept out of sight
A production report now lands every evening — the whole portfolio first, then each property, with the day's sales placed on their arrival dates over a rolling 60-day horizon. Super admins can activate or deactivate a property in one click, and a deactivated property genuinely disappears from the booking engine. Disabled room types no longer surface where they cannot be sold.
Child pricing moves to the property, connectivity provider hidden
The child-age policy lived on each rate plan, so eight rate plans meant eight identical grids to maintain — and a forgotten one showed up nowhere. It now belongs to the property, with a per-rate override for the case that warrants it: the meal plan. A simulator shows what a grid produces before it is saved.
Child supplements by age bracket
Children counted towards capacity but never towards price — the ages collected at booking were ignored by every calculation. Rate plans can now carry age brackets: free under 3, half price to 11, a fixed amount beyond, with a cap on how many children are billed.
Bulk update rebuilt, availability and rates sent correctly to the channels
The bulk update screen offered seven flat buttons mixing two independent dimensions, several of them duplicating actions available elsewhere. It is now a scope × attribute matrix with a server-side preview that counts exactly what will be written. Underneath, several defects were sending the wrong availability and rates to the channels.
Audit log, booking filters, marketing references
An activity log now records who did what, per property and across the platform. The bookings list gains date filters and sorting, and properties can opt into appearing among the references on the public site.
Real PDF generation for contracts & proposals, monthly billing option
Contract and proposal PDFs are now generated server-side (headless Chromium) instead of relying on the browser's print dialog, so "Download PDF" always produces a real file directly. Proposals also gain an Annual/Monthly billing-period option for offers structured as recurring payments instead of a single annual sum.
Foreign-currency visibility on the bookings list & reports
Follow-up to v1.13.0: bookings taken in a currency other than the property's own are now easy to spot at a glance, and reports break out how much revenue came from each currency instead of only showing the converted grand total.
Automatic currency conversion for reservations & reporting
Reservations taken in a currency other than the property's own (OTA bookings, corporate, or manual entry) are now converted to the property's currency at the exchange rate in effect at booking time, and every dashboard, report and KPI rolls up the converted figures — no more USD or EUR bookings silently mislabeled as DZD.
Booking engine — correct room count on a repeat search
Fixes the auto-selected room quantity on the booking engine getting stuck on a stale value after searching again with a larger party — the previewed price now always matches the number of rooms actually required.
Branded confirmation emails, corrected KPIs & custom date range
Confirmation emails now pick up each property's own brand colors automatically, ADR and related KPIs are corrected to reflect actual room-nights sold, and the dashboard gains a custom "from / to" date range.
Notifications, Best Offer & exports PDF
Live admin health notifications, a 'Best Offer' highlight on rate plans, PDF export for contracts and proposals, per-occupancy OTA rate configuration, and new Terms/Use Cases marketing pages.
Guides canaux, KPIs analytics & écrans admin
Structured French integration guides per channel, four new analytics KPIs, and four new full admin management screens: emails, proposals, contracts and analytics.
Corporate Booking Engine
A new private booking channel for corporate accounts — admin management, PO upload, its own calendar driven by corporate rates — plus a dedicated channel-availability management page.
Tri des chambres & tarifs par canal
Room display preferences, dedicated OTA rate-plan colour coding, and layout refinements across the calendar and booking-calendar search.
SEO, GEO & site multilingue
Full multilingual routing launch for the marketing site (French / English / Arabic with hreflang), a GEO push for AI answer engines, a public search page, dynamic per-property currency display, and new manual pricing-override modes in the calendar.
Encre & Cuivre : refonte + durcissement sécurité
Full 'Encre & Cuivre' rebrand rolled out across marketing, dashboard and admin, alongside a critical security upgrade (6 high-severity advisories), major refactors, an accessibility pass, and layout performance fixes.
Landing & Performance
Premium redesign of the public landing page trust section, logo visibility improvements, and a full development-server stability fix.
Sync, Billing & Emails
Major OTA sync engine hardening, billing upgrade gates across the dashboard, admin support mode, and automated hotel email notifications.
Reports, Notifications & i18n
Complete Reports page with KPIs and Excel export, real-time booking notifications with sound, No Show workflow, full booking engine internationalisation (FR / EN / AR with RTL), and a detailed help documentation page.
Dashboard, Booking Engine & Admin
Full dashboard overhaul with KPI tooltips, revenue chart, and Excel export. Complete booking engine redesign with a warm design system. SUPER_ADMIN panel, user management with invitation emails, and deep OTA connectivity.
Initial Release
First production-ready release of Bridg_. Core booking engine, bidirectional OTA integration (Booking.com, Expedia, Agoda…), calendar with live pricing, property media management, and all foundational backend APIs.