ERPNext Manufacturing, Portugal

Goods movements and the transport document question

Portugal has rules on documents that accompany goods in transit, and those documents may need to be produced by approved software, with the tax authority notified ahead of departure. For a manufacturer this reaches further than customer deliveries: material sent to a sewing workshop, a finishing plant or a heat treatment supplier can also count as a movement of goods. Your accountant decides which movements fall under the rules and which exemptions may help.

ERPNext records every one of these movements as a stock entry, delivery note or subcontracting transfer. That does not make it the right program to issue the transport document. As with invoices, I would not assume that ERPNext, or an app on top of it, holds the needed approval unless its publisher confirms in writing exactly what is covered and your accountant accepts it.

The design I work through with you:

• A list of every movement type: customer shipments, transfers to workshops, returns and transfers between your own sites.
• For each one, the program that issues the document and the trigger from ERPNext.
• The document reference stored back on the ERPNext entry, so warehouse and planning see it.
• A rule for urgent shipments when the link is down.

The invoicing side of the same split is described on ERPNext in Portugal.

Garments and textiles: size grids, dye lots and sewing workshops

A clothing producer working for foreign brands handles collections with many styles, each in several colors and sizes, made from fabric that varies by dye lot. ERPNext can represent this with item templates and variants, batches and subcontracting, but the structure needs care or the item list grows unmanageable within a few seasons.

Design choices I test with your planners:

• Variants: size and color as attributes on a style template, with the BOM defined once at template level where your version allows variant BOMs, and exceptions only where consumption truly differs by size.
• Dye lots: fabric received as batches, so cutting can stick to one lot per order and shade complaints can be traced.
• Cutting and sewing: cut pieces produced in-house, then sent to outside workshops through subcontracting orders with a warehouse per workshop.
• Size breakdowns: customer orders entered by style and size, so production plans and material needs follow the real mix.

ERPNext has no built-in matrix entry screen for size and color grids, which buyers' orders often arrive in. A spreadsheet import or a small custom screen usually fills that gap; I scope it rather than promise it. Pattern-making and marker software stays separate. For broader sector context see ERP for manufacturing.

Mold makers: one tool, one project

Portuguese mold makers build injection molds and tooling for automotive, packaging and consumer goods customers, often abroad. Every tool is a one-off: design, steel purchase, machining, EDM, heat treatment by a supplier, assembly, trials and corrections, then shipment. The commercial terms frequently include payments at milestones.

In ERPNext I model a mold as a project linked to the customer's sales order, with work orders or timesheets for internal operations and subcontracting orders for outside processes. The points that need design:

• BOM depth: a full multi-level BOM for every mold is rarely worth the effort; a project with material requests and purchase orders charged to it often gives better control.
• Machine hours: timesheets or job cards per workstation, priced at hourly rates the controller agrees.
• Milestones: billing milestones on the sales order, with invoices issued by your approved invoicing program and referenced in ERPNext.
• Trials and changes: customer-requested changes recorded as separate tasks so their cost is visible and can be charged.

CAD and CAM data stay in engineering tools; ERPNext tracks cost, time and purchasing. Shop-floor scheduling of a few expensive machines across many tools is where ERPNext is thin, so a planning board or custom view may be needed.

Ceramic tableware for foreign retail buyers

Portuguese ceramics and stoneware producers often supply retailers abroad under the buyer's own label. The same base shape may be sold in several glazes and decors, packed differently for each customer, and produced in campaigns tied to the retailer's season. Breakage and lower-grade pieces after firing are part of normal operations.

How I approach it in ERPNext:

• Shapes and decors: a base item with variants for glaze and decor, or separate items where a decor carries different materials or operations.
• Customer-specific packing: a finished item per customer packaging where barcodes, labels or carton specifications differ, linked to the shared production item.
• Firing batches: each kiln load or production day recorded as a batch, so quality issues can be traced.
• Loss and grading: breakage recorded as process loss, and lower-grade pieces as secondary output where your version supports it, or through a sorting entry.
• Inspection: templates for dimensions, glaze defects and the tests a buyer specifies, with results kept against the batch.

Retail buyers may also expect EDI orders, advance shipping notices and specific labeling, which require integration work rather than standard features; my ERP integration service covers that specification.

Costing, limits and who supports ERPNext

ERPNext posts stock movements to the ledger as they happen, so product cost depends on agreed valuation methods, workstation rates, and how subcontracting charges, process loss and lower grades are treated. I agree these with your controller and accountant, then compare ERPNext cost with your current estimates on a sample of styles, tools or shapes before go-live. If ERPNext also holds the books, the ERPNext Accounting in Portugal page covers the ledger design.

Limits I raise early:

• Finite scheduling of constrained machines or kilns needs a specialist tool or custom work.
• Machine data capture and real-time monitoring sit outside the core product.
• Garment size-grid entry and buyer EDI need custom screens or integrations.
• Every link to the approved invoicing and transport document program must be retested after upgrades on either side.

Support can come from a developer you employ, a Frappe specialist firm or a contractor. One person alone is a risk, especially when the integration with the Portuguese program depends on them. I help you write the arrangement down, with custom code in a separate app. I sell no hosting or development hours. If a platform whose partner can confirm Portuguese document status suits you better, see Odoo Manufacturing in Portugal and the ERPNext vs Odoo manufacturing comparison. Work is remote, with plant visits by arrangement.