A medical robotics company in Chennai had no online store and no way to manage distributors. Elevate Aura built a custom storefront, a distributor portal with quotations and ordering, UTR payment verification, and 253 product and city landing pages across four product lines.
Medline Robotics is a medical robotics company in Chennai. Elevate Aura built its e-commerce and distributor platform: a custom storefront, a distributor portal, quotations, distributor ordering and payment verification by UTR, plus 253 product and city SEO landing pages across four product lines.
The stack is Supabase, JavaScript and Playwright, with Playwright doing the automated generation and checking that makes a page set of that size maintainable by one person.
There was no online store and no way to take orders or manage distributors for a multi-line catalogue. Enquiries arrived by phone and message, quotations were prepared one at a time, and distributors had no place of their own to see prices, place an order or check where it had reached.
The second half of the problem was discovery. A multi-line catalogue sold across many cities has a large number of genuine search queries behind it, one for each product and place combination, and none of them had a page to land on.
One platform with a public face and a partner face, and a page layer built on top of both.
Supabase holds the catalogue, the partner accounts and the orders. Playwright generates and verifies the page set, so 253 pages stay consistent without 253 manual edits.
The same 30-working-day framework used on every Elevate Aura build, adapted to a platform with a public storefront.
Scope fixed before code: which product lines, what a distributor can and cannot do, how a quotation becomes an order, and how payment is confirmed. The page architecture is decided here too, because it follows the catalogue structure.
The storefront, the portal and the ordering flow are built and shaped to the catalogue, with branding applied across both faces of the platform.
Existing product and price information is brought into the catalogue, which is also what the programmatic pages are generated from, so the store and the SEO layer never disagree.
The team learns the admin side and the distributor-facing flow, with support afterwards direct from the person who built it, on WhatsApp and in person in Chennai.
| Component | What it replaced |
|---|---|
| Custom storefront | A catalogue that could only be enquired about by phone or message |
| Distributor portal | Partners asking the office for prices, stock and order status |
| Quotation and quote-to-order flow | Quotations prepared individually and re-keyed when they became orders |
| Distributor ordering | Orders sent in as messages and entered by hand at the other end |
| UTR payment verification | Confirming bank transfers by asking and checking statements separately |
| 253 product and city pages | One site with no page for most of what buyers actually search for |
| Playwright automation | Editing and checking a large page set by hand |
The company now has two doors instead of one. The public storefront gives a buyer somewhere to arrive, read about a product and ask for a quotation without a phone call first. The distributor portal gives a partner somewhere to log in, see their own pricing, place an order and follow it, without going through the office for each step.
The workflow change in the middle is the quote-to-order path. An enquiry, a quotation and an order are now stages of the same record rather than three separate documents, which removes the re-keying step where details used to drift.
The page layer changes how buyers find the catalogue at all. Each product and city combination has its own page generated from the same catalogue data the store uses, so the two stay in step. The same approach is offered as programmatic SEO.
A custom storefront, a distributor portal, quotations, distributor ordering and payment verification by UTR, plus 253 product and city SEO landing pages across four product lines. The stack was Supabase, JavaScript and Playwright.
Because buyers search by product and by place, and each combination is a different query. Generating a page per combination from the catalogue means the site answers those queries directly instead of sending everyone to one general page.
B2B buyers in India commonly pay by bank transfer, which produces a UTR reference. The platform captures that reference against the order so payment can be confirmed against the order record rather than reconciled separately.
Yes. Orders from a portal can create sales orders and reduce stock in Aura Business, so the partner-facing side and the internal operations side work from the same records.
Yes. Storefronts, distributor portals and catalogue sites are scoped on a call and built in WordPress or on a Supabase stack depending on how much of the site is really an application. See web development.
B2B storefronts and quote-to-order.
Dealer login, pricing and ordering.
Product and city pages at scale.
The whole web service.
A 12-module operations platform.
Every project in one place.
Tell us how your business runs today and we will scope what a platform like this would look like for you, with a fixed timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it