If you make things you can count, such as bikes, furniture, electronics, machines, doors, shoes or auto parts, you run discrete manufacturing. Your product has a clear shape, a list of parts and a number of units. That is different from making a liquid, a chemical or a flour batch, where you cannot count the pieces.
This difference matters when you choose ERP. A system built for process industries can feel awkward for a discrete factory, and the reverse is also true.
This guide explains what to look for, what it costs in Bangladesh, and how to run a trial that tells you the truth before you sign.
Discrete vs process manufacturing: the quick difference
| Discrete | Process | |
|---|---|---|
| What you make | Countable units | Batches, volume, weight |
| Recipe | Bill of materials (BOM) and routing | Formula and recipe |
| Example | Bike, chair, sewing machine, shoe | Paint, chemical, food, drink |
| Tracking | Serial or lot number | Batch and expiry |
| Common issue | Part shortage, assembly delays | Yield, quality, consistency |
Many factories mix both. A footwear unit counts pairs, but also uses glue and chemicals. A good ERP handles the mix. For the general flow, see how ERP works in manufacturing.
What a discrete manufacturing ERP must do well
1. Multi-level BOM
A bike has a frame, wheels, an engine and electrical parts. Each of these has its own parts. The ERP should handle sub-assemblies and show the total need for one finished bike. It should also handle BOM versions when you change a design.
2. Routing and work centres
A routing is the path a product takes: cutting, welding, painting, assembly, testing, packing. The system should know machines, labour, time and cost at each step.
3. Production orders and work orders
The plan should create orders by product and by step. Supervisors should see what to make, in what order and with which material.
4. Material planning (MRP)
It should tell you what to buy, how much, and by when. This matters most when you have many small parts with long import lead times. See production planning ERP for factories.
5. Serial and lot tracking
For bikes, electronics and machines, you need to track by serial number for warranty and recalls. For footwear and apparel, you may track by size, colour and style.
6. Shop floor entry
Output, scrap, rework and downtime should be easy to enter on a tablet or phone. If entry is hard, people will skip it.
7. Quality control
Incoming, in-process and final checks, with reasons for rejection and rework.
8. Costing
Actual cost by order, with material, labour, machine and overhead. This is where many owners find the real margin.
9. Sales, dealer and after-sales
For auto and bike makers, dealer orders, spare parts and service records matter. See our PinCraft ERP for automotive business, bike ERP software in Bangladesh and dealership management software.
How much does discrete manufacturing ERP cost in Bangladesh?
Note: These are planning ranges based on market patterns, not a price list. The right price depends on users, modules, complexity and support. Get a written quote.
For a Bangladeshi discrete manufacturer, the budget usually has these parts:
| Cost part | What it covers | Typical range (BDT, estimate) |
|---|---|---|
| Software | License or yearly subscription | 1,50,000 to 15,00,000+ per year |
| Implementation | Setup, BOM and data import, configuration | 1,00,000 to 10,00,000+ |
| Training | Staff and supervisors | 30,000 to 2,00,000 |
| Hardware | Tablets, barcode scanners, labels, server (if on-premise) | 50,000 to 5,00,000+ |
| Customization | Special reports or flows | Per day rate or fixed quote |
| Support | Yearly support and updates | Often 15% to 25% of license, or included in subscription |
Rough size guide:
- Small plant (20 to 50 users, one site): lower end of the ranges, simple modules.
- Mid-size plant (50 to 200 users, multiple lines): mid ranges, with MRP, costing and QC.
- Large or multi-plant group: upper ranges, with integrations and custom work.
For wider budgeting, read ERP software cost in Bangladesh, ERP software price in Bangladesh and ERP implementation cost.
What pushes the cost up or down
Up:
- Many levels in your BOM
- Many products and variants (size, colour, model)
- Several plants or warehouses
- Custom reports and approval flows
- Integration with machines, barcode or other systems
- Messy data that needs heavy cleanup
Down:
- Clear BOMs and item master before the project starts
- Standard flows with small changes
- Cloud deployment
- Phased rollout: stock and purchase first, production next
- A strong internal owner who answers questions fast
Hidden costs to ask about
- Fee for each extra user or plant
- Price for new modules later
- Cost of customizations after go-live
- Charges for data migration
- Upgrade cost between versions
- Support hours and response time
- Cost to export your data if you leave
Why a trial matters more for discrete manufacturing
A sales demo shows a clean example. Your factory is not clean. It has odd BOMs, change in design, loose parts and workers who enter data in a hurry.
A proper trial tells you three things:
- Can the system model your real product?
- Can your people use it on the floor?
- Are the numbers right?
A 30-day trial plan you can use
Before the trial (week 0):
- Pick one product family, ideally your top seller or most painful product
- Collect the BOM, routing, item list with units, and current stock
- List three real problems you want to test
- Name two users from stores, production and accounts
Week 1: Set up
- Load items, BOMs and routings
- Load opening stock for the test area
- Create users and roles
Week 2: Run purchase and stock
- Create a purchase order from MRP
- Do a goods receipt
- Check if stock and value match your books
Week 3: Run production
- Create a production order for a real batch
- Issue material, record output, scrap and rework
- Check the cost report
Week 4: Sell and review
- Create a sales order, delivery and invoice
- Compare actual cost with your Excel cost
- Collect feedback from supervisors and accounts
Trial scorecard
| Test | Pass? | Notes |
|---|---|---|
| BOM with 3 or more levels loads correctly | ||
| MRP suggests correct purchase quantity | ||
| Supervisor can enter output in under 2 minutes | ||
| Scrap and rework are recorded with reason | ||
| Order cost matches a manual check within a small gap | ||
| Stock matches physical count | ||
| Reports needed by owner are available | ||
| Vendor responds to questions within agreed time |
If the system passes most of these on your own data, you can move ahead with confidence. Ask for a written plan for rollout and price at the end of the trial.
Red flags in a trial
- The vendor will not use your real BOM
- Every missing feature is ‘a custom job’
- Workers find data entry slow or confusing
- Stock and cost do not reconcile, and nobody can explain why
- The trial is only a sales demo, not a working test
Implementation tips for discrete factories
- Start with a clean item master. Fix duplicate items, wrong units and missing codes.
- Freeze BOM changes during go-live week.
- Train supervisors, not only managers.
- Run the old system beside the new one for one cycle.
- Count stock physically before the cut-over.
- Review after 90 days. Adjust rules, reports and permissions.
Our ERP implementation steps guide lists the full path.
Examples from different discrete industries
- Footwear: size-wise BOM, cutting, stitching, lasting, finishing. See ERP for footwear industry and PinSole.
- Auto and bikes: multi-level BOM, serial numbers, dealers and spare parts. See ERP for auto industry.
- Furniture, plywood and board: cutting plans, wastage and finishing. See plywood and board ERP.
- Tiles and ceramic: batch and shade tracking along with unit counts. See tiles and ceramic ERP.
Frequently asked questions
Is a free ERP trial available? Ask the vendor. Many offer a guided trial or a pilot on one product line. Always insist on your own data.
How long does a discrete manufacturing ERP rollout take? A small plant may go live in two to three months. A multi-line plant often needs four to six months.
Can I start with only stock and purchase? Yes. This is a good first phase. Add production, costing and QC next.
Do I need barcode scanning? Not on day one. It helps when you have many parts, fast movement or serial tracking.
Can I connect forecasts to production? Yes. See demand forecasting in manufacturing ERP.
What about HR for my factory staff? Attendance and payroll can link to production cost. See what is HR software and our HR software in Bangladesh guide.
Final word
Choose discrete manufacturing ERP like you would choose a machine: test it with your own material, on your own floor, before you pay. See our manufacturing ERP software hub and ask for a trial built around your real BOM.