About the role
- Gather and document business requirements from stakeholders — merchandisers, buyers, warehouse teams and finance controllers. Learn the process before proposing to change it.
- Deep dive into customer workflows, pain points and product gaps through research, interviews and data analysis.
- Map current-state operational flows and locate where the ERP forces a workaround.
- Analyse data and provide insights that support product and business decisions; prepare the reports and presentations that carry the argument.
- Participate in ideation, scoping and prioritisation of new features and enhancements.
- Bring sized, evidenced opportunities into the ERP roadmap with a Feature Brief.
- Convert business problems into functional requirements — PRDs, detailed business requirements (FRDs), user stories, process flows, workflows, scenarios and API documentation.
- Cover master-data impact, document states, statutory treatment, posting logic and acceptance criteria explicitly. Ambiguity in an ERP specification becomes a reconciliation problem later.
- Design wireframes, workflows and mockups for the screens and reports your modules own, collaborating with UI/UX as needed.
- Interact with the solution architect in support of architecting the solution.
- Own data-migration and backward-compatibility thinking — ERP customers carry years of transactional history.
- Scope and estimate with Engineering; map dependencies on POS and OMS for stock, pricing and article master.
- Groom your backlog weekly on Jira with clear stack ranking.
- Deliver prototypes and mockups, not just documents — validate before engineering handoff.
- Coordinate with the development team on a day-to-day basis to develop specifications into the product solution.
- Facilitate sprint planning, backlog grooming and agile ceremonies.
- Take scope and trade-off decisions in your area; at Product Manager 2, negotiate cross-module and cross-pod dependencies directly.
- Conduct user acceptance tests with QA to ensure requirement fulfilment — including reconciliation, statutory and multi-period scenarios.
- Troubleshoot integration problems by understanding the API response against your functional understanding.
- Triage defects and hold the quality bar on financial and inventory accuracy specifically.
- Escalate date risk early with a proposed mitigation.
- Validate solutions with stakeholders both before and after development.
- Define success metrics before you build and monitor product performance after launch.
- Monitor feature adoption, gather feedback and recommend iterations — particularly where the change asks a finance or merchandising team to alter an established routine.
- Engage directly with key customers during UAT, feedback sessions and demonstrations to validate solutions.
- Provide support on gaps in delivered features and fold them into the next iteration.
- Use data and analytics to inform continuous improvement and prioritisation.
- Identify where AI can be embedded into ERP workflows — automation and copilots that remove manual effort, not another report.
- Act as the bridge between business, technology and customer-facing teams.
- Liaise with Customer Success, Sales and Support to gather feedback and evangelise product capability.
- Publish release notes to customers and stakeholders ahead of every release.
- Conduct webinars and create release videos, and deliver training so customers can actually operate what changed.
- Create and maintain the user guide and change-management documentation for your modules.
- Create and maintain public-facing integration and API documentation, and the customer-facing articles that back the product.
- Equip Sales, Support and Customer Success on what changed and which customer segment it matters to.
- Continuously improve internal processes related to product discovery and delivery.
- As Product Manager: own a single ERP module end to end across discovery, definition, delivery and adoption.
- As Product Manager 2: own a module cluster, lead the harder and more ambiguous problems, negotiate cross-module and cross-pod dependencies directly, and guide an Associate Product Manager.
- Decide scope and trade-offs within your area; own and prioritise your backlog.
- Accountable for adoption outcomes, not only delivery.
- Placement between the two levels is confirmed on assessment, based on demonstrated scope, independence in ambiguity, and cross-module dependency handling.
- 3–7 years of relevant experience in Business Analysis and/or Product Management, with at least 2 years on an ERP, accounting or supply chain product.
- Commerce background (, BBA, CA, CMA, CS or equivalent) or demonstrable equivalent domain depth.
- Strong functional grounding in at least one of: merchandising and buying, inventory and warehouse operations, distribution, or financial accounting and statutory compliance.
- Excellent understanding of functional and operations mapping in an application; very methodical in drafting a solution and defending a decision.
- Understanding of API integrations and their depth, and of master-data flows between systems.
- Understanding of RDBMS and SQL including table joins — comfortable interrogating data rather than requesting a report.
- Very good hands-on Microsoft Office (Excel, Word, PowerPoint); working knowledge of Jira, Confluence, Lucidchart or Visily, Figma and product analytics.
- Awareness and active use of AI tools for requirements, discovery, analysis and prototyping.
- Good communication, documentation and presentation skills.
- Working knowledge of Indian statutory requirements — GST, e-invoicing, e-way bill, TDS.
- Hands-on with widely accepted business applications — SAP, Oracle, Navision, Tally or Ginesys.
- Experience with costing, landed cost, margin or stock valuation logic.
- Exposure to replenishment, allocation or open-to-buy planning.
- Exposure to POS or omnichannel order flows and how they integrate with ERP.
- Prior experience in a Business Process or Operations Management–IT team in a retail or distribution organisation.
- Not a feature-request coordinator.
- Not a sales escalation buffer.
- Not a Jira ticket manager.
- Not a documentation-only role.