61 questions about Lekhio

Lekhio comes from लेख (lekh) — the Nepali, Hindi and Sanskrit word for something written: an article, a record, an inscription. It descends from the Sanskrit root लिख् (likh), “to scratch or inscribe”. The name means, roughly, “whatever you need written” — which is the product: a system with no fixed forms that you shape to your own business.

The root is. लिख् (likh) is a Sanskrit verbal root meaning to inscribe or write, and it gives लेख (lekh, a piece of writing), लेख्य (lekhya, a written legal instrument) and लेखा (lekhā, a line — and, in modern Nepali and Hindi, accounts). “Lekhio” itself is coined: lekh plus the software suffix -io.

Because the same Sanskrit root reaches both ends of an ERP. लेख means anything written — which is what a no-code Collections engine gives you, a blank page with no fixed modules. And लेखा, from the identical root, is the everyday Nepali and Hindi word for accounts: a लेखापाल is an accountant, लेखा परीक्षण is an audit. One word for “write whatever you need” and “keep the books” is an unusually exact description of what Lekhio does.

LEY-khee-oh — three syllables, /ˈleɪ.kʰi.oʊ/, written लेखिओ. The stress is on the first syllable and the “kh” is the aspirated ख of लेख: a soft breath after the k, not a throaty “ch”.

लेख means a piece of writing. The related form लेखा (lekhā) is the one that means accounts — it is the standard term across Nepali and Hindi officialdom: लेखापाल (accountant), लेखा परीक्षण (audit), महालेखा परीक्षक (Auditor General). Both come from the same root, which is precisely why the name works for software that spans free-form data and formal accounting.

The name was chosen by the team at Lacspace Corporation Pvt. Ltd., the company behind the product, founded in 2021 by Eallen Karna and registered in both India and Nepal. It was picked after the no-code Collections engine already existed — the engine came first, and the name had to describe something that deliberately refuses to be one fixed thing.

No. Lekhio’s interface is in English, and the name is the only part of it you will need to pronounce. The etymology explains the design philosophy; it is not a requirement to use the product.

No. Lekhio is built first for the realities of doing business in Nepal and India — how invoices are itemized, how receivables are chased, how stock moves — because the team lives in those markets. But a system flexible enough to model any business, connected end to end and available on web, mobile and API, serves companies well beyond the region.

Minutes to a working account, and typically a day or two to model your business properly. Sign up, and you get a working structure straight away — customers, products, orders and invoices — which you then rename, extend or replace with pages of your own.

No. You build your data structure, forms and views visually — no code required. When you do want to integrate with something else, a self-documenting REST API, scoped API keys and webhooks are ready for your developers.

Yes. CSV import is available on every plan, including the free Starter plan, so you can bring customers, products, stock and open balances across from spreadsheets or your previous system. Enterprise includes hands-on migration assistance.

Yes, at any time and on any plan. Your data stays exportable to CSV throughout, and the REST API can read everything programmatically. There is no export paywall and no lock-in.

Growth customers get guided setup resources and email support. Enterprise includes custom onboarding, data migration assistance and a dedicated success manager to help roll Lekhio out across teams.

Structure is editable at any point — add, rename or remove fields and pages as your understanding improves. Documents that must not change, like sent invoices, are protected instead: voiding preserves the record rather than deleting it, so the history stays intact.

The full B2B and B2C operation: customizable collections, sales and orders, itemized invoicing and billing, purchases and inventory, finance and receivables, plus live reports and dashboards — all connected in one system rather than stitched across several.

Invoices carry both product lines and free-form service lines, each with quantity, unit price and tax. They move draft → sent → void, with voiding preserving history rather than erasing it. You can record full or partial payments, generate running customer statements and export a designed PDF.

Yes. Set a schedule and Lekhio raises the invoice for you on time, every time — useful for retainers, subscriptions, rent and maintenance contracts.

Yes. Keep B2B and B2C customers on separate pages, give products a price column per tier, and map each customer page to its column. The server resolves the tier from the customer on the order — never from the request — so the price cannot be changed by the client. If a product has no price for a tier, it falls back to the standard price rather than billing zero.

Purchase orders, goods receipt, per-location stock and low-stock alerts. Stock moves as orders and receipts are processed, so what you see is what is actually on the shelf rather than a number somebody remembered to update.

Yes. Finance covers payments, partial payments, aging buckets and per-customer statements, so the collections conversation starts from a figure both sides can see rather than from a reconstruction.

Yes — the Billing Station. It is a fast counter screen for building a cart from your product catalog, attaching a customer, applying discounts and charges, and raising the order or invoice. It runs full-screen, and what it shows is priced by the same server logic that bills it.

Yes, without scripts. Build rules as WHEN / AND / THEN sentences — when stock drops below a threshold and the status is still “In stock”, notify the buyer and raise a purchase order. Automations run against your own collections and fields, whatever you named them.

Every organization is a separate tenant with strict data isolation, JWT-based authentication and role-based access control (owner, admin, manager, staff) so people only see what they should. One tenant’s queries can never reach another tenant’s records.

Yes. Roles set the baseline, and permissions can be narrowed per page and per action, so a counter staff member can raise invoices without seeing supplier costs or payroll. Filtering happens on the server, not by hiding things in the interface.

Sensitive personal fields on a team member’s profile — an emergency contact, for example — are visible only to that person and to owners and admins. Other staff see the directory without them.

Yes. Records carry creator and last-editor attribution, so you can see who added a customer or last touched an order. Voided documents keep their history rather than disappearing.

Email and password, or a one-time code sent by email. Sessions use JWT access and refresh tokens, and access is revoked immediately when a team member is removed.

No. Your operational data belongs to your organization and is not used to train models. The Privacy Policy sets out exactly what is collected, why, and how long it is kept.

Yes. The Starter plan is free forever and includes one organization, up to three users, customizable collections, and full sales, orders and invoicing. It is a real working plan, not a time-limited trial.

No. You can create an account and start using Lekhio without entering any payment details. A card is only needed if you choose to upgrade to a paid plan.

A user is any person with their own login who can view or edit data in your organization. Starter supports up to three users; Growth and Enterprise include unlimited users, so you can invite the whole team.

Yes. Paying annually saves roughly 20% compared with month-to-month billing on paid plans, and you can switch between monthly and annual billing at any time from your account settings.

Yes. Plans are month-to-month with no lock-in. You can downgrade or cancel whenever you like and keep access through the end of your current billing period, with your data exportable via CSV throughout.

Nothing is deleted. Features above your new plan become unavailable, but your records stay intact and exportable, and everything returns as it was if you upgrade again.

Every business is isolated in its own tenant with role-based access and encrypted data.