The big one, in final testing now. Order ops for Shopify brands: fulfilment, returns, and COD reconciliation across Indian couriers, with WhatsApp handoffs baked in. One dashboard, not five.
The problem
Running D2C ops, the biggest rupee leak I saw wasn't marketing or pricing. It was fulfilment and returns. Orders pull from Shopify, then get pushed by hand into one courier portal or another. Packages get stuck and nobody notices until the customer calls. Returns and COD reconciliation turn into spreadsheet archaeology. Every gap in that chain costs money, and the founder is the one stitching it together manually.
What I built
- Klyft solves the biggest rupee leak I saw running D2C ops: fulfilment and returns.
- It pulls orders from Shopify and pushes them through Delhivery, Bluedart, and Shiprocket in one flow, instead of three separate portals.
- WhatsApp handoffs are baked in, so customers hear about a delay before they think to ask.
- It's in final testing now.
This is the lean version of the ERP work, narrowed down to the part that actually moved money. The full story of how an everything-ERP became Klyft is its own post.
How it works
Next.js front to back. Orders flow in over the Shopify API and out through the Delhivery, Bluedart, and Shiprocket integrations, with one dashboard sitting over fulfilment, returns, and COD reconciliation. Customer-facing updates go out over WhatsApp at the moments that matter, like a delay or a dispatch.
Outcome
In final testing now, so there's nothing live to measure yet. If you run a Shopify brand shipping with Indian couriers, the full product and waitlist live at /klyft.