Technical Notes · Dashboard

The Razorpay, order, and inventory loop

How ecommerce payments should connect to fulfilment without exposing private keys or losing stock discipline.

3 Jun 2026
The Razorpay, order, and inventory loop field evidence

Razorpay is not just a payment button. In a serious ecommerce workflow, the server creates the order, the customer pays through Razorpay Checkout, and the backend verifies the payment signature before marking an order as paid.

For Amrit Dhara, that payment status should then connect to inventory: incense cones, sambrani cups, the one-and-one combo, and the two-cone two-cup family ritual pack. Paid orders should reserve stock. Failed or pending orders should not quietly reduce inventory.

The public customer experience can stay simple: choose product, pay securely, receive confirmation. Behind it, the command dashboard should show payment status, fulfilment status, product drawdown, and any failed verification.

The most important rule is security. Razorpay key secrets belong on the server, never in browser code. Test mode can validate flow, but live mode needs final approval, webhook configuration, and real payment verification.

From Water Testing to Waste Prevention field evidence

Founder Notes

From Water Testing to Waste Prevention

Moulik's founder-journal story: how water-quality research led him from testing polluted water to preventing sacred offering waste at the source.

20 Jun 2026
Lessons from Har Ki Pauri Awareness Drives field evidence

Founder Notes

Lessons from Har Ki Pauri Awareness Drives

What field conversations around Har Ki Pauri taught the team about devotion, behaviour change, collection discipline, and public trust.

19 Jun 2026