How do I connect imos iX to my ERP with one article code?
Let your ERP, imos iX and cutting software share one article code, so materials, edge banding and hardware import without retyping or manual matching.
Short answer: Make the ERP the master for articles and give every imos item a reference to the unique, permanent article number from the ERP. Use the ERP order number as the order name in imos iX too. Your ERP, imos and cutting software then refer to the same article and the same order, with no retyping.
Applies to
- imos iX CAD; applied in iX 2019 up to and including iX 2025
- Areas: master data (materials, edge banding, connectors and hardware), order data, cutting list and CSV export
- Integrations: ERP packages with an import module for imos data (for example Proteus), cutting software such as Ardis
- Last reviewed: October 2026
Step 1: Agree which system is the master
- Make the ERP the source of article data: article number, search name, supplier and price.
- Do not fully create articles in both systems. imos only needs the technical data and a reference to the ERP article.
- Ask your ERP supplier which import module or mapper is needed to read imos data. For some packages this is a separate add-on.
Step 2: Fix codes and search names
- Use an ERP article number that is unique and increments automatically. That number never changes.
- Give every article a clear, unambiguous search name containing what you would search for (for screws, include the length).
- Use the same code structure for materials and edge banding in the ERP, imos and the cutting software, for example
EGG_SPA_18,3_W980_ST02. - Restrict who can create articles and work with template articles and mandatory fields.
Step 3: Link imos items to the ERP article
- For connectors and hardware in imos, enter the ERP article number in the order number field (Bestelnummer in the Dutch interface).
- Map on that permanent number, not on the search name. Search names get edited; the number does not.
- Map stock items such as screws, dowels and hinges as well. The ERP can then reserve them instead of ordering them.
- Avoid ERP sub-articles for hardware with varying parts, such as hinges with different mounting plates. Link those parts separately.
Use a material or colour variable in imos for hardware colour variants (nickel or black, for example). The correct ERP article then appears on the list automatically, without the designer having to search for it.
Step 4: Use the ERP order number as the order name
- When saving a job in imos iX, use the ERP order number as its unique name.
- Add a drawing number and revision, for example
ORDER_2024_001_01A:01for the drawing or section,Afor the revision. - Complete the order data and status in imos. Let the title block show this data and do not explode the title block, because the data is also passed to the ERP.
Step 5: Send additional information along
- Add comments per panel in imos; the export can pass them to the ERP and the cutting software.
- Include the unique panel ID from imos as an extra import field, so any part in the ERP can be traced back to the drawing.
- Make sure edge codes travel in fixed columns per edge. Panels with complex contours otherwise produce dozens of edge codes that need checking by hand.
- Have the ERP export a material list as CSV for the cutting or nesting software: material name without spaces, board size X and Y, and one line per material.
Test every change to the integration with a reference order before going live. A wrongly mapped article only surfaces at purchasing or in the workshop, and by then you are too late.
Why this approach?
As long as the ERP, imos and the cutting software each use their own name for the same item, someone has to translate. That costs time and causes typing errors. With one article code the import becomes a single click: a complete picking list for the workshop, insight into consumption per project for post-calculation, and purchase orders ready per supplier. In practice, companies quickly save a significant share of preparation time per order.
Using the ERP order number as the order name keeps CNC programs and barcodes unique. That is the foundation for barcode or QR scanning at the machine later on. An imos order called Kitchen family X is not unique; an ERP number is.
This approach is ERP-independent. Field and module names differ per package; the principle does not.
Common mistakes
- Mapping on search name. If the search name is edited in the ERP, the link silently breaks.
- Creating everything twice. Two complete article databases always drift apart. Let one system be the master.
- Free-text order names in imos. Without a unique order number, CNC files and barcodes are ambiguous.
- Not mapping stock items. Screws and hinges then go missing from the picking list and post-calculation is off.
Codes that are right at the source. Wood Intelligence Plus is built on fixed abbreviations and a structured naming convention. In the materials library you also give each material and edge band its own ERP code and order text before it reaches imos iX. That way the link with your ERP is settled at the source.
Frequently asked questions
Does this work with any ERP package?
The principle does. Whether the ERP can read imos data directly differs per package. Ask your ERP supplier about their imos import module.
Should I link board materials and edge banding too?
Yes. Materials and edge banding benefit most from one code, because they also appear in the cutting list and on the labels.
What about articles that do not come from imos?
Manage those in the ERP as usual. The integration only covers what imos draws and calculates.
Can I still open existing orders after the switch?
Yes. Old orders keep their own data. Do test whether an old order still imports correctly before rolling out changes.
Further reading
- Naming materials and edge banding in imos iX
- Generate cutting lists from imos iX
- Place and renumber position numbers in imos iX
- imos iX consultancy
More than one solution
Almost every question in this knowledge base has more than one solution. The best fit depends on your workflow, machinery and integrations. Not sure which applies to you, or are you using software we don't (yet) support? Feel free to email Wood Intelligence. We're happy to think along with any challenge.
imos is a trademark of imos AG. Wood Intelligence is an independent consultancy.