Manufacturing
Manufacturing ERP & MRP Software
Connect MRP, production scheduling, shop-floor execution, quality and production costing in Tellency AI-native manufacturing ERP. Explore the complete workflow.
Manufacturing buyer guide
Evaluate a complete production cycle, not a feature list.
A manufacturing ERP selection needs input from planning, production, quality, purchasing and finance. Use one transaction pack across every shortlisted system so the team can compare the same business result.
By the Tellency team · Reviewed
1. Bring a real product and its manufacturing definition.
Start with a product that represents the complexity you need to manage. Include a revision change and an exception rather than choosing the simplest item in your catalogue.
- Prepare the multi-level BOM or formula, yields, units and routing.
- Include an alternative material or revision/effective-date scenario.
- Ask how the order retains the selected definition after engineering changes.
2. Prove the material and capacity plan.
Give each vendor the same demand, stock and expected receipts. Inspect the proposed replenishment and the source of every important exception.
- Review net requirements, lot sizing, lead time and pegging.
- Include an expired or quarantined lot, a late receipt and a planning time fence.
- Constrain a work centre with a holiday and a changeover; inspect the schedule and late-order result.
3. Run the order through the shop floor.
Ask an operator to follow the actual steps using the proposed terminal and devices. A demonstration should establish what is recorded automatically and what still requires an operator.
- Release the order, prepare materials and follow the dispatch queue.
- Issue a lot, record time, enter a weighing deviation and complete required checks.
- Record good output and scrap, print a lot label and review the batch record.
4. Demonstrate the quality exception.
A passing test shows only the easiest path. Investigate a rejected lot or out-of-spec check and the permissions needed to decide what happens next.
- Review quarantine, nonconformance, rework/scrap and release decisions.
- Trace a finished lot back to its input lots and affected records.
- Assign a corrective action, review effectiveness and test who can close it.
5. Reconcile the production result.
Finance should be able to connect the activity to WIP, output value, variances and the ledger. Agree the valuation method explicitly.
- Compare the cost definition with the recorded order activity.
- Inspect the close journals, absorption, stock-value reconciliation and period-end reports.
- Review account mappings, posting dates, currency and approval responsibilities.
6. Agree migration, access and rollout acceptance.
The purchase includes implementation work as well as software. Put the demonstrated outcomes and any missing integrations into the written scope.
- Map products, formulas/BOMs, routings, opening lots, balances and open orders.
- Test role permissions and an agent action that must request approval or be refused.
- List training, device/browser validation, network recovery, support, services, usage and recurring charges.
Before the demo
Questions worth asking.
Should we compare Tellency with NetSuite and Odoo?
Yes, when they fit your shortlist. Compare the configured manufacturing applications and modules needed for the same complete workflow. Licensing and implementation scope vary; a product-family name is not a complete proposal.
How many scenarios should the demo include?
At minimum, include a normal production cycle, a planning shortage, a constrained schedule, a failed inspection and a financial variance. Add the exceptions that matter most to your own operation.