ERPNext Manufacturing in Poland

Material your customers own

In contract manufacturing the customer may supply part of the bill of materials: castings, bar stock, printed circuit boards, fabric or branded packaging. That material sits in your warehouse and goes into your products, yet it is not yours, and it must not appear in your stock value or your cost of goods sold.

ERPNext has the building blocks. An item can be flagged as customer provided, a material request of the customer provided type records what you expect to receive, and the receipt brings it in at zero valuation. How I set it up:

• A warehouse per customer, or a customer-owned warehouse group, so balances can be sent to each customer on request.
• Separate item codes for customer-owned material even when the same part exists in your own stock, so the two never mix in valuation.
• Scrap and shortage rules agreed with each customer, recorded as stock entries with a reason, so the periodic reconciliation does not end in an argument.
• Reports showing material received, consumed and remaining by customer order.

Where customer material crosses a border for processing, the customs and VAT treatment belongs to your advisor, and ERPNext records whatever they decide. The standard manufacturing features are described on the ERPNext Manufacturing page.

Drawing revisions, BOMs and customer approvals

Your customers control the drawings, and every change arrives as a new revision with an effective point you agree together. ERPNext keeps several BOMs per item, each with its own materials, operations and quantities, and marks one as the default. That fits revision control reasonably well when the rules are explicit:

• An item code per customer part number, with the customer's revision stored on the BOM and in a custom field on the item.
• New revision, new BOM. The previous BOM stays active for open orders and spare parts, and the default changes only after the customer signs off the first article.
• Work orders fixed to a BOM, so every production run shows which revision it built.
• The BOM update tool used with care when a shared sub-assembly changes, because it replaces the component across every parent BOM.

Approval can run through ERPNext's workflow feature on the BOM: engineering drafts, quality reviews, production releases. For automotive or medical customers with formal change and part approval procedures, ERPNext records the outcome, while the documentation package belongs in a quality or document system alongside. I mark that boundary early in process mapping, so nobody expects the ERP to replace it.

Routings, job cards and subcontracted operations

A routing in ERPNext is a list of operations, each performed at a workstation with an hour rate and a planned time. Job cards record what operators actually did: time logs, completed quantity and who did the work. For a contract shop running CNC machining, injection molding, pressing or manual assembly, that data drives capacity planning and the cost evidence you need when a customer asks for a price reduction.

Questions I settle with production:

• How fine the operations are. Every operation means another job card entry, so minor steps are grouped to keep the shop floor recording.
• Workstation types for interchangeable machines, so planning is not tied to one specific press.
• Setup time recorded apart from run time when batch sizes vary between call-offs.
• Where data is entered: tablets at the cell, a terminal per area, or supervisors at shift end.

Outside operations such as galvanizing, anodizing, heat treatment or board population run through ERPNext's subcontracting flow in current versions: a subcontracting order to the supplier, material transferred to their warehouse and a subcontracting receipt that brings the finished item back with their charge added. I test it with your suppliers' real quantities, including partial returns and rejected pieces. The manufacturing industry page sets out the wider process view.

Traceability, inspection and costing per customer order

When a customer reports a defect, they will ask which material lot went into which delivery and how quickly you can contain it. ERPNext tracks batch and serial numbers through receipts, transfers, manufacturing entries and deliveries, so a report can walk backwards from a delivery note to the supplier lot. That only works if numbers are captured at receipt and never skipped at the machine, which is a training question as much as a configuration one.

Quality inspection templates hold the parameters and acceptance ranges for a part, and can be required at purchase receipt, at specific operations through the job card and before delivery. Statistical process control and gauge management belong in a quality tool, with results summarized in ERPNext.

Costing decides whether contract work pays. ERPNext calculates BOM cost from material rates and operating cost from workstation hour rates, then posts actual material and operating cost when production completes. With your accountant I agree:

• the valuation method for your own materials;
• how overheads enter workstation hour rates;
• how scrap and process loss are valued;
• a report comparing quoted, BOM and actual cost per customer order.

That comparison is what turns job card data into sharper quotes. See ERP for job costing for the general method.

Where ERPNext stops, and who keeps it running

ERPNext Manufacturing is strong at tying production to stock, purchasing and accounting in one open-source system with no per-user license fees. It is lighter in areas contract manufacturers care about:

• Finite scheduling. Production planning creates work orders and material requests, but detailed sequencing across constrained machines may need a scheduling tool or a custom view.
• Machine data. Collecting counts and stoppages from presses or molding machines is MES territory; ERPNext can receive the summaries.
• Automotive customer requirements such as EDI call-offs and particular label standards mean integration work or a specialist add-on. Confirm with Frappe or the partner what exists for your version.

If those gaps sit at the center of your business, compare Odoo Manufacturing in Poland and read ERPNext and Odoo for manufacturing before deciding.

Support is the other decision. A plant with an in-house Python developer can own custom apps and small changes; a plant without one should budget for an ERPNext service firm or contract developer, with response times written down. Since no partner or support contract pays me anything, my view on who should own the code has no hidden angle. Delivery stays remote, the engagement runs in English, and a plant visit can be planned by arrangement. The platform-level view sits on ERPNext in Poland, and my broader Polish work on the Poland hub.