A premium ceramic and sanitaryware showroom does not sell the way retail sells. The software that runs the floor has to follow walk-ins, designers, and vendor POs as one continuous journey, or it stays in the way.
By Mohammad Jamnagarwala · Simply Five Studio
A customer walks into a ceramic tiles and sanitaryware showroom in Chennai or Bengaluru on a Saturday afternoon. They have been to two other showrooms already this month. They are not buying today. They are looking. They pause in front of a series of large-format Italian tiles, take a photograph, mention the bathroom they are renovating, and ask whether the same series comes in a smaller size. The salesperson answers, notes the customer's interest, exchanges WhatsApp numbers, and watches them walk out. Three weeks later, the customer returns with their interior designer. The designer suggests two substitutions. A week after that, the customer commits to an order. The showroom places purchase orders to four different vendors to fulfil it.
This sequence is the operational reality of a premium ceramic and sanitaryware showroom. Walk-ins. Repeated visits. Designer triangulation. Vendor coordination. Slow-burn buying journeys that span weeks. Generic retail software does not know how to follow it, because the software was built for a different buying pattern.
This essay is a working specification for what showroom ERP actually needs to do. It is also a vertical answer. Founders of ceramic and sanitaryware showrooms in India keep searching for software that fits their category. The category exists. The software has to be built for it specifically, not adapted from a retail product that assumes the customer makes the decision in one visit.
Generic retail CRM and POS software, including the Indian SaaS options that pitch to showrooms, assumes a transactional buying pattern. The customer arrives, browses, selects, pays, leaves. The system captures the sale, the customer record, and enough preference data to enable a return visit.
The model works in supermarkets, in fashion chains, in electronics retail. It does not work in a premium ceramic showroom, for three specific reasons.
First, the decision is not made in the store. The buyer captures options, takes them home, consults their designer or spouse, considers the budget, returns a week later. The software has to support the considered journey, not collapse it to a single session.
Second, the catalogue depth defeats generic search. A premium showroom carries several thousand SKUs across multiple vendors. The buyer rarely knows the SKU. They know "the matte green one near the entrance" or "the wood-effect plank we saw last time". The product master has to be rich enough, and searchable enough, that the salesperson can pull up the right item from a fragment of description.
Third, the proforma is not a transaction. It is a working document that goes through rounds of revision. Generic systems treat the proforma as a draft invoice. A showroom proforma is closer to a moodboard with prices attached. It includes product images, vendor information, finish details, and pricing that the customer carries home, shares with their designer, and brings back marked up.
Retail software does none of these jobs well, not because the software is bad, but because the software is for a different category.
A purpose-built showroom ERP follows the buying journey from first walk-in to vendor purchase order, treating each stage as a structured operational record.
The walk-in is captured at first contact. Name, phone, interest area, whether a designer or contractor is involved, the items the customer noticed during the visit. The customer record persists, which means the second visit picks up where the first one ended. The salesperson opens the existing record, sees what was shown last time, and continues the conversation without making the customer repeat themselves.
The proforma is assembled from the catalogue as the customer browses. Product images, descriptions, finish details, prices, and stock status pull automatically. The PDF is brand-correct. The customer receives it by email and on WhatsApp before they leave the showroom. By the time they get home, the document is already on their phone, ready to be forwarded to their designer.
Revisions happen inside the same proforma record, with versioning. The customer comes back wanting to swap three items. The salesperson opens the prior proforma, makes the swaps, regenerates the PDF, sends it again. The earlier version is retained for reference. The customer sees a continuous conversation rather than a series of disconnected documents.
When the customer commits, the proforma converts to an order. The order's line items split automatically by vendor. Purchase orders generate to each vendor with the correct items, quantities, and delivery requirements. The salesperson does not have to remember which tile came from which supplier. The system parses the catalogue metadata and produces the POs.
This is the workflow that was built for TNCC Arkadia, the premium ceramic tiles and sanitaryware showroom in Chennai whose work is on this site. Every stage of the journey, from walk-in capture to vendor PO generation, runs through a single operational record.
The vendor coordination piece is where most showrooms feel the most acute friction, and where the operational gain from a fitted system is largest. A premium showroom carries items from a dozen or more vendors, sometimes more. Italian, Spanish, Morbi-based, North Indian sanitaryware brands, hardware accessories from yet other suppliers.
In the manual workflow, the salesperson assembles a customer proforma that itemises everything the customer wants. When the customer commits, the salesperson has to translate that single proforma into multiple vendor POs. Which of these tiles came from which series? Which series belongs to which vendor? What is the minimum order quantity? What is the lead time?
The translation is doable. It is also slow, error-prone, and the kind of work that depends on the salesperson having a clear head on the day they do it. Mistakes mean that a vendor PO is missed, the order ships incomplete, and the customer's installation date slips. For a premium customer, this is exactly the kind of friction that does not get forgiven.
The fitted system removes the translation entirely. Each catalogue item carries its vendor metadata. When the proforma converts to an order, the system groups line items by vendor and generates one PO per vendor with the correct items, quantities, and delivery schedule. The salesperson reviews and confirms. The vendor receives the PO. The order is on its way before the customer has left the showroom.
The operational saving is hours per order. The reliability gain is larger and harder to measure precisely. Orders ship complete. The customer's experience of the showroom is shaped by every interaction, and shipping complete is a much bigger driver of repeat business than any individual sales conversation.
The single feature most absent from generic showroom software is walk-in capture that treats the buying journey as a sequence of visits rather than a single transaction.
A purpose-built system creates a customer record at the first interaction, regardless of whether anything sold that day. Contact details. Interest area. Items they paused on. Whether they are buying for themselves or with a designer. Approximate timeline. Approximate budget if disclosed. The record persists. The salesperson who greets them on their next visit knows everything that was captured the last time.
The compounding effect across a year is large. A showroom that captures every walk-in develops, over twelve months, a structured customer database that includes prospects who never bought, prospects who almost bought, customers who bought once, and customers who bought repeatedly. The same data, in the generic-software case, lives in the salesperson's memory or not at all. The compounding does not happen. The showroom's institutional knowledge stays bound to whoever happens to be on the floor.
The follow-up workflow that the captured data enables is the second operational gain. A customer who was interested in a particular tile series, three months ago, but did not buy, is a warm prospect when that series goes on promotion or when the vendor adds a complementary size. The salesperson reaches out with the relevant update. The customer is reminded of the showroom at exactly the moment a purchase is more likely. None of this is possible without the captured record.
The deeper essay on why showroom buying is structurally different from retail buying is at showroom CRM is not retail CRM. The short version is that the single most important data structure in a showroom system is the customer journey, not the transaction.
A premium showroom typically carries between three and ten thousand SKUs on the floor. Each SKU is a specific finish, size, and series combination from a specific vendor. The catalogue is large enough that even an experienced salesperson cannot hold it in their head. The customer's question, "what is this tile, and is it in stock?", defaults to a manual lookup that takes minutes.
The operational shift that QR-code or barcode tagging enables is that the lookup goes away. The salesperson scans the tile. The system surfaces the SKU, the price, the stock position, the vendor, the available sizes in the same series, and adds the item to the customer's working proforma if the salesperson is in capture mode.
What this does to the floor's tempo is significant. The salesperson's attention stays on the customer, not on the lookup. Proforma assembly happens in real time as the customer walks the floor. By the time the customer reaches the seating area for the price discussion, the proforma is ready. The friction of the manual catalogue lookup, which was always the slowest part of the conversation, is gone.
The barcoding rollout itself is not trivial. Five thousand SKUs is weeks of labelling work, with adjustments to the data model to support the codes and to the system surface to support scanning. Most showrooms run it in phases, starting with the highest-velocity series. The full payoff arrives once the rollout is broad enough that scanning is the default rather than the exception.
The phase that follows barcoding is journey analytics. The system now knows, for every walk-in, exactly which items the customer paused on. Patterns emerge. Which displays attract the most attention. Which combinations of items get scanned together. Which items appear on proformas that never convert. Each pattern is a piece of decision data the founder previously had no access to.
A custom ERP for a ceramic tiles or sanitaryware showroom is not a template product. It is a system fitted to the buying journey of a considered purchase category, with multi-visit support, designer involvement, multi-vendor fulfilment, and a catalogue depth that defeats generic search.
The components are stable across showrooms in this category. Walk-in capture. Customer record with visit history. Catalogue with rich metadata. Proforma assembly with images. WhatsApp and email share from inside the system. Vendor PO auto-generation. Barcoding for floor capture. Reporting on what walks in, what sells, and what moves through the vendor pipeline.
The implementation is a fitted build, not a SaaS subscription, for the same reason every other operational system in this category is a fitted build. The workflow is specific. The catalogue is specific. The vendor relationships are specific. A product designed for general retail will deliver general retail capabilities. A showroom needs showroom capabilities, which means the system has to be built around how a premium showroom actually runs.
The investment compounds. Every captured walk-in strengthens the customer database. Every accurate proforma improves the customer experience. Every complete vendor PO shortens the next delivery cycle. The system pays for itself in operational reliability. The strategic case is that the showroom's institutional knowledge stops walking out the door when a salesperson moves on.
Generic school management software does not understand voluntary contributions, WhatsApp as the parent channel, or the relationship between a tahfeez and its community. A fitted system does.
Indian print-on-demand is artwork-heavy. The operational backbone for a 20 to 100 order-per-day shop covers capture, approval, production scheduling, and dispatch.
CA firms, tax consultancies, architects, and legal practices cost projects by hand. A one-screen calculator with the rules baked in turns 30 minutes into 30 seconds.
The contact form takes about two minutes. The reply comes from the founder within two working days.
