Aura Business handles a catalogue of thousands of individual instruments, the sets and kits assembled from them, the loan sets that go out to a theatre for a case and come back, and the lot and serial traceability a hospital expects you to produce on request.
A surgical instrument distributor carries far more part numbers than almost any other medical trade, and a large share of them are never sold on their own. They are members of a set: a tray of instruments and sizes that goes to a theatre together because the surgeon may need any of them. Software for this business has to model the set as a thing you own, book out, price and chase, while still holding every instrument inside it as a stock item with its own lot or serial.
The second complication is that a set comes back. It goes out on a delivery challan for a case, the used items are billed, and the tray returns to be cleaned and sterilised before it can go anywhere else. Aura Business tracks the set as stock in a location, with a movement out, a consumption record, a return and a turnaround stage, so what you can actually promise a hospital next week is a real number rather than a count of trays on a shelf.
Most of these businesses run on a catalogue spreadsheet, a challan book and the memory of whoever handles the theatre calls.
You know you own six sets. You cannot say where four of them are today or which are fit to send tomorrow.
A tray comes back short of two sizes and nobody notices until the next case, because nothing checked the set against its contents list.
The theatre note says what was implanted, the invoice follows a fortnight later, and some of it is never billed at all.
A hospital asks which lot went into a particular case, and the answer means searching a challan book.
Thousands of part numbers, similar names and many sizes, so quoting is slow and the wrong reference is picked.
Sets waiting to be cleaned and sterilised look like available stock, so two theatres are promised the same tray.
A theatre requests a set for a date; the request is logged against the hospital account with the surgeon and the case.
The set moves out of its location on a delivery challan, scanned item by item against its contents list.
After the case, the items consumed are recorded against the challan with their lot or serial numbers.
A tax invoice is raised for what was used, with the balance returned rather than billed.
The tray is received back, checked against its contents, and held in a turnaround location until it is ready to go out again.
Consumed sizes trigger reorder alerts, and a purchase order goes to the principal to make the set whole.
Workflow: The set is shown as issued with a return date, and the second request is offered the next free tray or a date after turnaround.
Result: No promise that cannot be kept.
Workflow: The return is scanned against the set contents and two sizes are missing, so a short-return note is raised on the hospital account the same day.
Result: The loss is recovered while the case is still remembered.
Workflow: Consumed items are entered against the challan on return, and the tax invoice is raised from those lines with lot numbers on it.
Result: Nothing used goes unbilled.
Workflow: The hospital asks about a specific reference; the item's movement ledger shows the goods receipt, the challan it went out on and the case it was billed against.
Result: A traceable answer instead of a search through challan books.
Sets and sizes out for a case, billed on consumption.
Large catalogues sold to hospitals and nursing homes.
Sutures, disposables and single-use items with lot control.
Holding a principal's sets in a territory.
A rate contract at head office and sets moving between sites.
Problem: A distribution business run entirely on WhatsApp and Excel.
Built: Field app, manager dashboard, GST billing and payment tracking.
Stack: React Native, Supabase, WordPress.
Problem: No online store or way to manage distributors.
Built: Storefront, distributor portal, quote-to-order and 253 SEO pages.
Stack: Supabase, JavaScript, Playwright.
Yes. The set is held as stock in a location with a contents list, while each instrument or implant inside it remains a catalogue item with its own serial or lot. Issue and return are scanned against the contents so shortages are visible immediately.
Create the hospital-side holding as its own location. Stock moved there stays yours and stays visible, movements are recorded, and consumption at the site is what triggers the invoice.
Yes. The consumed lines are recorded against the challan after the case, and the tax invoice is raised from those lines with lot or serial numbers carried onto it. The rest is received back into stock.
Use a turnaround location. A returned set is received into it and only becomes available when it is moved back to the issuable location, so sterilisation time is reflected in what you can promise.
Yes. Product lookup, barcode scanning and brand-aware catalogue records are designed for large catalogues, and quotations are built by searching the catalogue rather than typing descriptions.
The stock movement ledger holds every step from goods receipt to challan to invoice, and the audit log records who did what. That chain is what you show when a hospital asks about a specific reference.
Locations, transfers and movements.
Lot control on every line.
Goods that move before they are billed.
Fast-moving theatre stock.
Surgeons, committees and accounts.
When the sheet stops coping.
Chairs, small equipment, consumables.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it