If you deliver building materials to the Danish construction centers, your product data must be in ByggeBasen — and the requirements are not getting fewer. OpenDIMS has a standard app for InLoad that runs your master data, prices, logistics data, images, documents and EPDs all the way through. No development hours, no installation, and the DB/TUN numbers are returned the same way.

Today, DIY chains set strict requirements for what must be included in ByggeBasen: statutory documentation, sustainability data, EPDs, candidate list substances, DGNB criteria, images, logistics data and prices. Danish Construction Centres has systematised the requirements in an industry book, and the list is getting longer — not shorter.

For most vendors, this means spreadsheets that are sent back and forth, images in folders on a drive, documents that expire without anyone noticing, and a colleague who spends far too many hours typing the same thing in multiple places. It’s rarely a data quality issue. It’s a flow issue.

One source of truth, one app

OpenDIMS is the source of truth for your product data — products, variants, attributes, images, documents, and certificates all in one place. On top of that, there’s the default app for InLoad.

It’s not a custom-built integration project that you have to pay for and wait for. It’s part of OpenDIMS like the other apps, and it’s turned on like any other connection: you choose which products and which fields to include, and which way to go.

InLoad runs the last stretch

InLoad provides the ByggeBase connector as a fully serviced integration. It’s bi-directional, it requires no installation on your computer — just a browser — and it’s queue-based, so data is waiting safely if a receiving system is down.

Through it, master data, prices, logistics data, catalogue data, images, documents and EPDs flow. And the other way, DB/TUN numbers and other data can be pulled out of ByggeBasen again and land back in OpenDIMS — so that your source of truth remains true.

Why the coupling is painless

What usually makes ByggeBasen a project is the distance between your own systems and the connector: who collects data, who keeps the fields updated, who remembers to pass on the new datasheet.

If you use OpenDIMS PIM and have a connector for InLoad, that stretch is already built. There are no development hours to estimate and no deliverables to wait for — there is an app to set up.

• Right in one place. A new price list, an updated data sheet or a new product image is corrected in OpenDIMS and flows on by itself.
• The documentation holds. Certificates, EPDs and statutory documents are stored in DAM together with the product — not in an email thread.
• Faster from product to shelf. The faster the data is at the chains, the faster they can sell.
• Automatic image rear. If the packaging changes, the image also changes at the recipient.

ByggeBasen is one channel out of several

The crucial thing is that ByggeBasen does not become an island of its own. Through InLoad, the same product data also reaches Cobuilder, the Industry Catalogue, Finfo and NOBB — and directly to construction centers and wholesalers such as Bygma, STARK, XL-BYG, Silvan, Bauhaus, Johannes Fog, Davidsen, Solar, Ahlsell, Brdr. Dahl, Lemvigh-Müller and AO.

The product can come from your ERP, be enriched in OpenDIMS, sent to ByggeBasen, to the webshop and to the retailers with their own language and price list — without any of it being custom-built.

Who is it for?

• Manufacturers and suppliers of building materials who sell through Danish construction centers, timber merchants and wholesalers.
• Companies that currently maintain ByggeBasen manually in spreadsheets and web forms.
• Brands with multiple channels that want ByggeBasen, webshop and retailers fed from the same source.
• Smaller vendors just starting out — OpenDIMS starts at $0/month, so you can get started without a budget first.

Get started

Gather your product data in OpenDIMS, turn on the app for InLoad, and agree on the ByggeBase connector with InLoad. Then the flow is up.

The coupling itself is setup, not development. The hard part is to get your data in order in the first place — and that’s exactly what OpenDIMS is built for.