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.
Commerce + ritual bookings · one platform
01
Products + bookings in one cart
SKUs and bookable slots in one shape
02
Scheduling that respects context
Practitioner availability · auspicious timing
03
Multilingual, team-published
Content team ships without engineers
04
Payments across Indian options
UPI · cards · net banking · wallets
05
One account view
Orders · bookings · subscriptions, together
One tool where there used to be two
What we did
The commerce engine treats a scheduled service as a product type, not an afterthought. One catalogue, one cart, one checkout handling physical products and bookable slots together.
Scheduling that respects practitioner availability and the auspicious timing constraints the business works within. Multilingual content the content team publishes without engineering help. Payments across the Indian options (UPI, cards, net banking, wallets), with each one's quirks and partial failures handled properly rather than ignored.
A customer account showing order history, upcoming bookings and recurring subscriptions in one view. Nobody logs 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.