Signing an ERP contract without a structured evaluation is one of the most avoidable mistakes a manufacturing business can make. Vendors are skilled at demonstrating strengths and glossing over gaps. Your job, before any signature, is to reverse that dynamic — to surface the gaps while you still have negotiating leverage.
This checklist is written for the people who carry the real risk: the owner approving the budget, the plant head who will live inside the system, the finance controller who needs accurate books, and the IT lead who will manage the rollout. Use it in every vendor conversation, in every demo, and in every contract review.
Why fit matters more than features
Every ERP vendor will show you a feature list that looks comprehensive. The relevant question is not whether a feature exists — it is whether it works the way your plant works. A system built for discrete assembly behaves very differently from one suited to process manufacturing, textile jobbing, or chemical batch production. Gujarat's manufacturing base spans all of these, and a mismatch between your production model and the system's native logic will cost you in workarounds, manual corrections, and eventual re-implementation.
Before you watch a single demo, write down your five most complex operational scenarios — a job with mixed raw material grades, a subcontract loop, a quality hold that touches dispatch — and insist that the vendor walk through each one live, in the base product, without custom scripting prepared specifically for your visit.
Costing fit questions to ask
Costing is where ERP implementations quietly fail. The system goes live, transactions flow, and six months later the management accounts look nothing like reality.
- What costing methods does the system support natively? Standard, actual, weighted average, and job costing each suit different production models. Confirm which one aligns with how you currently price and account for your goods.
- How does the system handle co-products and by-products? This is particularly relevant for chemical, pharmaceutical, and agro-processing units common across Gujarat.
- Can you trace cost variances back to a specific batch, work order, or input lot? Variance analysis at this level is what makes costing actionable.
- How does it handle process losses, yield variation, and rework costs? Ask for a live demonstration with realistic figures, not a cleaned-up training dataset.
- Does landed cost calculation work across multiple legs of procurement? For importers and traders feeding into manufacturing, multi-leg freight and duty allocation must be automatic, not manual.
Production and planning fit questions
A system that cannot keep pace with your shop floor will be abandoned by operators within weeks of go-live, leaving supervisors reverting to spreadsheets.
Work order and routing
- Can the system model your actual routing steps, including parallel operations, alternate work centres, and operator skill dependencies?
- How does it handle rush orders that must be expedited through standard queues?
- Does it support subcontracting within a work order, or only as a separate procurement transaction?
Scheduling and capacity
- Is finite capacity scheduling available in the base product, or is it an add-on that carries additional licensing cost?
- How does the system respond when a machine goes down mid-schedule? Can the planner re-sequence interactively, or does it require a full re-run?
Shop floor data capture
- What are the mechanisms for operators to log progress — barcode scanning, touchscreen terminals, mobile app? Who pays for the hardware integration?
- If your plant has areas with poor connectivity, does the system support offline data capture with synchronisation?
If you are still assessing whether your operations are ready for this level of process formalisation, the ERP readiness self-assessment is a useful starting point before you begin vendor conversations.
Quality management and traceability
For manufacturers supplying to export markets, retail chains, or regulated sectors, quality module depth is non-negotiable.
- Does the system enforce inspection checkpoints at goods receipt, in-process, and finished goods stages — and can each stage have its own configurable test parameters?
- Is batch and serial number traceability end-to-end, from raw material supplier lot through to customer delivery note?
- Can quality holds automatically block dispatch without a manual override step that bypasses the system?
- How does it handle customer-specific quality plans or approved supplier lists?
- What does a non-conformance and CAPA (corrective and preventive action) workflow look like, and does it tie back to procurement and production records?
Statutory and regulatory compliance
This is the area where generic global ERP products most frequently underdeliver for Indian manufacturers, and where localised implementations matter most.
- GST: Can the system generate e-invoices directly via the IRP API, handle credit note matching, and manage the reconciliation between GSTR-2A and your purchase register?
- E-way bill: Is e-way bill generation integrated, or does it require a manual export-import step through a third-party portal?
- TDS and TCS: Are both handled within the accounts payable and receivable workflows, including section-wise mapping and Form 26Q/27EQ generation?
- Industry-specific compliance: If you operate in chemicals, pharmaceuticals, or food processing, ask specifically about FSSAI, Drugs & Cosmetics Act, or hazardous goods documentation requirements.
- Labour compliance: PF, ESIC, professional tax — are these payroll elements managed in the same system or will you carry a separate integration?
For a broader view of how these requirements shape manufacturing software decisions, the discussion on ERP for manufacturing operations provides useful context.
Data migration — questions that protect you
Data migration failures are a leading cause of delayed go-lives and cost overruns. Do not let this topic be deferred to "post-contract" discussions.
- What is the vendor's documented methodology for migrating open purchase orders, open sales orders, current stock positions, and historical transactions?
- Who is responsible for data cleansing — your team or theirs — and what tools or templates are provided?
- How many mock migration runs are included in the scope, and at what stage is data sign-off formalised?
- What happens to historical data that does not migrate? Is it accessible in a read-only archive, or does it disappear from your reach?
- Ask to speak with a reference customer specifically about their migration experience, not their go-live experience.
Licensing, support, and total cost of ownership
The licence fee is rarely the largest cost. Implementation, training, customisation, and ongoing support typically exceed it.
- Is the pricing per named user, concurrent user, or entity-based? How does your growth change the cost?
- What is included in the annual maintenance or subscription fee — patches, minor upgrades, major version upgrades?
- Where is support handled — local, regional, or an offshore helpdesk — and what are the contractual response and resolution SLAs for critical issues?
- If you need a custom report or a regulatory change applied urgently, what is the process and who bears the cost?
The comparison of commercial and licensing models available in the Odoo vs SAP analysis for mid-market manufacturers is worth reading alongside this section if you are weighing contrasting licensing structures.
Ownership of customisations and exit rights
This section is frequently skipped by buyers in a hurry. It should not be.
- Who owns the intellectual property in any customisations built for your business? This must be explicit in the contract, not assumed.
- If you terminate the contract, can you export your data in a standard, machine-readable format — and is this right documented?
- What format does the data export take, and is it usable by a successor system without significant transformation effort?
- If the vendor is acquired, merged, or ceases to support the product, what are your contractual protections?
- Are customisation source files held in escrow, or can they be transferred to you on request?
These questions feel adversarial to raise, but any vendor with a mature commercial practice will answer them without hesitation. Evasion here is a warning sign.
Evaluating the implementation partner, not just the software
In most ERP projects, the implementation partner determines the outcome more than the product itself. The software is the instrument; the partner's methodology and knowledge of your industry is what makes it play in tune.
- Ask for a detailed project plan with milestones, deliverables, and named resources — not just a timeline.
- Who will actually work on your project? Request CVs of the consultants who will be assigned, and ask about their manufacturing sector experience specifically.
- What is the escalation path if the project runs into difficulty? Is there a steering committee structure with defined checkpoints?
- How does the partner handle scope creep — additional requests that emerge during implementation? Is there a documented change request process with cost implications agreed in advance?
If you would like to work through these questions with a consultant before approaching vendors, ERP consulting services are available to support that preparatory phase. Reviewing what to expect from an ERP engagement can also help you frame the right scope discussion internally before any external conversations begin.
Taking the next step
This checklist is most useful when it is applied consistently across every vendor you evaluate — not just the one you are leaning towards. Vendor selection decisions made under time pressure or based on a polished demo rarely survive first contact with production reality.
If you are at the stage of shortlisting vendors and want an independent sounding board before you commit, we are happy to review your requirements and help you stress-test what you are being offered. Reach out to the team at KoderClub in Surat to arrange a working session.