What Is ERP in Manufacturing? A Guide for Canadian Plants That Build to Order

Key Takeaways: 

• An ERP becomes ERP in manufacturing the moment it can hold a record saying this item is made from those items  
• A works order opens with a standard cost and closes with an actual one, and the difference between them is the system's real output  
• Discrete plants build countable units from parts lists, process plants make batches from formulas, and the two need different data models underneath  
• CBSA can ask a Canadian producer to prove a CUSMA claim, and the evidence is a costed bill of materials with origin on every line  
• Business Central puts production in its Premium tier, which is the licensing detail plants find out about too late

ERP in manufacturing is the system a plant uses to plan production and cost it, then record what got built. One record sets it apart from every other kind of business software. The bill of materials lists what a finished product is made from, and buyers, planners, cost accountants and the quality team all work from it.

That record has a second use in Canada. A producer claiming preferential tariff treatment under CUSMA has to show where each component came from and what it cost. CBSA can ask for that evidence years after the goods shipped.

What is ERP in manufacturing?

Distribution software holds an item with a quantity and a price. ERP in manufacturing gives that same item a structure underneath it. That structure names every component the item is built from, with a quantity and a cost against each one.

Everything a plant needs from software follows from that one change. A buyer can break a finished unit down into every part required to build it, and a cost accountant can total material and labour to reach a figure no one had to estimate.

• Ordering stops running on reorder points and starts running on demand
• Quoted prices reflect what a product costs to build this month
• A promised date has a capacity calculation behind it
• One recall question resolves in an afternoon
• Margin gets reported at product level

Plants without that structure are running distribution software, built for a wholesaler who buys a case and sells it on unchanged. The ERP manufacturing modules exist for a plant that buys steel and sells a bracket.

Most of the ERP myths manufacturers repeat to each other trace back to someone buying a distribution platform and calling it a plant system, and comparing types of ERP software gets easier once you know that. Ask whether an item can be made from other items. Then ask how many levels deep that goes.

How does a work order move through ERP in manufacturing?

Following one job from promise to invoice explains a plant system faster than any feature list. Each step writes something the next reads, which is why a fault at the top reaches the shop floor.

1. A sales order arrives with a date. It goes in against a finished item that already has a parts list and a routing behind it.
2. The planning run breaks it down. Material requirements planning reads the parts list, nets it against stock and open purchase orders, then proposes what to buy and what to make. This is the step ERP MRP software exists to perform.
3. Purchase orders leave. Bought components get ordered against supplier lead times, so material lands when the operation needs it and not three weeks early.
4. The work order releases to the floor. Operations appear in sequence against named work centres, each carrying hours and a standard cost already calculated.
5. Material gets issued and time gets reported. Components come out of stock against the job while operators book hours to each operation. Scrap gets recorded where it happened.
6. Output posts to finished goods. Completed units enter stock at their calculated cost, and the general ledger moves at the same moment.
7. The variance appears. What the job should have cost and what it did cost get compared by cause, so a margin problem points at a supplier, a work centre, a standard that was wrong or a routing left un-updated.

The costing loop at the end is what most demonstrations skip. Ask a vendor to run a planning cycle on your own parts list, then close a job and produce the variance report from it. ERP vs MRP confusion is why that half gets shown as a checkbox and never demonstrated at all.

Running ERP production planning properly means every job returns evidence. After six months a plant knows which products earn money and which have been subsidised by the rest.

All of it depends on the parts list being right. A component superseded in 2022 and still present on a bill of materials produces a purchase order for something the plant no longer uses, and that error reaches the shop floor before anyone spots it.

Does your plant need discrete or process ERP in manufacturing?

This is the fork every manufacturer hits and no other kind of buyer ever does. Discrete plants build countable things from parts lists, so an assembly holds three brackets and eight bolts and can be taken apart again. A process plant works the other way round, turning flour and water into dough that no one can separate afterwards.

The data model underneath differs in ways that decide whether a platform fits at all.

• Discrete work runs on bills of materials with fixed quantities, serial numbers, rework routes and revision control
• Process work runs on recipes that scale, with batch control, potency or grade attributes, and yield that varies between runs
• Discrete plants trace a unit through its whole life, from the serial number back to the parts that went into it
• Process plants trace a lot through everything it touched, and one batch can throw off co-products needing cost apportioned across several outputs

Canadian food and beverage producers get caught out most often here, because a discrete platform sold as flexible will hold a recipe as a bill of materials and then fail the first time a yield comes in under target. The discrete vs process manufacturing distinction belongs in the requirements document, well before the demo.

Mixed mode gets handled unevenly across the market, and plenty of Canadian plants need it. A shop buying discrete manufacturing ERP software with a batch process on the side should test that early. 

A machine shop that also does surface treatment is one. Plants working through how to choose an ERP system should settle the mode question before the requirements list gets written. Ask any vendor to demonstrate a batch and an assembly in the same session. One who can't has answered you already.

What does ERP in manufacturing have to prove for a CUSMA claim?

Most Canadian producers shipping into the United States claim preferential tariff treatment under CUSMA. Making that claim takes a moment and defending it without records can run for months, because goods have to satisfy the product-specific rule of origin written for their classification.

Most of those rules ask for one of two things. Either a tariff shift, where inputs moved to a different classification through production, or a regional value content calculation showing enough of the finished price came from North America. Both read the costed bill of materials, one component at a time.

The Canada Border Services Agency can request that evidence, and the certification of origin itself has no prescribed format. What it carries is a set of minimum data elements, backed by whatever the certifier holds to support it. The Trade Commissioner Service tells exporters to keep origin documentation for at least six years after the goods leave.

A verification asks for a specific set of records.

• The certification itself, carrying the minimum data elements
• The origin criterion claimed against each product's tariff classification
• The costed parts list behind any regional value content calculation
• Supplier declarations for components the plant didn't make itself

Blanket certifications turn this from paperwork into exposure. One certification covers repeated shipments of the same product for up to twelve months, so a purchasing decision made in March can undermine a claim already filed on goods that left in February. Dated cost and origin history on every component lets a producer name the affected shipments, and a spreadsheet leaves them guessing.

Getting this right is a configuration decision made once, which is why ERP implementers working with cross-border plants raise it in the first workshop. Country of origin and tariff classification both become fields on the item, populated during implementation, so the evidence file gets built from records the plant already held. 

Retrofitting means revisiting every part record. Leaving it until a verification arrives means doing that work twice.

How does ERP in manufacturing connect to the shop floor?

Every plant has a boundary between the system and the machines, and where you draw it decides how good your data is. A paper sheet that travels with the job and gets collected at the end of shift leaves you looking at yesterday. Terminals on the floor bring that down to this morning, and a direct connection to the machines reports the last four minutes.

Cost climbs across that range and so does accuracy, which makes the boundary a budget decision as much as a technical one. Anyone weighing ERP WMS capability against a separate warehouse product is answering the same question one floor down. Three positions cover most Canadian mid-market plants.

• Operators book time and quantity at a shared terminal, which suits low-mix assembly work
• Barcode scanning at each operation, which suits plants where traceability is a customer requirement
• Direct capture from PLCs or a manufacturing execution system feeding the ERP, which suits high-volume runs where minutes of downtime carry weight

Statistics Canada gives plants another reason to care about capture quality. Its Monthly Survey of Manufacturing collects sales of goods manufactured, inventories, orders and capacity utilisation rates in current Canadian dollars, so a plant guessing at those figures is submitting estimates the federal government uses to measure the economy.

Stock handling belongs on the same continuum, and it decides whether manufacturing inventory control software proposes purchase orders for parts already on a shelf. Bins, zones, directed putaway and cycle counting turn a stockroom into something the planning run can trust. 

That description is the half of ERP software inventory management most projects rush, and everything downstream runs off it. Bin accuracy below about 95% turns planning output into guesswork. Licence spend never recovers ground lost at that stage.

Why do ERP in manufacturing projects go over budget?

Ask any plant that has been through this and they'll say data, every time. Bills of materials that were right when someone wrote them. Routings built around a machine sold in 2019. Phantom parts that exist in the system and nowhere else. 

All of it needs correcting before a single module reads from it. Plants replacing one of the old ERP systems inherit twenty years of that, and ERP experts walking a working plant will price the cleanup before anything else.

That work sets the budget more than the software does, and the ERP implementation phases a vendor proposes tell you where they expect the pressure to land. A plan with no data phase in it has hidden that risk. A service quote responds to plant complexity far more than to headcount.

• Parts list depth, since every extra level in an assembly adds configuration work behind it
• Work centre count, and whether shop floor output gets captured electronically or on a clipboard
• Lot and serial requirements, which regulated producers need and general engineering shops skip
• Cross-border volume, because origin and tariff fields need setting up before the first claim goes out

Licensing is the other surprise, and it comes from how the whole market packages production. Platforms put shop floor functionality in a higher tier than the finance and sales one a buyer prices first, so a number quoted early in a conversation can exclude the plant entirely. Ask every vendor which tier covers production before you compare anything.

Published list prices are the exception here, and Microsoft is one of the few offering them. That gives a Canadian buyer one public figure to set other proposals beside, and a published ERP pricing comparison fills in the rest of the range. 

Production belongs to the Premium tier at CAD $149.20 per user each month, where Essentials runs at CAD $108.50 and stops short of the shop floor. Both Business Central pricing figures have applied since 1 November 2025.

Ask for the data cleanup as its own line before comparing anyone's total. Split what remains using the ERP implementation cost headings. Anything well outside that range needs explaining before it gets signed. Plants that skip all this reach go-live with a quote that stopped resembling the invoice around month three.

How does Business Central handle ERP in manufacturing?

Dynamics 365 Business Central is Microsoft's cloud platform for mid-sized companies, and production is what puts it in this category at all. Works orders, multi-level bills of materials, routings, capacity scheduling and material requirements planning all ship in the Premium licence. The wider Business Central modules list reaches past the plant into sales, service and finance.

Two things give it an edge over the sector specialists competing for these plants. Finance underneath it is a full ERP, so job costs reach the general ledger without an interface between two products. ERP in accounting and ERP in manufacturing share one set of books here, and a plant with its own controller notices that inside the first month. 

Everything in the Microsoft stack around it reads the same data, so Outlook, Teams, Power BI and Excel stay in step. Plant managers who spend their day in spreadsheets tend to care about that more than the architecture.

Recent release waves have added Copilot across operations. Copilot for manufacturing drafts item descriptions and proposes matches, with a person approving every one. Reading and keying are the parts it takes away.

Sector specialists come at the same plant from a different angle, with deeper production tooling and a thinner ledger underneath. Dynamics 365 Business Central vs Epicor Kinetic is the comparison a discrete assembler ends up running.

On process ground the same decision goes by another name. Microsoft Dynamics 365 Business Central vs SYSPRO is where a batch producer lands. Either way it comes down to how much depth a plant needs on the production side.

Microsoft Dynamics 365 Finance and Operations vs Business Central is where a plant that has outgrown the mid-market draws its line. Heavy process work with recipe scaling and by-products belongs on the far side of it, along with very high-volume discrete production needing machine-level scheduling. Settling that before anyone drafts a paper for the board saves a second implementation inside three years.

How does Gestisoft implement ERP in manufacturing?

Production work at Gestisoft gets delivered bilingually from four Canadian offices, built on Business Central. Microsoft technology has been the firm's ground since 1997, and it holds Solutions Partner status.

The item master and the parts list come first, before any other module gets switched on. Every downstream function reads them, so a routing resting on a wrong component schedules work that can't happen.

What Gestisoft asks before building ERP in manufacturing

The answers shape every module that follows.

• How products are structured, and how deep the assemblies run
• Where subassemblies repeat across more than one finished item
• Which components arrive from outside North America
• What a costed job needs to tell the plant when it closes

Cross-border scope gets designed at that same point. Country of origin and tariff classification become fields on the item, so a CUSMA verification gets answered from the same place the production plan comes from. A manufacturer adding that after go-live pays to revisit every part record.

Few Canadian partners deliver Dynamics 365 and the production platform together. A quote raised in sales and the work order it becomes gets modelled once here.

Whoever mapped your parts list stays on the account afterwards, which is the whole point of keeping a Business Central specialist attached to a plant. The account doesn't get handed to a stranger at go-live.

Anything that only surfaces once real volume moves through the shop floor goes to Business Central support services, with the original design notes in front of them.

Every plant has one person who understands how the parts list truly works. Ask Gestisoft how that knowledge gets into Business Central before they retire.

Explore more:

1. Engineer to order manufacturing software
2. ERP manufacturing process
3. Excel vs ERP
4. Manufacturing accounting software
5. Manufacturing ERP benefits