If your team can say it, your stock can track it.जो आपकी टीम बोल सके, वही आपका स्टॉक दर्ज कर सके।ನಿಮ್ಮ ತಂಡ ಹೇಳಬಲ್ಲದ್ದನ್ನು ನಿಮ್ಮ ದಾಸ್ತಾನು ದಾಖಲಿಸಬಲ್ಲದು.
SmartSupply turns the voice notes and WhatsApp messages your staff already send into a live, reconciling supply chain — in any language, in any industry that keeps stock, with a paper fallback for the days the network fails.
Tap a sample utterance
Sample utterances, played from synthesised speech — not recordings of real staff.
Sound familiar?
Indian hospitals run procurement on tools never designed for it. The cost is real: delayed deliveries, stock-outs, audit failures.
WhatsApp order chaos
Orders buried in group chats, no confirmation, no trail. A nurse asks for gloves and nobody knows if they were ordered.
Excel stock-outs
Storekeeper updates the sheet — maybe. By the time the ward head notices, the item is out and a patient procedure is delayed.
No audit trail
Auditor asks who approved that ₹2 lakh order. You dig through WhatsApp. You find nothing. The hospital fails compliance.
Everything your hospital needs
SmartSupply replaces the chaos with a single platform designed around how Indian hospitals actually work.
Live Stock Visibility
INV-1 protectedEvery ward sees current stock levels in real time. Confidence scoring flags items that may be inaccurate — green, amber, or red.
One-Tap Purchase Requests
Mobile-firstWard heads raise requests on their phone. Purchase managers approve with a tap. No calls, no WhatsApp, no paperwork.
Delivery Confirmation
Full / Partial / RejectStorekeeper confirms Full, Partial, or Reject. A short delivery notifies the purchase manager with the shortfall. Stock updates the moment goods are received.
Smart Notifications
Quiet hoursThe right person gets the right alert at the right time. Hospital staff are not disturbed 22:00–07:00 IST. Emergencies always get through.
Complete Audit Trail
Compliance-readyEvery request, approval, and delivery is timestamped and stored. Auditors get a clean record. Finance gets accurate PO data.
Role-Based Access
5 rolesWard Head, Storekeeper, Purchase Manager, Hospital Admin — each sees only what they need. Supplier portal included.
This is the actual product
Screenshots of the running application, not mockups. The hospital and supplier names in them are our own demo tenant seeded from a real catalogue — we have no paying customers yet, and nothing here is a customer.
A nurse asks for stock without opening WhatsApp
Pick the ward, search the catalogue, send. The request exists as a record from the moment it is raised, so nobody has to ask later whether it was ever placed.
The supplier dispatches against the order, not against a phone call
The dispatch dialog is pre-filled from the purchase order — item, quantity ordered, an optional delivery estimate. The supplier can send less than was ordered; what they enter is what the hospital is told to expect.
The loading dock gets one button, and an honest second one
Confirm All is the common case and is sized for a gloved thumb. Partial / Note sits beside it because short deliveries are normal and pretending otherwise is how a stock figure starts lying. A partial receipt drops that item’s confidence score.
Confirmed, timestamped, and off the to-do list
The delivery leaves the pending queue and joins the confirmed record with the time it was received. This is the moment the project exists for: stock updated without a spreadsheet.
And the number moves, for both sides, at the same time
Your supplier sees the shelf they are responsible for. Every row carries a confidence score, so a figure the system is unsure about says so instead of looking as solid as one that was counted this morning.
Step 02, the approval, is missing from this tour on purpose. The purchase manager approves the request between steps 01 and 03, and that screen works — but every screenshot we hold of it shows a light panel inside the dark app, a layout defect we have logged and not yet fixed. We would rather show you four screens and this paragraph than a fifth we had touched up.
Proof, not promises
We have no customer logos to show you yet. So every claim below names the migration, policy, or build gate that makes it true. If we cannot point at it, it is not on this page.
Every stock movement and its ledger entry are written in one atomic transaction. The ledger reconciles — exactly.
migration 077 · fn_write_stock_movement() · row-locked, re-checked under lock
Every tenant-scoped query must carry its tenant filter, and row-level security enforces it in the database. A query that forgets fails the build, not the code review.
92 RLS policies · scan-invariants-v2.ts (INV-2) · runs on every deploy
Every push runs an automated cross-tenant isolation (IDOR) suite against a live staging database before code leaves the machine — authenticated as a hospital admin in one tenant, it tries to read and write another tenant’s users, orders, and stock with real tokens against real row-level security; any leak blocks the push, and it fails closed. Separately, every deploy runs a static scan that fails the build if a tenant-scoped query drops its tenant filter.
idor-isolation.integration.test.ts + gate:isolation
Consent-first WhatsApp messaging, with quiet hours and erasure on request. No data export yet — that one we have not built.
migration 055 consent_records · quiet-hours.ts (22:00–07:00 IST) · DPDP §12 erasure endpoint
SOC 2 and ISO 27001: not yet — on the roadmap. We’d rather tell you that than pretend.
no certificate to link — that is the claim
From request to delivery in 4 steps
Every role gets a purpose-built view. No one sees more than they need. Everything is tracked automatically.
Raises a purchase request
ICU Surgical Kit — 50 units needed by Friday
Reviews and approves
Approved ₹12,500 · appears in the supplier’s queue
Receives order, dispatches
Order dispatched · ETA Thursday
Confirms delivery
50/50 units received · Stock updated live
Enough to decide with
What it takes out of your week, what it would ask of you, what it will not do, and who should not bother. The last two panels are the ones we would want to read first.
What it replaces
Four things stop being someone’s memory
- The WhatsApp group as the place a request officially exists. The group can stay — this is a WhatsApp-first product and your team keeps the app they already use. What moves is the record: the request lives in the system, not in a scroll.
- The Excel stock sheet as the number people trust. Stock moves when goods move, and each figure carries a confidence score so an uncertain number looks uncertain.
- The paper challan file as the audit answer. Who ordered, who approved, what arrived and when are one timestamped chain a finance or accreditation auditor can be walked through.
- The phone call asking whether it was dispatched. Both sides look at the same order and see the same status.
If you say yes
What the first week would look like
Stated in the conditional, because no hospital has run it yet — you would be our first, and that is the single most important fact on this page. Here is the order we would work in, so you can hold us to it.
- Your catalogue goes in first — the items you actually order, with your SKUs and units, not a generic list you have to correct.
- One ward and one supplier go live before anything else. A narrow first loop is easier to fix and easier to abandon if it is wrong.
- The storekeeper is the person we train, because the delivery confirmation is the step the whole ledger hangs on. Everyone else’s screen is a queue; theirs is the one that writes.
- The WhatsApp group keeps running in parallel the whole time. We do not ask anyone to switch off the fallback while the new thing is unproven.
- At the end you compare the ledger against the shelf yourself. If the two disagree, we have not earned the second ward.
What it does not do
The honest gaps
Extending the card above, which says SOC 2 and ISO 27001 are not yet held. The rest of the list is the same kind of sentence.
- It does not run a tender. An order goes to the supplier attached to the product. Comparing three suppliers on price is later work, and it is waiting on a business rule about who wins, not on code.
- There is no data export for an individual’s own record yet — we have not built it. Procurement CSV reports exist; a data principal’s copy of their personal data does not.
- It is not your accounting system. It produces purchase orders and reports; it does not post entries to your books.
- It speaks English, Hindi and Kannada. Three languages, and that is the whole list — if your staff work in a fourth, the screens will not be in it.
- SOC 2 and ISO 27001: not yet, and no third-party audit has been done. We would rather write that here than let you find out during procurement review.
Who it is not for
Reasons to close this tab
A demo that ends in a polite no wastes your afternoon and ours. If you are one of these, we would rather you knew now.
- A hospital whose ERP already has a procurement module that people actually use. Replacing something that works is a worse trade than it looks.
- A practice with no receiving point — no storekeeper, no loading dock, nobody whose job includes signing for a delivery. The loop has nowhere to close.
- Anyone who needs a certificate on file before a pilot can start. We do not have one to send you.
- Anyone who cannot be first. We have no reference hospital to introduce you to, nothing written up about a previous rollout to forward, and nobody else using this you could call. That is a real reason to wait, and it will stay true until it isn’t.
Ready to replace WhatsApp procurement?
Book a free 30-minute demo with our team. We'll walk you through SmartSupply on your hospital's device and answer every question. No commitment required.
- Live demo tailored to your hospital size
- Setup and onboarding included — no IT team needed
- Free pilot for the first 30 days
Book your free demo
We'll reach out within 24 hours
By submitting, you agree to our Privacy Policy. No spam, ever.