Trademark Class Conflict in Nepal: How Conflicts Work Across the 45 Classes
When is a mark a trademark class conflict in Nepal — same class, similar goods, or different class? How the DOI reads the 45 classes in practice.
You found a near-identical mark on the register — in a different class. Or the same class, but selling something unrelated. Is either one a trademark class conflict in Nepal, or a neighbour you can live with?
The answer decides whether you file, negotiate or redesign, and it is more nuanced than 'same class equals conflict'. Nepal's single-class system plus the similarity rules produce patterns every applicant should know before paying fees.
In short
A trademark class conflict in Nepal is assessed class by class — Section 18A files one class per application, and the DOI examines each against earlier marks in that class. A same-class hit with overlapping goods is the classic conflict; a same-class hit for unrelated goods may coexist; and similar goods in different classes can still clash where the examiners treat the goods as related. The goods/services wording, not the class heading, decides the case. Add the bilingual dimension — cross-script similarity counts — and clearance becomes a reading exercise, not a class-number match.
The class system that frames every conflict
Nepal applies the Nice Classification — 45 classes, goods 1–34 and services 35–45 — under Section 18A of the PDTA, with one application per class. Each application is examined against earlier marks in its own class, published on its own schedule, and renewed on its own clock.
That structure produces the first rule of Nepalese clearance: the conflict analysis starts inside the class, but it does not end there. The class heading ('Class 30: coffee, tea, cocoa…') is only a gateway — the specification wording is what examiners compare against the earlier mark's goods.
The three trademark class conflict patterns in Nepal
Same class, overlapping goods is the classic Section 18(1) case: a conflicting mark for 'packaged tea' versus your application for 'tea' in Class 30 is a live conflict regardless of spelling differences that survive a phonetic test. Same class, unrelated goods can coexist — two Class 30 filers, one for seasoning spices and one for coffee beans, are usually neighbours, not enemies.
Different classes, similar goods is the pattern applicants miss: related-goods analysis can put a Class 29 dairy mark and a Class 30 milk-tea mark in each other's way, and retail services (Class 35) frequently intersect with the goods they sell. Bilingual marks add the fourth pattern: a Devanagari application can conflict with your Latin-script mark when the sounds match.
| Pattern | Example | Likely reading |
|---|---|---|
| Same class, overlapping goods | Two Class 30 marks for tea products | Conflict — Section 18(1) refusal or opposition |
| Same class, unrelated goods | Seasoning spices vs. coffee beans, Class 30 | Often coexistence; wording decides |
| Different classes, related goods | Class 29 dairy vs. Class 30 milk-based drinks | Possible conflict — related-goods analysis |
| Goods vs. retail of those goods | Class 30 tea vs. Class 35 retail services | Case-by-case; similarity factors apply |
| Cross-script sound-alikes | EVEREST vs. एभरेष्ट | Conflict — transliteration counts |
How to test a hit: the four questions
When a search surfaces a candidate, four questions sort threats from neighbours. One: are the marks similar — visually, phonetically, conceptually — including across scripts and translations? Two: do the goods or services overlap, or would a consumer reasonably think they come from the same source? Three: which mark is earlier — the first-to-file date is usually the whole argument? Four: is the earlier right documented and currently in force, or lapsed and vulnerable?
If the answers cluster toward overlap, the options are a redesign, a coexistence approach to the earlier owner, or — where the earlier right is yours — an opposition inside the 90-day window if the conflicting application has just published.
Searching for conflicts the way the DOI does
A clearance search should mirror the examination: exact name first, then phonetic and spelling variants (PH/F, C/K, doubled letters, plural forms), then transliterations into Devanagari and back, then the class filter with the goods text read line by line. A same-class hit for unrelated goods is a maybe; a same-class hit for your exact goods is a no.
Two disciplines catch what naive searches miss. Search across all 45 classes when the goods relationship, not the class number, is the question — the appliance importer's Class 9 mark and the repair service's Class 37 mark live in different class numbers and the same dispute. And read the earlier mark's full specification, because breadth of wording is where coexistence is won or lost.
Exact and variant passes
Search the name as spelled, then the variants you would be annoyed to be opposed by, across English and Devanagari.
Class-by-class reading
Filter to the candidate classes, then read the goods text of every hit against your specification — not the class heading.
When classes are also strategy
Class choice shapes future conflicts as much as it reflects the current business. Filing narrowly leaves the adjacent product line exposed to the next applicant; filing classes you cannot use invites weak registrations and renewal waste. The working rule is to file where revenue is, plus the class you can credibly show you are entering next — and to remember that each class is a separate NPR 1,000 application and, later, a separate NPR 3,500 renewal every seven years.
Before filing, search the whole field, not just the class. The conflict you avoid at the search stage is the cheapest one you will ever manage.
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.