ERPNext for Manufacturing in India: Complete Workflow (BOM → MRP → Work Orders → QC → Dispatch)

For Indian manufacturers—whether you’re running a metal fabrication unit in Ahmedabad, an FMCG packaging line in Chennai, or an auto-component shop in Pune—the ERPNext manufacturing workflow isn’t just about documenting what you make. It’s about creating a disciplined, auditable trail from the moment someone orders something to the second it leaves your dock with the right paperwork.

I’ve seen manufacturers operate ERPNext beautifully for years, and I’ve also watched implementations collapse because teams skipped fundamental workflow steps or customized too early. This guide walks you through the actual ERPNext manufacturing workflow as it works in practice—not just theory—with specific attention to Indian manufacturing realities: job-work challans, batch expiry tracking, multi-warehouse transfers, rejection loops, and the interplay between production and GST compliance.

What “Complete Workflow” Actually Means

When we say “complete ERPNext manufacturing workflow,” we’re talking about the full production cycle that a typical Indian SME manufacturer needs:

It’s not just modules—it’s the actual sequence of decisions, documents, stock movements, and approvals that happen when raw material becomes a finished good and gets dispatched to a customer.

In ERPNext terms, this covers:

• Upstream: How demand triggers material planning and procurement
• Production floor: How Work Orders, Job Cards, and Stock Entries track material consumption and transformation
• Quality gates: Where inspection happens (incoming RM, in-process WIP, outgoing FG)
• Downstream: How finished goods link to Sales Orders, get picked, packed, and invoiced

Practical tip: A “complete” workflow doesn’t mean you use every single ERPNext feature. It means you have a documented, repeatable process where every production batch can be traced forward (which customer got it?) and backward (which raw material lot was used?). That’s what auditors and customers actually care about.

For Indian manufacturers, “complete” also means your workflow naturally accommodates:

Handling rejections and rework without breaking your costing

Sending materials to job-workers with proper challans (India Compliance App handles ITC-04 reporting for subcontracting)

Tracking batch numbers and expiry dates for pharma/FMCG compliance

Managing material across multiple warehouses or branch locations with different GST registrations

Understanding the ERPNext Manufacturing Workflow: The Big Picture

Before diving into individual stages, here’s how the ERPNext manufacturing workflow pieces fit together:

┌─────────────────┐
│  Sales Order    │ ← Customer places order
└────────┬────────┘
         ↓
┌─────────────────┐
│ Production Plan │ ← MRP calculates material needs
│     or MRP      │   (checks BOM, current stock, pending POs)
└────────┬────────┘
         ↓
┌─────────────────┐
│  Work Order     │ ← Manufacturing instruction created
│  (with BOM)     │   Reserves raw materials, schedules operations
└────────┬────────┘
         ↓
┌─────────────────────────────────────┐
│ Stock Entry:                        │
│ Material Transfer for Manufacture   │ ← Raw materials → WIP warehouse
└────────┬────────────────────────────┘
         ↓
┌─────────────────┐
│   Job Cards     │ ← Shop floor executes operations
│ (if operations  │   Tracks time, employees, workstation usage
│   are defined)  │
└────────┬────────┘
         ↓
┌──────────────────────┐
│ Quality Inspection   │ ← In-process QC checkpoints (optional)
│   (In-Process)       │
└──────────┬───────────┘
           ↓
┌─────────────────────────────────┐
│ Stock Entry: Manufacture        │ ← Consumes WIP, creates finished goods
│ (Finished Goods Receipt)        │   Assigns batch/serial numbers
└────────┬────────────────────────┘
         ↓
┌──────────────────────┐
│ Quality Inspection   │ ← Final QC before dispatch
│   (Outgoing)         │
└──────────┬───────────┘
           ↓
┌─────────────────┐
│ Delivery Note   │ ← Pick, pack, dispatch to customer
│   + Invoice     │   Generate e-Way Bill (India)
└─────────────────┘

Watch out: Many teams try to skip the “Material Transfer for Manufacture” step to save time. This breaks traceability—you won’t know which specific batch of raw material went into which finished batch. If you’re in pharma, food, or any regulated industry, this will fail audits.

Stage 1: Setup Prerequisites (Item Masters + Warehouses + BOMs)

The ERPNext manufacturing workflow starts long before you create your first Work Order. You need clean master data.

1.1 Item Masters

Every raw material, sub-assembly, and finished good needs an Item record. According to ERPNext documentation, key settings for manufacturing items include:

• Item Type: Set to “Manufactured” for items you produce
• Default BOM: Link to the active Bill of Materials
• Warehouses: Define default Source (raw material), WIP, and Target (finished goods) warehouses
• UOM conversions: If you buy raw material in KG but consume in Grams, set up UOM conversions
• Batch/Serial tracking: Enable “Has Batch No” or “Has Serial No” as needed (ERPNext batch tracking documentation)

Practical tip: Use a logical naming convention. For example: RM-STEEL-304-6MM for raw materials, WIP-BRACKET-A1 for work-in-progress, FG-BRACKET-PAINTED for finished goods. This makes BOM navigation much easier.

1.2 Warehouse Structure

Manufacturing requires at least three warehouse types:

1. Stores/Raw Material Warehouse: Where purchased materials land
2. Work-in-Progress (WIP) Warehouse: Temporary holding during production
3. Finished Goods Warehouse: Where completed products wait for dispatch

For Indian manufacturers operating across locations, you might have:

• Ahmedabad-Stores, Ahmedabad-WIP, Ahmedabad-FG
• Mumbai-Stores, Mumbai-WIP, Mumbai-FG

Each location can have its own GST registration, which the India Compliance App handles during invoicing.

Practical tip: Don’t create too many warehouses initially. Start with the minimum viable structure. You can always split warehouses later, but merging them is painful.

1.3 Bill of Materials (BOM) Creation

A BOM is the “recipe” for making something. ERPNext supports multi-level BOMs, meaning your finished good can contain sub-assemblies that themselves have BOMs.

Key BOM fields:

• Item to Manufacture: The output product
• Quantity: How many units this BOM produces (usually 1)
• Items table: List all raw materials with quantities
• Operations table (optional): Manufacturing steps with workstation, time, and cost

According to ERPNext BOM documentation, “Workstations are defined only for product costing and Work Order Operations scheduling purposes not tracking inventory. Inventory is tracked in Warehouses set in the Items table of the BOM.”

Common pitfall I’ve seen: Teams create BOMs without specifying source warehouses for each item. Later, when creating Work Orders, they have to manually select warehouses every time. Fix this upfront in the BOM.

1.4 BOM Versioning and Engineering Changes

Manufacturing isn’t static. When your engineering team changes a design, you need BOM revision control.

ERPNext approach:

• When you need to modify a BOM, cancel the old one and create a new version
• Link the new BOM as the default in the Item master
• Work Orders created after the change use the new BOM automatically
• Old Work Orders retain the original BOM (historical accuracy)

Practical tip: In the BOM form, enable “Do Not Explode” checkbox for specific sub-assembly items if you want to track them as complete units rather than exploding to raw components. This is useful when you manufacture certain sub-assemblies separately and stock them (ERPNext BOM features).

Stage 2: Material Planning via MRP

Once you have BOMs and sales demand, ERPNext’s Production Planning and Material Requirements Planning (MRP) logic kicks in.

2.1 How MRP Works in ERPNext

Material Requirements Planning calculates:

• What raw materials you need
• How much quantity is required
• When you need them (considering lead times)

ERPNext’s MRP functionality works through Production Plans. According to Frappe documentation, “Create production plans based on material requests or sales orders, then the MRP system will generate material requirements in one go.”

The MRP flow:

1. Create a Production Plan from Sales Orders or Material Requests
2. ERPNext explodes the BOM to calculate gross requirements
3. System checks current stock levels and open Purchase Orders
4. Net requirements are calculated (Gross – Available – In-Transit)
5. Generate Material Requests or Purchase Orders for shortfall

Practical tip: In the Production Plan, enable “Include Exploded Items” to see all raw materials across multi-level BOMs. This gives you a complete procurement view (ClefinCode MRP guide).

2.2 Material Request Generation

From a Production Plan, you can create Material Requests with one click. These trigger the procurement workflow:

• Material Request (Purchase) → Request for Quotation → Purchase Order
• Material Request (Manufacture) → Work Order (for sub-assemblies)
• Material Request (Material Transfer) → Stock Entry (inter-warehouse transfer)

Watch out: If your lead times are inaccurate in Item masters, MRP will give you the wrong required dates. Update lead times based on actual supplier performance, not wishful thinking.

Stage 3: Work Order Creation and Operations

A Work Order is the manufacturing instruction. It tells your shop floor what to make, how many, using which BOM, and by when.

3.1 Creating Work Orders

Work Orders can be created:

• Directly from a Sales Order (Make → Work Order button)
• From a Production Plan (batch creation)
• Manually (for make-to-stock scenarios)

According to ERPNext Work Order documentation, required information includes:

• Item to Manufacture: Links to BOM
• Quantity to Manufacture: Production target
• Source Warehouse: Where to pull raw materials from
• WIP Warehouse: Intermediate storage during production
• Target Warehouse: Where finished goods land
• Planned Start Date: Scheduling parameter

Practical tip: If you link a Work Order to a Sales Order, ERPNext automatically reserves materials for that specific customer order. This prevents you from accidentally allocating the same material to two different orders.

3.2 Operations and Workstations

If your BOM includes Operations (manufacturing steps like “Cutting,” “Welding,” “Assembly”), ERPNext creates Job Cards for each operation when you submit the Work Order.

Operations track:

• Which Workstation (machine/line) performs the work
• Time required (hours/minutes)
• Operating cost based on workstation hourly rate
• Employees assigned to the operation

According to ERPNext Job Card documentation, “Job Card allows each Operation’s workstation to issue a ‘Material Request’ and ‘Stock Transfer to Manufacture’ for raw material required against a Job Card.”

Practical tip: If you’re not ready to track detailed operations and time, it’s fine to create BOMs without operations initially. You can always add them later. Don’t let operation complexity delay your go-live.

Stage 4: Material Transfer and WIP Tracking

Once you submit a Work Order, you need to physically move raw materials to the production area. ERPNext handles this via Stock Entry: Material Transfer for Manufacture.

4.1 The Material Transfer Step

Click “Start” on a submitted Work Order to create this Stock Entry. It moves materials from:

• Source Warehouse (e.g., Stores)
• To WIP Warehouse (e.g., Production-Floor-WIP)

According to ERPNext Stock Entry documentation, “In the manufacturing process, raw-materials are issued from the stores to the production department (generally WIP warehouse). This Material Transfer entry is created from Work Order. Items in this entry are fetched from the BOM.”

Why this matters: This step formally reserves materials for a specific Work Order. If materials are short, the system will alert you before you start production.

Watch out: Some implementations enable “Skip Material Transfer” to save time, allowing direct backflushing. This works for simple scenarios but breaks traceability—you can’t prove which batch of raw material went into which finished batch. I’ve seen this fail ISO audits.

4.2 Partial Transfers for Large Orders

If you’re manufacturing 1000 units but want to produce in batches of 100, you can create multiple Material Transfer entries against the same Work Order—just transfer what you need for each batch.

Practical tip: Use the “Transferred Quantity” field in the Work Order to track how much material has already been issued. ERPNext won’t let you over-transfer beyond the required quantity (ClefinCode manufacturing guide).

Stage 5: Production Execution via Job Cards

If your BOM has Operations, ERPNext auto-generates Job Cards when you submit a Work Order. According to Frappe Job Card documentation, “Job cards track the work performed at each workstation. After a work order is submitted, job cards tell a workstation to start producing goods—using a defined item, quantity, and set of operations.”

5.1 What Job Cards Track

Each Job Card represents one operation on one workstation:

• Operation: e.g., “Machining,” “Painting,” “Testing”
• Workstation: e.g., “CNC-Machine-01,” “Paint-Booth-A”
• Employees assigned
• Time logs: Actual start/end times
• Completed quantity

Shop floor operators update Job Cards as they complete work. This feeds actual cost and timing data back to the Work Order.

5.2 Time Tracking and Costing

When an employee logs time on a Job Card, ERPNext calculates:

• Actual Operation Time = End Time – Start Time
• Actual Operating Cost = (Actual Time × Workstation Hourly Rate)

This updates the Actual Operating Cost in the Work Order, giving you real production cost vs. planned cost.

Practical tip: If you don’t have operations/workstations set up yet, you can still track production time manually in a spreadsheet and enter total labor hours as an “Additional Operating Cost” in the Work Order. This gets you 80% of the benefit without the full complexity.

Stage 6: Quality Inspections and Rejection Handling

Quality checks are not optional in a proper manufacturing workflow. ERPNext supports Quality Inspection at three stages:

6.1 Three Types of Quality Inspections

1. Incoming (Purchase): Check raw materials when they arrive from suppliers
2. In-Process (Manufacturing): Check semi-finished goods during production
3. Outgoing (Sales): Final inspection before dispatch

According to ERPNext Quality Inspection documentation, “You can create a Quality Inspection for Job Card in order to monitor the quality of in-process items. In this case, you can create a Quality Inspection for the Production Item in Job Card.”

6.2 Creating Quality Inspection Templates

Before you can inspect anything, create Quality Inspection Templates that define:

• Parameters to check (e.g., “Diameter,” “Hardness,” “Color”)
• Acceptance criteria (min/max values for numeric checks, pass/fail for non-numeric)
• Sample size (how many units to test from a batch)

Link these templates to Items in the Item Master. When you create a Quality Inspection, the template auto-fills the parameter list.

6.3 Handling Rejections and Rework

What happens when a batch fails inspection?

ERPNext workflow:

1. Quality Inspector sets status to “Rejected” in Quality Inspection
2. If linked to a Purchase Receipt, you can create a Purchase Return to send defective material back to supplier
3. If linked to a Job Card (in-process), you can:
   • Create a new Work Order for rework
   • Scrap the rejected quantity (Stock Entry to Scrap Warehouse)
   • Accept with deviation (document why in remarks)

Practical tip: Set up a dedicated “Rejection/Rework” warehouse. When items fail QC, move them there via Stock Entry. This separates them from good stock and makes it visible that action is needed.

Watch out: Don’t let rejected items sit in the system without resolution. I’ve seen warehouses with thousands of units in “rejection” limbo for months because nobody wants to scrap them. Create a weekly review process to clear rejections.

6.4 Batch-Level Quality Tracking

For industries like pharma or FMCG, you need to link quality test results to specific batches. ERPNext handles this:

• Quality Inspection can reference a Batch No
• If the batch fails, you can block dispatch of that entire batch
• You can generate reports showing which batches passed/failed over time

Stage 7: Finished Goods Receipt and Batch Assignment

Once production is complete and quality-checked, you create a Stock Entry: Manufacture to officially receive finished goods into inventory.

7.1 The Manufacture Stock Entry

Click “Finish” on the Work Order to create this entry. It:

• Consumes raw materials from WIP Warehouse (debits WIP)
• Produces finished goods into Target Warehouse (credits Finished Goods)
• Assigns batch/serial numbers to finished goods (if applicable)

According to ERPNext Stock Entry documentation, “On submission, stock of raw-material items are deducted from Source Warehouse, which indicates that raw-material items were consumed in the manufacturing process.”

7.2 Batch and Serial Number Assignment

If your finished goods have batch tracking enabled (common for pharma, food, chemicals):

• ERPNext prompts you to enter or auto-generate a Batch No
• You can set Manufacturing Date and Expiry Date on the batch
• All units in this production run get the same batch number

If your finished goods have serial number tracking (common for electronics, machinery):

• ERPNext prompts for serial numbers (one per unit)
• You can auto-generate serials based on a naming series (e.g., PUMP-2024-.####)

According to ERPNext batch tracking documentation, both batch and serial numbers “provide granular control over inventory management, enhancing traceability, quality control, and compliance efforts.”

Practical tip: For batch-manufactured items, use a naming convention that includes date and shift: BATCH-PRODUCT-20260207-SHIFT-A. This makes it easy to trace back to production logs if there’s ever a quality issue.

7.3 Handling Scrap and Process Loss

Manufacturing often produces scrap material. ERPNext lets you:

• Define Scrap Items in the BOM with expected scrap percentage
• Designate a Scrap Warehouse
• When you finish production, the Stock Entry automatically adds scrap quantity to the Scrap Warehouse

According to ClefinCode manufacturing documentation, “If a Scrap Warehouse is defined, the system will prompt to record the actual scrap quantity produced and stock it into that warehouse. Scrap items can even carry a value if they are recyclable or saleable by-products.”

Stage 8: Sales Order Linkage, Pick-Pack-Dispatch

Your finished goods are now in stock. The final stage of the ERPNext manufacturing workflow is fulfilling customer orders and dispatch.

8.1 Linking Production to Sales Orders

If the Work Order was created from a Sales Order, ERPNext maintains this linkage. When you finish manufacturing, the system knows which customer that batch is reserved for.

Benefits:

• No accidental allocation to wrong customer
• You can track order-specific costs
• Customer can see production status (if you enable portal access)

8.2 Pick, Pack, and Dispatch

ERPNext’s fulfillment workflow:

1. Pick List: Generate a picking list showing which items to pull from which warehouses for pending Sales Orders
2. Packing Slip (optional): Document which items go in which boxes/crates, useful for large orders
3. Delivery Note: The official dispatch document that transfers stock from warehouse to customer

According to ERPNext Delivery Note documentation, “A Delivery Note is made when a shipment is shipped from the company’s warehouse to the customer. A copy of the Delivery Note is usually sent with the transporter.”

Watch out: If you create a Delivery Note without linking it to a Sales Order, you might dispatch the wrong batch or accidentally deliver someone else’s reserved stock. Always link properly.

8.3 Invoicing and GST Compliance (India)

After dispatch, create a Sales Invoice from the Delivery Note. For Indian businesses, this triggers:

• GST calculation based on customer location and HSN codes
• e-Invoicing generation (if annual turnover > ₹5 crores, as per India Compliance App)
• e-Way Bill generation for inter-state transport of goods > ₹50,000

The India Compliance App documentation states: “e-Waybill shall be generated from Sales Invoice or Delivery Note based on configuration. For movement of goods without an Invoice (say, for Job Work or Transfer of goods to different warehouses), enable e-Waybill generation from Delivery Note.”

Practical tip: Set the “Invoice Value Threshold for e-Waybill Generation” in GST Settings. ERPNext will auto-generate e-Way Bills only when invoice value exceeds this threshold, saving manual work for small shipments.

India-Specific Manufacturing Twists

Indian manufacturing has specific practices that ERPNext handles through the India Compliance App. Here’s how to configure your ERPNext manufacturing workflow for these scenarios.

11.1 Job-Work / Subcontracting with Challans

What it is: You send raw materials to a third-party (job-worker) who processes them and returns finished/semi-finished goods. This is common in textiles, metal treatment, assembly, etc.

ERPNext workflow:

1. Create a Subcontracting BOM (mark “Is Subcontracted” checkbox)
2. Create a Purchase Order to the subcontractor for the service
3. Create a Stock Entry: Send to Subcontractor to issue raw materials with delivery challan
4. Job-worker processes the materials
5. Create a Subcontracting Receipt to receive finished goods back
6. System auto-consumes the raw materials sent earlier

According to India Compliance App documentation, “When the finished goods are received back from the supplier and require some rework, they must be sent back to the supplier for further processing. This process can be effectively managed in ERPNext through Subcontract Returns.”

For GST compliance: The India Compliance App automatically generates challan references for ITC-04 reporting (Table 4 and Table 5). This tracks materials sent to job-workers and materials received back within the prescribed time limits.

Practical tip: Set up a virtual warehouse for each job-worker (e.g., Subcontractor-ABC-Location). When you send materials, they move to this warehouse. When you receive finished goods, materials consume from this warehouse. This keeps perfect track of what’s physically at the job-worker’s location.

Watch out: GST rules require you to receive materials back within 1 year (for inputs) or 3 years (for capital goods) from the date of dispatch. If not, it’s deemed as supply and you owe GST. ERPNext doesn’t automatically flag this—you need to run periodic reports to catch overdue challans.

11.2 Multi-Warehouse Operations with Different GST Registrations

If you have factories/warehouses in different states (e.g., Gujarat and Tamil Nadu), each location needs a separate GSTIN.

ERPNext setup:

• Create separate Address records for each location with its GSTIN
• Create location-specific warehouses (e.g., Gujarat-Stores, TN-Stores)
• When creating Sales Invoices, select the dispatch warehouse—ERPNext picks the correct GSTIN automatically

For inter-state stock transfers:

• Create Stock Entry between warehouses
• Generate e-Way Bill from Delivery Note (enable this in GST Settings)
• Mark purpose as “For Own Use” since it’s not a sale

11.3 Batch Tracking with Expiry Management

For pharma, FMCG, or chemical industries, you must track batch expiry dates.

ERPNext features:

• Set Has Batch No in Item Master
• Enable Has Expiry Date checkbox
• When manufacturing, enter Manufacturing Date and Expiry Date in batch
• Run Batch-Wise Balance History report to see all batches with expiry dates
• Set up alerts for batches approaching expiry

Practical tip: Create a custom report that shows all batches expiring in the next 60 days. Review this weekly with your dispatch team to ensure FIFO/FEFO (First Expiry First Out) is followed.

11.4 Multi-UOM Conversions

Indian manufacturers often deal with:

• Buying in MT (metric tons), storing in KG, consuming in grams
• Buying in boxes, storing in pieces, consuming in sets

ERPNext supports UOM conversions. Set up conversion factors in Item master:

• 1 MT = 1000 KG = 1,000,000 Grams
• 1 Box = 50 Pieces

The system auto-converts quantities during BOM explosion and Stock Entries.

Watch out: If UOM conversion factors are wrong, your material planning will be completely off. Double-check these before going live.

Manufacturing Workflow Map: Step-by-Step Reference Table

Here’s a comprehensive reference showing each stage of the ERPNext manufacturing workflow, the ERPNext documents involved, inputs required, outputs produced, and common pitfalls to avoid.

Step #	Manufacturing Stage	ERPNext DocType	Key Inputs	Key Outputs	Common Pitfalls
1	Setup: Item Masters	Item	Item Code, UOM, BOMs, Warehouses	Item records with manufacturing flags enabled	Creating items without BOM defaults; inconsistent naming
2	Setup: Warehouse Structure	Warehouse	Warehouse names, parent-child hierarchy	Stores, WIP, FG warehouses	Too many warehouses initially; no clear naming logic
3	Setup: BOM Creation	BOM (Bill of Materials)	Output Item, Raw Materials, Quantities, Operations (optional)	Active BOM linked to Item	Not specifying source warehouses; wrong quantities
4	Material Planning	Production Plan / MRP	Sales Orders, Demand Forecast, Current Stock	Material Requests for shortfall items	Ignoring lead times; not exploding multi-level BOMs
5	Procurement	Material Request → Purchase Order	Supplier, Items, Quantities	PO issued to supplier	Buying without checking current stock first
6	Goods Receipt	Purchase Receipt + Quality Inspection (Incoming)	PO Reference, Quality parameters	Stock updated in Stores warehouse	Accepting material without QC; wrong batch assignment
7	Work Order Creation	Work Order	Item to Manufacture, BOM, Quantity, Warehouses	Manufacturing instruction with material reservation	Creating WO without checking material availability
8	Material Issue to WIP	Stock Entry: Material Transfer for Manufacture	Work Order reference, Source warehouse	Materials moved to WIP warehouse	Skipping this step (breaks traceability)
9	Shop Floor Execution	Job Card (if operations defined)	Operation, Workstation, Employees	Time logs, actual costs, completed quantities	Not tracking time; no employee assignment
10	In-Process Quality Check	Quality Inspection (In-Process)	Job Card reference, Quality template	Accept/Reject status for batch	Ignoring in-process QC until final stage
11	Finished Goods Receipt	Stock Entry: Manufacture	Work Order, WIP warehouse, Target warehouse	FG received, batch/serial assigned, WIP consumed	Not assigning batch numbers; accepting without final QC
12	Final Quality Check	Quality Inspection (Outgoing)	FG batch, Quality template	Accept/Reject status before dispatch	Dispatching before final QC approval
13	Linking to Sales Orders	Sales Order	Customer, Items, Delivery date	Reserved stock for customer	Creating WO without SO linkage (can’t trace order)
14	Pick and Pack	Pick List / Packing Slip	Sales Orders pending delivery	Picking instructions for warehouse team	Picking wrong batches; FIFO violations
15	Dispatch Documentation	Delivery Note	Customer, Items, Batch nos, Transporter	Stock transferred to customer; e-Way Bill (India)	Missing e-Way Bill for inter-state; wrong GSTIN
16	Invoicing	Sales Invoice	Delivery Note reference, GST details	Invoice, e-Invoice (India), accounting entries	Invoice before dispatch (stock mismatch)
17	Subcontracting (India)	Subcontracting Order / Receipt + Stock Entry	Job-worker, Raw materials, BOM	Materials sent/received with challan reference for ITC-04	Not tracking ITC-04 return period; missing challans
18	Rejection Handling	Stock Entry: Rejection → Scrap/Rework	Failed QC batch, Rejection warehouse	Rejected qty moved to scrap or rework WO created	Leaving rejected stock in main warehouse

Ready to set up a manufacturing workflow that actually works for your business? Get a manufacturing workflow assessment from PrimoERP—we’ll map your current process and show you exactly where ERPNext can eliminate bottlenecks.

Data You Must Prepare Before You Start

Before you can run the ERPNext manufacturing workflow, you need clean master data. Here’s the checklist—gather this information during your implementation project:

Master Data Checklist

Items:

• ✅ Complete list of raw materials (with UOMs, reorder levels, lead times)
• ✅ Complete list of finished goods (with default BOMs, batch/serial settings)
• ✅ Sub-assemblies and WIP items (if applicable)
• ✅ Scrap items and by-products (if you track them)
• ✅ Service items for job-work/subcontracting

BOMs:

• ✅ Accurate quantities for each raw material per finished unit
• ✅ Source warehouses for each BOM item
• ✅ Operations and routing (if you’re using Job Cards)
• ✅ Scrap percentages (if applicable)

Warehouses:

• ✅ At minimum: Stores, WIP, Finished Goods, Rejection/Scrap
• ✅ For multi-location: Location-specific warehouse groups
• ✅ For job-work: Virtual warehouses for each subcontractor

Workstations & Operations:

• ✅ List of production lines/machines (if tracking operations)
• ✅ Hourly operating costs for each workstation
• ✅ Operation names (Cutting, Welding, Painting, Assembly, Testing, etc.)
• ✅ Time standards for each operation (from industrial engineering)

Suppliers:

• ✅ Supplier master data with GSTIN (India)
• ✅ Lead times for each key raw material
• ✅ Payment terms and credit limits

Quality Parameters:

• ✅ Quality Inspection Templates for critical items
• ✅ Acceptance criteria (min/max values, pass/fail logic)
• ✅ Sample sizes for batch testing

Customers:

• ✅ Customer master data with GSTIN (India)
• ✅ Billing addresses and shipping addresses
• ✅ Credit limits and payment terms

Chart of Accounts Mapping:

• ✅ Raw Material Expense account
• ✅ WIP account (asset)
• ✅ Finished Goods account (asset)
• ✅ Manufacturing Expense / Overhead account
• ✅ Scrap / Wastage account

Practical tip from a recent project: Don’t try to load 10 years of historical data before go-live. Start with current stock levels as of go-live date (via Opening Stock Entry) and begin transacting forward. You can always keep old data in Excel for reference.

Phase 1 vs Phase 2 Rollout: What to Go Live With First

Implementing the full ERPNext manufacturing workflow in one go is a recipe for failure—I’ve watched teams try this and get overwhelmed. Here’s how to phase it for Indian SME manufacturers.

Phase 1: Must-Have (Go-Live Foundation)

Week 1-6 Priority:

✅ Item masters (Raw Materials + Finished Goods only, skip sub-assemblies initially)
✅ Basic BOMs (single-level, without operations)
✅ Warehouse setup (Stores, WIP, FG—minimum three)
✅ Work Order creation and tracking
✅ Stock Entry: Material Transfer + Manufacture (the core two entries)
✅ Quality Inspection (at least final QC before dispatch)
✅ Sales Order → Delivery Note → Invoice (fulfillment basics)
✅ Purchase workflow (Material Request → PO → Purchase Receipt)

What you can track:

• What you manufactured (which FG, how many units, when)
• What raw materials you consumed (basic material accounting)
• Which customer got which batch (basic traceability)
• What’s in stock right now (inventory accuracy)

What you’ll do manually/outside system:

• Detailed time tracking (use a spreadsheet for labor hours)
• Capacity planning and machine scheduling
• Detailed cost variance analysis

Why this works: You get a functioning manufacturing workflow in 6 weeks. Shop floor sees immediate value (no more Excel-based material tracking). Accounting gets clean inventory values. Management gets visibility into WIP and production status.

Practical tip: Go live with Phase 1 in your smallest product line or single factory location first. Prove it works for 2-3 months, then expand to other products/locations.

Phase 2: Nice-to-Have (Post-Stabilization)

Week 7-12 and Beyond:

🎯 Multi-level BOMs (add sub-assemblies, explode material requirements better)
🎯 Operations and Job Cards (track shop floor time and workstation usage)
🎯 Advanced MRP (Production Planning Tool with forecasting)
🎯 In-process Quality Inspections (QC at intermediate stages)
🎯 Batch expiry management (for pharma/FMCG)
🎯 Subcontracting workflow (job-work with challan tracking)
🎯 Pick Lists and Packing Slips (warehouse optimization)
🎯 Custom reports and dashboards (KPIs, production analytics)

What you can now track:

• Shop floor efficiency (machine utilization, cycle time by operation)
• Material consumption variance (BOM vs. actual usage)
• Cost variance (planned vs. actual production cost)
• Subcontractor performance (challan aging, return time compliance)

Watch out: Don’t add Phase 2 features until Phase 1 is stable. “Stable” means: (1) users are entering data daily without constant support tickets, (2) month-end stock reconciliation matches physical inventory within 2%, (3) team has stopped asking “where’s my Excel sheet?”

For most companies, that takes 2-3 months minimum after go-live. Resist the temptation to add complexity early.

How to Keep the Workflow Clean

A manufacturing ERP doesn’t stay clean on its own. It requires discipline. Here’s what separates good implementations from chaotic ones.

1. Approval Matrix and Role Permissions

Set up proper approvals based on value/risk:

• Work Orders > X units: Require production manager approval
• BOMs: Engineering team creates, senior engineer approves before activation
• Stock Entries > Y value: Supervisor approval required
• Quality Rejections: QC manager must review before scrap/rework

Practical tip: Use ERPNext’s Workflow feature for critical doctypes. For example, create a “Work Order Approval Workflow” that routes high-value orders to management before they hit the shop floor. This catches planning errors early.

According to PrimoERP’s implementation methodology, role-based access control is configured during the setup phase to prevent unauthorized changes to master data like BOMs and Item pricing.

2. Naming Conventions and Standards

Establish clear rules:

• Work Orders: Auto-number with prefix (e.g., MFG-WO-2024-0001)
• Batches: Include product code + date + shift (e.g., PROD-A-20240207-S1)
• Items: Category prefix + description (e.g., RM-STEEL-304-6MM, FG-BRACKET-PAINTED)

Why this matters: When you’re looking at a report with 500 Work Orders, clear naming lets you instantly understand what each one is without opening the record.

3. Change Request Discipline for BOMs

BOMs change frequently in the first year of production. Without discipline, you get chaos.

Best practice:

1. Engineering team requests BOM change via ticket/email
2. Production planner reviews impact on current Work Orders
3. If approved, old BOM is canceled, new version created
4. New BOM tested on a trial Work Order before making it default
5. All open Work Orders using old BOM are flagged for review

Watch out: I’ve seen cases where someone changed a BOM while Work Orders were in progress, breaking material calculations. Always check “dependent documents” before modifying a BOM.

4. Weekly Stock Reconciliation

Don’t wait for month-end to find discrepancies.

Weekly checklist:

• Run Stock Balance report for WIP warehouse (should be minimal if you’re finishing Work Orders properly)
• Compare Stock Ledger to physical count for top 20 fast-moving items
• Review Negative Stock Report (if you allow negative stock, flag items that are consistently negative—this indicates planning issues)

5. Training and Adoption Support

The workflow is only as good as user adoption.

What works:

• Role-specific training: Operators need Job Card training, not BOM creation training
• Quick reference cards: One-pagers showing “How to complete a Work Order” with screenshots
• Regular refresher sessions: Monthly 30-min sessions to cover common mistakes
• Super-users on shop floor: Identify 2-3 tech-savvy employees who can help peers with basic questions

What doesn’t work: One-time training during implementation, then hoping for the best. Skills decay, people forget, new employees join.

If you need help setting up training materials and adoption workflows, PrimoERP’s implementation services include end-user training and post-go-live support to ensure your team actually uses the system correctly.

What a Good Implementation Looks Like vs Common Failure Patterns

After seeing dozens of implementations (both smooth and painful), here’s what separates success from failure.

✅ What Good Looks Like

Month 1 after go-live:

• Shop floor staff are creating Stock Entries without asking for help
• Work Orders close within 1-2 days of completion (people aren’t leaving them open for weeks)
• Quality Inspections happen before dispatch, not as an afterthought
• Stock reconciliation shows <5% variance between system and physical count

Month 3 after go-live:

• You can generate a report showing which raw material batch went into which finished goods batch (full traceability)
• Month-end closing happens in 2-3 days instead of 10+ days (because inventory values are always current)
• You’ve stopped using Excel for production planning—MRP/Production Plan drives material purchasing
• Management reviews dashboards showing actual vs. planned production costs

Month 6 after go-live:

• Customer service can tell a customer exactly where their order is in the production queue
• You’ve added Phase 2 features (operations tracking, subcontracting) without breaking the core workflow
• New employees get trained by existing staff using documented procedures
• You’re using ERPNext data to make decisions (which products are most profitable, which suppliers have best lead times)

❌ Common Failure Patterns

“We’ll fix master data later” syndrome:

• Team goes live with incomplete BOMs or wrong quantities
• Shop floor finds errors every day, creates Work Orders with manual overrides
• After 6 months, you have 50% of Work Orders with BOM overrides
• Now you can’t trust any cost or material consumption reports
• Fix: Don’t go live until at least 80% of active products have verified BOMs

“We need to customize everything” disease:

• Team wants custom fields, custom workflows, custom reports before understanding standard functionality
• Implementation drags on for 12 months
• By the time you go live, ERPNext has had two version updates and your customizations break
• Fix: Use standard ERPNext for at least 3 months before customizing anything. Most “requirements” evaporate once you understand the system.

“We’ll train people after go-live” mistake:

• Implementation team learns the system, assumes they can train everyone else later
• Go-live happens, shop floor staff don’t know how to use system
• They fall back to Excel, ERPNext becomes a parallel system for reporting only
• Fix: Train end-users during UAT (User Acceptance Testing). Let them break things in a test environment before go-live.

“One person knows everything” risk:

• Implementation is led by one super-user who becomes the system gatekeeper
• Nobody else understands the workflow or configuration
• Super-user leaves or gets promoted
• System knowledge evaporates
• Fix: Document everything. Create at least 3 super-users across different departments (production, warehouse, accounts).

If you’re worried about falling into these traps, a partner like PrimoERP who specializes in manufacturing implementations can help you avoid these common pitfalls and stay on track.

Quick Summary

The ERPNext manufacturing workflow for Indian manufacturers follows this sequence:

1. Setup: Clean Item masters, Warehouses, and BOMs
2. Planning: Use Production Plans/MRP to calculate material needs based on Sales Orders
3. Procurement: Generate Material Requests and Purchase Orders for shortfall materials
4. Work Order: Create manufacturing instructions with BOM, quantities, and warehouses
5. Material Transfer: Issue raw materials from Stores to WIP warehouse (traceability checkpoint)
6. Production: Execute via Job Cards (if using operations), track time and costs
7. Quality Checks: Inspect at incoming, in-process, and outgoing stages
8. Finish: Receive finished goods, assign batch/serial numbers, consume WIP
9. Dispatch: Link to Sales Orders, Pick, Pack, create Delivery Note with e-Way Bill (India)
10. Invoice: Generate Sales Invoice with GST compliance, e-Invoicing (India)

India-specific considerations:

• Subcontracting with challans tracked via India Compliance App
• Batch expiry management for pharma/FMCG
• Multi-warehouse with different GSTINs
• e-Way Bill and e-Invoice automation

Implementation approach:

• Start with Phase 1 (basic workflow without operations) for 2-3 months
• Add Phase 2 features (operations, advanced MRP, subcontracting) only after stabilization

Success metrics:

• Full traceability (raw material batch → finished goods batch → customer)
• <5% stock variance at month-end
• Work Orders completed within 1-2 days of production finish
• No Excel-based material tracking by Month 3

Ready to implement a manufacturing workflow that works?

Whether you’re struggling with stock traceability, drowning in Excel-based material planning, or need to set up job-work compliance, PrimoERP specializes in manufacturing implementations for Indian SMEs.

Request a rollout plan & estimate or book a 20-minute manufacturing demo call to see how ERPNext can transform your production floor.

Prefer WhatsApp? Reach us via the contact page.