Related Goods in Nepal Trademark Law: When Different Classes Still Conflict
Related goods can collide across classes in Nepal trademark practice — how examiners weigh similarity of goods, and the cross-class pairs that trip brands.
The most dangerous sentence in Nepalese trademark planning is: 'we are in different classes, so we are safe.' Sometimes it is true. Often it is not — because related goods can conflict even when their class numbers differ, and the examiner knows it even when the brand owner does not.
Class numbers organise the register; they do not decide confusion. What decides it is whether the goods are the kind consumers would assume come from the same business.
In short
Related goods in Nepal trademark practice are goods whose proximity — in nature, purpose, trade channels or consumers — makes confusion plausible even across class lines. Nepal applies the Nice Classification under Section 18A with one application per class, but examination weighs the goods wording, not just the class heading. The recurring cross-class traps: packaged foods (Class 30) against retail services (Class 35), solar apparatus (9) against installation (37) and power generation (40), recorded software (9) against SaaS services (42). Search strategy must screen across related classes, not only your own — or clearance becomes a formality that misses the conflict that matters.
The trademark class system, and its limits in Nepal
The Nice Classification sorts all commerce into 45 classes — 1–34 goods, 35–45 services — and Nepal's Department of Industry files, examines and registers one class per application. The structure keeps the register legible. It does not keep consumers from being confused.
That is the gap the related-goods concept fills: two marks in different classes can still be deceptively similar for the same commercial world, and a Section 18(1) objection can reach across the class boundary when the goods' proximity makes confusion real.
The cross-class pairs that actually trip Nepali brands
Each row is a real pattern in Nepalese practice: the café chain files Class 43 and is surprised by a Class 30 conflict when it packages its signature blend; the software house files Class 9 and meets a Class 42 opponent at the platform stage.
| Class pair | The goods | Why they collide |
|---|---|---|
| 30 vs 35 | Packaged foods vs retail/trading services | The same product sold through the same channel — the retailer's brand meets the producer's |
| 9 vs 42 | Recorded software vs SaaS/development services | One product, delivered two ways — app and platform collide routinely |
| 9 vs 37 vs 40 | Solar apparatus vs installation vs power generation | The same trade seen from three desks — buyers cannot tell the marks apart |
| 30 vs 31 | Processed foods vs fresh produce of plant origin | Honey, tea and similar products straddle the processing line |
| 5 vs 30 | Dietary supplements vs foodstuffs | Health-adjacent products share consumers and shelves |
| 43 vs 30 | Restaurants vs packaged foods | The café chain that bottles its sauce lives exactly here |
How proximity is actually assessed
The assessment is comparative, and it runs on ordinary commercial sense: are the goods of the same nature or used for the same purpose? Do they move through the same trade channels — the same shops, the same importers, the same online categories? Are they bought by the same consumers, in the same manner, with the same attention level? The class heading is a doorway; the goods wording is the room the examiner actually walks through.
That is why specification drafting and clearance search are the same exercise from two ends: the wording that describes your goods precisely is also the wording that reveals which neighbouring classes your conflicts live in.
Searching across related goods and classes
The businesses that skip the neighbourhood map usually meet their real conflict at examination — at the one moment when changing course is most expensive.
Map the neighbourhood before the search
List the classes adjacent to your product: same consumer, same channel, same delivery mode. The Class 30 food producer's neighbourhood includes 35 and 43; the app developer's includes 9 and 42 together.
Screen every class in the neighbourhood
Exact, phonetic and Devanagari variants across all of them — 71,000+ published records, filtered class by class. A clean search in one class proves nothing about the next.
Read the hits as goods, not numbers
A same-class hit for unrelated goods may be survivable; a cross-class hit for the same buyer's basket may not. The wording decides, not the digits.
File where the conflicts will live, not just where you sell
Sequenced filings: the core class now, the adjacent ones as entry becomes real — each its own application, fee and renewal.
What this means for opposition and defence
The pattern behind all of it: Nepal's single-class filings keep the paperwork tidy, but the market stays one market. Related goods are how the law says so — and the brands that internalise it search wider, file smarter and oppose earlier than the ones that trust the class number.
- Oppositions: cross-class proximity is a ground — your own Class 30 registration can oppose a Class 35 retail application for a confusingly similar mark
- Defences: 'different class' is not a defence; 'different goods, different channels, different consumers' is
- Coexistence: where proximity is arguable but manageable, a documented coexistence agreement beats a proceeding
- Budget: defending a cross-class conflict is priced in professional time, not filing fees — prevention is the cheap end
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.