Hiring a Business Central manufacturing consultant: what to assess

Describe your factory before describing the software

Manufacturing is not a single process. A make-to-stock assembly operation has different planning decisions from a machine builder managing long production cycles and changing specifications. Explain the product structure, typical order sizes, routing complexity, subcontract work and how demand reaches production.

Ask supervisors to describe a normal order and an awkward one. Where do materials wait? Who reports consumption? When is output considered complete? Which decisions happen outside the ERP? These details help a consultant distinguish a system problem from an operating policy that has never been agreed.

When reviewing Business Central manufacturing consultant profiles, look for relevant process exposure rather than a claim of experience across every industry. A candidate should be able to explain the assumptions behind a previous configuration and identify what would need reconsideration in your factory. An honest boundary is more useful than an immediate promise to fit every practice into standard functionality.

Make master-data decisions visible

Production information depends on the quality of the underlying item, component and operation data. Before configuration workshops, identify who maintains product structures, units, expected quantities, operation times and planning assumptions. A consultant can design controls, but engineering and operations must approve what the records mean.

Use a small set of representative products to test the data model. Include a straightforward item, a product with several operations and one with recurring exceptions. This sample should expose decisions about alternative materials, revisions and units before thousands of records are prepared.

The consultant should deliver a data responsibility matrix and validation checklist, not only an import template. Ask how changes are approved after go-live and how downstream users learn that a structure has changed. Poor ownership can undermine a technically correct implementation within weeks as new products are introduced using inconsistent assumptions.

Test the whole production-order lifecycle

Microsoft documents production orders as the basis for recording manufacturing execution, including material consumption, time and output. For a hiring assessment, ask the candidate to walk through your intended lifecycle and explain which users act at each stage. Keep the discussion tied to business evidence rather than a memorized menu tour.

Use a hypothetical order with partial completion and a material shortage. Ask what planners need to see, what stores must do and how the production supervisor reports progress. Then ask how finance checks the resulting cost information. The scenario should reveal whether the candidate understands the connections between departments.

Require the consultant to distinguish a proposed setup from behavior already demonstrated in your version and licensed scope. A written process walkthrough with sample documents is more useful than a broad statement that manufacturing is supported. Include the exception paths in user acceptance testing before approving the workstream.

Choose reporting methods that match shop-floor evidence

Automatic reporting can reduce entry effort, but it must reflect how reliably the business can infer actual activity. Microsoft describes manual and automatic approaches to consumption and output. The operational decision is whether expected quantities and times are a defensible basis for the transaction or whether actual reporting is needed.

A hypothetical factory with frequent substitutions and variable scrap should examine the consequences of reporting expected consumption automatically. The question is not whether automation is attractive; it is whether exceptions can be identified and corrected promptly enough for inventory and costing to remain useful.

Ask the consultant to compare reporting options with supervisors and finance together. Record who captures exceptions, when entries are reviewed and what happens if an order is completed incorrectly. This is where domain experience matters: a setup choice that saves a few clicks can create substantial reconciliation work if it ignores how production actually behaves.

Evaluate the consultant with a factory-focused scorecard

A useful interview should cover the decisions your team finds difficult. Give the candidate enough context to reason, then ask them to state assumptions and describe a validation approach. You are assessing judgment and communication, not their ability to guess undocumented factory policy.

Use the following scorecard to compare candidates. Ask for anonymized evidence where permitted and distinguish personal responsibility from work delivered by the wider project team. If the assignment includes warehouse design or complex financial treatment, determine whether the consultant can cover it or needs a colleague. Broad ownership should be supported by evidence rather than inferred from seniority.

Connect manufacturing with warehouse and finance

A production workstream cannot be accepted in isolation. Materials must be available where the process expects them, and output must reach the appropriate inventory state. The warehouse team needs clear instructions for movement, while finance needs a consistent basis for understanding costs and variances.

Microsoft’s inventory setup guidance includes item units and location-specific stockkeeping information. In a project, these are shared decisions, not separate clerical tasks. Ask how the manufacturing consultant will coordinate them with Business Central warehouse and inventory specialists. Agree who owns an issue that crosses both workstreams.

Finance should participate before the first final production test. Define the expected postings and reports, identify cut-off rules and confirm the treatment of incomplete work. Where more detailed reporting is required, involve Business Central finance consultants to establish the measures before developing dashboards. A visually appealing production report cannot compensate for ambiguous source transactions.

Select the model around the manufacturing workload

Hourly Model is suitable for a targeted process assessment, planning review or troubleshooting a defined production issue. Provide sample orders and the relevant master data so the consultant can investigate rather than spend most of the engagement gathering context. Agree the expected written findings.

Project Based fits a bounded manufacturing workstream with agreed product families, processes, configuration and acceptance tests. State which data the factory will supply and which adjacent areas are included. A manufacturing configuration assignment should not silently expand into an unrestricted redesign of warehouse operations or financial reporting.

Dedicated Resource suits a sustained implementation or improvement programme where the consultant works closely with planners, supervisors and finance. Define floor-access needs, workshop language and meeting overlap. For a European or North American factory using India-based expertise, remote work can support many tasks, but any need for physical observation should be identified explicitly and planned separately.

Build acceptance around decisions operators can use

A useful manufacturing acceptance pack contains agreed process flows, key setup decisions, master-data rules and representative test evidence. Include operating instructions for common exceptions. The person on the late shift should not need to interpret a lengthy implementation document to understand a routine production correction.

Review readiness with the people who perform the work, not only department managers. Can stores identify what is required? Can the supervisor report actual progress? Can planning see an exception early enough to act? Can finance trace the result? These questions keep acceptance grounded in operational usefulness.

After rollout, review a sample of real production orders with the consultant and process owners. Record recurring difficulties as specific improvements, distinguishing data quality, training, setup and development needs. This evidence helps decide whether occasional support is enough or whether a dedicated manufacturing resource remains justified during stabilization.

• Representative products, operations and difficult production scenarios.
• Named owners for engineering data and shop-floor reporting.
• Joint acceptance from production, stores and finance.