Trademark Conflict Assessment in Nepal: Fatal Conflict or Manageable Neighbour?
A trademark conflict assessment in Nepal: which register hits are fatal to a launch, which are manageable, and the tests practitioners apply before you rebrand.
The search came back with hits. Now what? Most businesses overreact to the first conflict and underreact to the second kind — treating a fatal collision as negotiable, or a manageable neighbour as the end of the brand.
The difference is not the length of the register extract. It is a structured assessment: how close the marks really are, how close the goods really are, and who is earlier.
In short
A trademark conflict assessment in Nepal sorts register hits into three groups: fatal (identical or near-identical mark, same or similar goods, earlier filing — stop and rebrand), negotiable (similar mark, partial goods overlap, an owner open to coexistence or consent), and noise (same name, unrelated goods and classes). The tests are Section 18(1)'s similarity analysis applied with local texture — phonetic comparison across English and Devanagari, goods proximity, and first-to-file priority — plus an honest look at your own evidence of use.
The three tests behind every trademark conflict assessment
Section 18(1) of the PDTA refuses marks identical or deceptively similar to earlier marks for the same or similar goods. Every conflict assessment runs the same three questions in the same order: similarity of the marks — visual, phonetic and conceptual, including across scripts; proximity of the goods or services — the class number is the starting point, not the answer, since related-goods analysis reaches across classes; and priority — in a first-to-file system, the filing date decides who is 'earlier' in most cases.
Miss one of the three and the assessment distorts. A mark identical in sound but in a distant class is often noise. A mark that looks different but sounds the same in Nepali, in your exact goods, is usually fatal — no matter how different the logos look.
The verdict table
| Scenario | Verdict | Why |
|---|---|---|
| Identical mark, same class, earlier filing | Fatal | Section 18(1) refusal is near-certain; opposition would fail |
| Phonetic match across scripts, your goods | Fatal | Nepalese practice treats transliteration sound-alikes as conflicting |
| Similar mark, adjacent goods, no overlap in trade channels | Manageable | Arguable case either way — negotiation or a narrowed specification may clear it |
| Same name, different class, unrelated goods | Noise | Coexistence is the norm; monitor, don't panic |
| Similar mark, owner open to consent | Negotiable | A consent letter or coexistence agreement can settle it |
Running the assessment properly
The mechanics matter as much as the framework.
Search in both scripts, then search again phonetically
The DOI's published records index more than 71,000 Bulletin entries, in English and Nepali. An exact-name search is the beginning, not the search — transliteration variants and phonetic matches in Devanagari are where the real conflicts hide.
Read each hit's goods, not its class
A hit in Class 30 for 'spices' may be harmless to a bakery brand in the same class; a hit in Class 35 for retail of your exact goods may be worse than a Class 30 lookalike. Goods wording and trade channels decide proximity.
Check the hit's status and dates
A published application is not yet a registration; a registration may be years into its 7-year term with lapsed renewals; a dead or withdrawn mark is a filing opportunity, not a conflict. The Bulletin entry and register status separate live threats from history.
Assess your own position honestly
If you have prior use in Nepal — dated invoices, signage, listings — that evidence changes the negotiation. If you have nothing on paper, a conflict against an earlier filer is a rebrand conversation, however unfair it feels.
Where conflict assessments go wrong
Four failure patterns account for most misjudged conflicts. Searching by exact name only — and missing the transliteration that is the real threat. Trusting the class number — a Class 30 hit against a Class 43 brand can still conflict where the goods overlap in practice. Ignoring register status — treating a dead application as a live conflict, or a live registration as a dead one. And assessing similarity in one script — the Devanagari form of an English name is where the surprise conflicts live, in both directions.
The corrective is the same for all four: run the assessment as a written exercise with the exhibits attached — marks side by side, goods wording quoted, status and dates printed — rather than a verdict formed from a search result list.
What to do with each verdict
Fatal means stop before money flows into packaging, signage and launch media. Rebranding on day 20 of a campaign costs a fraction of rebranding on day 200 — this is the outcome the assessment exists to catch early.
Negotiable opens the structured routes: a coexistence agreement recording how the marks will operate side by side, or a consent letter offered to or sought from the earlier owner in the opposition context. Both are writing exercises with the earlier owner, and both need the earlier registration to stay alive and renewed.
Noise gets logged and monitored. The hit goes into the decision log with its reasoning, so the next search cycle starts where this one ended instead of re-litigating the same extract.
Want this handled for your brand?
IP Watch monitors new trademark publications in Nepal and alerts you to potentially conflicting marks — with the context needed to review them.
This article is general information, not legal advice.