For the merchant
Sell without living inside every chat.
- Stock truth on site and WhatsApp
- GST invoices
- Holds that do not double-sell
Storefront and order layer
A storefront that can tell the truth about the product — and the order.
Catalogue, WhatsApp selling, order status and returns, grounded in live inventory. Fashion, grocery, electronics, craft, wholesale — if you sell a SKU, the site and the chat should share a count.
Built for D2C brands, retailers, marketplaces-in-miniature and catalogue businesses.
Scope this with usThe problem
Shoppers abandon when a question about size, stock or spec sits unanswered. Post-purchase ‘where is my order’ buries the desk. A piece gets double-sold because the site and WhatsApp do not share a count.
In practice
A shopper asks whether it is in stock, what the spec actually is, and when it would arrive. The layer answers from the product record, checks that this SKU is still unsold, and explains the return window — or hands a high-value consult to a human with the order already open.
One
Count across site and WhatsApp
A sold SKU stays sold
Grounded
Product answers
From the record, not a generic FAQ
Down
WISMO load
Status from the order, not the inbox
Human
High-value consults
Custom, wholesale and exceptions still reach a person
The shift
From a pretty catalogue to a desk that can sell and stand behind it
From this
- ✕A brochure site with no stock truth.
- ✕WhatsApp selling on a personal number.
- ✕‘Is this actually in stock?’ answered differently every time.
- ✕Double-sold SKUs — unique pieces or the last size.
- ✕Where-is-my-order as the whole support queue.
- ✕Returns policy in a PDF nobody opens.
To this
- ✓PDP and chat reading the same inventory.
- ✓A house WhatsApp number with the order attached.
- ✓Specs and care from the product record.
- ✓Holds that actually hold.
- ✓Shipment status from the courier, in the thread.
- ✓Returns inside policy; exceptions with the order open.
What's included
Catalogue, conversation, and the back office
Catalogue with real specs
The fields that matter for what you sell — variants, materials, care, warranty. The PDP is evidence, not adjectives.
Inventory that matches how you stock
Repeatable SKUs, made-to-order, or one-of-a-kind — with holds that expire.
WhatsApp selling
The number the house owns. Photos, availability, partial payments — written to the order.
Checkout and GST
UPI, cards, invoices a CA will accept. No surprise charges after the chat.
Order status
Packed, shipped, out for delivery — from the system, in the thread.
Returns and exchanges
Policy-aware. Custom, wholesale and high-value cases route to a human.
Drop and restock alerts
The list that wants the next drop, without spamming everyone.
Human consult
High-value conversations leave the bot with the SKU, budget and context attached.
Every role connected
Built around how each desk actually works
For support
WISMO leaves the queue. The hard cases still reach you.
- Order already open
- Policy on returns, not vibes
Go-live
Implementation without a year-long project
- 1
Week 1
Catalogue truth
Fields that matter for your category: variants, stock type, care, whatever the shopper actually asks.
- 2
Week 2
Site + WhatsApp
Same inventory, same holds. House number, not a personal chat.
- 3
Week 3
Orders and GST
Payment, invoice, status, the courier you actually use.
- 4
Week 4
Returns and consults
Policy, exceptions, the path that must stay human.
Example live build
One storefront we shipped — the same pattern fits any catalogue
An example, not the only category
Banaras Karigari
A Banarasi silk storefront: honest product records, checkout, and room to grow without double-selling a piece. Fashion, grocery, electronics, wholesale — your catalogue is different; the storefront-and-order layer is the same idea.
- Product pages that name materials and sourcing, not just adjectives.
- Categories and checkout that survive contact with GST and shipping.
- Built so unique pieces and later collections share one inventory truth.
- Instagram and newsletter on top of a real catalogue — not instead of one.
- Your store can be any category. This is one live example.
Ideal for
Anyone selling a catalogue who needs the site and WhatsApp to share a count
Deployment
Cloud storefront plus the WhatsApp number the house owns
Commercials
Scoped per catalogue complexity — unique pieces vs repeatable SKUs
How we approach it
- 1
We connect catalogue, inventory and orders so pre-sale answers and post-sale status are the same truth.
- 2
Each product carries the fields that matter for that category — size, material, variant, care, warranty — not a generic blurb.
- 3
WhatsApp and the site share stock so a conversation cannot sell what just sold.
- 4
Returns and exchanges stay inside policy; exceptions reach a human with the order open.
FAQ
Questions about e-commerce & retail
Is this only for craft or sarees?
No. The live example is a silk storefront. The build is a storefront-and-order layer for any catalogue — fashion, grocery, electronics, wholesale, or one-of-a-kind.
Can it handle one-of-a-kind SKUs and regular stock?
Yes. Unique pieces, made-to-order, and repeatable lines — with holds, and a hard stop so WhatsApp cannot sell what the site just sold.
Will it invent a product spec?
No. Answers come from the product record. If the field is empty, it says so and routes a human.
Want the catalogue to tell the truth?
Bring a dozen SKUs — any category — and the WhatsApp that currently sells them. You leave with a written plan for storefront, holds and order status.
We’ll tell you if a platform already fits better.
