---
title: "White label booking: your name on the ticket, one platform behind it · Supaferry"
description: "What white label means for a ferry booking system, which surfaces must carry the operator's identity, what the platform keeps visible, and how to set it up in an afternoon."
url: https://supaferry.com/resources/journal/white-label-booking-for-ferry-operators
language: en
published: 2026-07-07
---
[Journal](https://supaferry.com/resources/journal)

# White label booking: your name on the ticket, one platform behind it

2026-07-07 · 22 min read

What white label means for a ferry booking system, which surfaces must carry the operator's identity, what the platform keeps visible, and how to set it up in an afternoon.

![Three stacked booking-site frames, the front one with a blue header and an orange button, beside a column of five colour swatches](https://supaferry.com/blog/white-label-booking.webp)

*The same booking engine under three identities. The operator supplies a colour, a logo and a name; the platform computes the rest, down to whether the button text is white or ink.*

## Key takeaways

- White label means the passenger deals with the operator on every surface: site, ticket, email, SMS and receipt, with the platform named only in the small print.
- Branding should be stored as data (colour, logo, sender name, reply-to, footer, domain) and applied by the system, including the choice of white or dark text on the operator's colour.
- The legal identity of the processor, the merchant of record on the card statement and the privacy notice can never be hidden; everything else can carry the operator's name.
- A sender domain needs SPF, DKIM and DMARC before the first confirmation email; without them the ticket lands in spam and the passenger phones the office.
- White label, reseller and aggregator are three different contracts; the difference that matters is who holds the passenger's data and who takes the dispute.
- The whole setup fits in an afternoon if the operator arrives with a logo file, a hex colour, a reply-to address and access to its DNS.

A passenger on an island does not buy a ticket from a software company. She buys it from the line that has run the Tuesday boat for thirty years, or from the state shipping office whose name is painted on the hull. When the booking site, the ticket and the confirmation message carry a different company's name, two things go wrong at once: the passenger hesitates, and the operator gives away a relationship it spent decades building. **White label** is the arrangement that prevents both. The operator's identity is on everything the passenger sees; the platform's identity stays where the law requires it and nowhere else.

This article explains what white label means in a booking and ticketing system, which surfaces should carry the operator's identity, what the platform must keep visible, and the technical and contractual questions an operator or agency should settle before signing. It ends with a checklist that fits in an afternoon and a worked example for a state shipping agency with four counters.

## What white label means on a booking site

The term comes from retail. A manufacturer makes the product, a retailer puts its own label on it, and the customer never learns who ran the factory. In software it means one platform, built, hosted and maintained by the vendor, presented to the public under the customer's brand. The passenger sees the operator's name, colours and domain. The vendor's name appears in the privacy notice, in the footer line about who processes the data, and on the card statement if the vendor collects the money. Nowhere else.

White label is not **custom development**. The operator does not get its own copy of the code, and should not want one: a fork has to be patched, hosted and upgraded on its own, and the price of that is a second product. What the operator gets is a configuration layer thick enough that nobody buying a ticket needs to know the vendor exists. It is also not a **theme**. A theme changes colours on the website and stops there. The ticket still says the vendor, the email still comes from the vendor's address, and the SMS still arrives from a shortcode the passenger has never seen.

Three tests separate a real white label from a themed product:

- The address bar. The booking site answers on the operator's own domain, with a certificate for that domain, not on a subdomain of the vendor.
- The sender. Confirmation emails show the operator's name, replies reach the operator, and the SMS sender is the operator's name or number.
- The documents. The PDF ticket, the receipt, the manifest sent to the authority and the cash report all carry the operator's name, logo and footer text.

> White label is a promise about who the passenger is dealing with, not a coat of paint on the vendor's website.

## Why an operator wants its own name

The reasons differ by who the operator is, and each one is worth more than the cost of the setup.

On an island with eight thousand people the brand is a person. The passenger knows the office, knows the clerk, and phones the landline when the boat is late. A ticket with an unfamiliar name on it gets questioned at the wharf, and a confirmation from an unfamiliar sender gets deleted as phishing. The Aeolian Islands, the Canaries and the Western Isles all have lines whose names are older than the ships; nobody there would accept a booking page that looked like it belonged to someone else.

A government shipping office has a second reason. A public service sold under a private vendor's name looks like a privatisation that nobody announced, and in several jurisdictions it breaches the procurement rules that require public services to be identified as such. The ticket is a receipt for public money. The revenue report goes to the finance ministry and the donor under the department's letterhead, and the audit trail refers to the department, not to a software company in another time zone.

An agency has a third reason, and it is contractual. A shipping agency that sells for two or three ship owners needs its own name at the counter and the owner's name on the ticket, because the passenger's contract of carriage is with the owner and the receipt for the money is from the agency. The agency agreement says exactly this: the agent acts in the principal's name. A booking system that cannot print both names on the right documents makes the agency break its own contract.

## Branding is data, not a build

The practical consequence of all this is that every piece of identity must be a value stored in the operator's settings, read by the system wherever that identity appears, and changeable without a deployment. The list is short. A **primary colour** as a hex value. A **logo** as an uploaded file. A **sender name** for email and a **reply-to address** that reaches a person. A **footer note** printed on tickets and emails: office hours, where to pay, what to bring. A **domain** for the booking site and, optionally, a **sending domain** for email. Two switches, one for email and one for SMS, so an operator can turn a channel off while it sorts out its DNS or its SMS contract.

In Supaferry the whole set is one record on the operator settings. The public booking site reads the colour into its CSS token on every page load, so the buttons, links and header change the moment an administrator saves. The PDF ticket draws the logo in the header of each passenger's page and prints the footer note under the QR code. Every passenger email uses the sender name and reply-to, and attaches the ticket on confirmation. Settings saved before a field existed come back with defaults, so adding a new branding field never breaks an old operator. Mail clients block images embedded as data, so the emails reference the logo through a public URL served by the platform rather than embedding it.

Equally important is what is not data. Fonts stay fixed: custom typefaces need licences, break PDF generation and make the accessibility work start over. Layout stays fixed: the order of the booking steps, the position of the fare table and the size of the QR code are the product, and an operator that could move them would also be able to hide the price until the last step. The operator chooses the colour; the platform decides what the colour is applied to.

### Contrast when the colour is dark or light

Here is the detail that separates branding done properly from branding done once. An operator picks a navy from its flag, a pale yellow from its logo or an orange from a safety vest. Buttons and headers take that colour. What colour is the text on them? If the designer chose white when the demo was blue, the orange operator's buttons become unreadable, and the complaint arrives from the one passenger with low vision who could not find the Pay button.

The answer is to compute it. Convert the colour's red, green and blue channels to linear light, weight them (0.2126, 0.7152, 0.0722) and sum them: that is the colour's **relative luminance** as defined by WCAG, a number between 0 for black and 1 for white. Compare it with a threshold and pick white text below it, dark text above it. The threshold has to be tested against real brand colours, because a mid-tone can pass the 4.5 to 1 contrast ratio with white and fail it with dark text, or the reverse. Apply the same rule in the email templates and in the PDF, where there is no stylesheet to fall back on.

> **Note:** Worked example. A ferry blue, #2F7394, has a relative luminance of about 0.15. White text on it gives a contrast ratio of 5.2 to 1, dark ink text 3.4 to 1: white wins and passes the 4.5 to 1 minimum. A signal orange, #FF5A1F, has a luminance of about 0.29. White on it gives 3.1 to 1 and fails; dark ink gives 5.7 to 1 and passes. A threshold of 0.2 separates the two correctly, and a pale yellow at 0.55 falls on the ink side with room to spare.

In dark mode the rule is the same with a different surface. The operator's colour does not change, because a brand does not have a night version; the page behind it does, and the text on the colour is still computed from the colour alone.

> If the colour is data, the contrast has to be computed, not chosen.

### The languages the passenger reads

An island service often works in two or three languages, and the brand is the same in all of them. The interface strings, the names of the booking steps and the error messages are translated by the platform. The operator's own copy, the footer note, the names of the extras it sells and the questions it asks at booking, is entered once per language in the settings, with a fallback to the operator's default language when a translation is missing, so that a half-translated settings page never shows an empty label.

The ticket is the document that most needs to be bilingual, because the boarding officer, the master and the passenger may not share a language. Print the field labels in the local language and in English, and keep the operator's name untranslated: it is a proper noun. The email goes out in the language the passenger booked in. The SMS goes out in one language, the local one, with the English fallback only where the passenger chose English at booking, because two languages in one message means two segments.

## What must stay visible

A white label is not a disguise, and three things cannot be removed however large the licence fee.

The first is the **legal identity of the processor**. Under the GDPR the operator is the controller of the passenger data and the platform is a processor acting on its instructions under a written contract, the data processing agreement of article 28. The operator's privacy notice must tell the passenger that a processor exists and where the data is hosted. A platform established in Spain also has to identify itself on its own site under article 10 of the LSSI-CE, and it does that on its own domain, not on the operator's. Outside Europe the words differ and the principle holds: the passenger must be able to find out who holds the record.

The second is the **merchant of record**. If the platform or its payment provider collects the fare, the name that appears on the passenger's card statement is theirs, not the operator's. A passenger who does not recognise the descriptor disputes the charge, and a chargeback costs the operator the fare and a fee. The fix is either to put the operator's own merchant account behind the payment page, so the descriptor is the operator's, or to tell the passenger before paying what name to expect. On lines where most tickets are paid at the counter the question is simpler: the receipt comes from the finance office and names it.

The third is the **"powered by" line**. Operators ask to remove it. The honest answer is that it belongs in the small print and should stay there: it tells the auditor, the regulator and the next IT officer who runs the servers, which matters more on the day something goes wrong than on the day of the launch. Some vendors sell its removal; the operator should ask what else changes in the contract when the vendor's name disappears, because an invisible vendor is also an unaccountable one.

On the ticket itself the hierarchy is simple: operator name and logo large at the top, voyage and passenger in the middle, the QR code and the footer note below, the processor line at the very bottom in the smallest legible size.

## One platform, several operators, one agency per state

Most ferry booking platforms serve many operators from one deployment. Each operator is a tenant with its own settings record, its own tariff, its own voyages and its own passengers, and every query the system runs carries the tenant's identifier so that one operator's clerk can never list another's bookings. The branding record lives at that level. This is the right place for it, and it has a consequence that surprises people: the agency does not get its own branding.

Consider a national line that sells through one agency in each of four states, which is how several Pacific and Caribbean services are organised. The agency in each state has its own accounts, sees its own counter sales, its own holds and its own daily cash, and reconciles against its own finance office receipts. The ticket a passenger carries from one state to another must look the same everywhere, because the master checks it and the boarding officer in the next state scans it. So the ticket carries the operator's name and colour, and the agency appears as the point of sale on the receipt and in the audit log: issued by the Northern State agency, receipt number such and such, clerk such and such.

The reverse case exists too. An independent agency that sells for three owners is itself the tenant, with three operators under it, and switches branding by the vessel on the ticket. The data model has to allow both, and the contract has to say which one applies, because the question of whose name is on the ticket is the question of who the passenger has a contract with.

## Domains, email and deliverability

The address bar comes first. The operator registers the booking domain in its own name, book.islandline.example or tickets.islandline.example, and points it at the platform with a CNAME record. The platform obtains a certificate for that name automatically, through the ACME protocol, and renews it; the operator adds a CAA record naming the certificate authority so no other authority can issue for the domain. The main website stays where it is; only the booking subdomain moves. The vendor must never own the domain, because at the end of the contract the domain is what the operator keeps.

Email is where white labels fail silently. There are two ways to send the confirmation. The first uses the platform's own verified sending domain with the operator's name as the display name and the operator's reply-to address; it works on day one and is what most operators start with. The second sends from the operator's own domain, tickets@islandline.example, which needs three DNS records before the first message.

- **SPF**, a TXT record on the sending domain that lists the platform's mail servers as allowed senders. Keep it under ten DNS lookups or receiving servers ignore it.
- **DKIM**, a public key published as a CNAME or TXT record under a selector, with which the receiving server checks that the message was signed by the platform and not altered. Use a 2048-bit key.
- **DMARC**, a TXT record at _dmarc.islandline.example that says what receivers should do when SPF and DKIM fail. Start with p=none and a reporting address, read the reports for two weeks, then move to p=quarantine.

Since February 2024 Google and Yahoo reject or spam-folder mail from senders that lack SPF and DKIM alignment or exceed a 0.3 percent spam complaint rate, and they require a one-click unsubscribe on promotional mail. Ticket confirmations are transactional and do not need the unsubscribe, but the authentication rules apply to them in full. A new sending domain should also be warmed up: a few dozen messages a day for the first week, not the whole season's reminders in one burst.

Two housekeeping rules protect the sending reputation that the operator now depends on. Hard bounces must be suppressed automatically, so an address that does not exist is never tried twice. And demo data must never reach a mail server: seeded passengers, training bookings and test agents get addresses on reserved domains, example.com and the like, and the sender drops them before they leave. One training session with a hundred invented passengers at invented but real-looking domains is enough to get a sending domain blacklisted.

SMS has its own rules. An alphanumeric sender name, ISLANDLINE, is at most eleven characters and is allowed in many countries but not all; the United States requires a registered number, and several Asian countries require the sender name to be registered with the regulator in advance. A message in the GSM-7 character set carries 160 characters; one accented letter or one emoji outside that set drops the segment to 70 characters and doubles the cost. Keep the operator name in plain ASCII and the message short: the reference, the voyage, the departure time and the office phone number fit in one segment.

## White label, reseller, aggregator: who owns the passenger

Three commercial models put an operator's sailings in front of the public, and they are often confused because all three show a booking form.

In the **white label** model the operator sells under its own name on a platform it licenses. The passenger's contract is with the operator, the data belongs to the operator, the platform is a processor, and the operator can export every booking at any time in an open format. The platform is paid a licence.

In the **reseller** model a third party, a travel agency or a hotel, sells the operator's tickets under the reseller's own name, often on an allotment of seats agreed in advance. The passenger's contract is with the operator for carriage and with the reseller for the sale, the reseller holds the customer's details and passes the operator a manifest, and the reseller keeps a commission. Resellers are useful; they are not white label, and the operator should not expect to see the passenger's email address.

In the **aggregator** model a marketplace lists many operators side by side, takes the booking, takes the payment and takes a commission that in the European ferry market typically runs between 5 and 15 percent of the fare. The aggregator is an independent controller of the data it collected, the passenger relationship is the aggregator's, and the operator receives a booking file and, later, the money. The aggregator's brand grows with every ticket; the operator's does not.

An operator can use all three at once, and many do: the aggregator for international visitors who would not have found the line, resellers for hotels and tour desks, and a white label site for the residents and institutions who are the bulk of the year's traffic. The point is to know which is which, and to keep the direct channel under the operator's own name, because that is the channel whose data the operator will still have in ten years.

> Whoever holds the passenger's email address owns the relationship, whatever logo is on the ticket.

### What white label costs

Pricing follows the model. In a licence, the operator's name on the site, tickets and emails is normally included, because it is configuration rather than work. What is sometimes charged separately is the setup of a custom domain and a sending domain, which takes a technician an hour or two plus a day of waiting for DNS, and it is reasonable to pay for that once. Multi-brand setups, an agency with three owners or a group with two lines, are priced per brand. Removing the processor line is sometimes offered as a paid option, with the caveat above.

In a revenue-share arrangement the operator pays nothing up front and a percentage of each ticket, and the white label is used to make the arrangement look like a licence. Read the exit clause before anything else: who owns the domain, in what format the data is exported, how long after termination the export is available, and whether the sending domain's DNS records are removed. A fair contract says the operator keeps its domain, receives a complete export in CSV or JSON within thirty days, and has the records removed on request. A contract that is silent on these points will be read by the vendor's lawyer, not the operator's.

Other questions belong on the same list: where the data is hosted and whether a different region is available, who the sub-processors are, what the uptime commitment is during the sailing season, and who has the right to use whose trademark, in which direction, for how long after the contract ends.

## Setting it up in an afternoon

An operator that arrives with the inputs can be live under its own name in one working afternoon, with the DNS waits in between. The sequence, in order:

1. Collect the logo as an SVG or a PNG at least 512 pixels wide and under 200 KB, on a transparent or white background. Ten minutes, if someone knows where the file is.
2. Pick the primary colour as a six-digit hex value from the logo or the flag, not from memory. Check it against the contrast rule and look at a button in both text colours.
3. Decide the sender name, short and recognisable, and a reply-to address that a person reads every working day. A mailbox nobody reads is worse than none.
4. Write the footer note: office hours, where to pay a held booking, what identity document to bring. Three lines, in each language.
5. Register or choose the booking subdomain, add the CNAME to the platform and the CAA record. Wait for the certificate, usually under ten minutes once DNS has propagated.
6. If the operator will send from its own domain, add the SPF, DKIM and DMARC records and verify them in the platform. Propagation takes from minutes to a day.
7. Choose the SMS sender name and check the rules for the operator's country. Turn SMS off until the provider confirms the sender is registered.
8. Make a real booking to the operator's own address and phone. Read the email on a phone and on a desktop client, print the PDF, scan the QR code with the boarding app.
9. Check the card statement descriptor, or the counter receipt, and write what the passenger will see into the payment step.
10. Update the privacy notice to name the processor and the hosting region, and link the platform's own legal pages from the footer.
11. Create the agency accounts, one per counter, with the agency name that will appear on receipts.
12. Take screenshots of the site, the ticket, the email and the SMS, and file them with the contract. They are the record of what was agreed.

> **Note:** Rule of thumb. If a setup takes more than an afternoon, the delay is DNS, the logo file or the reply-to decision, never the software. Ask for those three things a week before the appointment.

### Worked example: a state shipping agency

Take a state shipping office in an island federation of four states. It runs two ships on multi-island voyages, carries about nine thousand passengers a year, and sells through one agency in each state. Until now each agency had a ticket book, a carbon receipt and a phone. The office wants to sell online for the residents who have moved to the capital and want to book for relatives, and to keep the counters for everyone else.

The office's colour is the navy of the state flag, #1A3F6F, luminance about 0.05: white text. The logo is the state seal, exported as a PNG by the printer who makes the letterhead. The sender name is Island Line Tickets; the reply-to is the shipping office's existing mailbox, which the dispatcher already reads. The footer says, in the local language and in English: pay at the State Finance Office, Monday to Friday 8 to 4, hold expires 48 hours before departure, bring a photo ID.

The booking subdomain is book.islandline.example, registered under the government's domain by the IT office that already manages it. For the first season the emails go from the platform's verified domain with the office's name as sender, because the government mail server is run by another department and the DNS change would take a month; the sending domain is moved in year two. SMS stays off until the national carrier confirms an alphanumeric sender, which in that country takes a registration form and three weeks.

The four agencies get one account each, named after the state. The ticket shows the office's seal and name; the receipt shows the agency and the finance office receipt number the clerk typed. The dispatcher at the capital sees all four counters and the online sales on one manifest per voyage. The revenue report that goes to the finance ministry carries the office's name and lists each agency's cash separately, which is what the ministry's auditor asked for in the previous year's management letter.

Done on Supaferry, the whole configuration is the settings page, the domain step and four agency accounts; the only waits are the certificate and the SMS registration. Nothing in the example is specific to the Pacific. A cooperative line in the Aeolian Islands, a municipal service on a Norwegian fjord or a provincial agency in the Philippines goes through the same list, with different office hours in the footer and a different flag colour on the button.

The passenger, at the end of it, sees exactly what she expected: the office she knows, on a page with its name, sending a ticket she can show at the wharf. The platform is in the small print, where it belongs.

## Questions people ask

**Does white label mean the operator gets its own copy of the software?**
No. The operator gets a configuration layer on one shared platform: colour, logo, sender name, reply-to, footer, domain and languages. A private copy of the code would need its own hosting, patching and upgrades, which is a second product at a second price. The point of white label is that nobody buying a ticket needs to know the vendor exists.

**Can the "powered by" line and the processor's name be removed entirely?**
The processor's legal identity has to appear in the privacy notice under the GDPR, and the merchant of record appears on the card statement whatever the site says. The footer line is negotiable and some vendors charge for its removal. It is worth keeping in the small print: it tells an auditor or the next IT officer who runs the servers.

**Which text colour goes on the operator's brand colour?**
Compute it rather than choose it. Convert the colour to relative luminance as WCAG defines it and pick white text below a threshold and dark text above it; a ferry blue at 0.15 takes white, a signal orange at 0.29 takes dark ink. Apply the same rule in emails and PDF tickets, which have no stylesheet to fall back on.

**What DNS records does the operator need before sending confirmations from its own domain?**
Three: an SPF record listing the platform's mail servers, a DKIM public key under a selector, and a DMARC policy starting at p=none and moving to p=quarantine after two weeks of reports. Google and Yahoo have enforced authentication and a spam complaint rate under 0.3 percent since February 2024. Until the records are in place, send from the platform's verified domain with the operator's name as display name.

**Does each agency get its own branding?**
Usually not. Branding belongs to the operator whose name is on the contract of carriage, so the ticket looks the same in every state and the boarding officer recognises it. The agency appears as the point of sale on the receipt and in the audit log, with its own accounts, holds and daily cash. An independent agency selling for several owners is the opposite case, with the owner's brand switching by vessel.

**How is white label different from listing on an aggregator?**
On an aggregator the marketplace takes the booking, the payment and a commission of roughly 5 to 15 percent, holds the passenger's data as its own controller and sends the operator a booking file. In a white label the passenger's contract and data are the operator's, the platform is a processor under a data processing agreement, and the operator can export everything at any time. Many operators use both and keep the direct channel under their own name.

**What should the contract say about leaving?**
That the operator owns its domain and keeps it, that a complete export of bookings, passengers and settings is delivered in CSV or JSON within thirty days of termination, that the sending domain's DNS records are removed on request, and that neither party may use the other's trademark after the end date. A contract silent on these points favours the vendor.
