Nobody became an engineer to retype article numbers. Yet in many companies that is the final step of every design: the assembly is done, the drawings are finished, and then someone spends an hour copying lines from Inventor into the ERP system. Every line is a chance for a typo, and every design change means doing it all over again.
The good news: an Inventor ERP integration does not have to be a year-long project. Between retyping everything and fully automatic synchronization sits a ladder with rungs you can climb one at a time. In this article we walk that ladder: what each level involves, what it takes to set up and what it delivers. That way you can start small, for instance with a structured export from a toolbox like Thundercad, and only climb further when the need is real.
The ladder: four levels of integration
Almost every Inventor to ERP connection can be reduced to four levels. The difference is who does the work: the engineer, a file, or software that talks to the ERP directly.
| Level | How it works | Setup effort | Typical payoff |
|---|---|---|---|
| 1. Manual | Engineer retypes BOM lines into the ERP | None | None: this is the baseline |
| 2. Structured export | Fixed export from Inventor, the ERP import function reads it | Once, an afternoon to a day | Typing nearly gone, fewer errors |
| 3. Article link in CAD | Engineer looks up and places ERP articles inside Inventor | A few days, with your ERP admin | Numbers correct while designing |
| 4. Custom API | Software exchanges data with the ERP automatically | A project of weeks, plus upkeep | Orders, statuses and documents too |
The temptation is to point at level four right away. Resist it: every level builds on the previous one, and the biggest payoff per hour of setup work sits at the bottom of the ladder.
Level 1: retyping, the silent baseline
Manual copying does not feel like an integration, but it is one: the engineer is the interface. Run the numbers, with assumptions you should adjust to your own situation: a machine with a hundred and twenty BOM lines, half a minute per line for looking up, typing and checking. That is an hour per machine, and every revision brings part of it back. Worse than the time are the errors: a swapped article number only surfaces once purchasing orders the wrong item.
Still, this baseline has value. Whoever describes the manual process once knows exactly which fields the ERP needs. That list is the foundation for every next rung.
Level 2: structured export, the ERP reads it in
The first real rung is a file as the interface. Almost every ERP has an import function that reads lines from an Excel or CSV file, provided the columns match exactly. So the assignment is: make sure the export from Inventor always looks exactly the way the import expects. Column order, units, article number format: define it once, never think about it again.
With Export BOM from Thundercad you export the bill of materials to Excel in your own template, in precisely the column layout your ERP import expects, without shuffling cells afterwards. How to get the underlying BOM data flow in shape, from model structure to purchasing list, is covered in One source of truth: your BOM into purchasing and ERP without retyping; here we stick to the interface itself.
Level 3: your articles in view inside Inventor
Level two removes the typing, but the engineer still works blind: only at import time does it turn out whether an article number exists. The next rung brings the ERP into the CAD environment. With Article Manager you consult articles from your ERP directly inside Inventor: look up a purchased part, see the correct article number and description, and place the component with that data attached. Numbers are right while designing, not just after a check at the end.
The setup work here is mostly about agreements: who creates new articles, the ERP team or engineering? Which fields are leading? Reserve a few days for this together with your ERP admin, including a test on a live order.
Curious how levels two and three would play out in your environment? Build your own export template and browse your article data from inside Inventor, using your own data.
Try 30 days freeLevel 4: custom work for your process
Is there anything left to wish for? Sometimes: creating production orders straight from release, document links, feeding statuses back to engineering. That is the domain of custom integration: software talking to your ERP through an API. Within Thundercad, the Dashboard is the place for that: it is where you activate and manage the tools and connect them to your ERP or other software. How to run such a project without drowning in it is described in Custom links with your own software: how to approach the project.
Only start here once the lower levels are running. An API on top of an unstandardized process mostly automates your chaos.
How to pick your entry level
Which rung fits your company? Walk through these steps:
- Measure the current retyping: how many hours per week go into copying data, and how many errors does purchasing catch?
- Check what your ERP can import and request the specification.
- Put your article numbering policy on paper: without unambiguous numbers you are mostly integrating noise.
- Set up level two and run a few orders with it.
- Only then evaluate whether browsing from Inventor (level three) or custom work (level four) adds something essential.
The ladder is not a race: there are machine builders who happily stay at level two because their ERP import is simply good enough. Climbing only pays off when the current rung demonstrably pinches.
Frequently asked questions
Do I need to sort out my article numbers first?
Yes, that is the first requirement. If the same purchased part lives under three numbers in the ERP, or engineering invents numbers of its own, you will integrate that pollution right along with it. Agree on one numbering policy and define who creates new articles; after that, every form of integration suddenly gets a lot simpler.
What if my ERP has no API?
Then level two remains well within reach: almost every system can import files, and for many companies that covers most of the need. A file-based link is also robust and easy to verify. Custom work through an API is an option for later, not a requirement to get started.
How do I keep the integration from becoming an IT-only project?
By starting small and putting ownership with the process: engineering delivers the export, the ERP team handles the import, and together they test on real orders. If you want to experience the first rung yourself, the free trial month of Thundercad lets you set up your own export template and test it with your own BOMs right away.