Start with the operating problem, not a product demo

An ERP supplier should demonstrate how your accounting, purchasing, stock and sales teams will complete their daily work. List the current software, number of users, warehouses, approval steps and reports that fail today. Ask each supplier to price the same written requirements.

Configure ERPNext, extend it, or build custom ERP?

ApproachSuitable whenTrade-off to examine
Configure ERPNextStandard accounting, purchasing, sales and inventory broadly fitYour team may need to change existing habits; validate the fit in a demo
Extend ERPNextThe core fits but selected approvals, reports or integrations differCustom apps need testing and maintenance when ERPNext changes
Bespoke ERPA documented core workflow cannot reasonably fit an existing platformMore responsibility for security, testing, documentation and ongoing development

Compare suppliers on the same scope

  • Retail and distribution: demonstrate purchase receipts, multiple warehouses, returns, price lists and stock reconciliation. Include batch or expiry tracking if relevant.
  • Migration: distinguish masters, opening balances, open invoices and historical transactions. Request sample imports and accounting reconciliation.
  • Customization: identify configuration, custom app development and third-party dependencies separately.
  • Training: name the user roles, training sessions, reference materials and acceptance tests.
  • Support: specify support hours, issue priorities, response targets, upgrade testing and exclusions.
  • Ownership: document hosting access, backups, source access, licenses and the handover process.

Migration scope and price comparisons

A quote for masters and opening balances is not equivalent to a quote for several years of transactions. Historical migration needs a separate feasibility check for source exports, tax treatment, attachments and reconciliation. A parallel run and accountant sign-off should be agreed before cutover. Read our Tally migration preparation guide.

Ask for separate costs for discovery, setup, custom development, migration, training, hosting, third-party services, taxes and ongoing support. AI Build Infra quotes ERP work after reviewing the scope; figures from another project are not a fixed offer for yours.

What to request before signing

  1. A fit-gap document describing supported and unsupported workflows.
  2. A phased delivery plan with dependencies and testable acceptance criteria.
  3. A migration inventory with exclusions and reconciliation responsibilities.
  4. A handover and support agreement, including change-request pricing.

Compare our custom ERP development service with ERPNext implementation. Review the published BioArtha ERPNext project for workflow context, then request an ERP workflow assessment. Share your current software, users, warehouses and main bottleneck.