Phonetic Trademark Search vs Exact Search in Nepal: Why Spelling Alone Misleads
A phonetic trademark search finds what exact search misses in Nepal — sound-alikes, transliterations and Section 18(1) similarity. The layered clearance method.
An exact search of Nepal's trademark records answers the question 'is my spelling taken?'. The law asks a different question: would a customer briefly hearing both names in a shop mix them up?
Between those two questions sits every sound-alike conflict — PH for F, doubled letters, plural forms, and the whole cross-script world where EVEREST and एभरेष्ट are the same name. Exact search cannot see any of it.
In short
A phonetic trademark search is the layer that makes name clearance work in Nepal: Section 18(1) turns on deceptive similarity, not identical spelling, so PH/F swaps, C/K confusions, doubled letters, plurals and Y/I endings all generate live conflicts — and in a bilingual market, cross-script sound-alikes between English and Devanagari conflict even with no shared letters. The professional method is layered: exact match first, then phonetic variants, then transliterations, then a class-filtered read of the goods each hit covers. Exact search finds the copycat; phonetic search finds the conflict.
Why phonetic trademark search beats exact search alone
Section 18(1) of the PDTA — the dominant refusal ground and the dominant opposition ground — asks whether a mark is identical to or deceptively similar to an earlier mark for the same or similar goods. Similarity is judged by sound, appearance and the idea the mark carries, weighted for how ordinary Nepali consumers actually encounter brands: heard at a counter, read on a label, remembered imprecisely.
An exact search is still the first layer — identical hits are the high-certainty conflicts. It is simply not a clearance. The file that clears on spelling alone and stops there has not been searched; it has been typed.
The substitutions that generate live conflicts in Nepali practice
The working rule from Nepal's search practice: search the variants you would be annoyed to be opposed by. The list above is where those live.
- PH ↔ F: FANTOM/FANTOMM territory — the sound survives every spelling
- C ↔ K: KAFE/CAFE-class confusions, endemic in food and beverage naming
- Doubled letters: single and double consonants are the same word to a listener
- Plural forms: the singular and plural of a name read as one mark
- Y ↔ I endings: the classic tail-swap that defeats naive matching
- Cross-script pairs: एभरेष्ट and EVEREST share no letters and conflict completely
The layered search that clears a name properly
Exact match, all name fields
Search the mark as spelled across the fields the published records carry — device marks may print text that differs from the artwork.
Phonetic and spelling variants
Apply the substitution list — PH/F, C/K, doubled letters, plurals, Y/I — and search each variant that a Nepali ear would confuse.
Transliterations, both directions
Search the Devanagari form of an English name and the romanisations of a Nepali name. Cross-script conflicts are where exact matching fails completely.
Filter by class, then read the goods
Class narrows the field under Section 18A; the goods wording decides it. A same-class hit for overlapping goods is a conflict; a same-class hit for unrelated trade may not be.
Read each survivor as a record
For the hits that matter, capture mark, applicant, class, goods, filing and publication dates, and the Bulletin issue — the publication date starts the 90-day opposition clock on any live application.
What each search layer catches — and what it misses
The layers compound: each catches what the previous missed, and none replaces the last one. Structured search tools automate the first three; the fourth stays human.
| Layer | Catches | Misses |
|---|---|---|
| Exact match | Identical spellings in any name field | Sound-alikes, translated forms, transliterations |
| Phonetic variants | PH/K, C/K, double-letter, plural and ending changes | Cross-script equivalents and meaning-based similarity |
| Transliteration search | Everest ↔ एभरेष्ट and romanised Nepali names | Conceptual similarity — different words, same idea |
| Class-filtered goods read | The human judgment layer: real conflicts versus same-class strangers | Nothing — this is where a lawyer's hour earns itself |
From search result to legal judgment
A phonetic hit is a candidate, not a verdict. Nepalese similarity practice weighs how the marks sound, how they look, and what they suggest — always against the goods and the trade channels. A strong phonetic match across unrelated goods may be a neighbour; a weak-looking one in your exact goods may be fatal.
That judgment is the point where a practitioner earns the fee: ranking the hits, testing the honest confusion question, and deciding whether the name needs changing before money goes into printing and filing.
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.