Quotes that show their working: the design of AI Otel’s distribution hub

A B2B hotel distribution hub is software where hotels publish contracted rates to travel agencies and receive their bookings. AI Otel's distribution hub is built so that every quote shows its working: the hotel's net, each pricing rule that fired and the final price. It is built with seed data; no agency is connected yet.

An agency replies to a quote with one line: last month this stay cost less, why. The reservations manager opens a spreadsheet, finds four rules stacked on top of each other, and cannot say with certainty which of them produced the number that was sent. This article explains what a quote that shows its working contains, how one engine can serve two confirmation models, and what you should ask any distribution platform before you sign. It also states, plainly, what exists in our hub today and what does not.

What is a B2B hotel distribution hub, and what does showing its working mean?#

A B2B distribution hub is the place where a hotel publishes its contracted rates to travel agencies and receives their bookings. Showing its working means the quote prints the intermediate numbers and the rules behind them, not only the final figure.

A contracted rate is a price agreed in advance between one hotel and one agency, with conditions attached: stay dates, room type, meal basis, cancellation window and release period. A net rate is the amount the hotel receives for the room. The agency adds its own margin on top and sells to the traveler at its own price. The two numbers are different and should never be confused.

Showing its working borrows the school phrase: the answer alone is not enough, the steps are written down so anyone can check them. A channel manager pushes availability and rates to sales channels. A hub carries the commercial relationship as well: the terms, the agency-specific rates, and the calculation behind each quote. The market uses several names for this idea. What matters is not the label but whether the platform can explain a price after the fact.

The test is simple: hand the quote to a colleague who did not build it and ask them to reproduce the number.

Why can nobody trace a hotel quote today?#

Because a quote can arrive as a single number, produced by rules that live in a spreadsheet, an email thread or one person's memory.

The rules stack: seasonal rate, weekend supplement, length-of-stay discount, early booking, room-type upgrade, agency-specific adjustment, child policy, taxes. Each one is a legitimate commercial decision. Only the final number leaves the hotel. The reasoning stays behind, in a file that was built for internal use.

When the agency asks why, someone rebuilds the calculation backwards. The rebuild is done under time pressure and may not match the original. The cost is measurable in hours on both sides, and a slow answer usually loses the booking to a hotel that replied faster. If you want to see how these rules combine in practice, our article on hotel net rates for travel agents walks through them one by one.

There is a trust cost too. An unexplained number invites the agency to assume the hotel padded it, and that assumption is hard to reverse. There is an internal cost. When the person who built the spreadsheet leaves, the pricing logic leaves with them, and the next quote is a guess.

The problem is not the number of rules. It is that the rules are invisible at the moment someone needs to see them.

What does a quote that shows its working contain?#

Three things: the hotel's net, each pricing rule that fired with its effect, and the final price the agency is being offered.

The first line fixes the stay: dates, room type, occupancy and meal basis. Without it the rest of the calculation has no anchor. The second block lists the rules that fired, each named, each with the amount it added or removed. Rules that did not apply are not listed, so the quote stays readable. The third line is the final price. It is the only number most people read, and it is now the last line of an argument rather than the whole argument.

For example, a three-night stay at a stated net, a weekend supplement on the second night, and a length-of-stay rule that removes part of the third night, ending in one final figure. The numbers are illustrative and belong to no real hotel.

The agency gains something concrete: it can see whether its own margin still works before it quotes its client, and it can explain the price onward without calling the hotel. The hotel gains the same record in reverse. The question why was it cheaper last week is answered by opening the earlier quote, not by rebuilding it.

A quote is a dated record, not a conversation. If a term changes, a new quote is issued, and the old one stays where it is. For the vocabulary around these records, see our guide to hotel distribution terms.

How does one engine serve hotels that confirm instantly and hotels that confirm by hand?#

The same engine answers both: it confirms the booking immediately for a connected hotel, and routes the request to a hotel that confirms by hand, then carries the answer back.

Some hotels keep live availability and want the booking closed on the spot. Others want a person to look at every request, especially for groups, unusual dates or a client they have not worked with. Both are commercial choices, not maturity levels. A hotel that confirms by hand is protecting rate integrity, not falling behind.

The engine's job is to know which mode applies and never let the agency guess. A request that disappears into an inbox with no status is worse than a slow answer. While a request sits with the hotel, the room must not be sold twice elsewhere. The mechanism is a hold with an expiry, so the inventory returns if nobody answers.

The agency needs two things from the screen: the status of its request and the point at which the hold ends. Anything less and it will book elsewhere as a precaution. The trade-off is real. Instant confirmation wins short-notice business. Manual confirmation lets the hotel say yes with conditions, and protects a rate it did not mean to open on those dates.

The design principle is that the mode belongs to the hotel, not to the platform. The platform's only duty is to make the mode visible. Holds and release periods are related ideas; our article on hotel allotment contracts covers the clauses to check.

What does the hotel control, and what does the agency see?#

The hotel sets the terms, the rates and which agencies see which of them. The agency sees what has been opened to it, and nothing that belongs to another agency.

Terms: cancellation windows, release periods, minimum stay, blackout dates, meal basis and child policy. These are contract decisions, and the platform should carry them, not invent them. Rates: contracted rates per agency, per season and per room type. A rate built for one agency is not a public rate and should not behave like one.

Visibility: which agency sees which rate, and which rules apply to it. This is the part most often left to email, and the part most often misunderstood later. The agency's side stays clean: its own rates, its own quotes, its own bookings. It does not need to see another agency's contract to do its job.

The hotel remains responsible for what it publishes. A hub that quietly adjusted a hotel's price would be a pricing engine, and this one is not. Contract hygiene pays here: a release period that is written down and carried into the system is a release period that can be enforced without an argument.

What is the exact status of AI Otel's distribution hub?#

Built, with seed data; no agency is connected yet.

Built means working software ahead of launch, not in customers' hands. It is one of five status words we use, and it sits below Live. Seed data means example data loaded so the software can be exercised end to end. It is not a customer, a pilot or a signed agency.

No agency is connected, so there are no agency names, no booking counts and no claim that agencies use it. What does exist: the quote with its working, the two confirmation modes in one engine, and the hotel's control over terms, rates and visibility. What does not exist: connected agencies, live bookings, and any commercial figure attached to the hub. We publish none of those.

OtelCiro, the ecosystem's hotel growth and consultancy arm, works with paying hotel clients today. The distribution hub itself is not in their hands. The honest sentence is short, and it is the one to use: built, with seed data; no agency is connected yet.

What should you ask any B2B distribution platform before you sign?#

Ask for the calculation, the confirmation mode and the exit. Those three answers separate a working hub from a rate dump.

Ask for one real quote, printed with every rule that fired and the amount each one moved. If the platform can only show the final number, it cannot explain a price later either. Ask which of your agencies will see which rate, and whether you can change that yourself without opening a support ticket.

Ask whether the platform confirms instantly or routes the request to your team, and whether you can choose per agency rather than for the whole hotel. Ask what happens to a request while your team is deciding: is the room held, until when, and what does the agency see on its screen.

Ask who owns the rate and booking data, and what you get back if you leave. An export you cannot read is not an exit. Ask for the status in plain words: built, live or planned, and which agencies are connected today. A vague answer here tells you how the rest of the answers were built.

What to do next#

The three ideas fit together: a quote that prints its working can be defended by both sides, a confirmation mode that belongs to the hotel keeps the commercial choice where it belongs, and a status word that says built rather than live keeps the conversation honest. The next step is to bring one of your own quotes, the one that caused the last argument, and ask a platform to reproduce it line by line. If you want to see how we designed ours, request a briefing at https://ai-otel.com/contact.