How do I add eIFU to my website?Document access under your brand.

What is a white label eIFU portal?

White label means presenting document access under your company identity. For example, a fictional manufacturer can link example.com to a portal at ifu.example.com. Users see your logo and portal address, while technical setup and daily product–document management have defined owners. White label does not automatically mean source-code ownership or unlimited custom development; include those requirements explicitly in the proposal.

Can I connect WordPress or my existing website?

A website that supports a normal link or menu item can direct users to the document portal. You can retain your corporate content management system while giving users access to product documents. This is the starting point for WordPress, a custom website or another CMS. Do not assume a ready-made plugin, iframe embedding or API integration is included. Assess those options against your technical requirements and agreed scope.

How do we plan the domain, DNS and HTTPS?

Choose the portal address first: a subdomain you own or another address agreed during setup. Identify the domain owner, the person authorized to edit DNS and the party managing HTTPS certificates. The technical team should provide the DNS record for the verified hosting target; do not copy a generic IP address or CNAME into every deployment. Test HTTPS, redirects and the continued availability of your corporate site before release.

68 user application languages and worldwide markets

The user-facing application supports 68 interface languages. Choose your target markets from 290+ country and region options. User application language, portal interface language, IFU document language and product market are separate settings. Selecting an English interface does not translate every IFU into English. Your team provides, maps and approves each document translation. Selecting a country also does not establish eligibility for electronic IFU delivery there; assess each product and market separately.

How do website links and product QR codes differ?

A general documents link on your website can open portal search. A product-specific QR link offers a shorter path to that product’s document selection. Connect the QR to a planned product access address rather than a temporary file-upload URL. After a revision update, test that a printed QR still opens the correct product and published version. Plan domain ownership and redirects before a domain or supplier change.

What should I prepare before setup?

Prepare your logo and brand colour; domain and DNS contact; product references and GTINs where available; document types, revisions and files; intended users; target markets and required document languages; preparation, review and approval owners; and the team handling paper IFU requests. Start the discussion with one representative product and workflow rather than transferring an entire archive at the first meeting.

What do we test before going live?

Open the portal link from your corporate website. Find the same product by reference, GTIN where available and QR. Change audience, country and file language and check the correct published document. Review missing-language and withdrawn-document behaviour. Test mobile use, HTTPS, paper IFU requests and handover to the responsible team. Record the product, language, country, expected result and observed result for each test.

What should the proposal say about cost and ownership?

Separate white label scope, technical setup, training and subscription in the proposal. Clarify domain ownership, certificate renewal, backups, support, document translation and data handover responsibilities in writing. Do not assume a fixed installation time, price or that every integration is included. Request a plan for product data handover and continuity of printed QR links if the subscription ends.

Prepare the setup inventory →

Plan permanent product QR links →

Compare supplier scope and handover →