A perfect translation can still be an off-label claim in the next market

Pharma content localization is the work of turning a global core asset into one that is accurate and compliant in a specific market: checked against that market's label, its promotion rules, its local references and its own approval process. Translation is one step in it, and rarely the hardest. A sentence can be translated perfectly and still make a claim the local label does not support.

This article covers why translation alone fails, how labels and indications differ between markets, the local codes and approval steps that apply outside the US, how the global core and local adaptation model works, how to keep each claim traceable to each market's label, and how to split ownership between global and affiliate teams. It is a practical overview, not legal or regulatory advice: each market's rules should be confirmed with local regulatory and compliance colleagues.

Why is translation not localization in pharma?

Translation changes the language. Localization changes whatever the market requires, and in pharma that starts with the product's approved information, not its words. The same medicine can carry a different approved indication, population, dosing or warning in each market where it is authorised, because each regulator reviews it separately and on its own timeline.

So a global visual aid built on the US prescribing information can contain a claim that is on label in the US and unsupported in a European market where the indication is narrower or not yet approved. A good translator renders that claim faithfully. Only a check against the local label catches it.

Beyond the label, the frame around the content changes too: the local promotion code, the information that must appear on every piece, the people who must approve it, the channels that are allowed, and the references a local HCP expects to see. Each of those is a reason a translated asset can fail local review.

How do labels differ between the US and Europe?

In the US, the approved reference is the prescribing information, the FDA-approved label. In the EU, it is the summary of product characteristics, or SmPC, which the European Medicines Agency describes as the document setting out a medicine's properties and its officially approved conditions of use, and the basis of information for healthcare professionals. The UK also uses an SmPC. The two documents cover similar ground in different structures and, often, different wording.

The differences that matter for promotion are the ones that change a claim: the indication wording, the line of therapy, the population, the dosing, contraindications and warnings, and which study results appear in the label at all. EU law requires every part of an advertisement to comply with the particulars listed in the SmPC, and the UK's ABPI Code requires promotion to be in line with the marketing authorisation and not inconsistent with the SmPC.

Watch the vocabulary too. In US promotion, PI means the full prescribing information. In the UK, under Clause 12 of the ABPI Code, prescribing information is a defined summary that must accompany promotional material, as text or through a clear link or QR code: the legal classification, the cost, at least one authorised indication, dosage, key adverse reactions and warnings, the marketing authorisation number and holder, and the date it was last revised, along with a statement on reporting adverse events with a link to the MHRA Yellow Card scheme. A US-built asset has no slot for any of it.

Which local codes and approval rules apply outside the US?

Across Europe, industry self-regulation sits on top of the law. The EFPIA Code sets the ethical rules EFPIA members agree for promoting prescription-only medicines to healthcare professionals and for interactions with them, and national member associations apply it through their own national codes, which can set stricter or more specific rules. Content that clears one country's code is not automatically cleared in the next.

In the UK, the ABPI Code of Practice applies, administered by the Prescription Medicines Code of Practice Authority (PMCPA). The 2024 Code has applied in full since 1 January 2025. Under Clause 8, promotional material must not be issued until its final form has been certified on behalf of the company by a registered medical practitioner or a pharmacist registered in the UK, who is not the person who developed the material, and material still in use must be recertified at least every two years. A global approval does not stand in for that certification.

Channels change as well. EU law requires member states to prohibit advertising prescription-only medicines to the general public, and the UK keeps the same prohibition. The US and New Zealand are the two countries generally cited as permitting DTC advertising of prescription medicines; as of October 2026, New Zealand's government has said its planned Medical Products Bill would keep that permission. A US consumer campaign does not localize into Europe. It is replaced by disease awareness content written to local rules, or by nothing.

The EU's pharmaceutical legislation is also being rewritten. As of October 2026 the new texts were still completing formal adoption, with a transition period to follow, so current rules continue to apply and local teams should track how the change lands in each market.

How does the global core and local adaptation model work?

Most multinational brands run some version of the same model. Global builds a core: the scientific narrative, the brand identity, the core claims with their references, and core assets such as a visual aid, a website structure and email templates. Affiliates adapt the core for their market, then run it through local review and approval.

The model works when the core is built to be adapted. That means claims kept as separate, referenced building blocks rather than baked into finished layouts, so an affiliate can remove a claim its label does not support without redesigning the asset. It is the same discipline as a modular claims library, covered in how to build a claims library your MLR team trusts.

It also means saying, in writing, what an affiliate may change and what it may not. Brand identity and the core narrative are usually fixed. Claims, references, obligatory information, safety text, imagery that reflects local practice, and the call to action are usually local. A core asset that arrives with no slots for local prescribing information or a local adverse event statement forces every affiliate to rebuild it.

How do you keep claims traceable to each market's label?

Keep a claim matrix. For every core claim, record the reference that supports it and, for each market, the section of the local label that allows it, or a plain note that it is not supported there. When an affiliate localizes an asset, the matrix tells them which claims they can carry before anyone writes a word.

Version it against label changes. Labels update on different dates in different markets. When the SmPC changes in one market, the matrix shows which claims in which local assets depend on the changed section, so the affiliate knows exactly what to withdraw or rework.

Keep local references local where they matter. A European HCP may expect European guidelines, local epidemiology and local health system context rather than US data. Adding them is part of localization, and every added reference needs the same claim-to-source annotation the core has. The test throughout is simple: every claim in a local asset should be on label for that market, and anyone reviewing it should be able to see why.

Who should own what between global and the affiliates?

Global owns the core: the narrative, the core claims and evidence, the brand rules, and the quality of the master assets. Global review checks that the core is accurate and fair, but it cannot approve content for a market whose label and code it does not apply.

Affiliates own local compliance: the check against the local label, the local code, obligatory information, local references, translation review by a qualified local reader, and final approval or certification under local rules. They also own the decision not to use a core asset when it does not fit.

The handoff between the two needs a loop back. When affiliates repeatedly remove the same claim or rebuild the same layout, the core should change. When a label update in one market affects a core claim, global needs to know which markets are using it. A shared record of claims, markets and approvals is what makes both directions work.

Where SwishX fits

Magic Studio generates content from one Brand Dossier and claims library, with every claim cited to its source and checked against the label for its market. Fair balance and safety information are placed in the asset as it is made, and anyone can ask an asset where a line came from, which is the question local reviewers ask most.

Finished work goes into the MLR queue and on into Veeva PromoMats with every claim and its reference attached, so local reviewers start from a traced asset rather than a translated one. Local approval still belongs to local reviewers. See how it works on the Magic Studio page.

Frequently asked questions