Supplier profile
Wego is a travel metasearch engine with a strong audience in the Middle East and South Asia. It does not sell you inventory. It sends travellers who compare prices. This page explains how Wego works, the two ways a PHPTRAVELS site can connect to it, and what we build for you on request.
Two directions
A metasearch engine sits between travellers and sellers. Before any build, decide which side of it you want to be on.
You add Wego search tools to your website as an affiliate. Visitors search, compare on Wego and book with its partners. You earn a share of the revenue when they do.
Your visitor → Wego results → partner booking
Content sites, bloggers and agencies without their own inventory
You become a booking partner. Wego shows your prices in its results, and a click sends the traveller straight to your checkout to pay you.
Wego traveller → your price → your checkout
OTAs and agencies that already sell flights or hotels from their own suppliers
Both directions need an agreement with Wego first. Commercial terms, tools and technical formats are set by Wego and change over time, so confirm them with Wego before you plan a build.
What the traveller sees
On a metasearch results page the cheapest clear price wins the click. Your fare has to be accurate, complete and still bookable when the traveller lands.
The price on Wego and the price on your checkout must match, taxes and fees included.
A fare that sold out an hour ago costs you the click and the traveller's trust.
The click opens the selected fare, not your home page, so the traveller continues where they left off.
Sample data. Prices and sellers are illustrative.
Fact sheet
The basics we checked before writing this page. Ask Wego for current figures and terms.
What we build
When your Wego agreement is in place, PHPTRAVELS builds the parts your direction needs on top of the flights and hotels modules you already run.
Wego affiliate search forms and links placed in your theme, with your affiliate ID set from the admin.
AYour fares or rates exported in the format Wego asks for, with your markup and currency rules applied first.
BA link that opens the exact fare or room the traveller chose on Wego, rechecks it and goes straight to passenger details.
BThe source of each Wego visit saved on the booking, so reports show what Wego traffic earns and costs.
A + BLogs and alerts for feed errors and price mismatches, so a broken feed is caught before Wego flags it.
Bhttps://your-agency.example/flights/book?
Example format only. Wego and your build define the real parameters.
How custom integrations are scoped and priced:Custom API integrationFlightsStays
Before you start
Bring the answers to the first call and the estimate gets much sharper.
FAQ
What agencies ask before they connect to a metasearch engine.
Talk to salesNo. Wego is not one of the built-in suppliers. We build the connection as a custom integration once you have an agreement with Wego, and it then runs inside your own PHPTRAVELS installation.
No. Wego is a metasearch engine, not a wholesaler. For inventory you connect suppliers such as GDS systems, consolidators and bed banks, and then you can show those prices on Wego.
If you have no inventory of your own, affiliate tools are the only option. If you already sell flights or hotels, listing your prices on Wego brings travellers to your own checkout, which is usually worth more.
Wego does. It decides which partners, markets and products appear in its results and on what commercial terms. PHPTRAVELS builds the technical side once you are accepted.
The landing page rechecks the fare with your supplier before payment. If the price moved, the traveller sees the new price before paying, and the mismatch is logged so you can fix the feed.
Mostly yes. Deep link landing, tracking and price checks are the same idea everywhere. Each engine has its own feed format and rules, so each one is scoped on its own.
Keep exploring
Cookies for ad measurement
We use Google cookies to measure which ads bring visitors and enquiries, and to show you relevant ads. Accept to allow them, or reject to keep only the cookies the site needs to work. Privacy statement
