Tanvrit
Lekhita
Pre-release

लेखित — written down, recorded.

Billing, catalog, customers and reports for Indian merchants, under its own brand. Built on the same engine as Mandee, for shopkeepers who want the ledger first and the storefront second.

  • Billing and catalog built for a counter, not a spreadsheet

  • Customers, ledger and daily reports

  • Same engine as Mandee, its own brand

  • Landing page live; the app is pre-1.0

Android
iOS
Desktop
Web
Get notifiedAll products

What Lekhita will be

Lekhita — लेखित, written down, recorded — is billing, catalog, customers and daily reports for Indian merchants, under its own brand. It is built on the same engine as Mandee, for shopkeepers who want the ledger first and the storefront second. The landing page is live at lekhita.com. The app itself is pre-1.0 and has not shipped, so what follows describes what is being built, not something you can download today.

The ledger comes first

The order of the screens is the whole difference. Lekhita is being built for a shopkeeper whose day is billing, customers and the day's total — not merchandising. Billing and catalog are shaped for a counter rather than a spreadsheet, customers and their ledger sit next to the bill rather than in a separate module, and daily reports are the thing you check when you close. A storefront exists, but it is not what the app opens on.

Same engine, separate brand

Lekhita and Mandee share the commerce engine underneath: the same Tanvrit SDK modules for catalog, customers, billing and media, carried by the same release train. Above that line they are deliberately separate — two apps, two app identities, nothing shared at build time. That keeps a fix in the shared engine reaching both, while letting each brand make its own choices about naming, colour and what the first screen is.

Where it stands

The app is at 0.1.0 and nothing has been released to the stores. It builds today for Android, iOS, JVM desktop and the web as Compose Multiplatform, and the brand system — the icon set, the business-type artwork — is generated from SVG masters rather than hand-drawn per size. What remains is product work and the release process, not a rewrite. Treat any date you have not heard from us as unannounced.

Frequently asked questions

Can I use Lekhita today?
Not yet. The landing page at lekhita.com is live, but the application is pre-1.0 and has not been released on any platform. If you need a shipping product now, Mandee is the same engine under a different brand.
How is Lekhita different from Mandee?
The engine is shared; the emphasis is not. Lekhita is built ledger-first, for merchants whose day is billing, customers and the daily total, with the storefront as a secondary surface rather than the headline.
What does the name mean?
Lekhita (लेखित) means written down, or recorded. It is a description of what the product is for: keeping a reliable written record of what was sold, to whom, and what is owed.
Which platforms will it run on?
The same four as the rest of the commerce line — Android, iOS, desktop and the web — from a single Compose Multiplatform codebase. All four targets build today; none has been released.
If it shares code with Mandee, is it the same app rebranded?
No. They share the underlying commerce engine but are separate applications with separate identities and nothing shared at build time. Each can diverge in what it shows and how it is set up without disturbing the other.

Lekhita shares its foundations — one SDK, one API, one account — with the rest of what we build.