ERP for manufacturing: how brands that make their own products run production and online sales

Product brands need a manufacturing ERP that runs work orders and bills of materials (BOMs) or recipes in one system with webshop and marketplace orders. Add batch tracking, expiry dates, landed cost and production costing, so every finished unit becomes sellable stock with a known cost.
That combination is what an ERP for manufacturing should deliver when your brand makes products and sells them online. Most brands start with inventory software and a production spreadsheet. The setup holds until order volume grows.
This guide covers how BOMs feed channel stock, which features to check, how traceability and landed cost work, and how to choose a system.
What is an ERP for manufacturing brands?
An ERP for manufacturing brands is one system that runs production and sales for companies that make what they sell. For brands selling online, a manufacturing ERP also links production output to webshop and marketplace orders in one stock record.
Factory systems solve a different problem. MRP (material requirements planning) software calculates which materials to buy and when. MES (manufacturing execution system) software tracks machines and operators on the shop floor.
Both tools help a plant with many production lines. A brand that makes products in batches and ships to consumers needs production and ecommerce sharing the same stock. If the category is new to you, start with what an ERP system does.
Why does standard inventory software break when you make your own products?
Standard inventory software breaks for product makers because it tracks finished items but has no native work orders, BOMs or recipe management. Most brands believe an inventory app plus a spreadsheet can handle assembly and online sales.
In practice, production planning drifts away from raw material stock and customer orders. Take a skincare brand that sells one face cream. Each jar of cream needs 4 components: the cream base, a glass jar, a lid and a label.
A Shopify sale reduces finished cream stock by one. Nothing reserves the components for the next batch. The planner finds out when the jar shelf is empty, while the webshop still shows stock that cannot be made in time.
The root cause is structural. Generic inventory tools have no BOM to break a sale into components, and no work order to turn components into finished goods. A manufacturing ERP for small business teams closes that gap by keeping recipes and sales orders in one record.
How do work orders and bills of materials connect to online sales?
Work orders and bills of materials connect to online sales by turning channel demand into production, then finished output into sellable stock. An ERP for manufacturers selling online runs that loop in four steps.
Prim.io's built-in manufacturing features include work orders, BOM/recipes, costing, batches, serial numbers, and expiry dates. The steps below show how those pieces fit together in any manufacturing ERP.
Step 1: define the BOM or recipe
A bill of materials or recipe is the list of components and quantities needed to make one finished unit. For the face cream, that list is base, jar, lid and label, with a quantity for each.
Recipes suit products made by weight or volume, like creams or sauces. BOMs suit assembled items, like a lamp with a base and a shade. Get the BOM right first, because every later step reads from it.
Step 2: create the work order from demand
A work order is an instruction to make a set quantity of one product, built from its BOM. Demand comes from open channel orders and stock reorder points.
When the work order is created, the ERP checks whether the components are in stock. Short components show up before production starts, while there is still time to buy.
Step 3: consume components and record output
Consuming components means the ERP deducts the materials a work order used and records the finished units it produced. Batch numbers and expiry dates get attached at this point, so each finished unit has a traceable history.
Actual usage can differ from the BOM, for example when a batch has waste. Recording actual quantities keeps stock counts and unit cost accurate.
Step 4: finished goods become channel stock
Finished goods become channel stock when the work order closes and the output joins available inventory. Every connected webshop and marketplace then sells from that same stock count.
Nobody re-keys numbers between a production sheet and the store admin. The planner and the finance team read the same record.
What features should product brands look for in a manufacturing ERP?
Product brands should look for manufacturing ERP features that link production to stock and sales channels. The table lists each feature, why it matters online, and a question to ask any vendor.
| Feature | Why it matters for an online brand | Question to ask the vendor |
|---|---|---|
| Work orders | Turns channel demand into planned production runs | Can a work order start from open sales orders? |
| BOM and recipes | Breaks each product into components and quantities | Does it handle assembled items and recipes by weight? |
| Production costing | Gives a true cost per finished unit | Does unit cost update from actual component usage? |
| Batches, serial numbers and expiry dates | Supports recalls and first-expiry picking | Can one batch be traced to every order that shipped it? |
| Landed cost | Adds freight and duties to component cost | Do freight and duty costs flow into BOM cost? |
| Channel connectors | Brings orders in and sends stock out, often as paid add-ons | Which connectors exist, and what does each cost per month? |
| Multi-warehouse | Tracks materials and finished goods by location | Can production pull from one warehouse and ship from another? |
| BI and reporting | Shows margin by product and channel | Can production cost and channel sales appear in one report? |
| AI assistant | Answers questions from your own business data | Does the AI need approval before it changes records? |
Use the question column as your demo script. Ask each question with your own product data on screen.
How does batch tracking work in a manufacturing ERP?
Batch tracking in a manufacturing ERP records which component lots went into each production run and which customer orders received the output. Serial numbers do the same for single units, and expiry dates tell the warehouse which stock to ship first.
When a supplier flags a bad ingredient, the brand can list every affected batch and the orders that shipped it. That speed matters for any recall, and food brands face formal rules.
The FDA Food Traceability Rule (FSMA 204) requires covered firms to provide traceability records within 24 hours of an FDA request. The compliance date is July 20, 2028.
The EU General Food Law (Regulation (EC) No 178/2002) requires food business operators to trace one step back and one step forward. Batch records that sit next to sales orders turn both directions into a quick search.
How does landed cost change your true product margin?
Landed cost changes your true product margin by adding freight, duties and insurance to the purchase price of each component. When landed cost flows into the BOM, the unit cost of every finished product reflects what you actually paid.
Here is an example for the face cream's glass jars, bought in one shipment of 10,000 units. All numbers are for illustration only.
| Cost line (example) | Example amount | Example cost per jar |
|---|---|---|
| Purchase price | €4,000 | €0.40 |
| Freight | €600 | €0.06 |
| Customs duties | €300 | €0.03 |
| Insurance | €100 | €0.01 |
| Landed cost | €5,000 | €0.50 |
In the example, each jar costs €0.50 landed against €0.40 on the supplier invoice. That is 25% more, or €1,000 across the shipment that a purchase-price BOM would miss.
Repeat the math for the base, lid and label, and the gap in unit cost grows. Leave out taxes you reclaim or collect, such as EU VAT or US sales tax, and confirm the treatment with your accountant.
How do product brands choose a manufacturing ERP?
Product brands choose a manufacturing ERP by testing it against their own products and costs before signing. These five steps keep the evaluation practical.
- Map your process on one page. Show each step between a supplier order and a shipped customer order.
- Test with your real BOM in a demo account. Build one product and run one work order, then check that stock and unit cost update.
- Check which channel connectors exist. Ask what each connector costs per month, since many are paid add-ons.
- Check published pricing and onboarding. Ask for the plan price and the one-time onboarding fee in writing, and whether prices include VAT.
- Check the go-live time. Ask how many weeks a brand like yours takes to go live, and what makes projects run longer.
For reference, here is how Prim.io prices connectors. Store, marketplace and courier connectors are priced per connector (€20 to €50 per month); finance connectors are free. A marketplace connector is €50 per month, a webshop €30 and a courier or 3PL €20.
How Prim.io handles manufacturing for ecommerce brands
Prim.io handles manufacturing for ecommerce brands with built-in AI on top of one shared record for production and sales. The Prim.io AI assistant answers from the company's own sales, stock and finance data. It also reads invoices, corrects addresses and matches payments.
Prim.io MCP is built to connect Claude, ChatGPT and Cursor, with per-user permissions and approval before any change. See the Prim.io MCP page for availability.
Behind the AI sits an all-in-one ERP, BI and CRM built for ecommerce. Prim.io is a cloud ERP with built-in AI for ecommerce and multi-channel brands, running orders, stock, finance, CRM, production and BI in one system.
The manufacturing features listed earlier run inside that same system. Finished goods from a work order join the stock your channels sell from.
COCOSOLIS has relied on Prim.io for 9 years for production and sales operations. The brand opens new markets without changing systems.
Free demo account, no credit card needed, cancel anytime.
Why ecommerce brands choose Prim.io
Ecommerce brands choose Prim.io for its order scale, native integrations, built-in BI and published Prim.io pricing plans.
- Prim.io handles 3.1M+ orders monthly and offers 50+ native integrations, listed on the Prim.io integrations page.
- Built-in BI is powered by Qlik, so production and sales reports come from one data set.
- Prim Plus is €180, Prim Pro €540 and Prim Enterprise €1,710 per month, billed annually, excluding VAT, with 3, 5 and 15 users included.
- Go-live takes about 6 weeks on average, 5 to 8 weeks depending on complexity. Onboarding costs €1,300 one-time (Prim Plus, Prim Pro) or €3,900 (Prim Enterprise).
Manufacturing ERP FAQ
These answers cover common questions about manufacturing ERP for product brands that sell online.
What does a manufacturing ERP do?
A manufacturing ERP plans production and records the materials, finished goods, sales and costs behind it in one system. For brands selling online, it also links work orders and BOMs to webshop and marketplace orders. Every finished unit becomes sellable stock with a known cost, and every sale points back to its materials.
How do BOMs work in Prim.io?
In Prim.io, a BOM or recipe lists the components and quantities needed for one finished product. Work orders use the BOM to plan production runs, and costing builds unit cost from those components. Batches, serial numbers and expiry dates can be recorded on the output, so finished goods stay traceable once they reach your sales channels.
Can manufacturing connect to Shopify and WooCommerce?
Yes, Prim.io connects manufacturing output to Shopify and WooCommerce through webshop connectors, priced at €30 per month each. Finished goods from work orders join the same stock those stores sell from. Marketplace connectors cost €50 per month and courier or 3PL connectors €20, so list the channels you need before comparing plans.
What features matter most in a small business manufacturing ERP?
The features that matter most in a small business manufacturing ERP are work orders, BOMs or recipes, batch tracking with expiry dates, and production costing. Next come landed cost and channel connectors for your stores. Built-in BI ties these together by showing cost and sales per product, with no spreadsheet exports needed.
How much does Prim.io cost?
Plans from €180 per month, billed annually, excluding VAT. Onboarding is a one-time €1,300 for Prim Plus and Prim Pro, or €3,900 for Prim Enterprise. Store, marketplace and courier connectors cost extra, at €20 to €50 per month each, while finance connectors are free.
Conclusion: your manufacturing ERP checklist
Your manufacturing ERP checklist comes down to five actions that connect the production floor to every sales channel.
- Define BOMs and work orders in your software stack.
- Connect manufacturing output to ecommerce inventory and sales channels.
- Track batches, serial numbers and expiry dates for traceability.
- Calculate landed cost for true margins.
- Review production efficiency and sales data in built-in BI powered by Qlik.
The fastest test is your own product. Build its BOM in a demo account and run one work order.
Free demo account, no credit card needed, cancel anytime.
Table of content
Table of content
Meet an expert
Prefer to talk? Call our team directly.
Ready to see it for yourself?
The best way to understand Prim.io is to try it. Start with a free demo account and explore at your own pace.

