Other ERPsFree referencePDF, Excel, Word exportERPNextDiscrete Manufacturing

ERPNext DocType Reference for Manufacturing

ERPNext, built on the Frappe framework, models everything as a DocType. This reference lists the DocTypes a small manufacturer touches in production, inventory, buying and selling, and where each one links.

Download:
DocTypeModuleWhat it holdsLinks to
Item
Stock
Item master: stock UOM, valuation, serial and batch flags
Item Group, UOM, Item Price
Item Group
Setup
Tree of item categories
Item
UOM
Setup
Unit of measure
Item
Warehouse
Stock
Storage location tree
Bin, Stock Entry
Bin
Stock
Current quantity of an item in a warehouse
Item, Warehouse
Stock Ledger Entry
Stock
Posted stock transaction line with valuation
Item, Warehouse, voucher
Stock Entry
Stock
Material receipt, issue, transfer, manufacture, repack
Work Order, Warehouse
Stock Entry Detail
Stock
Child table of Stock Entry item rows
Stock Entry, Item
Stock Reconciliation
Stock
Physical count adjustment with valuation
Item, Warehouse
Batch
Stock
Batch number for batch-tracked items
Item
Serial No
Stock
Serial number for serialized items
Item, Warehouse
Material Request
Stock
Request to purchase, transfer, issue or manufacture
Purchase Order, Stock Entry
Quality Inspection
Stock
Inspection result against a receipt, delivery or job
Item, Purchase Receipt
BOM
Manufacturing
Bill of materials with operations and costing
Item, Workstation, Operation
BOM Item
Manufacturing
Child table of BOM component rows
BOM, Item
BOM Operation
Manufacturing
Child table of BOM operations
BOM, Operation, Workstation
Operation
Manufacturing
Master of manufacturing operations
Workstation, BOM
Routing
Manufacturing
Reusable sequence of operations
BOM, Operation
Workstation
Manufacturing
Machine or work center with hour rate
Operation, Job Card
Work Order
Manufacturing
Production order to make an item from a BOM
BOM, Stock Entry, Job Card
Work Order Item
Manufacturing
Required material rows on a Work Order
Work Order, Item
Job Card
Manufacturing
Operation-level shop floor record with time logs
Work Order, Workstation
Production Plan
Manufacturing
Plans work orders and material requests from sales orders
Sales Order, Work Order, Material Request
Supplier
Buying
Vendor master
Purchase Order
Purchase Order
Buying
Order placed with a supplier
Supplier, Purchase Receipt
Purchase Receipt
Stock
Goods received against a purchase order
Purchase Order, Stock Ledger Entry
Customer
Selling
Customer master
Sales Order
Sales Order
Selling
Confirmed customer order
Customer, Production Plan, Delivery Note
Delivery Note
Stock
Shipment against a sales order
Sales Order, Stock Ledger Entry
Item Price
Stock
Price of an item in a price list
Item, Price List

Database tables are named with a tab prefix, for example tabBOM and tabWork Order. DocType fields vary slightly between ERPNext versions, so confirm in the DocType List or Customize Form screen.

Need ERPNext data mapped for reporting?

Optional: have an expert review your DocType mapping and reporting plan.

Optional. The tool and every export work without this. No spam.

How to use this reference

Use it before you write a REST query, a custom report, a Server Script or an import file. Search by DocType, module or purpose. Child tables such as BOM Item and Stock Entry Detail are included because they are what you query when you need component or line-level data. Export the list to Excel and keep it next to your implementation notes.

  • Search Manufacturing to see the production DocTypes
  • Use Bin for current stock and Stock Ledger Entry for history
  • Child tables are fetched through their parent in the REST API
  • Confirm fields in the DocType List screen for your version

The production flow

A Sales Order or a Production Plan leads to a Work Order against a BOM. The Work Order reserves required items, creates Job Cards per operation on a Workstation, and is completed through Stock Entry documents (material transfer for manufacture, then manufacture). Finished goods land in the target warehouse and Stock Ledger Entry rows record the movement and valuation. Knowing the chain helps you find where a stuck order stopped.

Stock numbers: Bin versus ledger

Bin is a fast summary per item and warehouse, while Stock Ledger Entry is the source of truth that every valuation report rebuilds from. If the two disagree, the ledger wins, and the repair is a reposting of item valuation rather than editing Bin. Never edit stock tables by hand; use Stock Reconciliation so the ledger and accounting entries stay consistent.

Common mistakes

Confusing a BOM with a Routing, which are separate DocTypes. Forgetting that submitted documents are locked, so changes need cancel and amend. Querying only the parent and missing child rows. Counting quantities in the stock UOM when a transaction used another UOM with a conversion factor. Each mistake shows up later as a quantity that does not reconcile.

Frequently Asked Questions

What is a DocType in ERPNext?

A DocType is the Frappe definition of a record type: its fields, permissions and behavior. Each DocType gets a database table named tab plus the DocType name, and child tables are separate DocTypes linked to their parent. Customizing a DocType is done through Customize Form or a custom app.

Where is current stock stored in ERPNext?

Current quantity per item and warehouse is in the Bin DocType, updated whenever stock transactions post. The Stock Ledger Entry holds every posted movement with valuation, and reports like Stock Balance are computed from it. Treat the ledger as the source of truth.

How does a Work Order consume materials?

A Work Order lists required items from its BOM. You transfer materials to the work in progress warehouse with a Stock Entry, then post a Manufacture entry that consumes the components and receives the finished item. Backflushing from the source warehouse is an available setting.

Can I query these DocTypes from outside ERPNext?

Yes. The REST API exposes each DocType under /api/resource, and authenticated users with permission can read and write it. Use API keys for service accounts. Direct database access is possible for reporting but bypasses permission checks and validations.

If you want natural-language answers over ERPNext or another ERP without moving data off your servers, Netray can set that up read-only.