A Partoo alternative, built for India.

INR-native pricing is the practice of quoting a per-location, per-month subscription price in Indian Rupees with a GST invoice, rather than presenting a USD figure that the customer has to convert at a moving exchange rate and reconcile against a foreign-exchange invoice. For an Indian brand, the difference is concrete: a USD-priced plan means the number on the pricing page is not the number the finance team can plan against, because the rupee cost drifts every month, and a foreign vendor may not issue a GST invoice at all, which turns a routine software expense into a reconciliation headache. INR-native with GST invoicing means the figure you see is the figure you budget, and the invoice you get is the one your accountant expects — which is the whole point of publishing a price list in rupees rather than converting a global price into local currency.

The India geo hierarchy is the State → City → District → Taluk administrative structure that Indian operations teams use to organise a multi-location estate, and it does not line up neatly with the address model Google Maps exposes. A tool that understands the four-level Indian hierarchy lets you filter, group, and report on your estate the way an Indian operations team actually thinks about it — by state, by city, by district, by taluk — rather than forcing every pin into a flat list. The hierarchy is one of the two India-specific features the PlaceOptimizer Starter tier includes by default, alongside the diff-and-apply CSV import, and it stops being a nice-to-have the moment your brand spans tier-2 and tier-3 markets where the standard Google locality field is too coarse to be useful.

A multi-location estate is the set of every Google Business Profile your brand operates across every city or market you serve, treated as one connected network rather than a collection of independent pins. The point at which a single brand becomes an estate is roughly five locations: at that scale, manual consistency checks stop working, because a wrong category in Pune, missing hours in Jaipur, and a duplicate in Surat cannot all be tracked by hand, and the structural relationships between listings — fragmented names, drifted categories, and proximity-based duplicate candidates — become the dominant signal that moves the brand’s overall visibility. The audit reads the estate as one graph: every listing is compared against every other on four consistency axes, and a proximity-based duplicate detector flags same-brand pins within one kilometre for human review.

NAP consistency is the practice of spelling your business name (N), address (A), and phone number (P) identically across every Google Business Profile your brand operates. For a multi-location estate, NAP is the single biggest consistency lever you control, because Google uses these fields to reconcile all your listings into one brand entity; drift across any of the three makes that reconciliation harder and weakens the entity confidence Google applies to your pins. The audit automates four consistent dimensions: business name, primary category, website hostname, and phone-number format — particularly whether the Indian +91 country-code prefix is applied consistently across the estate. NAP fixes are manual by design, because deciding the canonical spelling of a brand name is a brand decision, not a mechanical one, and the engine reports the drift so a human can correct it rather than applying edits on the brand’s behalf.

A covered playbook is the labelling convention PlaceOptimizer uses to mark a check as one the engine automates today, as opposed to a manual verification item or a roadmap feature. The glossary is not strictly a PlaceOptimizer term, but the seven-category audit separates every signal into automated, manual, and roadmap, and the published audit posts are written so that a brand can read the checklist and know exactly which checks fire automatically and which still need a human. The discipline matters because an audit tool that pretends everything is automated is lying to you; covered playbook is the term for the kind of honest inventory that earns the right to be trusted when the engine does claim a score, because the operator can see where the machine stops.