The posting
Fynd is a frontier technology company. We started at the intersection of technology and retail because that is where technology was the least available. Over the years, we became one of India’s largest retail technology platforms. But retail was the entry point, not the boundary.
Today, Fynd builds intelligent software that runs business operations. Not tools that help people work faster, but systems that absorb entire functions: manufacturing, marketing, logistics, commerce, quality control. We sit inside our customers’ businesses, harvest deep domain context, and build AI systems that operate autonomously. We are expanding from retail into manufacturing, generative media, physical AI, and healthcare.
We are an AI-native unified commerce platform backed by Reliance Retail. We power OMS, POS, Storefront, Clienteling, Supply Chain (WMS, TMS, RFID), and AI tools for enterprise retailers across 30+ countries, working with leading retailers and brands across the Middle East, Africa, and Southeast Asia.
About the Role
Fynd has built its own ERP — Fynd ERP — as part of our unified commerce platform. We’re hiring an ERP Solution Architect whose primary charter is to own the deployment and rollout of Fynd ERP for our customers, end to end. Because most enterprises we work with already run on SAP or Microsoft Dynamics 365 (D365), this person also needs to deeply understand both platforms — their modules, data models, and integration surfaces — well enough to:
- Architect and build integrations between Fynd ERP and SAP/D365 (or specific modules within them) wherever a customer needs their existing ERP to coexist with Fynd ERP rather than be replaced outright.
- Understand a customer’s existing SAP or D365 implementation in depth — their configuration, customizations, master data, and process flows — so we can correctly scope what Fynd ERP will own, what stays on the legacy ERP, and how the two will talk to each other.
- Bring that SAP/D365 experience back into Fynd ERP itself — using firsthand knowledge of how SAP and D365 solve a given problem to identify gaps, propose enhancements, and help shape Fynd ERP’s own roadmap so it holds up against the platforms our customers are used to.
In short: this person deploys Fynd ERP, uses their SAP/D365 depth as the tool that makes that deployment succeed inside real, messy, already-SAP-or-D365-running enterprises, and feeds what they’ve learned on those platforms back into making Fynd ERP itself better — spanning commerce and supply chain systems in particular.
This is not a role for someone who has only briefly touched SAP or D365. We need someone who has genuinely operated at the level of an SAP Solution Architect or D365 Solution Architect — someone who has led full-lifecycle implementations, speaks the terminology fluently, and understands what “good” looks like on those platforms — because that’s the bar our customers’ own SAP/D365 architects will hold us to.
Mindset & Working Style
Beyond the platform depth, we’re specifically looking for someone who is:
- Hands-on, not just advisory: Someone who will get into the configuration, the code, the API payloads, and the data — not just draw architecture diagrams and hand them off.
- AI-first: Someone who instinctively reaches for AI/LLM-based approaches to speed up ERP work — data mapping, code generation, documentation, testing, migration scripting — rather than doing everything the traditional, manual ERP consulting way.
- Genuinely enthusiastic about pushing boundaries: Someone who gets energized by “how do we do this better/faster/differently” rather than defaulting to how SAP or D365 implementations have always been done.
- Equally comfortable in the ERP world and the open-source world: Traditional ERP work (SAP/D365, proprietary tooling, enterprise integration patterns) tends to live in a different universe from open-source engineering culture (GitHubnative workflows, open APIs, community tooling, modern dev stacks). We need someone who can move fluidly between both — bringing open-source speed and pragmatism into ERP work, and enterprise rigor into how we build Fynd ERP.
What You’ll Do
Fynd ERP Deployment (Primary Responsibility)
- Own end-to-end deployment of Fynd ERP for customers — discovery, solution design, configuration, data migration, integration, testing, go-live, and hypercare.
- Translate customer business processes (commerce, supply chain, finance, inventory) into Fynd ERP configuration and, where needed, custom extensions.
- Define the “system of record” boundary for each engagement — which processes and data live in Fynd ERP vs. the customer’s existing SAP/D365 estate.
- Act as the primary technical/architectural point of contact for customers during Fynd ERP rollouts.
SAP & D365 Integration Depth
- Architect and build integrations between Fynd ERP and SAP (ECC/S4HANA) or D365 (F&O/Business Central) — using APIs, IDocs/BAPIs/RFCs on the SAP side, Data Entities/AIF/DMF on the D365 side, and middleware/iPaaS tools as needed.
- Design integration patterns for the specific modules most likely to be in scope: SAP FI/CO, MM, SD, WM/EWM; D365 Finance, Supply Chain Management, Business Central.
- Ensure master data consistency (SKUs, customers, vendors, pricing, inventory) flows correctly and reliably between Fynd ERP and the customer’s SAP/D365 environment.
- Design for event-driven, real-time, or batch integration depending on the customer’s SAP/D365 landscape (on-prem ECC vs. S/4HANA Cloud, D365 on-prem vs. cloud).
Understanding the Customer’s SAP/D365 Landscape
- Perform in-depth technical discovery of a customer’s existing SAP or D365 implementation — configuration, RICEFW customizations, integration points, data model, and known technical debt.
- Speak fluently in SAP/D365 terminology and process language (e.g., SAP Activate methodology, Clean Core/BTP extensibility, S/4HANA migration paths; D365’s Data Management Framework, Power Platform extensibility) so that customer-side SAP/D365 architects treat you as a peer, not a vendor rep.
- Identify risks, gaps, and dependencies in the customer’s current ERP setup that will affect the Fynd ERP deployment.
- Advise customers on brownfield vs. greenfield approaches where Fynd ERP is being introduced alongside or in place of parts of SAP/D365.
Cross-Cutting
- Set integration and architecture standards across engagements so patterns are reusable rather than reinvented per customer.
- Work closely with Fynd ERP product and engineering teams to feed back real-world SAP/D365 integration requirements into the product roadmap.
- Use prior hands-on experience with SAP and D365 to identify capability gaps in Fynd ERP and propose concrete enhancements — effectively acting as a product advisor grounded in what mature ERPs already do well.
- Mentor implementation consultants and vet any external SIs/partners engaged on SAP or D365 workstreams.
Must-Have Experience
- 8–15+ years in ERP implementation, consulting, or architecture roles.
- Proven, hands-on, end-to-end implementation experience on both SAP (ECC/S4HANA) and Microsoft Dynamics 365 (F&O/Business Central) — not exposure to one platform and theoretical familiarity with the other.
- A track record equivalent to an SAP Solution Architect and/or D365 Solution Architect: has led or architected multiple full-lifecycle implementations (requirements → solution design → build/configuration → data migration → testing → go-live → hypercare) on each platform.
- Deep, working fluency in SAP terminology and concepts — e.g., FI/CO, MM, SD, WM/EWM, RICEFW objects, IDocs, BAPIs/RFCs, SAP Activate methodology, S/4HANA migration (brownfield vs. greenfield), SAP BTP/Clean Core, SAP Integration Suite (CPI)/PI-PO.
- Equal fluency in D365 terminology and concepts — e.g., D365 Finance, Supply Chain Management, Business Central, Data Entities, Data Management Framework (DMF), Application Integration Framework (AIF), X++ extensibility, Power Platform (Power Automate/Power BI), Azure Integration Services.
- Real experience integrating a non-SAP/non-D365 system into an existing SAP or D365 landscape — this is the exact pattern we need for Fynd ERP.
- Strong understanding of commerce and supply chain processes (order management, inventory, procurement, fulfillment) and how they map to ERP modules.
- Comfortable owning technical discovery directly with a customer’s IT/ERP team, including their SAP/D365 architects.
- Hands-on and builder-minded — writes/reviews integration code, works directly in configuration and data, and doesn’t stop at architecture diagrams.
- AI-first working style — actively uses AI/LLM tools to accelerate ERP work (data mapping, migration scripting, documentation, test generation) rather than relying purely on manual, traditional ERP-consulting methods.
- Demonstrated comfort operating in both the ERP world and the open-source world — e.g., has used or contributed to open-source tools/frameworks alongside enterprise ERP platforms, and can bring that pragmatism into how we build and extend Fynd ERP.
Good to Have
- SAP certifications (e.g., SAP Certified Application Associate/Architect – S/4HANA) and/or Microsoft Dynamics 365 certifications.
- Prior experience with a product company building its own ERP/commerce platform, rather than only working ERP implementations as a consultant/SI.
- Experience in retail, D2C, or unified-commerce environments specifically.
- Familiarity with modern iPaaS/API management tooling (MuleSoft, Boomi, Azure API Management, or similar).
- Exposure to cloud infrastructure (Azure, AWS, GCP) supporting ERP and integration workloads.
What We’re NOT Looking For
- Someone who has only worked on one ERP platform and has “read about” the other.
- Pure functional consultants without integration/technical architecture depth.
- Project/program managers without hands-on solution design and implementation ownership.
- Someone looking for a purely internal role — this position is customer-facing and will regularly sit across the table from a customer’s SAP or D365 architects.
Ideal Candidate Profile
Someone who can walk into a customer’s environment already running SAP or D365, quickly map out what their system actually does, tell us exactly where Fynd ERP should plug in and what needs to integrate versus what needs to be replaced — and then go build and deploy that solution themselves. They’ve done this more than once, on both platforms, and can hold their own in a room full of SAP/D365 architects because they’ve genuinely been one.
They’re also restless in a good way — they reach for AI tools to move faster, they’re as comfortable pulling from open-source communities as they are navigating enterprise ERP conventions, and they’re always asking why something has to be done the slow, traditional way when it doesn’t have to be.
