ERPNext Manufacturing in Denmark

How Danish design brands make things

A Danish lighting or furniture brand may sell a few dozen designs, each in many combinations of size, color, material and finish. The design team owns the drawings and specifications. Production is spread out: metal shades from a spinning workshop, glass from a specialist, wood components from a turner, cables and electrical parts from a component supplier, sometimes complete products from a contract factory elsewhere in Europe or in Asia. A Danish workshop may then assemble, wire, finish and pack to order.

That model creates ERP needs that differ from a classic factory:

• Many variants, modest volumes: the item master grows quickly, and naming discipline matters.
• Outsourced making: the most important production steps happen at suppliers, so purchasing and production planning are tightly linked.
• Short in-house routing: assembly, wiring, quality check and packing, often across few workstations.
• Quality at arrival: finish and fit problems are cheaper to catch at goods receipt than after a retailer complains.
• Cost in several currencies: suppliers invoice in euros, dollars or other currencies, while margin is managed in kroner.

ERPNext handles this with item templates and variants, multi-level BOMs, subcontracting orders, work orders and job cards, quality inspections, batch numbers and landed cost vouchers, all in one open-source database. The question is how to configure them so a growing collection stays manageable. The general approach is on my ERPNext manufacturing page.

Variants and BOMs that survive a growing collection

The structure of items and BOMs decides whether ERPNext helps or hinders a design company. ERPNext item templates carry attributes, and each combination becomes a variant item with its own code, stock and price. A pendant lamp in several sizes and finishes becomes a set of variants that the warehouse, sales and the web shop all recognize.

BOMs need more thought. ERPNext allows a BOM on the template that variants can draw on, and individual BOMs per variant where the structure really differs. I work through the collection with your product and operations people and agree rules such as:

• finish-dependent components, like a painted shade or an oiled wooden base, are variants of their own component items
• shared components, like a cord set or socket, are referenced once and reused
• sub-assemblies prepared ahead, such as wired fittings, get their own BOM and stock
• a new finish triggers a defined checklist rather than ad hoc copying

For brands launching new colors each season, a bulk creation routine through ERPNext's data import or a small script can generate variants and their BOMs from a spreadsheet the product team maintains. That needs an owner, but it replaces hours of manual entry and inconsistent naming.

If your sales depend on customers configuring products online with rules between options, a dedicated configurator connected to ERPNext usually serves better than forcing every combination into variants.

Contract makers, subcontracting and in-house assembly

Danish design brands work with outside makers in two distinct ways, and ERPNext should reflect which applies to each supplier.

Buying finished or semi-finished goods. The maker sources its own materials and delivers a component or complete product to your specification. In ERPNext this is a normal purchase order against the item, with the specification and drawing revision attached. Supplier lead times and minimum quantities feed planning.

Supplying materials for conversion. You send your own materials, for example fabric for upholstery or shades for painting, and pay the supplier for the work. ERPNext's subcontracting order transfers your material to a supplier warehouse, and the receipt consumes it while adding the service cost. Your stock stays visible while it sits at the supplier.

In-house work picks up from there. A work order for final assembly consumes the purchased and subcontracted components, job cards record wiring, finishing and packing time, and the finished variant enters stock with its cost. Where you assemble to order for retailers or contract projects, work orders can be raised directly from sales orders.

Points to settle before go-live:

• how partial shipments from overseas makers are received
• how rejected pieces are returned, credited or replaced
• which supplier documents, such as test reports, are attached to each receipt

Each answer is tested with real documents from a recent order.

Inspection, traceability and landed cost in kroner

Quality problems at a design brand are usually visible ones: a finish that varies between batches, a wooden part that does not fit, a lamp missing its required markings. ERPNext's quality inspection can be made mandatory on purchase receipts for chosen items, with templates listing the checks and readings. Lighting brands might check finish, dimensions and the presence of required electrical safety markings; furniture and textile brands might record color batch or dye lot. The product safety and marking requirements themselves are for your compliance advisor to define; ERPNext only records that the checks were done.

Batch numbers connect the chain. A batch on incoming shades or fabric, carried into the assembled product, lets you answer which retailer orders received items from a questioned delivery.

Cost needs the same care. A product made in Asia carries freight, duty, insurance and handling on top of the supplier's price, and those costs arrive on separate invoices weeks apart. ERPNext's landed cost voucher spreads such charges across the receipts they relate to, by value, quantity or weight, and updates stock valuation. Without it, margins by finish or product look better than they are.

Supplier invoices in euros or dollars are converted at the document rate, and your accountant decides how exchange differences are posted. For the finance side see ERPNext accounting in Denmark, which also covers the Danish bookkeeping questions that apply to the whole system.

Who supports it, and when another system fits better

ERPNext suits Danish design manufacturers that are willing to own their system. The support options are a staff developer who knows Python and the Frappe framework, an ERPNext implementation partner working under contract, often remotely from another country, or managed hosting with a freelance developer for occasional changes. Ask any partner which manufacturers they have supported, how fast they respond and who holds the rights to the code, and confirm the details with them rather than relying on my summary. Every custom app, script and integration goes into a register with an owner and an upgrade test.

Integrations deserve their own plan. Design brands often run a web shop, retailer portals or EDI with large retailers, and a product information system for images and texts. Each connection to ERPNext needs an owner and a decision about which system holds master data.

ERPNext is probably not the best fit if:

• online product configuration with complex option rules drives sales
• you need full PLM with formal approval of design changes
• large volumes and many constrained resources require advanced planning
• nobody will look after custom code and upgrades

A specialist system or Odoo Manufacturing in Denmark may then suit you better. I am independent of Frappe and every implementer. Work runs remotely, with a workshop visit only by arrangement. See the ERPNext Denmark page and the ERP consultant Denmark page.