The Challenge
Building a Connected Platform Meant Solving Across Every Layer.
Building for a brand with five product categories, a complex SAP-based back end, and an established organic search presence made this more than a standard web build.
Five distinct challenges shaped the architecture from the first conversation.
01. Finding a Platform Architecture That Could Actually Scale:
The existing Magento setup carried server and maintenance costs that were creating real limits on how quickly the brand could grow online. The real opportunity was a platform migration designed for scalability: lower operational overhead, stronger commerce capability, and the flexibility to support what Kenstar was planning.
02. Building a Shopping Experience That Works Across Every Category at Once:
A product range spanning air coolers, food preparation, cooking, fabric care, and heating appliances does not fit a single buyer journey. Designing an experience that serves every category with equal clarity, and moves customers quickly from the right product to a completed purchase, was as much an information architecture challenge as a UX one.
03. Connecting SAP and Shopify Without Leaving Any Gaps:
Kenstar runs order management and accounting on SAP. Building a Remote Function Call integration to connect SAP with Shopify, cleanly, at scale, and without requiring manual reconciliation at either end, was one of the most technically demanding requirements of the entire build.
04. Building Order Tracking Customers Could Actually Rely On:
India’s online shoppers expect real-time visibility into their orders. A custom API to deliver that visibility at every stage of fulfilment was not a feature to be added later. It was a consumer trust requirement baked into the platform architecture from the start.
05. Protecting Search Rankings Across a Complete Platform Migration:
Moving from Magento to Shopify meant migrating an entire catalogue of URLs that had already accumulated organic search equity over years. A comprehensive 301-redirect implementation was the difference between a migration that held Kenstar’s search performance and one that cost it.