Why Light Manufacturers Need MRP, And Where Cin7 Fits

Light manufacturers occupy an awkward middle ground. They need something between spreadsheets and manual reorder points on one side, and the full weight of enterprise MRP II systems built for multi-plant, multi-currency operations on the other. Cin7's MRP module handles this segment well when it's configured to match the scale of the business, using only the settings the operation actually needs rather than everything the platform offers.

The mistake we see most often is treating MRP setup as a checkbox exercise. A business turns on the module, accepts the default run parameters, and wonders three months later why purchase suggestions don't match reality. MRP is only as good as the BOM structure, demand source configuration, and inventory data feeding it. Get any of that wrong and the MRP run produces numbers nobody trusts, which defeats the entire point of having it.

Before You Start: Module Requirements And Subscription Setup

Cin7 Core requires the MRP module added to the base subscription (a paid add on for subscriptions created after February 1, 2024) before MRP becomes available. The advanced manufacturing module is a separate requirement on top of that, and it only comes into play if the operation runs production BOMs and work orders. Light manufacturers relying solely on standard assembly BOMs for simple kitting, or on purchase and transfer logic without production orders, can run MRP on the base inventory system with just the MRP module added. The distinction is not visible until someone is already inside the platform looking for a menu that does not exist for their subscription tier. Confirm the correct modules are active for the operation before doing anything else. Then check that product records have accurate lead times, supplier information, and reorder settings populated, and that Supply Rules are configured at the location level. A Supply Rule tells Cin7 whether a given item at a given location is purchased, transferred, assembled, or produced, and MRP relies on that assignment to generate a suggestion at all. If demand exists for a SKU but no Supply Rule is assigned to it at that location, MRP cannot generate a suggested order and throws a warning instead. Missing Supply Rules, alongside incomplete product records, are among the most common reasons a first MRP run produces suggestions that make no operational sense. Reviewing Cin7 Core's general settings before turning on MRP can save a lot of rework later.

Building Your BOM Structure For Accurate MRP Runs

Multi-level BOMs are where light manufacturers most often get MRP wrong. If finished goods are assembled from sub-assemblies, each sub-assembly needs its own BOM, not a flattened single-level structure that lists every raw material against the finished product.

A single-level BOM might look simpler to set up, but it breaks MRP's ability to plan production of the sub-assembly itself, which means someone ends up manually tracking component availability at the exact layer MRP was supposed to handle. For a light manufacturer building, say, packaged retail kits from componentry, that often means raw materials feeding into components, components feeding into sub-assemblies, and sub-assemblies feeding into the finished kit, sometimes with additional layers depending on how the product is engineered. Each level needs its own accurate BOM with correct quantities and unit costs.

Building the BOM correctly only pays off if the MRP run is told to use it. When executing the run, the BOM Explosion setting needs to be selected in the run parameters. Leave it unchecked, and MRP only generates a demand suggestion for the top level parent SKU. It will not break down that demand through the sub-assembly and component layers underneath, no matter how carefully those BOMs were built. Get the structure and the run parameters right together, and the rest of the MRP setup becomes far more forgiving. It also directly protects against the kind of BOM accuracy and cost margin drift that quietly erodes profitability over time.

Configuring Demand Sources And Run Parameters Correctly

When a new MRP run is started from Inventory, the operator defines which demand sources are included in the calculation: sales orders, production orders, assembly orders, and stock transfers. The selection matters more than most documentation lets on.

If unconfirmed sales orders are included in demand, MRP will generate purchase suggestions based on deals that might not close, inflating raw material buys. If transfers between warehouses are excluded, MRP will not account for stock already committed to move, and the result is over-ordering for a location that's about to receive inventory anyway. The right configuration depends on how firm the sales pipeline is and how many locations are being balanced across. A light manufacturer running a single facility with confirmed order backlogs should weight demand sources differently than one running multiple warehouses with transfer heavy replenishment, which is also where multi-location transfer errors in Cin7 tend to surface first.

Running Your First MRP Report: What To Expect And How To Read It

The first MRP run rarely looks clean. Expect purchase suggestions that seem too aggressive or too conservative until the output has been validated against what's known about current stock and open orders. Check whether the suggested quantities match the actual understanding of current demand, and whether lead times used in the calculation match actual supplier performance.

If the numbers look off, the likely causes are a BOM quantity error, a lead time that was never updated after a supplier change, a demand source setting that's pulling in orders it shouldn't, or a Supply Rule that's missing or pointed at the wrong method. Trace the output back to its source before adjusting anything downstream, the same way a purchase suggestion that's clearly wrong should be investigated rather than just overridden.

Common setup mistakes That Break MRP Accuracy

The same handful of errors show up across most light manufacturer implementations: stale lead times that no longer reflect actual supplier performance, BOMs that were built once and never updated after a component substitution, demand sources configured once at setup and never revisited as the sales process matured, Supply Rules that were never assigned or were left on the wrong method after a process changed, and reorder points set arbitrarily rather than calculated from actual lead time and usage data.

None of these show up as an obvious error message. They show up as an MRP report that slowly drifts from reality, and a team that stops trusting it and goes back to manual ordering, which is why getting the team to adopt and rely on the system is part of the implementation work itself, not something that happens on its own after go-live. Data governance drives MRP accuracy, which is exactly the kind of system governance problem that compounds if it's left unaddressed.

Where AI-driven Demand Planning Fits In, And When You Don't Need It Yet

Cin7 Core does not require a premium add on to bring historical sales trends into an MRP run. The native Sales Demand Forecast report uses historical sales data, including moving averages and weighted averages, to build a forecast that can be exported as a CSV or fed directly into MRP. For a lot of light manufacturers, that native report already covers what's needed.

ForesightAI sits above that as a separate, premium predictive add on. It replaces standard demand forecasting with predictive planning based on historical patterns, rather than relying purely on confirmed orders and reorder points. For a light manufacturer with seasonal or promotional demand swings, that can meaningfully improve purchasing accuracy.

But it's not the right starting point for every business. If the core BOM structure, demand sources, Supply Rules, and reorder logic aren't configured properly yet, adding a predictive layer on top just means forecasting on a foundation that isn't reliable. Get the fundamentals working first, using the native Sales Demand Forecast report where historical trends are genuinely needed. Layer in ForesightAI once the base MRP setup is producing numbers the team already trusts.

When To Bring In An Implementation Partner

Cin7's manufacturing tools are built to connect production planning with inventory the way production planning and MRP software that integrates with Xero is meant to work, and light manufacturers running multi-level BOMs with regular component substitutions see that connection hold up in practice once the setup is right. Most light manufacturers discover that MRP accuracy depends on decisions made outside the module itself, including BOM structure, product data quality, demand source logic, Supply Rule assignment, and the ongoing discipline to keep all of it current as the business changes. That's implementation work, and it's the layer where most DIY setups stall.

Fiskal is the Cin7 specialist building Cin7 MRP setups for product businesses that need the system to hold up under real operating conditions, not just meet a deployment deadline.

Frequently Asked Questions

What is MRP?

What production planning tools does Cin7 offer?

Cin7 Core offers MRP, multi-level BOM management, work order management, and production scheduling tools within its advanced manufacturing module. These tools connect inventory, production, and sales data into a single planning view without separate systems.

Can Cin7 Core manage manufacturing and material requirements planning?

Yes, Cin7 Core supports manufacturing operations including BOM management, work orders, and MRP. The MRP module itself only requires the base inventory system for simple assembly and purchase and transfer logic, while production BOMs and work orders additionally require the advanced manufacturing module. Light manufacturers running assembly based production can configure MRP to match their BOM structure and demand patterns.

How does Cin7 Core compare with Cin7 Omni?

Cin7 Core is built for product businesses with manufacturing, inventory, and wholesale complexity, while Cin7 Omni is focused on omnichannel retail and order management. Businesses with production and BOM requirements typically need Cin7 Core rather than Omni.

How does Cin7 support shop floor control?

Cin7 Core supports shop floor control through work orders that track production stages, material consumption, and labor against a BOM. Real-time inventory updates during production give visibility into what's been consumed and what remains available for the next run.

Material requirements planning is a system that calculates what materials and components a business needs to purchase or produce, based on demand from sales orders, production schedules, and current inventory levels. It uses BOM structures and lead times to generate purchase and production suggestions.

Is Cin7 Core the same product as DEAR Inventory?

Cin7 Core was previously known as DEAR Systems before Cin7 acquired the platform and rebranded it. The underlying product has continued to develop since the acquisition, but the core inventory and manufacturing functionality traces back to DEAR.

How does Cin7 Core allocate costs for products?

Cin7 Core allocates costs using methods including standard cost, FIFO, and landed cost allocation across BOM levels. For manufactured products, costs roll up through each BOM level, so accurate component costing at the lowest level directly affects the accuracy of finished good costs.

Can Cin7 Core export inventory and report data?

Yes, Cin7 Core supports exporting inventory, production, and financial report data for use in external BI tools or accounting systems. This is a common requirement for product businesses that need reporting beyond what's available natively in the platform.

Does Cin7 Core support barcode scanning and warehouse picking?

Cin7 Core supports barcode scanning for receiving, picking, and stock movements across warehouse locations. This integrates with the same inventory data used in MRP calculations, so accurate scanning directly improves MRP accuracy.

How difficult is Cin7 Core to implement and onboard?

Cin7 Core implementation difficulty depends heavily on the complexity of BOM structures, integrations, and existing data quality, not just the software itself. Most light manufacturers underestimate the data governance work required, including Supply Rule assignment and BOM Explosion configuration, which is why implementations that look complete at go-live often need rework within months. It's the reason Fiskal builds MRP setups with that data governance work included from the start, rather than treating it as a follow-up project.

How is cost calculated for coproducts, byproducts, and joint production products?

Cin7 Core allows cost allocation methods for coproducts and byproducts, including approaches like net realizable value, which is recommended when separable costs after the split-off point are significant. Getting this allocation right matters directly for margin reporting on joint production processes, and it's the kind of setup detail Fiskal builds into a Cin7 MRP implementation rather than leaving for a business to discover later.

What is a production scheduler?

A production scheduler is a tool that plans and sequences work orders across available capacity, time, and resources. In Cin7 Core, production scheduling connects to MRP output, since planned production needs to reflect both material availability and shop floor capacity.

What is a production scheduler?

A production scheduler is a tool that plans and sequences work orders across available capacity, time, and resources. In Cin7 Core, production scheduling connects to MRP output, since planned production needs to reflect both material availability and shop floor capacity.

Does Cin7 Core integrate with Shopify and Xero?

Yes, Cin7 Core integrates natively with both Shopify and Xero, syncing inventory, order, and financial data between the platforms. These integrations are common in light manufacturing businesses that sell direct to consumer while managing accounting separately in Xero.

Can Cin7 Core manage Amazon FBA inventory and fulfillment?

Cin7 Core supports Amazon FBA integration, syncing inventory levels and order data between FBA and the broader inventory system. This keeps MRP demand calculations aware of Amazon channel sales alongside other sales channels.

How does Cin7 Core compare with Katana?

Cin7 Core offers broader inventory and multichannel functionality alongside manufacturing, while Katana is built primarily around production and MRP for smaller manufacturers. Businesses that need manufacturing plus multichannel sales and accounting integration typically outgrow Katana's scope faster than Cin7 Core's.

Can Cin7 Core prevent overselling across Shopify and multiple warehouses?

Yes, Cin7 Core syncs real-time inventory levels across Shopify and multiple warehouse locations to prevent overselling. This relies on accurate sync mapping and inventory governance, which is often where DIY setups break down.

What is a capacity planner?

A capacity planner is a tool that visualizes available production resources, such as labor and equipment time, against planned work orders. In Cin7 Core, capacity planning works alongside MRP to make sure material availability and production capacity are planned together rather than in isolation.

Run a Cin7 Core Health Check

If your Cin7 setup has not been reviewed since a channel launch, a warehouse change, or a staff transition, a Diagnostic Call can identify where configuration may have drifted from how the business now operates, before it shows up in reconciliation or margin reporting.

Share on your socials.

Finance Ops:
Bookkeeping
Controlling
FP&A
Industries

Why Fiskal:
About us
Customer Stories
Careers
Contact Us

Contact Details:
+1 (954) 415-7895 or +1 (267) 717-7923
info@fiskalfinance.com
Offices:
Florida
New York
Pennsylvania
Stellenbosch

Resources
Blog
The Fiskal Score
Cin7 Academy
FAQs
Privacy Policy

Cin7 Solutions:
Problems We Solve
Integrations
Report Accuracy
Forecasting & MRP
Cin7 Implementation
Cin7 Support