We have integrations with Uniconta, Microsoft Dynamics 365 Business Central and NAV, and we have customers running Visma Business, Visma.net and Iptor. If you run a different system, get in touch. If it has an API, or runs on-premises on SQL Server, there's usually a way.
Chainbox PIM
An overview of a large product range, with your product data from the ERP as the foundation, out of the box.
Why Chainbox PIM
In many companies, a small team has to handle a lot of item numbers. Data from suppliers varies in quality and availability, and there's often old product data that needs cleaning up first. After that, the range has to be maintainable over time, so you can easily get on with what matters.
We've made a few key decisions about the workflow for creating products, and beyond that we offer a very flexible PIM, where building category hierarchies, publishing channels, modelling the data structure and setting up the editing interface are largely up to you and how you want it configured - including which fields are owned by the ERP and which are edited in PIM.
The core workflow you'll see with our solution is that - when a product is created in the ERP - it'll be available for editing in PIM shortly after - the rest is really up to you, there are lots of options, and it can grow with you as your needs change.
The workflow for creating products from the ERP isn't the only way in. Products can also be created manually or by CSV import in the interface, and cleaning up old product data can be done with bulk updates or by exporting to a spreadsheet, correcting it and importing it again. The automation can be extended through the included API, which opens up integrations with, for example, supplier ranges.
Battle‑tested in the real world
We see benefits from connecting a PIM to your ERP from as few as 1,000 item numbers - most of our customers have more than 20,000 item numbers in PIM, and many have over 100,000 - the more products you handle, the more value you get from the system.
Editing that fits how you work
In PIM you shape the editing experience yourselves, so it makes sense for you and lets you work as efficiently as possible.
Create specification fields for products and categories from a wide range of data types, grouped logically according to your own product taxonomy.
Set up your own forms and tabs with selected fields, and create efficient editing experiences for specialised workflows.
Define your own task queues with built-in views, so you can work your way towards "inbox zero" in the hunt for perfect product data. When the queue is empty, you're up to date, and when a new product arrives from the ERP, it shows up on its own.
Bulk updates
Save time by editing many products at once.
In a single action, you can update all the relevant products using the powerful filters and our bulk update tool. That works for both standard system fields and your specialised data attributes. Before the change is made, you can see how many products it affects.
AI may be everywhere, but there's real satisfaction in simply solving a simple task with a big result, quickly, without having to write a prompt or wait for an agent to run its workflow.
Overview and cross-sections
Set up advanced views of any cross-section of your product data using filters.
You can set up as many views as you like, zooming in on selected product segments and showing specific fields.
Get a quick overview of what matters in a given context, and support an efficient workflow.
The integration
The built-in ERP integration makes sure product data flows into PIM automatically.
Every update to product data - whether it comes through the integration or from editing in PIM - publishes changes as system-to-system messages. That means external sales channels or other systems that depend on product data can be updated quickly and efficiently.
Images and files
Configure the image sizes you need in PIM, and the system does the rest. When you attach media to products and categories, they're optimised automatically and available via the API. You can configure a CDN endpoint so you can share digital media with external parties without giving them API access to the rest of the system.
Import/export
In PIM it's easy to export selected fields for the whole range, or a segment of it, to CSV. It's just as easy to import CSV data into PIM.
That means data can quickly be made available for further work in other systems, for example if you'd rather do some of the data work in a local spreadsheet. When importing, you can choose to update existing products only, so a typo in an item number doesn't create a new product.
Support for several category hierarchies and publishing channels
The PIM lets products be searched for, related to and navigated through one or more product category hierarchies.
That means you can create lots of different entry points to specialised product views, and the system supports different workflows and data requirements. For example, copywriting and data completeness aimed at a specific language or sales channel.
Languages and locales
You can create any number of locales in the PIM, and for product data to be translatable, the relevant fields must be created with a data type that supports multiple languages. Once the languages you need are set up and translation is enabled, you can maintain translations in the supported fields.
That's why it's important to configure the fields' data types correctly from the start, so product information can be maintained in the relevant languages and shown correctly in the related sales channels.
Technical values such as dimensions are usually shared across all languages, while product names and descriptions often need to be translatable.
If a user is working on text in a field, and the field has values in other languages for that product, automatic translation becomes available. The translation then needs to be reviewed and corrected manually if necessary.
Variants
A work jacket in three colours and five sizes is 15 item numbers in the ERP, but the customer should see one product where they choose colour and size. In PIM, the variants are grouped under a parent product with one or two dimensions, for example colour and size, and each variant is still its own item number with its own data.
You can create as many variant groups as your range needs, for example colour, size, length or power. The groups and their values are created in one place and reused across the range, and each product uses one or two of them.
Images can be added per colour, so the customer sees the right colour when they select it, and the description is maintained on the parent product.
Develops with our customers
Chainbox PIM has run without interruption for 9 years and is continuously developed. Much of what the system can do today was added because a customer had a need that had to be met.
Updates roll out to all customers continuously, without you having to buy a new version or start an upgrade project.
A selection of our PIM customers
B2B & B2C
B2B & B2C
B2B & B2C
B2B & B2C
These are four of more than 70 live installations. If you'd like to talk to a customer in your own industry, we'll find a reference you can call.
Built for people - with room for AI
PIM is built for the people who work with product data every day. It's quick to find the products that are missing something, and quick to fix them, even without AI.
But there are tasks where a machine can do the heavy lifting, for example writing product descriptions from specifications or aligning copy across a whole range. For that, we have AI Product Workspace.
AI suggests - you decide
You choose the products to work on and write the instructions. One agent writes the copy, and another agent checks it, before someone from your team reviews the changes and approves them. Only then do they go into PIM. The AI works on a cache of your data, not directly in PIM, so it can't put load on the system or change anything on its own.
Your own AI access
You connect your own agreement with, for example, OpenAI or Anthropic and pay the AI provider directly for what you use. We don't sell AI tokens or usage bundles, so you can see exactly what the AI costs and choose the model yourselves.
Or your own way
Of course, you can also work with AI without AI Product Workspace. Export product data from PIM, let the AI work on the copy in your own environment, and import it again. With the API, you can also build it straight into your own workflows.
FAQ
Once the integration with the ERP is set up, the products come into PIM. Then you enrich them: import from CSV, change lots of products at once in PIM or via the API, or fine-tune individual products or variants.
We handle the ERP integration, the data mirror, PIM and the webshop, and we host and monitor all of it. You maintain products, customers and prices in the ERP as usual, and product copy and images in PIM. Your ERP partner takes care of customisations and support in the ERP. If you choose to build the front end in another webshop system, you and your web agency are responsible for it.
No. Data goes from the ERP to PIM. The fields that come from the ERP are locked in PIM and are corrected in the ERP as usual, and what you add in PIM stays in PIM.
Yes. PIM doesn't depend on the webshop, and your own front end can fetch data via the API. It's the webshop that builds on PIM and Webshop Management, not the other way round.
Yes. Data in PIM can be exported to text or fetched via the API, including images and files.
Is Chainbox PIM right for you?
Book a demo and we'll show you PIM with your own products, and together we'll work out whether it's right for you.
Book a demoOr call +45 70 22 11 97.