Running ticketing on your own brand: who handles what.
White-label means you own the relationship with your buyers. It should not mean you inherit every operational problem alongside it. Here is the actual split — including the parts we do not do.
The honest summary: on a white-label platform you own the brand, the buyer relationship and the customer support inbox — but not the infrastructure. With BoxOfficeTech you choose whether you or the platform is the merchant of record, so chargeback exposure is a decision rather than an automatic consequence. Certificates, email deliverability and platform updates are ours. Check-in keeps working with no internet at all; selling deliberately does not, because prices and inventory are confirmed on the server. Concession volume is paced by limits your vendors set. Seat maps can be imported from a photograph, and your event pages are published with the structured data that makes them findable in search and readable by AI assistants. What genuinely stays yours is marketing to your own list and answering your own buyers.
How deep does the white-labeling go?
The useful way to compare vendors is by depth, not by whether the word appears on the pricing page. Here is where we sit on each level \u2014 including the one we do not reach.
| Depth level | What BoxOfficeTech does |
|---|---|
| 1 · Logo, colors and theme | Yes, and deeper than a recolor. Your portal renders its own theme — logo, palette, type and layout — alongside content pages you write and edit yourself. Attendees are not looking at a BoxOfficeTech page with your logo dropped in the corner. |
| 2 · Your own domain | Yes. Sell on tickets.yourbrand.com with one DNS record and certificates issued and renewed automatically, or on yourbrand.boxofficetech.com from day one. Every buyer-facing page serves on that host — event pages, the seat map, checkout, confirmation, the attendee account, memberships and concession ordering. |
| 3 · Email, tickets and receipts | Buyer email always carries your organization as the sender name, your logo and color in the body, and your address for replies — there is no BoxOfficeTech wording in a confirmation, receipt, ticket or password reset, and phone wallet passes are issued under your name. The from address can sit on your own domain too, once that domain is verified with our email provider: a step we do with you, and not a prerequisite for going live. The "Powered by BoxOfficeTech" link in the portal footer is on by default and comes off on request. |
| 4 · On-site box office and hardware | The software, yes: the box office sells your inventory in any browser, and the gate scanner carries your logo and name in its header and shows only your events. Two limits worth knowing before you compare us — the staff console and the scanner app itself are BoxOfficeTech-branded, and we ship no hardware at all. There are no card terminals and no printed ticket stock; tickets are emailed and added to a phone wallet. |
On hardware, so there is nothing to discover later. We do not sell, rent or integrate card terminals, thermal ticket printers or dedicated scanning guns, and nothing in the platform talks to one today. If your venue needs printed stock or a chip-and-PIN reader at the counter, say so on the call: we will help you scope it and find a supplier, and it would be work we take on with you rather than a feature you switch on. Worth applying the same scrutiny to anyone else’s claim at this level \u2014 ask which specific device, and ask to watch it print.
The level that trips most comparisons is the third one, because a platform can put your logo on an email while still sending it from its own address with its own name in the inbox. Ours sends under your organization’s name with replies going to you from the first confirmation, and moving the from address onto your domain is a verification step rather than a project. The box office and gate scanner are where level four is decided \u2014 see exactly what they look like in your hands before you take anyone’s word for it.
The responsibility split, line by line
What you are taking on, and what you are handing over.
| Operational area | Who handles it |
|---|---|
| Card disputes and chargebacks | Whichever merchant account you sell through — and you choose. Your own Stripe, PayPal or Square account makes you the merchant of record, with the direct payout and the disputes. Our platform account makes us the merchant of record, and disputes come to us. |
| Card fraud checks | The platform. Every card charge asks the buyer’s bank to verify the cardholder through 3-D Secure, and the processor’s own CVC, address and risk results are recorded on the order for your staff to read. |
| Refunds | Your staff, from the admin — a whole order or a single ticket, through your gateway, with the seats returned to inventory. No support ticket and no processor dashboard. |
| Attendee support email | You. The confirmation carries your brand, so the reply reaches you. Buyers can re-download tickets from their own account without asking anyone. |
| Platform uptime, security and updates | Us. Nothing to install, no server to patch, no version to upgrade — new capability appears in your admin. |
| SSL certificates | Us, automatically, including on your own custom domain. Nothing to buy, renew or diarize. |
| DNS for a custom domain | You point one record at us. Or skip DNS entirely and use a free subdomain of ours — your branding either way. |
| Email deliverability (SPF/DKIM) | Us by default. Confirmations go out from our verified sending domain under your organization’s name, with replies routed to your address — so there is no DNS record for you to add and nothing that silently starts failing. |
| Check-in hardware | Nobody buys any. Staff scan on the Android phones they already carry, and the app validates offline when the venue has no signal. |
| Concession throughput during a rush | The platform paces it. Set a maximum number of open orders and ordering pauses itself until your vendors catch up; pre-order slots carry their own per-slot caps. |
| Building the seat map | You, in the designer — or import one from a photograph of an existing chart. No professional-services fee and no waiting on us either way. |
| Being found by search and AI | The platform. Every event page publishes complete Event structured data and sits in an hourly sitemap, so your events are eligible for search event results and legible to AI assistants without you configuring anything. |
| Reaching people who have never heard of you | Shared, and it compounds rather than switching on. Your own pages earn search and AI visibility over months; a marketplace listing you keep reaches strangers today. Both can sell the same inventory. |
| Selling through a marketplace or agent | Still theirs to sell, and you decide who. A marketplace, ticket agent or partner you grant access to can sell your assigned events through the reseller API from your live availability, with each sale recorded here so counts stay correct and your gate scanner reads their tickets. |
Money, disputes and fraud
The objection most often raised about direct-merchant white-label — and the part of it that is a genuine choice.
You pick who is the merchant of record
Connect your own gateway and revenue lands in your account on its normal payout schedule, with the disputes that come with being the merchant. Prefer not to carry that? Sell through our platform account instead — same checkout, same reporting, and the dispute correspondence is ours.
Every card charge asks the bank to verify the cardholder
Card payments request 3-D Secure rather than hoping the issuer declines a bad one. When the bank approves an authenticated payment, liability for a fraudulent-use chargeback moves to the card issuer — the single biggest lever on dispute exposure, and it is on by default rather than an upgrade.
Refunds without leaving the admin
Refund a whole order or one ticket out of a party of six. The refund goes through your own gateway, the seats return to inventory immediately, and who did it and why is recorded on the order.
What happens when the network does not cooperate
Venue wifi is the assumption every event platform quietly makes. Here is exactly which parts of ours depend on it.
The gate works with no signal at all
The scanner holds the full ticket list on the phone, so it validates, admits and rejects duplicates with the network completely down, queuing scans and syncing when signal returns. Staff see whether a verdict came from the phone or the server.
Selling needs a connection — deliberately
Online checkout and the box office both confirm price, inventory and payment on the server rather than trusting the device. That is why the same seat cannot be sold twice, and it is also why a dead network stops new sales. It never stops the door.
The kitchen sets its own limit
A vendor can cap open orders and ordering pauses itself; mark an item sold out from the order queue in one tap; give each item its own prep time; take pre-orders against per-slot capacity so a rush is spread rather than absorbed.
The setup work people assume is heavy
Seat mapping, domains and deliverability are where white-label projects usually stall.
Seat maps from a photograph
Upload a picture of an existing chart and the seats are detected from the image itself, with printed section names, the stage and the price-tier legend read off the same picture and rows turned to face the stage. What is left to tidy is listed as a checklist rather than left for you to find.
Double-booking is prevented, not monitored
A seat is locked in a database transaction the moment a buyer selects it, and inventory is re-verified against sales and holds immediately before the card is charged. Publishing a chart runs a validation pass first, and a republish that would remove a seat somebody has already bought is refused.
Going live on your own domain
One DNS record, certificates handled automatically, and transactional email that works on day one because it sends from our verified domain under your name. There is no deliverability project between you and your first confirmation email.
What we do not do
There is no card terminal. Counter card payments run through the same checkout as online, which means no reader to buy or pair — and also that they are processed at card-not-present rates with no chip-and-PIN device. If your volume makes that difference material, price it before you commit.
The box office needs a connection. Check-in is built to survive a dead network; selling is not, because price, inventory and payment are confirmed on the server rather than trusted from a device. That is a deliberate trade for never selling the same seat twice, but it is a real one: if the venue drops, walk-up sales stop until it returns. The same applies to handing over a concession order, which is verified online on purpose — food given away twice cannot be un-given.
There is no email marketing tool yet. You can email your members, capture newsletter signups from your portal, and export your buyer list. What is not in the platform is a general campaign builder for blasting your whole past-buyer list — today you export and send from the tool you already use. It is on the roadmap; it is not here.
We do not have a standing crowd to rent you on day one. Your events are built to be found on their own — every event page publishes full Event structured data (dates, the venue with its coordinates, you as organizer, the ticket offer), every public tenant is in an hourly sitemap, and you are listed on our own public event index. That is real discovery, and it accrues to your brand rather than to somebody else’s listing. But it compounds — search and AI visibility build over months, where a marketplace can put you in front of a stranger tomorrow. Which is why we do not ask you to give one up: keep the listings that are still introducing you, and where that marketplace or agent connects to our reseller API, it sells from the same live inventory as your own site.
Two offline gates can each admit the same ticket once. Where there is signal, the server settles it and the second scan is refused. Fully offline, no system can prevent it without a network — so we detect it on sync and surface it for review rather than pretending it did not happen.
Operational questions
Through the branding, the domain and the buyer’s email, but not into hardware. Your portal runs its own theme on your own domain, and every confirmation, receipt, ticket and password reset goes out under your organization’s name with your logo and your reply-to address and no BoxOfficeTech wording in it — the from address can sit on your domain too, once that domain is verified with our email provider. Phone wallet passes are issued under your name. The footer attribution link comes off on request. Where it stops: the staff console and the scanner app carry our name, and we ship no card terminals and no printed ticket stock — tickets are emailed and added to a phone wallet. We will help you source hardware if your venue needs it, but it is not something the platform does today.
Bring us the objection we have not answered
If there is an operational risk on this list that matters to your venue, say so on the call and we will show you the actual screen rather than a slide — including the parts we told you we do not do.