Integrating 300+ stores for V2 Retail to deliver a seamless omnichannel experience to their customers

We built the customer-facing storefront on a unified commerce platform engineered as a single system rather than a plugin stack.

The performance decision mattered here: V2 Retail’s target customers in tier-2 and tier-3 cities shop predominantly on mid-range Android devices over mobile data connections.

A higher load time would kill conversion before a customer ever saw a product. We designed a CDN-first, sub-1-second architecture for exactly this context.

The platform delivers sub-1-second page load times through a global CDN and intelligent caching, ensuring a seamless experience for mobile-first users on bandwidth-constrained networks.

It supports native UPI, COD, and card payments via Razorpay and PhonePe, eliminating dependency on third-party plugins and avoiding additional latency.

To scale catalogue management, the system uses AI-generated product descriptions and metadata, removing the need for manual cataloguing across thousands of fashion SKUs. It also enables smart collections that dynamically group inventory by season, occasion, and trends; for example, ‘Festive Kurtis’ or ‘Monsoon Casuals’.

The platform enables automated customer acquisition through Meta and Google Dynamic Product Ads (DPA), where campaigns pull live inventory for real-time retargeting.

It extends the product catalogue natively to social channels through WhatsApp Commerce and Instagram Shop integrations, allowing customers to discover and engage across multiple touchpoints.

To improve conversion and retention, the system incorporates a smart cart with abandoned cart recovery, prepaid discount nudges, and COD-to-prepaid conversion incentives.

It further supports RFM-based segmentation, enabling automated loyalty programs and review collection workflows to drive repeat purchases and long-term customer engagement.

A Store-Led Fulfilment Architecture was the most architecturally significant decision of the engagement. Rather than routing all online orders through a central warehouse, we designed three complementary fulfilment models that treated the store network itself as the fulfilment infrastructure.

Nearest Store Allocation

When a customer places an order, the system identifies the store with available inventory closest to the delivery pin code and routes the order to that store. This reduces last-mile logistics costs and delivery time, critical for a value fashion brand with thin margins.

BOPIS

Buy Online, Pick Up In Store. Customers browse online, purchase digitally, and pick up at their nearest V2 Retail location. With 300+ stores, BOPIS is a genuine competitive advantage that no D2C-only brand can match.

Hub Fulfilment

For regions with multiple nearby stores, designated hub stores handle consolidated fulfilment for surrounding locations, reducing per-order handling complexity while maintaining the distributed inventory model.

The 15–30-minute SAP sync lag was the most dangerous technical risk on the project. An e-commerce platform that shows ‘Available’ when a store has already sold the last unit offline creates a failed order and a damaged customer relationship. We designed the inventory layer to be lag-tolerant by default.

The system ensures inventory accuracy through a buffer-based visibility mechanism, where online stock availability is calculated using a configurable safety buffer. This prevents the last unit from being sold online while offline transactions are still pending synchronization.

To further reduce inconsistencies, a real-time reservation layer is implemented: when a customer places an order, the item is immediately soft-reserved at the application layer before the SAP sync cycle completes, eliminating the risk of double-selling.

In cases where conflicts arise, such as an offline sale consuming a reserved unit, the system automatically resolves this through dynamic reassignment to the next-nearest store with available inventory.

It also incorporates graceful degradation, where inventory data that becomes stale beyond a defined threshold is temporarily hidden from the storefront rather than displayed with uncertain accuracy. All inventory operations are routed through a dedicated API integration layer, ensuring that e-commerce reads and writes remain isolated while preserving the stability of core SAP ERP workflows.

Headquarters needed visibility, and store staff needed execution tools. We addressed these two needs through a paired OMS admin dashboard and a dedicated Android store application. We built a real-time order management system for distributed operations that provides order lifecycle tracking across four status tabs: New, Pickup, Shipment, and Return. It enables COD management with delivery attempt tracking and daily reconciliation, along with store-wise order volume and fulfilment rate dashboards that identify bottlenecks at specific locations in real time. The system also supports return and exchange management with automated refund triggers and includes a courier integration dashboard that tracks dispatch status for each shipment.

Store staff had no tools to action online orders before this engagement. We built a purpose-designed Android application giving store associates a structured, scan-validated workflow from order receipt to handover. The app provides a structured picking list with product name, SKU, size, and quantity, eliminating manual interpretation. Each picked item is validated through barcode or QR code scanning before packing to prevent dispatch errors. It maintains clear separation between picked and packed stages with timestamp logging at each step. The application also generates a courier handover confirmation linked to the courier’s scanning system, closing the fulfilment loop. For BOPIS, it supports in-store pickup confirmation where staff verify the customer and mark the order as collected, triggering automatic closure.