Skip to main content

Manufacturing & distribution

ERPNext Production Plan Not Creating Work Orders: Fix Ladder (2026)

Submit a Production Plan, click Create Work Order, and get nothing or fewer work orders than lines. Five causes, in the order to check them.

Updated 12 Oct 20269 min readBy ManojFirst published 9 Aug 2026

When an ERPNext Production Plan doesn't create Work Orders, it is usually one of five things: the Item is not set up as a manufactured stock item, its BOM is not Default or is Inactive, the plan's company doesn't match a warehouse's company, the user lacks Create permission on Work Order, or, on early v16 releases, a Semi-Finished Good's untagged raw materials are left out. Each has its own symptom, and most tickets close quickly once you check them in the right order.

The Create Work Order button on a submitted Production Plan either produces a green toast with the WO count, a red toast with a specific error, or, in the worst case, a green toast that lies and creates fewer WOs than plan lines. The ladder below tells the three apart. I am Manoj, and I lead ERPNext and Frappe implementations at MithTech, a team of Frappe specialists in Bengaluru. This is the order we check in when a manufacturing client reports it.

The five causes at a glance

CauseSymptomFirst check
1Item not set up as manufactured stock item"Create Work Order" button greys out or completes silently with 0 WOsItem form: Is Stock Item, Include Item In Manufacturing, Default BOM
2BOM inactive or not set as defaultItem allows WO in theory but the button creates nothingBOM list, filter Item = X: is any BOM Is Active + Is Default?
3Company mismatch between Production Plan and a warehouseSome rows not created, or a warehouse-company error; fewer WOs than plan linesProduction Plan → Company; each Warehouse row → Company
4User lacks Create on Work OrderError toast: Not permitted to create Work OrderRole Permissions Manager: user's role on Work Order
5Semi-Finished Goods raw material untagged (early v16, #51172)WOs created, but SFG raw material missing from Material Request / Job CardBOM form: every raw material row → Operation field non-empty

Is the Item set up as a manufactured stock item?

Answer

An ERPNext Production Plan will refuse to create a Work Order for any row where the Finished Good Item is not a stock item, does not have Include Item In Manufacturing ticked, or has no Default BOM set on the Item master. All three are on the Item form. If any is missing, that row gets no Work Order, sometimes without a clear error.

Open the Item form for the FG on the plan line and confirm all three:

  • Is Stock Item: must be ticked. Non-stock items cannot be produced through Work Orders because there is nothing to receive into inventory.
  • Include Item In Manufacturing: must be ticked. This is the master switch for whether ERPNext considers the item a manufacturing candidate at all. If it is off, the item is invisible to Production Plan → Work Order creation, even with a valid BOM.
  • Default BOM: must reference an active BOM. If the field is empty, Create Work Order has nothing to instantiate from and skips the row.

If any of these is off, fix it on the Item form, then re-open the Production Plan and try Create Work Order again. You don't need to re-submit the plan: the button re-reads the item state on each click.

Is the BOM Default AND Active?

Every WO needs a specific BOM version. ERPNext picks the one that satisfies both: Is Active = 1 AND Is Default = 1. The common failure modes:

  • No Default BOM at all. The Item has three BOMs, none marked Default. Fix: open the intended BOM, tick Is Default, save. ERPNext auto-unmarks the other BOMs of the same item.
  • The Default BOM is Inactive. Someone deactivated it after a rate change or a supersession. Fix: either re-activate it (if the deactivation was a mistake), or mark the new active BOM as Default.
  • A newer BOM version was made but not set as Default. Common once BOMs start being revised. Fix: on the intended BOM, tick both Is Active and Is Default.

To confirm quickly, open the BOM list, filter Item = <your FG>, and check the two boolean columns. You want exactly one row with both green.

Does the company on the plan match the warehouse company?

Every warehouse in ERPNext belongs to exactly one Company. A Work Order's target warehouse, WIP warehouse and raw-material source warehouses must all belong to the plan's Company. If one doesn't, that row fails: depending on version and path you get a warehouse-company error or simply fewer WOs than plan lines.

To debug:

  1. Open the Production Plan; note the value of Company at the top.
  2. For each row in Assembly Items, click through to the referenced Warehouse.
  3. On each Warehouse form, confirm Company equals the plan's Company.
  4. If any row is on a warehouse in a different Company, either move production to a warehouse of the correct Company, or create the plan under the Company that owns the warehouse.

This is common in setups where a parent company holds the master warehouses and a subsidiary is trying to plan production against them. The reference won't work; produce from a warehouse the plan's Company actually owns.

Does the user have permission to create Work Orders?

If the operator can submit a Production Plan but the WO create button errors with Not permitted to create Work Order (or, more subtly, produces zero WOs with no error on some ERPNext builds), their role is missing Create on Work Order. The plan itself only needs Submit; the WO create step runs as the same user and needs Create on the target doctype.

Two clean fixes:

  1. Grant the role Create on Work Order via Role Permissions Manager. The "Manufacturing User" role usually has this already; verify.
  2. If the operator should not have Create, have a Manufacturing Manager click Create Work Order on their behalf; the plan can stay under the operator's ownership.

The v16 select-only permission regression noted in ERPNext v16 bulk edit not working can also cause this to fail if the operator has Select but not Read on Work Order; grant Read.

Are Semi-Finished Goods raw materials being ignored on v16?

If your BOM has Track Semi-Finished Goods enabled with several operations, and one or more raw materials are not tagged to a specific operation, check #51172. Symptom: the Work Order is created, but when you raise a Material Request against it or open the Job Cards, the untagged raw material is not listed. No error, no warning: the row just isn't there. The issue was closed in December 2025 without a linked fix, so test it on your point release.

The workaround, which is safe on any version:

  • Open the BOM in question.
  • For every raw material row, fill the Operation field with one of the BOM's operations; even if the material is generic and used by more than one operation, pick the earliest.
  • Save and re-submit the BOM (make new Version if needed).
  • Re-run Create Work Order on the Production Plan.

Tagging every row costs nothing and keeps the material picture complete, so it is a sensible standard for Track-SFG BOMs whatever your version.

What is the correct end-to-end setup order?

0 of 7 steps done

Tick a step’s number when it is done; the ticks stay on this device.

Item master: set the three flags

On every Finished Good and every Sub-Assembly: tick Is Stock Item, tick Include Item In Manufacturing, and (once the BOM exists) set Default BOM. Do this before any BOM work; it's cheaper to check now than to debug missing WOs later.

BOM: active, default, correct company

Create the BOM for each manufactured item. Before submitting, tick Is Active and Is Default. Check the Company field matches the plan you'll run the item through: a BOM from Company A cannot be used by a Production Plan for Company B.

If using Track Semi-Finished Goods, tag every raw material

Tag every raw material row on a Track-SFG BOM to a specific Operation. On early v16 releases untagged rows could drop out of the WO's material picture (#51172).

Warehouse setup: one Company per warehouse

Confirm each warehouse used in the plan (source for raw materials, target for FG, WIP warehouse for operations) belongs to the same Company as the Production Plan. Cross-company warehouse references stop Work Orders being created.

Role permissions: Create on Work Order for the operator

The user who clicks Create Work Order must have Create on Work Order. Manufacturing User typically does; custom roles may not. Verify in Role Permissions Manager before you go live.

Production Plan: submit, then Create Work Order

Create the plan from Material Requests or Sales Orders as usual. Submit the plan. Click Create Work Order. Read the resulting toast: it will tell you either "N Work Orders created" (expected count = plan lines), or a specific error. If the count is lower than expected, walk the ladder above starting at cause 3.

Post-create sanity check

For each created WO, open the Required Items table and confirm every raw material from the BOM is present. If any is missing on a Track-SFG BOM, you've hit #51172: go back and tag the untagged rows.

Which problems look like this but aren't?

Three failure modes that look like "Production Plan not creating work orders" but need different fixes:

  • Production Plan creates WOs but marks itself "Completed" while WOs are still open. That was #27480, closed in 2021: a status-tracking issue, not a create-time one.
  • Production Plan tags and attachments not carrying to the WO. #46619, still open: cosmetic, not blocking.
  • A partial Production Plan won't produce the remaining quantity. That is a different diagnostic path; see Production Plan partial completion.

FAQ

Why does Create Work Order create fewer WOs than my plan has lines?

Usually one of two things. One or more plan lines use a warehouse in a different Company from the plan, or one or more Items on the plan are missing Include Item In Manufacturing or have no Default BOM. Either way those rows get no Work Order. Compare the toast's WO count against your plan's row count; the difference is the number of rows to audit.

Do I need to un-submit the Production Plan to fix the Item or BOM flags?

No. Production Plan reads the current Item and BOM state each time you click Create Work Order, so no re-submit is needed. Fix the flags, re-click, and the WOs create against the corrected setup.

The button greys out entirely. What does that mean?

The plan is already fully produced (every row has WOs created for its full quantity) or the plan is in a state that prevents WO creation (draft, cancelled). Check the plan's Status field. If it says Completed or Cancelled, no more WOs can come out of it.

Is there a way to force Production Plan to skip permission checks?

No, and you shouldn't want one: WO permissions gate who can commit inventory to production, which is a real control. If a specific user must be able to create WOs from plans they submit, grant that user's role Create on Work Order via Role Permissions Manager. Skipping the check would defeat the audit trail on why a WO exists.

Live demo

Your next step

Production Plan silently skipping rows on your ERPNext instance?

Manufacturing

Made to order

3 screens · about 5 min · you end with stock moved

See it live

Sales OrderTo deliver and bill

The customer's confirmed order: who it's for, the items at their price list and when it's due.

Customer
A demo customer
Prices
From their price list

Mith Demo Traders · demo company

Manufacturing & distribution

Now see how ERPNext runs a plant like yours

How we set up ERPNext for manufacturers, from bills of materials and job work to costing and the shop floor.

Comments & ratings

No comments yet. Start a new discussion.

0

Manoj · Published on 9 August 2026

Worked with us? Leave a Google review

Questions about this? Talk to the team.

Book a 30-minute Google Meet, WhatsApp us, or send a message. The engineer who works on this replies.

Send us a message

Your details go to our team's CRM and are used only to reply.