White-label surfaces for the people outside your company
Your suppliers do not have a relationship with your PLM vendor. Sending them to a portal wearing somebody else's brand is a small indignity that produces a real support burden.
Three layers, and which ones matter
White-labelling is usually presented as a logo swap. It is three distinct layers, and the one that matters most is the one that costs the most to implement.
- Visual — logo, colour palette, typeface, favicon and email templates. Straightforward, and the layer everybody demonstrates.
- Domain — the portal served from
suppliers.yourcompany.comunder your certificate, and notification email sent from your domain with your SPF and DKIM alignment. This is the layer that decides whether a supplier believes the message. - Language — no product name in the interface a supplier sees. Not in navigation, not in error messages, not in the automated emails, and not in the page titles that show up in a browser tab.
Why the domain layer is the real one
A supplier receiving an email from an unfamiliar domain asking them to log in and download a drawing is receiving something indistinguishable from a phishing attempt. Many of them will treat it as one, correctly, and the ones who do not are being trained badly.
The observable cost is a support queue. Suppliers call to ask whether the email is genuine, or ignore it and miss a change notification, and both outcomes land on the person who administers the portal.
Serving from your domain under your certificate, with email aligned to your SPF and DKIM records, removes the question. The supplier receives a message from a domain they already do business with, which is what makes them act on it.
The language layer matters for a narrower but sharper reason: an error message naming an unfamiliar product tells a supplier to contact a company they have no contract with. Support requests then arrive at the wrong organisation and get a slow answer from people with no context.
The failure it prevents
A manufacturer rolls out a supplier portal. Change notifications go out from the vendor's domain. Adoption is measured at forty percent after three months and the rollout is judged a failure of supplier engagement.
The actual cause is that two of the largest suppliers have mail rules quarantining messages from unrecognised domains asking for authentication, and a third's security team told their buyers not to click links in them. None of that reached the manufacturer as feedback; it registered as silence.
Adoption was never about willingness. The suppliers were not refusing to engage — the invitations were not arriving in a form their own security policies would let them act on.
How it meets the rest of the product
Controlled copies carry your branding rather than Manufacturing PLM's. A watermarked drawing reaching a supplier is stamped with your revision, your control markings and your identity, which is what a controlled document is supposed to look like.
Notification templates are editable per tenant, so the wording a supplier receives is yours. That matters more than it sounds: the phrasing of a change notification is a commercial communication, and default vendor wording is rarely how a company would put it themselves.
Internal surfaces are a separate decision. Most tenants leave the internal interface unbranded because their own staff have no confusion to resolve, and configuring both is possible where a company would rather everything look like one system.
Access control is unaffected by any of it. A branded portal is the same permission model wearing different colours, and a supplier sees exactly the documents and requests their scope grants them — the branding changes what the page looks like and never what it contains.
Multiple brands are supported per tenant where a company trades under more than one, so a supplier working with two divisions sees the division they actually contract with rather than a parent name they may not recognise on an invoice.
How it meets your ERP
Where a supplier reaches documents through a link on a purchase order, that link should resolve inside your branded domain. A PO from your company pointing at an unfamiliar host is the same trust problem in a different place, and it is the more common one.
Some organisations already run a supplier portal alongside their ERP, in which case the branded Manufacturing PLM surface should match it rather than introduce a second look. Matching an existing portal is the ordinary case, not the exception.
Manufacturing PLM does not brand or alter anything inside your ERP. The white-label surfaces are the ones it serves — the supplier portal, notification email, controlled copies and any customer-facing pages.
Where the boundary is
White-labelling is a presentation layer, not a resale licence. Serving Manufacturing PLM to your own customers as a product of your own is a commercial arrangement governed by your agreement, and the branding configuration does not by itself grant it.
The layer is also not unlimited. Colours, typefaces, logos, domains and wording are configurable; the interaction design, screen structure and workflow are not, because a tenant-specific interface is a tenant-specific product with a support and upgrade cost to match.
Facts
| Three layers | Visual · domain · language |
| Most demonstrated | Visual — logo, palette, typeface, favicon |
| Most important | Domain — your host, your certificate, your SPF and DKIM |
| Why | An unfamiliar domain asking for a login is indistinguishable from phishing |
| Language layer | No product name anywhere a supplier can see it |
| Controlled copies | Watermarked with your identity, not ours |
| Templates | Notification wording editable per tenant |
| Not configurable | Interaction design · screen structure · workflow |
Frequently asked
Isn't white-labelling just a logo swap?
That is one of three layers and the least consequential. Domain — your host, your certificate, your SPF and DKIM alignment — decides whether a supplier believes the message at all, and language decides whether their support requests reach the right company.
Why does the sending domain matter so much?
Because a supplier receiving an email from an unfamiliar domain asking them to log in and download a drawing is receiving something indistinguishable from a phishing attempt. Many will treat it as one, correctly, and the ones who do not are being trained badly.
What does that cost in practice?
A support queue and misread adoption numbers. Suppliers call to ask whether the email is genuine, or quarantine it under their own mail rules and miss change notifications — and that silence gets recorded as unwillingness to engage rather than as a delivery problem.
Why remove the product name from error messages?
Because an error naming an unfamiliar product tells a supplier to contact a company they have no contract with. The support request then arrives at the wrong organisation and gets a slow answer from people who have no context on the relationship.
Do controlled copies carry our branding?
Yes. A watermarked drawing reaching a supplier is stamped with your revision, your control markings and your own identity, which is what a controlled document is supposed to look like when somebody outside your company opens it and has to decide whether to trust it.
Should we brand the internal interface too?
Most tenants do not, because their own staff have no confusion to resolve and the branding buys nothing internally. It is configurable where a company would rather every system its people touch looks like one coherent environment, but it is rarely the priority.
Can we resell Manufacturing PLM as our own product?
Branding configuration does not by itself grant that. Serving Manufacturing PLM to your own customers as a product of your own is a commercial arrangement governed by the terms of your agreement, rather than something the white-label settings decide on their own.