Every channel has its own stock figure
Own site, two marketplaces, three stores. The moment they disagree you are either overselling or holding back sellable stock.
Retail & E-commerce
Retail and e-commerce software, where the stock count is actually right
D2C storefronts, omnichannel POS, distributor ordering portals and marketplaces. Built around one inventory truth, with GST and logistics wired in from the start.
5 solution blueprints
19 systems we integrate
10–24 weeks, typical build
The starting point
What is usually broken before we arrive
Oversell costs more than the order
A cancelled marketplace order damages the seller rating. That costs future orders long after the refund is done.
Nobody chases the settlement gap
Marketplace and gateway payouts arrive in different formats on different cycles. Differences get written off because tracing them takes longer than they are worth.
In plain terms
Retail software development covers what a retailer or brand sells through and runs on. Online storefronts, point of sale in stores, inventory and warehouse management, order management across channels. Plus the payment, logistics and accounting integrations that turn an order into a delivered, invoiced, reconciled transaction.
Almost every retail software problem is an inventory problem wearing a disguise. Stock counted in six places will eventually disagree, and then you are cancelling orders or sitting on stock you could have sold.
The second problem is that the sale is only the start. An order becomes a picked shipment, a GST invoice with the right place of supply, a tracking number, a delivery confirmation, then a settlement line. Retailers rarely lose money at the till. They lose it in returns and settlement gaps.
So we build order management and inventory as the centre. A good storefront on a broken order system just produces angry customers faster. Once one system owns stock and order state, every channel becomes a way into the same truth.
What we build
Retail & E-commerce systems, and who builds each one
Every card links to the practice that does the work. Follow one if you want the detail.
D2C storefronts and headless commerce
Fast, search-friendly storefronts with product, variant and bundle handling. Headless, so one catalogue serves web, app and marketplace.
ExploreInventory and order management
One stock ledger across warehouses, stores and channels. Allocation rules, reservations, transfers and cycle counts, so the site shows what exists.
ExplorePOS and omnichannel retail
Billing counters that keep working offline, loyalty recognised across stores and online, and buy-online-pickup-in-store handled as one order.
ExploreB2B distributor and dealer portals
Price lists per customer tier, credit limits and outstanding visibility, schemes and slab discounts, and reorder built for somebody ordering weekly.
ExploreDemand forecasting and replenishment
SKU-level forecasts using seasonality and promotion history, turned into reorder points and purchase suggestions instead of a chart nobody acts on.
ExplorePerformance marketing and catalogue feeds
Google Merchant Center and Meta catalogues kept in sync with live stock and price. Campaigns judged on margin after returns, not on ROAS.
ExploreAI search, recommendations and support
Search that understands how customers describe products, recommendations from real basket behaviour, and assistants handling returns within policy.
Explore Solution blueprints
Open one and see exactly what gets built
The situation it answers, the architecture, every module, the systems it plugs into and how long it takes. These describe our work, not one client's project. Named clients with measured results are in the case studies.
01 D2C headless storefront 10–14 weeks
The situation
A brand selling on marketplaces that wants its own channel, better margin and a direct customer relationship. The catalogue has variants, bundles and frequent promotions. Marketing needs to launch campaign pages without waiting for a developer.
How it is built
A headless commerce backend holds catalogue, pricing and orders. An Astro or Next.js storefront renders statically wherever possible, for speed and search. Content and campaign pages come from a headless CMS, so marketing ships them alone.
Rules it has to follow
Invoices carry the correct place of supply and HSN codes, raised through the NIC IRP where turnover requires it. Return and refund timelines are stated on the product page under e-commerce consumer protection rules.
Modules 12
- Catalogue with variants, bundles and kits
- Price lists, promotions and coupon engine
- Search and faceted navigation
- Cart, checkout and abandoned-cart recovery
- Payment with UPI, cards, netbanking and cash on delivery
- Serviceability and delivery-estimate by pincode
- GST-compliant invoicing with correct place of supply
- Shipping label generation and tracking
- Returns, exchange and refund workflow
- Loyalty and referral programme
- Customer accounts with order and return history
- Campaign landing pages from the CMS
Plugs into
- Razorpay
- Shiprocket
- Delhivery
- GST e-invoicing (NIC IRP)
- Google Merchant Center
- Meta Catalog
02 Omnichannel POS with inventory sync 14–18 weeks
The situation
A retailer with several stores and an online channel, where each store runs its own billing software and stock is counted per location. Online orders cannot pull from store stock. A customer cannot return in a different store. Head office sees consolidated numbers after month end.
How it is built
An offline-capable POS built local-first. It queues transactions and syncs to a central order and inventory service, with conflict handling for stock movements recorded on both sides during a disconnect.
Rules it has to follow
Each store bills under the correct GSTIN with the right state tax treatment, and interstate stock transfers are documented as required. Cash is recorded per shift down to denomination, which makes a till difference traceable.
Modules 12
- Offline-capable billing counter with queued sync
- Central item, price and promotion master
- Store-level stock with transfer and receipt workflow
- Serial and batch tracking where the category needs it
- Cross-store returns and exchanges
- Ship-from-store and pickup-in-store fulfilment
- Unified loyalty across stores and online
- Cashier shift open, close and cash denomination
- Barcode and label printing
- Cycle counting and variance approval
- Store-wise sales, margin and footfall reporting
- Head-office price and promotion push
Plugs into
- Tally ERP
- GST e-invoicing (NIC IRP)
- Razorpay POS terminals
- Unicommerce
- GS1 barcode standards
03 B2B distributor ordering portal 12–16 weeks
The situation
A manufacturer or importer selling through distributors and retailers. Orders arrive by phone and WhatsApp. Prices differ by customer tier and region. The sales team spends its week confirming stock and outstanding balances instead of selling.
How it is built
A React portal and an Android app for field sales, on an order service that resolves customer-specific pricing, credit limits and scheme eligibility at the point of order. Nothing waits for a later approval step.
Rules it has to follow
E-way bills are generated for consignments over the value threshold, with vehicle and transporter details captured at dispatch. Credit notes for scheme claims follow the GST treatment for post-sale discounts.
Modules 12
- Customer tiers with contracted price lists
- Credit limit, outstanding and overdue blocking
- Scheme, slab and quantity-discount engine
- Live stock visibility by warehouse
- Quick reorder from purchase history
- Order approval workflow for exceptions
- Dispatch planning and part-shipment handling
- e-Way bill generation for qualifying consignments
- Field sales app with beat plan and visit capture
- Claims, returns and credit note handling
- Ledger and statement of account for each buyer
- Territory and sales-representative performance reporting
Plugs into
- Tally ERP
- GST e-way bill (NIC)
- GST e-invoicing (NIC IRP)
- Razorpay payment links
- WhatsApp Business API
04 Multi-vendor marketplace 18–24 weeks
The situation
An operator building a category marketplace where independent sellers list and fulfil their own stock. The hard parts are seller quality, catalogue consistency when several sellers list the same product, and settlement sellers trust enough to keep listing.
How it is built
The catalogue service separates the product from the seller offer, so several sellers compete on one product page instead of creating duplicate listings. A settlement engine computes commission, shipping recovery and returns per order line.
Rules it has to follow
Seller settlement runs through split settlement on a licensed payment aggregator, never a pooled operator account. Seller identity, GSTIN and grievance officer details are held and displayed as e-commerce rules require.
Modules 12
- Seller onboarding with GSTIN and bank verification
- Product catalogue with seller offers and buy-box logic
- Bulk listing upload with validation and error reporting
- Seller-level inventory and dispatch SLA tracking
- Order routing and split shipment handling
- Commission, shipping and payment-charge computation
- Returns, refund and seller chargeback workflow
- Seller settlement statements and payout scheduling
- Rating, penalty and delisting rules
- Dispute and grievance resolution tracking
- ONDC protocol adapter for network orders
- Category and seller performance reporting
Plugs into
- ONDC network protocol
- Razorpay Route
- Shiprocket
- GST e-invoicing (NIC IRP)
- Algolia search
05 Retail analytics and demand forecasting 10–14 weeks
The situation
A retailer buying from last season sales pulled into a spreadsheet, with no view of which SKUs tie up working capital and which went out of stock during their best week. Season-end markdowns are the recurring symptom.
How it is built
A warehouse consolidates POS, e-commerce, marketplace and purchase data nightly, modelled to SKU-store-day grain. Forecasting models feed reorder suggestions back into the ordering workflow instead of stopping at a report.
Rules it has to follow
Marketplace settlement data is reconciled against invoiced sales, so GST returns are filed against what was actually settled. Return credit notes match the original invoice instead of being adjusted in aggregate.
Modules 12
- Unified sales fact across store, web and marketplace
- SKU-store-day demand model with seasonality
- Promotion-effect separation from base demand
- Stock-out detection and lost-sale estimation
- Reorder point and safety stock computation
- Purchase suggestion feeding the ordering system
- Ageing, slow-mover and dead-stock reporting
- Margin analysis after returns and marketing cost
- Marketplace settlement reconciliation
- Category, brand and store performance views
- Return-reason analysis by SKU and channel
- Scheduled distribution to buyers and store managers
Plugs into
- Unicommerce
- Marketplace settlement reports
- Power BI Service
- Tally ERP
- Zoho Inventory
Regulation
What retail software has to comply with in India
Get these wrong and the build is not late, it is unusable. They are design inputs on day one.
GST e-invoicing and e-way bill
Above the notified turnover, invoices must go through the NIC Invoice Registration Portal and get an IRN before they are valid. Consignments over the value threshold need an e-way bill with transporter and vehicle details. Both work far better generated at billing or dispatch than reconciled later.
Place of supply and HSN
Interstate and intrastate orders attract different tax components, and place of supply follows the delivery address, not billing convenience. Getting it wrong is quiet. It surfaces at return filing, by which point hundreds of invoices need correcting.
ONDC network protocol
Selling on the Open Network for Digital Commerce means implementing the network catalogue, order, fulfilment and issue-resolution flows. Build the catalogue and order model to that structure from the start and joining is configuration. A bespoke model means a rebuild.
E-commerce consumer protection rules
Seller identity, country of origin, return and refund policy, and grievance officer details must be displayed, and stated cancellation timelines honoured. These are workflow requirements, so they belong in the product data model, not a policy page nobody updates.
Payment aggregator settlement
A marketplace collecting for sellers cannot hold those funds in its own account. Split settlement through a licensed payment aggregator is the compliant route, and it changes how the order ledger and payout cycle get designed.
Why Naryon Tech
How we approach retail projects
- One stock truth, then channelsWe build the inventory and order core first, then treat storefront, POS and marketplace as channels into it. That is what stops overselling, and why adding the next channel takes a week.
- Storefronts built for speed and searchStatic rendering where the page allows it, images sized and served in modern formats, structured data on products. Slow retail pages lose the sale before it starts.
- GST handled at the transactionPlace of supply, HSN, e-invoicing and e-way bills are resolved when the invoice is raised. Filing then reads from what happened instead of from a correction exercise.
- Margin after returns, not gross salesReporting nets out returns, shipping, payment charges and marketing spend. Gross order value is the number that hides a channel losing money on every sale.
Tooling
What we build retail systems with
Storefront
- Astro
- Next.js
- React
- Headless CMS
Commerce core
- Node.js
- PostgreSQL
- Redis
- Medusa
- Elasticsearch
Retail operations
- Offline-first POS
- GS1 barcodes
- Unicommerce
- Tally ERP
Growth
- Google Merchant Center
- Meta Catalog
- GA4
- Power BI
Working from Chennai and Trichy, with clients in
- Chennai
- Tiruchirappalli (Trichy)
- Coimbatore
- Madurai
- Salem
- Erode
- Tirunelveli
- Vellore
- Tiruppur
- Puducherry
Straight answers
Retail & E-commerce: what people ask us first
Should we build custom or use Shopify or WooCommerce?
If the catalogue is straightforward and you sell through one channel, a platform is usually right and we will say so. Custom earns its cost in three cases. Inventory shared across stores and marketplaces. B2B pricing and credit rules the platform cannot model. A checkout that must behave in a way the platform forbids.
How do you stop overselling across marketplaces?
One stock ledger owns the true quantity. Each channel gets an allocation instead of the full figure, with reservations held from the moment an order is placed. Channel updates push on every movement instead of a periodic sync, and a per-SKU buffer is configurable where a cancellation costs more than a missed sale.
Can you integrate with Tally and our accounting?
Yes. Sales invoices, credit notes, purchases and stock movements post to Tally on a schedule, with a reconciliation report showing anything that did not transfer. If your accounting system is something else, the pattern is the same. The operational system stays the source of truth and posts summarised entries.
What does ONDC readiness actually require?
Modelling the catalogue, order lifecycle, fulfilment states and issue resolution the way the network specifies, then writing the protocol adapter and completing onboarding. Building the underlying model that way costs nothing extra during a fresh build, so we default to it whether or not you plan to join.
How long does a D2C storefront take?
Ten to fourteen weeks for catalogue, checkout, payments, logistics, GST invoicing and returns. Shorter if you stay on a platform and we build the front end and integrations only. The timeline usually moves for content and photography, not engineering, so starting catalogue work in parallel is worth the coordination.
Does the POS keep working if the store internet drops?
Yes. Billing runs locally and queues transactions, syncing when the connection returns, because a store cannot stop billing. Stock movements made offline reconcile on reconnect with conflict handling. The shift close is computed locally, so a disconnected day still balances.
Close to this
Related industries
Building something for retail?
Tell us the workflow that keeps breaking. We will say honestly whether software fixes it, and what it would take.