Every till, every store, one position

Yes — price lists apply per store, with the chain-level list as the default.

Retail Chains is in the Cloud Suite only. It is not part of the Desktop Suite, and we mark that plainly on every card and page rather than leaving it to be discovered after purchase. If Retail Chains is why you are here, the Cloud Suite is the edition to choose.

Multi-store POS, loyalty, planogram and omnichannel. In practice that means counters and shifts, loyalty that means something and planograms — each of which is a working screen rather than a line on a roadmap. The full breakdown, with what every one of them does, is on this page above.

It is not a separate product and there is nothing to integrate. Retail Chains reads and writes the same database as the ledger, stock and customer master, so a figure it shows is the figure the books hold — not a copy synced overnight, and not a number you have to reconcile against another screen before you trust it.

Retail Chains sits in the Industry group of the catalogue, alongside Pharma, Real Estate, Distribution, Logistics & Fleet and Construction and 7 more. They are separate applications with their own screens, not modules of each other — but they share one database, so what you enter in any of them is immediately real to the rest.

Retail Chains is a Cloud Suite application, so it needs a connection — it runs in the browser against your tenant rather than a local file. If working with the internet off is a hard requirement for your business, the Desktop edition is the one to look at, and it does not include Retail Chains.

Not as a feature of this application, and we would rather say so than claim it. The AI surfaces in LekhaPro — Copilot, the CFO, the deterministic insight engines — read the data Retail Chains produces, so its records inform them, but Retail Chains itself is deliberately a plain, fast, keyboard-first application.

It is built for Retail & Shops and Kirana & Grocery in particular, and it is not exclusive to them — Retail Chains is part of the horizontal suite, so any business on LekhaPro can switch it on. Those trades are named because their industry pages describe how Retail Chains is used in that specific line of work.

Yes. Access is by role rather than all-or-nothing, so a billing clerk can reach Retail Chains without reaching the books behind it, and an approver can see what needs a decision without editing anything else. On the Cloud edition every change also carries who made it and when.

Yes — 14 days, no card. The honest way to evaluate Retail Chains is with your own masters and your own transactions rather than sample data, because the questions that matter are about your business's edge cases, not ours. Nothing is deleted if you decide against it.