# ERPNext DocType Reference for Manufacturing > Source: https://netray.co/tools/erpnext-doctype-reference-for-manufacturing > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Lookup table of ERPNext manufacturing, stock, buying and selling DocTypes with what each stores and where it links. ## Category other-erp ## Erp ERPNext ## Industry Discrete Manufacturing ## Audience - ERP developer - ERP consultant - Production planner ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### DocType **Key:** doctype **Type:** text #### Module **Key:** module **Type:** text #### What it holds **Key:** purpose **Type:** text #### Links to **Key:** links **Type:** text **Rows:** **Doctype:** Item **Module:** Stock **Purpose:** Item master: stock UOM, valuation, serial and batch flags **Links:** Item Group, UOM, Item Price **Doctype:** Item Group **Module:** Setup **Purpose:** Tree of item categories **Links:** Item **Doctype:** UOM **Module:** Setup **Purpose:** Unit of measure **Links:** Item **Doctype:** Warehouse **Module:** Stock **Purpose:** Storage location tree **Links:** Bin, Stock Entry **Doctype:** Bin **Module:** Stock **Purpose:** Current quantity of an item in a warehouse **Links:** Item, Warehouse **Doctype:** Stock Ledger Entry **Module:** Stock **Purpose:** Posted stock transaction line with valuation **Links:** Item, Warehouse, voucher **Doctype:** Stock Entry **Module:** Stock **Purpose:** Material receipt, issue, transfer, manufacture, repack **Links:** Work Order, Warehouse **Doctype:** Stock Entry Detail **Module:** Stock **Purpose:** Child table of Stock Entry item rows **Links:** Stock Entry, Item **Doctype:** Stock Reconciliation **Module:** Stock **Purpose:** Physical count adjustment with valuation **Links:** Item, Warehouse **Doctype:** Batch **Module:** Stock **Purpose:** Batch number for batch-tracked items **Links:** Item **Doctype:** Serial No **Module:** Stock **Purpose:** Serial number for serialized items **Links:** Item, Warehouse **Doctype:** Material Request **Module:** Stock **Purpose:** Request to purchase, transfer, issue or manufacture **Links:** Purchase Order, Stock Entry **Doctype:** Quality Inspection **Module:** Stock **Purpose:** Inspection result against a receipt, delivery or job **Links:** Item, Purchase Receipt **Doctype:** BOM **Module:** Manufacturing **Purpose:** Bill of materials with operations and costing **Links:** Item, Workstation, Operation **Doctype:** BOM Item **Module:** Manufacturing **Purpose:** Child table of BOM component rows **Links:** BOM, Item **Doctype:** BOM Operation **Module:** Manufacturing **Purpose:** Child table of BOM operations **Links:** BOM, Operation, Workstation **Doctype:** Operation **Module:** Manufacturing **Purpose:** Master of manufacturing operations **Links:** Workstation, BOM **Doctype:** Routing **Module:** Manufacturing **Purpose:** Reusable sequence of operations **Links:** BOM, Operation **Doctype:** Workstation **Module:** Manufacturing **Purpose:** Machine or work center with hour rate **Links:** Operation, Job Card **Doctype:** Work Order **Module:** Manufacturing **Purpose:** Production order to make an item from a BOM **Links:** BOM, Stock Entry, Job Card **Doctype:** Work Order Item **Module:** Manufacturing **Purpose:** Required material rows on a Work Order **Links:** Work Order, Item **Doctype:** Job Card **Module:** Manufacturing **Purpose:** Operation-level shop floor record with time logs **Links:** Work Order, Workstation **Doctype:** Production Plan **Module:** Manufacturing **Purpose:** Plans work orders and material requests from sales orders **Links:** Sales Order, Work Order, Material Request **Doctype:** Supplier **Module:** Buying **Purpose:** Vendor master **Links:** Purchase Order **Doctype:** Purchase Order **Module:** Buying **Purpose:** Order placed with a supplier **Links:** Supplier, Purchase Receipt **Doctype:** Purchase Receipt **Module:** Stock **Purpose:** Goods received against a purchase order **Links:** Purchase Order, Stock Ledger Entry **Doctype:** Customer **Module:** Selling **Purpose:** Customer master **Links:** Sales Order **Doctype:** Sales Order **Module:** Selling **Purpose:** Confirmed customer order **Links:** Customer, Production Plan, Delivery Note **Doctype:** Delivery Note **Module:** Stock **Purpose:** Shipment against a sales order **Links:** Sales Order, Stock Ledger Entry **Doctype:** Item Price **Module:** Stock **Purpose:** Price of an item in a price list **Links:** Item, Price List **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use this reference **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** If you want natural-language answers over ERPNext or another ERP without moving data off your servers, Netray can set that up read-only. **Faq:** #### What is a DocType in ERPNext? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms erpnext doctype list, erpnext bom doctype, erpnext work order doctype, erpnext job card, erpnext bin doctype stock, erpnext manufacturing module, frappe doctype reference, erpnext tab table names --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json