White-Label Booking Sites for Kashmir Agents · ZoonCabs

White-label booking sites for Kashmir travel agents are booking sites on an agency's own domain, under the agency's name, running on a supplier's fleet and dispatch behind them, and this is ZoonCabs's guide to what agents should look for in one and what the ZoonCabs version does.

A white-label booking site sits on a domain the agency owns, carries the agency's brand, and runs on a supplier's vehicles and dispatch behind it. For a Kashmir travel agent it is the difference between emailing quotes and letting clients book. This is what to look for in one, what to be wary of, and how the ZoonCabs storefront compares.

What "white label" has to mean

The supplier's name appears nowhere the customer can see. Not on the site, not on the voucher, not in the confirmation email, not in the payment description. If any of those carry the supplier's brand, the customer has been introduced to the supplier and the agency has paid for the introduction. Ask to see a live storefront and read the footer, the voucher and the email before signing anything.

Eight things to check

1. Your domain, or theirs. A site at agency.supplier.com is a page on the supplier's site with your logo attached. A site at book.youragency.com, with your certificate, is yours. Both exist; only the second builds anything for the agency.
2. Your markup, set by you. The site should sell at the agency's price, which is the supplier's rate plus whatever the agency decides, changed by the agency without asking.
3. Your customer stays yours. The supplier must not market to the customer afterwards. This is a policy question, and the honest answer is the supplier's business model: a supplier with a consumer arm cannot promise it.
4. Payments to you. The customer pays the agency; the agency pays the supplier from a wallet or on terms. A site where the customer pays the supplier directly belongs to the supplier.
5. The voucher. Agency brand, driver's details, itinerary, no price, no supplier name.
6. Search engines. The site's canonical links, sitemap entries and structured data should name the agency's domain, not the supplier's. Otherwise Google indexes the supplier's copy and the agency's site is a duplicate of it.
7. Your own pages. About, contact, terms: the agency's copy, with the agency's phone number and address, editable by the agency.
8. What happens when the supplier's name does appear. Some agencies are happy to say "transport by" a supplier in a footer, because it reassures customers. It should be the agency's choice, per site, off unless the agency says yes.

What the ZoonCabs storefront does

A ZoonCabs partner switches the storefront on from the account. It runs on a subdomain of the platform to start, and on the agency's domain with its own certificate when the agency points a DNS record at it. The agency sets the brand name, logo, accent colour, contact phone and email, and its markup. Customers book and pay the agency; the platform's vehicles and desk run the trip; the voucher carries the agency's brand. The storefront's canonical links, its sitemap, favicon and share card are the agency's. The platform's analytics and Search Console tags do not load on it. A "Transport by ZoonCabs" line in the footer exists as an option the agency can say yes to, and is off until it does. The transport booking page covers the booking flow the storefront runs on.

What a storefront does not replace

An agency's own selling. The storefront takes bookings; it does not find customers. Agencies that do well with one put it behind their own marketing, their own guides and their own relationships, and use it to stop retyping quotes. The B2B cab services page has the whole partner arrangement, including the API for agencies with their own software.

Frequently asked questions from agencies