ERP Business Analyst in Mumbai

A city headquarters with operations across the region

Rising rents and space constraints pushed much of Mumbai's warehousing and manufacturing outward over the decades. The result, for many businesses, is a head office that handles customers, pricing and finance, linked to godowns around Bhiwandi, factories in MIDC areas such as Taloja, Tarapur or Thane-Belapur, and sometimes a back-office accounts team working from Navi Mumbai. Information moves between them by phone, email, spreadsheets and messaging apps.

Each of those handoffs is a requirement waiting to be written. When head office confirms an order, how does the godown learn which lot to dispatch? When a plant runs short of a raw material, who raises the purchase request and who approves it? When a truck leaves Bhiwandi, when does the invoice get made and by whom?

I map these flows site by site, using process mapping that shows each location as its own lane. Delays and duplicate entries become visible quickly, and so do the places where the same fact is typed into different systems by different people. Those points become the core of the requirement set, because they are where a well-designed ERP adds the most value for a business with this shape.

Stock statements, debtors and what your bank expects

Mumbai is India's banking center, and many mid-sized trading and manufacturing firms in the city depend on working capital limits from banks. Those facilities typically come with regular reporting: statements of stock and receivables that support the limit, sometimes with ageing buckets and exclusions agreed with the lender. Importers may also work with letters of credit, and contractors with bank guarantees.

These obligations are often handled outside the accounting system, in spreadsheets prepared by the finance team at month end. An ERP project is the moment to make them requirements. Which stock is included and at what valuation? How are goods in transit or with job workers treated? How are old receivables or disputed invoices excluded? Which report must match which figure in the books?

I document these as explicit requirements with the reports and reconciliations they need, then check during gap analysis whether each shortlisted platform can produce them without manual rework. The exact terms of your facility come from your bank sanction letter and your CA, not from me; my job is to make sure the system can produce what they ask for consistently.

Approval rules in promoter-run businesses

In a promoter-run Mumbai business, many important decisions happen informally. A salesperson calls the owner to approve a lower rate for a valued customer. The accounts head messages a director before releasing a large payment. A credit limit is exceeded because the customer has traded with the family for years. These judgments are part of the business's strength, but they are invisible to any system.

An ERP that ignores them either blocks the business or gets bypassed. A good business analysis captures them as an approval matrix: which transactions need approval, above what conditions, by whom, and with what fallback when that person is traveling or unavailable. It also records which approvals should stay outside the system entirely because they depend on judgment no rule can describe.

I build the matrix with the promoter and senior staff together, which often surfaces disagreements about authority that are worth resolving before go-live rather than after. The outcome feeds directly into approval workflow design and into the user roles your implementer will configure.

SEZ, export units and separate documentation

The Mumbai region includes the SEEPZ special economic zone in Andheri, with a long association with gems, jewellery and electronics, along with export-oriented manufacturers and units in other zones across Maharashtra. A business that runs one of these units alongside a regular domestic operation has requirements a standard ERP template does not cover.

Typical questions include how stock held in a bonded or zone unit is kept separate, how movements between the zone unit and the domestic entity are documented, how export documentation links to invoices, and how the unit's own reporting is produced. Gems and jewellery units add questions about weight-based items, consignment stock and job work with artisans.

I capture these flows as requirements and identify where a platform will need configuration, an add-on or a specialist system alongside it. I do not interpret customs or zone rules; those questions are listed for your customs advisor and CA, and the requirement is written once they confirm the treatment. This keeps the BRD accurate without pretending to be a legal opinion. The general approach is described on my ERP requirements gathering page.

Workshops that reach the godown floor

Office teams in Mumbai usually work comfortably in English, but staff at a godown in Bhiwandi or a plant in Vasai may be more at ease in Hindi, Marathi or Gujarati. If requirement workshops only happen in boardroom English, the people who know the real process stay quiet, and the BRD describes what managers think happens.

The engagement runs in English. To reach the floor, I ask for a bilingual supervisor or colleague to join the sessions and help staff explain their routines in the language they prefer. Short phone videos of a stock register, a dispatch routine or a job work challan often say more than a long interview. Any Hindi, Marathi or Gujarati text that will appear in the final system, such as labels or print templates, is prepared or reviewed by native speakers within your team.

The deliverable is a business requirements document structured by site and process, with priorities and test conditions. It sits alongside the India-wide compliance requirements covered on my ERP business analyst India page, and supports the platform decisions described on the Mumbai ERP consultant page.