# Cloud MRP Vendor Demo Script Template > Source: https://netray.co/tools/cloud-mrp-vendor-demo-script-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A scripted demo agenda using your own part, BOM and job so you see how each cloud MRP handles your real work instead of a canned demo. ## Category erp-migration ## Industry Small Manufacturing ## Audience - Owner - Operations manager - Planner - ERP selection lead ## Tool **Kind:** template **Output:** document **Fields:** #### Company name **Key:** company **Type:** text **Default:** Northfield Fabrication LLC #### Vendor being demoed **Key:** vendor **Type:** text **Default:** Vendor A #### Demo date **Key:** demo_date **Type:** date **Default:** 2026-11-03 #### Sample finished good **Key:** assembly **Type:** text **Default:** FG-2200 Mounting Bracket Assembly #### BOM description **Key:** bom_note **Type:** textarea **Default:** 3 levels, 14 components, 2 purchased hardware kits, one outside-processing step (powder coat), one alternate supplier for the steel plate. #### Customer order scenario **Key:** scenario **Type:** textarea **Default:** Customer orders 250 pieces due in 4 weeks. Plate stock is short by 60 pieces and the powder coater needs 5 days. #### Attendees **Key:** attendees **Type:** text **Default:** Owner, planner, buyer, shop supervisor, accountant **Blocks:** #### Scripted Demo Agenda **Body:** Company: {{company}} Vendor: {{vendor}} Date: {{demo_date}} Attendees: {{attendees}} Please demonstrate the steps below using our data. We will not score features shown from slides or from a different dataset. #### Our data **Body:** Finished good: {{assembly}} BOM: {{bom_note}} Scenario: {{scenario}} #### Demo steps and scoring **Table:** **Columns:** - Step - What we want to see - Score 0-5 - Notes **Rows:** **0:** 1 **1:** Create the item and multi-level BOM with an alternate component **0:** 2 **1:** Enter the customer sales order and see the promised date **0:** 3 **1:** Run MRP and show shortage suggestions for plate and hardware **0:** 4 **1:** Convert suggestions to purchase orders in bulk **0:** 5 **1:** Release a production order with routing and outside processing **0:** 6 **1:** Report time and scrap from the shop floor on a tablet **0:** 7 **1:** Receive the PO partially and update inventory with lot numbers **0:** 8 **1:** Ship, invoice, and show job cost against the quote **0:** 9 **1:** Show the accounting integration posting #### Questions to ask live **Body:** What happens when a BOM changes while jobs are open? Which steps above needed a paid add-on or custom field? How many clicks did step 3 take? What are the limits on API calls, users, or locations at our price tier? #### Sign-off **Signatures:** - Evaluator - Vendor presenter **Notes:** Print one copy per evaluator and compare totals after all vendors have presented. Score the same day while memory is fresh. ## Content **Intro:** Canned demos always look good. A scripted demo with your own part, BOM and order shows whether the tool handles outside processing, alternates, partial receipts and job costing. This template creates the agenda and a scoring sheet you send before the call. **Sections:** #### How to use it **Body:** Choose one real finished good that is slightly awkward: multi-level, with one purchased kit and one outside process. Fill in the BOM description and a customer scenario with a shortage. Send the exported document to the vendor at least three days before the demo and ask them to load it. During the call, each evaluator scores steps from 0 to 5 and notes anything that needed a workaround. #### Why the steps are in this order **Body:** The sequence follows the order-to-cash and plan-to-produce flow: item and BOM, sales order, MRP, purchasing, production, receiving, shipping and accounting. It exposes where data must be re-entered. If a vendor needs a spreadsheet import or a consultant to bridge a step, you will notice in step 4 or step 9 rather than after go-live. **Bullets:** - BOM and alternates first - MRP shortage visibility next - Outside processing in the routing - Costing and accounting last #### Reading the scores **Body:** Add each vendor total and also count steps scored below 3. A vendor with a high total and two zeros on Must steps is riskier than one with consistent 3s. Compare the notes column for workarounds, and ask what each workaround costs in time or paid add-ons. Weight steps by how often you do them: daily steps like shop floor reporting should count more than annual ones. #### Common mistakes **Body:** Letting the vendor pick the data, accepting verbal answers such as it can be configured, and inviting too many people so that nobody scores. Keep the room to five people and one scribe. Record the demo if the vendor permits it, so the team can recheck a step later. **Cta:** Netray can sit in on a vendor demo as a neutral technical reviewer and compare the answers to your ERP data. **Faq:** #### How many vendors should I demo? **Answer:** Three is a good limit for a small plant. More than that creates evaluation fatigue and weaker scoring. Use your requirements document to shortlist before you book demos. #### Should I share my real data with a vendor? **Answer:** Share one anonymized part and BOM, not your full database. A single awkward assembly and a sample order are enough to expose most gaps. #### What score should disqualify a vendor? **Answer:** Any Must step scored 0 or 1 without an acceptable standard workaround is a strong signal to drop the vendor, regardless of price. #### Is a trial account better than a demo? **Answer:** Often yes. Many cloud MRPs offer trials. Use this script during the trial too, entering the same sample part, and compare notes with the vendor-led demo. ## Search terms erp demo script, mrp software demo checklist, erp vendor demo scorecard template, manufacturing software demo script, scripted demo erp, cloud mrp evaluation demo --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json