The situation
Oorja Devotion sells devotional products and ritual services to a culturally specific audience in India and abroad. Standard ecommerce could handle the products. It could not handle a cart that includes a booking for a priest's time next Thursday morning, in two different languages, with payment settling across UPI, cards, net banking and wallets.
What we did
The commerce engine treats a scheduled service as a product type, not an afterthought. The catalogue holds both SKUs and bookable slots in one shape. The cart can hold both at once. Checkout handles both in one transaction.
A scheduling layer that respects practitioner availability and the auspicious timing constraints the business works within. A cart adding a slot has to see what is actually bookable, not just what the calendar is empty on.
Multilingual content with proper script rendering, and a content model that lets the content team publish without engineering help.
Payment integration across the Indian payment stack: UPI, cards, net banking, wallets. Each rail has its own failure modes, and the platform handles the partial failures those rails produce rather than treating a timeout as a success.
Inventory synchronisation, order management and fulfilment tracking in one system.
A customer account showing order history, upcoming bookings and recurring subscriptions in one view, so a customer never has to log into two tools to see what they bought from the same brand.
The shape of it
Two to three engineers from MVP through launch and into ongoing support.
The outcome
A single platform where the business used to run an ecommerce tool and a parallel manual booking process, with the overhead of the manual half removed.