Industry: Industrial Machinery Manufacturing | Headquarters: Denmark
Challenge: Prices lived in the ERP, but the price lists were maintained across a mix of Excel, InDesign and Word, in several languages and currencies | Solution: Pagination generates the price lists straight from the structured data, so the ERP is the single source and each language and currency edition comes from one workflow
The Challenge: One Set of Prices, Three Tools
Kongskilde had its prices in an ERP, but the price lists themselves were kept in a mix of Excel, InDesign and Word. Every update meant moving numbers between tools by hand, and the company was, in its own words, looking for something closer to a system that both holds the data and lays it out.
The pattern is common in industrial machinery:
- The source of truth and the document are disconnected. Prices live in the ERP, while the price list is assembled somewhere else, so the two drift apart and updates are slow.
- It is a price catalogue, not just a table. The document carries product images, descriptions and naming alongside the price, so it has to be laid out, not just exported.
- Several editions, several languages and currencies. Kongskilde publishes multiple price lists, so the same content has to come out in different languages and currencies.
The Solution: The ERP as the Single Source
Pagination generates the price list directly from Kongskilde’s structured data, so the ERP becomes the single source and the document is produced from it rather than rebuilt across three tools.
| Project at a glance | Workflow setup |
| Source of truth | Prices held in the ERP, delivered as structured data |
| Document | A price catalogue with images, product descriptions, naming and pricing |
| Editions | Multiple language and currency versions |
| Manual work replaced | A manual mix of Excel, InDesign and Word |
| Output | Print-ready PDF from an InDesign template |
- One source, one workflow. The price data drives the document, so a price change in the source flows into the published list instead of being re-keyed.
- A catalogue, generated. Images, descriptions and naming are placed alongside the prices automatically, so the output is a finished price catalogue, not a raw table.
- Language and currency editions from one dataset. The same content is generated per language and currency, rather than maintained as separate files.
See Pagination price list automation page to discover more.
What Made It Work
The interesting part is that the data was already in good shape: the prices were in the ERP all along. The problem was the last mile, turning that data into a laid-out, multi-language document without three tools and a lot of copy-paste.
Modernising the layout was part of the move. The old price list was restyled, but the product styles stayed close to the original, which kept the setup focused on the data-to-document mapping rather than a redesign. Once that mapping was defined, each new edition became a generation step.
See It on Your Own Price List
See how the full approach fits together on the industrial machinery catalog automation page. Share a recent price list and an ERP or CSV export of the underlying data. A short review shows which parts can be automated and what the first generated price list would look like. Book a demo or reach out with a recent price list.
