The regulatory, biological, and economic reasons behind “bring your own” — and what a third path looks like
In hospitality, there is an unwritten rule: if you cannot control the quality of something from start to finish, it feels safer not to offer it at all.
With skin this creates a paradox. The largest organ of the body takes a big part of the load when a guest travels: from the flight and transfers to a new physical and microbial environment on arrival. Yes, skin can adapt but evolution tuned it to adjust slowly, over a season, not in 24 hours.
Modern travel breaks this rhythm. One day a person is in winter, the next day in high summer. Today in an office, a few hours later on a plane with very dry air, a day later on the Camino walking dozens of kilometres. Nature did not design us for such jumps.
Hoteliers, tour operators, and travel designers know this very well.
Where hosts stand today
In practice the message is still most often: “Bring your own.” At best, the guest receives basic hygiene: shower gel, shampoo, lotion.
For a host today there are usually three realistic options:
- let the guest bring their own products — the classic “BYO” model;
- gently recommend what to buy (a short list of formats or brands in a welcome email or guest guide);
- or add another layer of service and offer ready, scenario-based care on top.
The first two options are completely valid and often enough, because the real conflict for a host is simple:
- If you step into “your own skin care”, you take on legal and operational risk.
- If you stay away from skin care completely, your guests still face sun, wind, friction, and dryness — and your service stops at basic hygiene.
Most hosts solve this by protecting themselves first. The choice is driven by responsibility and regulation, not a lack of care. From a risk perspective, it is a very logical decision.
⸻
Why they are right
1. Regulatory load (Responsible Person, CPSR/PIF, CPNP)
To “do your own skin care” in Europe, you effectively have to become a small cosmetics company.
For every product you need:
- a legal entity acting as the Responsible Person in the EU;
- a Cosmetic Product Safety Report (CPSR) and a Product Information File (PIF) for each product;
- CPNP notification before placing it on the market;
- manufacturing that works under GMP principles for cosmetics.
If a hotel, tour operator, or retreat wants to release a product under its own brand, it is no longer “just giving a cream to the guest”. Legally it becomes the party that places a cosmetic product on the market under its name and takes on part of the responsibilities of a manufacturer / Responsible Person.
For a small host this is essentially a new type of business — with its own risks, documentation, and inspections.
2. Biological differences
Guests differ in many ways: skin type, age, allergy history, medication, hormonal status, skin barrier condition.
With cosmetics the reality is simple: no matter how careful you are, sooner or later someone will react badly even to a very mild and “universal” product. This is normal statistics, not a personal failure.
From the guest’s point of view the logic is also simple:
“You gave this to me — so you are responsible for it.”
Any cream that you “recommend” or “give from yourself” is automatically perceived as part of your service. This is where a very rational fear appears: even a small reaction can easily turn into a complaint or a claim against the host.
3. Economics
Personalising skin care around your own scenarios is expensive — and the numbers rarely work.
MOQs at most manufacturers are high. You pay not only for the product, but also for storage, distribution, expiry management, write-offs, and staff training. In mass, lower-priced tourism this cost is almost impossible to recover. In higher-service travel there is margin, but volumes are small: many boutique hotels, retreats, yacht companies or specialist tour operators see tens or a few hundred guests a year, not thousands. In that reality, an MOQ of 1,000+ units quickly turns into frozen stock and, later, write-offs.
Taken together, these three factors — regulation, biological differences, and economics — make one thing clear: “bring your own, we do not touch skin” is a rational choice.
⸻
How this can be delivered
Up to this point, hosts have often had to choose between taking on full responsibility for skin care — or avoiding it almost entirely. For many operators who design routes and experiences in detail, this creates a direct tension with their real goals: happier guests, fewer silent complaints, stronger reviews, and clearer differentiation.
A third path exists: offer precise, scenario-based care through a supplier that carries the product-side responsibility. In this model, the host remains a host — while the supplier remains responsible for the skin care product.
In short, the architecture looks like this:
Responsible Person and manufacturing
A specialised supplier can act as the Responsible Person (or work with a designated Responsible Person) and organise manufacturing. The host does not need to become a cosmetics operator.
Compliance sits on the supplier side
CPSR, PIF, GMP-compliant manufacturing, CPNP notification — this work sits with the product owner / RP. The host does not need to build a “mini compliance department”.
Contracts and insurance structure the risk
Appropriate contracts and product liability insurance can clarify roles and keep most product-related risk on the product side — as far as applicable law and agreements allow. There is no “zero risk” in cosmetics. The goal is to make the risk professional and manageable: documented formulas, defined roles, traceability, and insurance designed for this category.
Personalisation without extreme MOQs
Instead of creating a unique cream “from scratch” for every partner, scenario-based care can be built from a scenario library: a pool of ready, tested single-dose formulas that can be assembled into protocols when a route or season calls for specific support.
Under EU law, each formula used as a module is its own cosmetic product with its own CPSR, PIF, and CPNP notification. The protocol is then assembled from these compliant modules.
⸻
What the host’s role looks like
In practice, the host stays in familiar territory: describing what their guests face, choosing when and how to offer support, and placing a set the way they already place a towel or a welcome drink. The formulation, documentation, manufacturing, and compliance infrastructure stay on the supplier side.
⸻
What this looks like day to day
Guests return after a long stage and find a clear, ready protocol waiting for them. Staff do not have to guess, mix products, or give off-the-record advice — they hand over a small, documented set that matches the day. Complaints about sunburn, friction, or “my skin is on fire” become rare exceptions instead of a background pattern.
This does not cancel the options a host already uses. Guests can still bring their own products. A host can still recommend pharmacies and formats they trust. Scenario-based care simply becomes an additional layer for places that want to remove one more piece of silent discomfort from the guest’s journey.
⸻
High responsibility: why compliance lives in the supply chain
Scenario-based care is a high-responsibility category. EU cosmetics regulation is among the strictest in the world — and for good reason.
The architecture described above is designed to keep that responsibility where it belongs: with the party that has the infrastructure for it.
- Responsible Person (RP) — designated on the supplier side, carrying all obligations under the EU Cosmetics Regulation.
- CPSR and PIF — every formula has its own Cosmetic Product Safety Report and Product Information File, maintained by the RP.
- GMP-aligned manufacturing — production under Good Manufacturing Practice, auditable and documented.
- CPNP notification — each product notified before market placement.
- Product liability insurance — structured to cover the product category specifically.
- ESG and sustainability documentation — traceability, ingredient sourcing, carbon footprint data — available for the host’s own reporting requirements.
For the host, this means: the compliance burden does not transfer. The documentation exists. The certifications are in place. The host gets a fully documented, ready-to-offer care layer — without building a compliance department.
This is what makes the third path viable. It doesn’t remove responsibility entirely — it places it in a structure designed to carry it.
⸻
Co-branding
Co-branding can be structured without turning the host into a de facto manufacturer, as long as the Responsible Person remains clearly defined on the product side. In practice, this can range from simple partner credit (“Designed with [Property] for…”) to visual co-branding, depending on the model, documentation, and risk tolerance.
⸻
If nothing changes, this discomfort doesn’t disappear — it just stays on the guest. The practical question is where your service already functions as infrastructure, and where a scenario-based layer could prevent the predictable “pain points”.
⸻
Important note: This article is a general overview and does not constitute legal advice. Specific arrangements depend on the partnership model, product configuration, and the regulations that apply in your jurisdiction.
Core Concepts
Scenario-based care — the discipline of designing physical comfort into the rhythm of a guest journey, treating care as a service layer rather than a product category.
The two-layer model — the separation of hygiene infrastructure (Layer 1: soap, dispensers, basic products — managed as CPOR) from scenario-based care (Layer 2: optional, context-specific, tied to the guest’s actual day).
The Host — the hotelier, operator, guide, or captain who holds the actual context of the journey. Knowing the weather, schedule, and physical stressors in advance, they co-design the scenario-based care layer for their business to remove the guest’s cognitive load.
Responsible Person — (EU Cosmetics Regulation term) the legal entity responsible for placing a cosmetic product on the market, carrying all compliance obligations: CPSR, PIF, CPNP notification, GMP-aligned manufacturing.
Scenario-based skin care — a specific implementation of scenario-based care focused on the skin and body, delivered as single-dose capsules assembled for the physical stressors of a specific journey. The ÓCOMO brand operates in this space, designing care sets in three phases: before (prepare and protect) → during (support and manage exposure) → after (recover and reset).
Frequently Asked Questions
What are the legal requirements for hotels offering skin care products to guests? In the EU, any party placing a cosmetic product on the market under its name must comply with: Responsible Person designation, Cosmetic Product Safety Report (CPSR), Product Information File (PIF), CPNP notification, and GMP-aligned manufacturing. For most hotels and operators, this represents a separate business category with its own regulatory infrastructure.
How can a hotel offer skin care to guests without taking on compliance risk? By partnering with a supplier who acts as Responsible Person and carries the compliance infrastructure — CPSR, PIF, GMP manufacturing. The host selects and offers the protocol; the product-side documentation and liability structure remains on the supplier.
Why do most hotels use “bring your own” skin care and is this changing? The “BYO” model emerged from rational risk management: regulation, biological variability, and economics make it difficult for individual operators to manage skin care responsibly. This is changing as modular, compliant, low-MOQ formats make it possible for hosts to offer scenario-based care without becoming cosmetic manufacturers.
You are reading: Part I — Why Hosts Don’t Touch Skin Care — and Why That’s a Rational Decision
← Previous: The Halo Effect of Discomfort: Why Physical Failures Produce Unfair Reviews
→ Next: When Personalisation Becomes the Standard