Skip to content
Blog

How to share supplier content with partner agencies safely

Tekravel Editorial
Written with the help of AI

A partner agency messages you on a Thursday: they have a client wanting four rooms in Dubai and your contracted hotel rates are better than anything they can see. The fastest answer is sitting right there. You forward the login for the supplier portal, or paste the API key into a chat, and tell them to go ahead. It works. That is exactly why so many consolidators end up with it as their process, and why the process one day produces a very bad week.

If you want to share supplier content with partner agencies without that week, the thing to change is the model, not the discipline. Here is what is wrong with the shortcut, what a better arrangement looks like, and what it should never let leave your hands.

Why handing over credentials fails

A supplier login is not a permission slip for one partner. It is your identity with that supplier, and everything done under it is done as you.

Think through what that means in practice. The partner can search and book at your contracted rates, but so can anyone they pass the details to, and you will not know. Your supplier sees one account making bookings; when something is wrong with one of them, the conversation is with you. There is no way to give one partner hotels only and another flights only, because the login does not know about partners. And the day you stop working with an agency, the only revocation available is changing the password, which locks out every other partner who was quietly relying on the same one.

The shortcut also teaches the wrong habit. Credentials end up in chat history, in a spreadsheet, in the memory of someone who has since left. None of that is a breach until the day it is, and by then nobody remembers who ever had access.

What sharing through a group does instead

The alternative is that the partner never touches the supplier at all. Content is shared through supplier groups: you place the suppliers you want to offer into a group, you add the partners who should see them as members of that group, and each partner sees only what its groups grant. The credentials stay where you configured them. A partner searching your content is searching through the platform, on your contract, without ever being shown how to reach the supplier directly.

Groups are the only sharing path on the platform, and that is deliberate. It means the question "who can see what" has one answer you can read off a screen, instead of being scattered across the logins you have handed out over the years.

What a group grants, and what it does not

A group grants visibility of the suppliers it contains. It does not grant ownership of your contract, access to the supplier's own back office, or sight of the credentials behind the connection. A partner in the group can sell what the group shows; that is the whole of it. You can build several groups: one for the sub-agents you trust with net rates, another for a looser network that sees a narrower set. Same suppliers, different audiences, and each audience gets exactly the slice of your contracts you decided it should have, no more.

Revoking access without a fire drill

This is the part that decides whether the model is any good, because relationships end. A partner is late on settlement, or gets acquired, or simply stops selling.

With credentials, revocation is a password change and an apology to everyone else. With a group, it is removing that partner from the group, or removing the supplier from it, and nobody else notices. The other partners keep working. The supplier relationship never moved. You are changing who the platform shows content to, not rebuilding a connection.

It is worth doing this on a calendar, not only in anger. A quarterly look at who is in which group is cheap, and nearly every network turns up a partner that has not sold anything for a year and still sees your net rates.

 Passing the loginSharing through a group
What the partner holdsYour supplier credentialsNothing of yours
Split by partnerNo: one login, one identityYes: per group, per supplier
Stopping one partnerChange the password, lock out everyoneRemove them from the group
Who the supplier seesYou, for everythingYou, as the contract holder
Audit trailWhatever the supplier logsYour own platform's bookings and users

Customer contact data stays with whoever owns the customer

The other half of trust in a content network runs in the reverse direction. A partner worries you will poach the client; you worry the same about them. Sharing supplier content does not require either side to hand over the traveller.

The partner's customers book through the partner's own storefront, and their names, phone numbers and emails sit in the partner's own admin. Your side of the arrangement is the supplier content and the settlement, not the client list. Agree that in writing anyway, but know that the structure supports it rather than fighting it. Everything about credit limits and settling the money between you is a separate conversation, and a better one when neither of you is anxious about the customer.

What it costs you if you get it wrong

Be concrete about the downside, because it is why this is worth an afternoon of setup. Credential sharing fails in three ways. A supplier notices an odd pattern of bookings under your account and suspends it, taking every partner down at once. A partner's departing employee walks out with working access to your net rates. Or you cannot prove, when a dispute arrives, which partner made which booking, because they all made it as you. Each of those lands on the consolidator, never on the partner. The group model does not make disputes impossible; it makes them traceable, and it makes the cure small.

A short checklist before you open the network

  1. List the suppliers you are willing to share at all. Some contracts forbid onward distribution; read yours first.
  2. Decide your groups by audience, not by supplier: trusted sub-agents, a wider network, a pilot.
  3. Put partners in the smallest group that lets them sell.
  4. Agree in writing that you do not contact each other's customers.
  5. Set the review date for membership before the first partner joins.

If you are still working out how a consolidator account fits together, the guide on distributing net fares to sub-agents covers the pricing side, and the piece on hotel contracts and bedbank rates covers what you can legitimately pass on. The consolidator account itself is opened from the consolidator page.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.