A showroom cannot stop billing because a queue worker died or a cloud region had an incident. ambar 27 is built on a small, well-understood stack that runs on hardware you can point at — and keeps running when your internet does not.
There is no microservice mesh, no message broker to babysit and no JavaScript framework between the counter and the database. A request comes in, a worker handles it against MySQL, and a page comes back. That is the whole architecture, and it is why it is fast and why it stays up.
ambar 27 is installed for you, on infrastructure you own or rent in your own name. There is no shared multi-tenant database, no vendor lock on your data, and no scenario where a billing dispute takes your store offline.
The load pattern in Indian textile retail is brutal and predictable: eleven quiet months, then a Diwali week where every counter bills continuously. Worker mode and indexed reads are what keep an invoice under a second when all of them are busy.
Every integration uses your own credentials and your own accounts. We do not resell you an API.
IRN generation and cancellation with signed QR, plus e-way bill generate and cancel, configured per GSTIN with your GSP credentials.
GSTR-2A purchase register download and GSTR-2B reconciliation data pulled for matching against your purchase register.
Ledger mapping for sales, purchase, GST and expense heads, with XML voucher, ledger, stock item and unit generation.
Your business account and phone number ID, sending templated document messages for invoices, receipts and statements.
Online collection with reconciliation back to the customer ledger and the card settlement flow.
Statement import and matching against recorded bank transactions to drive reconciliation inside the ledger.
Direct thermal and label printing with a digital certificate, plus a dedicated scanner app for stock taking and inward.
A native Go service that registers employee face descriptors and matches attendance, running entirely on your server.
Real-time channels so counters, cashiers and floor managers see the same figures without refreshing.
Scanner tablets, feedback devices and your own tooling talk to ambar 27 over an authenticated REST API. If you need to push data from a marketplace, a website or a legacy system, that is the door — not a database connection.
The software is already written. What takes time is your data, your rules and your people — so that is where the schedule goes.
We walk your floors and your books: counters, warehouses, GSTIN structure, cheque practice, jobwork flow, incentive schemes, and who is allowed to approve what. The output is a configuration document you sign off, not a wishlist.
Categories, designs, attributes, sizes, suppliers, customers, ledgers, opening balances and live stock are imported and reconciled against your existing books. This is the phase that decides whether your reports are trustworthy, so it gets the most attention.
You bill on ambar 27 alongside your current system for an agreed period, with daily tie-outs on sales, stock and cash. We do not declare go-live until the two agree for a full week.
Role-wise training by function — counter staff learn billing and selections, cashiers learn settlement, accounts learn planners and returns — with printed SOPs left behind for each role.
A defined support window with the same team that implemented it, then transition to ongoing support. You keep the server credentials throughout.
| Area | How it works |
|---|---|
| Data ownership | Your database, on your infrastructure, under your credentials. Full dumps on request at any time, in standard MySQL format — there is no proprietary export to negotiate. |
| Backups | Scheduled database and file backups to storage you control, with a retention policy set during implementation. Restore is tested as part of go-live, not assumed. |
| Updates | Versioned releases deployed through a CI pipeline. Schema changes ship as forward-only migrations that run on deploy, with a rollback plan for each release. |
| Monitoring | Application error logging through Monolog, with alerting on failures. Failed IRN and e-way bill submissions surface as worklists in the application rather than in a log file nobody reads. |
| Support | A named team that knows your configuration. Support covers the application, the integrations and the deployment — including the server, if you have asked us to manage it. |
| Customisation | Reports, print templates and workflow rules specific to your business are built as part of implementation or a support engagement, and travel with your instance through upgrades. |
| Exit | If you leave, you keep the server, the database and the data. We hand over documentation and access. Nothing is held hostage. |
A 45-minute working session on your store data — your categories, your GST profile, your counters. No slideware.