In the event industry, "white label" almost always means subcontracting with a branding layer on top. One company books and bills the client, another company shows up and does the work, and the client never knows two businesses were involved. Vendors specifically ask for this arrangement (rather than just calling it subcontracting) because they want the experience presented as if the hiring company did everything themselves, including capturing any repeat bookings, referrals, or relationships that come out of the event.
This article covers the two sides of that relationship in Check Cherry: hiring subcontractors to perform work for you, and performing work as a subcontractor for another company.
Hiring subcontractors to perform work for you
When you accept the booking and then bring in another provider to perform some or all of the work, the cleanest setup in Check Cherry is to add that provider as a staff account with limited permissions. They get access to the events they're assigned to without seeing the rest of your business.
- View events they are assigned to from the web or the app
- Sync their calendar to stay up to date
- Receive automated email reminders so they don't miss an event
Hide pricing from the subcontractor. You can hide pricing from an assigned staff member or subcontractor through their role permissions. This matters: if a subcontractor can see what the client paid you, they can back into your margin and may either ask for a bigger cut next time or take the relationship direct. Keep the client-facing number private. See staff roles and permissions for how to configure this.
Performing a white-label event for another company
The flip side: another company books the client, and you're the one showing up to perform. The hiring company handles all client communication, collects payment, and manages expectations. You may never speak with the event host, and the event host may not know your business exists.
In this setup, the only party you have a business relationship with is the company that hired you. That is who should sign your contract and pay you. A contract should only be signed by the person who is paying, so do not send a contract to the event host. They are not your client, they are not paying you, and asking them to sign creates confusion about who is responsible for what.
The recommended workflow:
If the hiring company wants the event host to fill out a questionnaire, pick a design, or otherwise interact with planning tools, you can add the event host as a client on the booking with pricing hidden. That is their call to make, though, not yours.
When the event host is open to seeing your brand for planning
Not every subcontracting arrangement is fully invisible. Often the event host knows there is a separate vendor doing the work, they just do not particularly care which company it is. What matters to the hiring company is that the event itself is presented as theirs: apparel, signage, and anything guests see on the day belong to their brand. The planning conversation in the background is more flexible.
When this is the arrangement, Check Cherry's client portal can work well for planning communication, with a few configuration choices:
- Add the event host as the client. The host is who you will exchange details, timelines, and questionnaires with, so they need access to the portal. You may also want to add the hiring company to the booking. As an additional client, they see the same portal as the host. As a staff member with a limited role, they get admin-side visibility into only the events they are assigned to.
- Hide pricing from the client portal. The host is not paying you directly; they are paying the hiring company. If they can see what you charge, it creates confusion and can undercut the hiring company's margin. Same reasoning as hiding pricing from a subcontractor in the section above, just inverted. See staff roles and permissions for how to control pricing visibility.
- Coordinate automated messages with the hiring company. The hiring company is usually already sending their own confirmations, reminders, and follow-ups under their branding. If Check Cherry's automation goes out on top of that, the host gets duplicate touchpoints with mixed branding. Sometimes the hiring company is happy to step back and let all planning communication run through your Check Cherry portal, which is fine. The point is to make a deliberate call together so the host gets one coherent experience, not two competing ones.
- Keep the contract and invoice between you and the hiring company on the side. That is a B2B agreement and does not belong in front of the host. You can either skip the contract inside Check Cherry or use a non-client-facing internal record.
When the host shouldn't see your brand at all
Sometimes the hiring company has positioned themselves as doing the work entirely in-house, and the host should see no sign of you anywhere. In that case, Check Cherry's client portal is not a fit. The portal serves the customer of whichever business owns the booking, and it cannot present itself as a different company's portal in front of someone else's client.
In this arrangement, the hiring company handles all client-facing planning on their own systems. On your side, you still manage the booking inside Check Cherry, tracking the event, scheduling staff, recording expenses, but you do not engage the host through the portal at all. Details flow to you from the hiring company, not directly from the host.