ERP Migration & SelectionFree checklistPDF, Excel, Word exportDiscrete Manufacturing

Small Manufacturer MRP Vendor Demo Question Checklist

A vendor demo is built to look good on their sample data. This checklist helps a small manufacturer shift the demo onto its own BOMs, routings and tasks, and compare MRPeasy, Katana, Odoo, ERPNext, Fishbowl and similar tools on the same questions.

0%

0 of 34 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Before the demo

BOM, items and routing

Planning and purchasing

Inventory and traceability

Shop floor and costing

Integration, data and commercial terms

Tick each question the vendor answered clearly in the demo with your own data. Unanswered critical items are reasons to ask for a second session.

Want a second opinion on your MRP shortlist?

Optional: an expert reviews your answers and flags risks before you sign.

Optional. The tool and every export work without this. No spam.

How to run the demo

Send one real multi-level BOM and one real routing a week ahead. During the session, ask the vendor to enter your data live rather than click through a script. Keep the same questions across vendors and tick the items they actually show, not describe. Use the critical flags to decide which gaps end the evaluation and which can be worked around.

  • Share real data before the call
  • Ask to see each task done live
  • Score right after each demo, not a week later
  • Bring one operator, not only managers

What separates the tools

Cloud MRPs for small plants differ most in depth rather than breadth. Some are strong at inventory and orders with light production, while others handle routings, scheduling and traceability. Open source options such as Odoo and ERPNext give more flexibility but need an implementer. The checklist forces the differences to the surface: lot tracking, capacity scheduling, multi-level BOMs and outside processing.

Reading the results

Count the ticked critical items per vendor first, then the total. A vendor that misses two or more critical items needs a clear workaround plan or should drop out. Ask for the answer in writing when a feature is described as coming soon. Pair this checklist with a total cost view, since user count, implementation and add-on modules often change the ranking.

Common mistakes

Letting the vendor drive the agenda, judging on screen design, and forgetting integration with accounting. Another is evaluating on features you will not use in the first year. Write down the five processes that cost you the most time today and weigh those before anything else.

Frequently Asked Questions

How many vendors should I demo?

Three is usually enough for a small plant. Narrow a longer list with a short written questionnaire and public pricing first. More than three demos tends to blur the differences and delay the decision, while fewer than two leaves you with no negotiating position.

Should I give vendors my real data?

Share one representative BOM and routing with sensitive prices removed. It is the quickest way to see whether the tool fits your process. Use a short confidentiality note if the part data is proprietary, and avoid sending customer lists or full price files.

What is the most important question?

Ask the vendor to run your most complicated real job end to end: BOM, purchase, receipt, production with time tracking, finished goods and shipment. Any gap in that chain will hurt after go-live, whereas gaps in rare reports can usually be handled outside the system.

Does open source remove the need for a vendor?

No. Odoo and ERPNext have no license fee for community editions, but you still pay for hosting, configuration, data migration and support. Compare total cost including implementation hours, not just the subscription line.

If you want an independent view of your shortlist and the migration effort, Netray can review it with you.