Adobe Store Fulfillment — Walmart × Adobe Commerce
Solution Architect on the Walmart × Adobe joint venture that turned retail stores into BOPIS fulfillment centers for any Adobe Commerce merchant.
The Project
This was the flagship joint venture between Walmart Commerce Technologies and Adobe — a strategic partnership announced in 2021 to bring Walmart’s enterprise-grade store fulfillment technology to every Adobe Commerce (Magento) merchant in the United States.
The result was Store Fulfillment for Adobe Commerce by Walmart Commerce Technologies: a buy-online-pickup-in-store (BOPIS) and curbside pickup solution that transformed physical retail locations into on-demand fulfillment centers. It included a native iOS and Android Store Assist app guiding associates through Pick, Stage, and Handoff workflows — connected in real time to Adobe Commerce Inventory Management, existing POS systems, OMS, WMS, and ERP infrastructure.
Scale: 700 tickets · 79,000 lines of code · 30 contributors · 36 weeks.
Both companies are Fortune 500. Walmart ranks #1.
My Role
I was the Solution Architect at BlueAcorn iCi (Infosys) embedded on this engagement — the SA between two of the largest companies in the world and a 30-person delivery team.
That meant:
- Pre-sales and discovery — translating Walmart Commerce Technologies’ fulfillment platform requirements into an Adobe Commerce extension spec that would work across diverse merchant implementations
- Architecture decisions — defining how the extension integrated with Adobe Commerce’s Multi-Source Inventory (MSI), how it connected to Walmart’s Store Fulfillment API, and how the Store Assist mobile app communicated real-time order state changes
- Cross-organization alignment — bridging the Adobe product and engineering teams, Walmart Commerce Technologies, and the BlueAcorn delivery team through a 9-month build
- Implementation oversight — managing 30 contributors through 700 tickets without letting scope drift or integration gaps slip through to go-live
What Made It Complex
Dual Fortune 500 stakeholders. When both parties have platform opinions, enterprise security requirements, and legal review cycles, the SA role is as much diplomatic as technical. Every architectural decision had to survive scrutiny from two organizations with different priorities.
The integration surface area. The extension had to work across a wide range of Adobe Commerce configurations — different MSI setups, different OMS and WMS vendors, different POS systems. There was no single “reference implementation.” The architecture had to be genuinely flexible, not just documented as flexible.
The mobile layer. The Store Assist iOS and Android app had to maintain real-time sync with order state while operating reliably in high-traffic retail environments (poor WiFi, high device turnover, associate handoffs mid-pick). Offline resilience and conflict resolution weren’t afterthoughts — they were architectural requirements from day one.
Scale at delivery time. 700 tickets across 30 contributors over 36 weeks is a project where coordination overhead can collapse a team. Keeping the delivery tight required clear ownership at the ticket level, clear escalation paths, and an SA who could unblock both technical and stakeholder blockers quickly.
Delivery
The project shipped as a core Adobe Commerce extension available through the Adobe Commerce Marketplace. It was marketed jointly by Adobe and Walmart, included in Adobe Commerce product documentation on Adobe Experience League, and positioned as the turnkey BOPIS solution for Adobe Commerce merchants who wanted Walmart-grade fulfillment without building the infrastructure from scratch.
The extension connected Adobe Commerce natively to:
- Walmart’s Store Fulfillment API
- Adobe Commerce Multi-Source Inventory (MSI)
- Existing POS, OMS, WMS, and ERP systems
- Customer-facing email notifications (pickup confirmation, timing, curbside arrival)
What I’d Do Differently
The merchant configuration surface was wide — too many vendor combinations to fully validate at launch. I’d advocate earlier for a tighter reference implementation set with explicit “supported” vs. “community-supported” tiers from day one, rather than trying to accommodate every possible integration in scope. It would have shortened the QA tail significantly and set clearer expectations with merchant customers.
I’d also push for a dedicated mobile QA environment earlier. Real retail environments are brutal for wireless-dependent apps, and we discovered edge cases late that should have been caught in a purpose-built staging environment simulating store WiFi conditions.
Adobe discontinued the Store Fulfillment extension in February 2024. The partnership and the extension were genuine — the discontinuation reflects a strategic shift, not a delivery failure. The project shipped, it worked, and for its active period it was the only BOPIS solution of its kind available to Adobe Commerce merchants.