WhatWeBuiltAndWhyItMattered
BuildingaGroceryDeliveryPlatformwithAutomatedFulfilmentforLeMarche
How byenvigo built Le Marche's iOS and Android grocery delivery platform with automated delivery partner assignment, geo-local store selection, POS integration, and payment gateway connectivity in three months.
Context
Le Marche is a food and grocery retail chain operating under DS Group. Grocery delivery at retail scale requires a mobile platform that connects consumer ordering, store inventory, delivery partner operations, and payment processing within a single integrated system. Each of these functions involves its own operational logic, and the platform’s value depends on how reliably they work together rather than how well any individual component performs in isolation.
The complexity in grocery delivery is largely operational. Geo-local store selection, automated delivery partner assignment, POS synchronisation, and payment processing need to operate consistently and in sequence for an order to complete correctly. Platform failures in any layer affect fulfilment, not just user experience.
What Changed
Le Marche required a mobile platform that could support its grocery delivery operations across iOS and Android, with the full operational stack (order management, store selection, delivery assignment, payment, and POS integration) built and integrated within a single delivery programme.
Envigo’s Responsibility
Envigo was responsible for the iOS and Android application development, REST API architecture, automated delivery partner assignment system, geo-local store selection logic, payment gateway integration, POS integration, and the offers and discount module. Envigo owned all platform architecture and integration decisions.
Strategic Decisions
Decision 1: Design the REST API as the integration layer across all operational systems
The platform required connectivity between the consumer application, store management, delivery partner systems, payment gateway, and POS infrastructure. Envigo chose to design the REST API as the central integration layer through which all systems communicated rather than building direct point-to-point connections between individual components. Point-to-point integrations were rejected because they create a brittle architecture in which any system change requires updates to multiple connections simultaneously.
Decision 2: Automate delivery partner assignment
Manual delivery dispatch introduces delays and inconsistency that are operationally unacceptable in grocery delivery, where fulfilment speed is a competitive requirement. Envigo built an automated assignment system that matched orders to available delivery partners based on defined operational parameters. A manual workflow was rejected because it would not scale with order volume and would introduce human error into a time-sensitive operational process.
Decision 3: Implement geo-local store selection to route orders to operationally correct locations
Grocery delivery depends on matching a customer’s order to a store that is both geographically proximate and operationally capable of fulfilling it. Envigo built geo-local store selection logic that identified the appropriate store automatically based on the customer’s location. The alternative, a customer-selected store model, was rejected because it placed operational routing decisions with consumers rather than with the system, increasing the likelihood of fulfilment errors from orders routed to the wrong location.
System Design
The platform was built so that the consumer-facing application, store operations, delivery management, and payment processing operated as an integrated system rather than independent components. The REST API ensured that data flowed consistently between all layers. Automated delivery assignment and geo-local store selection removed manual decision points from the fulfilment chain. POS integration ensured that order data was reflected in store inventory management without requiring separate data entry.
Outcomes
The platform was delivered in three months across iOS and Android, with grocery delivery operations, automated delivery partner assignment, geo-local store selection, POS integration, and payment gateway integration within a single architecture.
Closing Reflection
Operational complexity in retail delivery is most reliably managed at the architecture level. Platforms built around a central integration layer, with automation removing manual decision points from the fulfilment chain, produce more consistent operational outcomes than platforms assembled from individually capable but loosely connected components.