Skip to main content

For manufacturers and wholesalers

PIM for Building Materials

Declared values as data, in every dealer's format

WISEPIM turns declarations of performance, datasheets and ERP exports into typed product data, then sends each merchant BMEcat with ETIM features, its own Excel template or a private dealer portal.

  • ETIM 10.0 model
  • BMEcat 2005 with order units
  • 70+ languages

Key features

  • Performance as data

    Thermal values, fire classes and dimensions as typed attributes with units, and the DoP as a file.

  • ETIM classes

    Adopt ETIM building materials classes as families and check each product against its class.

  • Dealer-ready output

    BMEcat 2005 with order units, Excel templates and a branded dealer portal.

Who it's for

Built for building product suppliers

WISEPIM fits manufacturers and wholesalers whose building products reach the market through merchants, dealers and installers.

Built for you if

  • You make or wholesale building materials, with 5,000 to 250,000 SKUs.
  • Your products carry declared performance: thermal values, fire classes, strength, dimensions per pack.
  • You supply 25 or more merchants, dealers or DIY chains, or run your own B2B portal.
  • Buying groups and merchants ask you for ETIM classes, BMEcat or their own Excel template.
  • You sell in 3 or more countries or languages, or plan to within a year.
  • Someone owns product data, and a technical colleague can check declared values.

Probably not yet if

  • You mainly sell to consumers in your own DIY webshop. The home improvement page linked at the bottom fits you better.
  • You need direct publishing to a sector data pool such as 2BA, or to GDSN. WISEPIM produces BMEcat files and feeds, but has no data-pool connection.
  • You want to manage BIM objects. WISEPIM has no BIM or IFC support.

Not sure? Run the free data readiness check on one supplier file, or book a demo and bring one merchant's data requirements. We check the fit on your own data.

Why building suppliers look for a PIM

Where building product data breaks

Declared values sit in PDFs, the ERP knows pallets but not specs, and every merchant asks for its own format.

  1. Declared values live in PDFs

    A product under a harmonised standard ships with a declaration of performance (DoP). Thermal conductivity, reaction to fire and compressive strength sit in that PDF, not in fields a merchant can filter on.

  2. The CPR is changing the paperwork

    Regulation (EU) 2024/3110 applies from 8 January 2026 and adds a digital product passport once its delegated act is in force. Both expect structured data, not a scanned PDF.

  3. One product, four sales units

    For example, a 1200 x 600 mm insulation board covers 0.72 m², a pack of 4 covers 2.88 m² and a pallet holds 12 packs. Merchants price per m², order per pack and receive per pallet. If the feed says pack where it means piece, the merchant gets a quarter of its order.

  4. Near-identical variants

    Thickness, length, colour and edge profile multiply into thousands of article numbers, each with its own EAN, dimensions and declared values.

  5. A format per merchant

    A buying group asks for ETIM and BMEcat, a DIY chain for its Excel template, a webshop for a feed. Your team rebuilds the same data for each of them.

  6. Each market has its own terms

    Dealers abroad need specs in their language and trade terms. A literal translation of a technical term is often wrong, and the bill grows with every new range.

How WISEPIM solves it

What a building materials PIM does

Six jobs WISEPIM takes off your product data team.

  • Declared performance as fields

    Typed attributes hold each declared value: decimals with a unit such as W/(m·K), option lists for classes such as the Euroclass, and ranges. The DoP and datasheets sit on the product as files.

    Merchants filter on the value instead of opening a PDF.

  • ETIM classes for building products

    WISEPIM ships with the ETIM 10.0 model, which covers building materials. Adopt your classes as product families, let AI map products and fill features, and check conformance per product.

    A buying group's ETIM requirement becomes fields, not a project.

  • Order units merchants can read

    BMEcat feeds write order unit, content unit, units per order unit, minimum quantity and order step from your attributes, with accessories and successors as references. Bulk actions convert units in one go.

    A merchant sees what one pallet or pack contains.

  • One source for every dealer

    Feed Hub publishes BMEcat 2005 and custom XML on a schedule, and saved templates cover Excel requests. Brand Portals give dealers a private catalog: one per dealer group or country, each with its own range, columns, languages and password.

    A new dealer means a new feed profile, not a new spreadsheet.

  • Checked before it leaves

    Quality Guard rules test any attribute per family or category, for example: hold back insulation without a thermal value or DoP file. The B2B data exchange and identifier integrity rule packs give you a start.

    Gaps are caught here, not by a merchant.

  • Sales copy and translations from specs

    AI writes descriptions and titles from your attributes and translates them into 70+ languages. A translation glossary keeps trade terms consistent, and your reviewer per language approves the result in the Review queue.

    Dealers abroad get the same data as your home market.

Integrations

Where your data goes next

Most building suppliers deliver files and feeds to merchants. Where you also run a B2B shop, a webshop or another PIM, these connections apply.

In the product

Read a supplier's BMEcat file

Upload a supplier's BMEcat file in Feed Hub. WISEPIM shows the ETIM release and classes the file declares and proposes the field mappings before anything is saved. ETIM features from the file only fill attributes that are still empty.

Feed Hub import: a supplier's BMEcat catalog with its ETIM classes, before anything is saved.

Compared

PIM versus ERP and spreadsheets

Your ERP stays the system of record for orders, stock and costs. The question is where declared values and dealer-ready data should live.

Building materials PIM compared with ERP product data, spreadsheets per merchant and enterprise PIM suites
What you needWISEPIMERP product dataSpreadsheets per merchantEnterprise PIM suites
Declared performanceTyped attributes with units, DoP as a fileMostly logistics and finance fieldsColumns copied from PDFsYes
ETIM classificationETIM model, AI class mapping and conformance checksRarely built inTyped in by handUsually, sometimes as a module
Order and content unitsFrom attributes into every BMEcat feedStored, but exported per partnerRetyped per fileYes, set up per channel
Merchant formatsBMEcat 2005, Excel templates and Brand PortalsCustom exports per partnerOne file per merchant, by handThrough syndication modules or partners
Copy and translationsAI drafts from specs in 70+ languages, you reviewNot its jobWritten and translated by handOften a separate tool or add-on
PriceFree up to 100 products, published plans after thatAlready paid forFree, paid in hoursUsually quoted on request

WISEPIM has no ERP connector and no data-pool connection. ERP data comes in as CSV, Excel or XML exports, or through the REST API on higher plans.

Compare PIM systems side by side

Setup path

From supplier file to first feed

Most suppliers start with one product family and one merchant format, then widen the scope. How fast it goes depends on how clean your source data is.

  1. Import an ERP export or supplier file

    First day

    Upload CSV, Excel, XML or BMEcat. AI proposes the column mapping, you confirm it and save it as a profile, so the next delivery imports without remapping. BMEcat features from your own suppliers are read into attributes.

  2. Model one product family

    First week

    Adopt the ETIM class you sell in, or define your own attributes for declared performance, units and the DoP file. AI fills empty features from your product text and web research findings, and you review the result.

  3. Send the first merchant its data

    First weeks

    Publish a BMEcat 2005 feed with ETIM features and order units in Feed Hub, save an export in the merchant's Excel template, or open a Brand Portal for your dealers. Add a Quality Guard rule first, so incomplete products stay home.

Proof

What runs on WISEPIM today

We have no published building materials case yet. These are facts about WISEPIM today and two technical catalogs that run on it.

e-commerce teams use WISEPIM
100+
WISEPIM, 2026
products managed per customer on average
26,488
WISEPIM, 2026
saved by Tackerplein, an industrial and hardware webshop, on German translations
€45,000
Tackerplein case
products and variants translated into German and British English for ProCleanroom, a technical cleanroom supplier
3,100
ProCleanroom case

FAQ

Building materials PIM questions

What manufacturers and wholesalers ask before they move their product data.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Book a demo

A product information management system for building materials is the one place where technical specs, declared performance, documents, sales units and marketing copy come together. Every merchant, dealer and channel then receives the same complete data in the format it asks for.

Yes. ETIM covers the building materials sector next to electrical and HVAC. The ETIM 10.0 model is already in WISEPIM: you adopt the classes you sell as product families, let AI map products to classes and fill features, and check conformance per product. Feed Hub exports BMEcat 2005 with ETIM features, and the importer reads the ETIM features in BMEcat files from your suppliers.

WISEPIM uses the international ETIM release, with English names for classes and features. National language packs are not included; the Dutch one, for example, is reserved for ETIM members. If you have access to a pack, ask us about adding it. Your product copy translates into 70+ languages, and the translation glossary keeps trade terms consistent.

Yes, as structured data. Keep the DoP number as an attribute, each declared value as a typed attribute with its unit, and the DoP PDF as a file attribute. A Quality Guard rule can hold back products in a family that miss them. WISEPIM does not draw up declarations or assess conformity: that stays with you and, where required, your notified body. Selling in several countries? Each member state can require the DoP in its own language, so keep one file attribute per language, for example DoP (NL) and DoP (DE).

Yes. A custom team role limits a member to the fields and attributes you choose. Content editors write descriptions and titles, while only your technical team changes declared values and the DoP file.

Regulation (EU) 2024/3110 entered into force on 7 January 2025, and its main part applies from 8 January 2026. The 2011 regulation and the new one coexist for a long period: a harmonised standard cited under the old rules stays valid under them until the Commission withdraws it. The new regulation adds a declaration of performance and conformity and a digital product passport, which becomes mandatory 18 months after the European Commission's delegated act on the passport system enters into force. WISEPIM does not issue passports. It keeps the values and documents they draw on structured per product.

Yes. Store the order unit, content unit, units per order unit, minimum order quantity and order step as attributes. BMEcat feeds write them into the order details of each article in an ETIM class, a Brand Portal shows them when you include them, and bulk actions convert units on many products at once. One thing to set before the first feed: BMEcat requires an order unit on every article, so a product without one goes out as C62, the code for piece. Fill it in for each family, for example MTK for goods sold per square metre, and add a Quality Guard rule that holds back products without one.

No. Run one Brand Portal per dealer group or country. Each portal has its own range by category, family or filter rule, its own columns, languages and password and, if you want, its own pricing rules. Dealers browse, export to CSV or Excel and download a PDF datasheet per product.

Not the ETIM features. Features from a supplier's BMEcat file only fill attributes that are still empty, so a declared value your team corrected stays as it is. The mapping for each supplier is saved as a profile, so the next delivery imports without remapping.

Not directly. WISEPIM has no data-pool connection. It produces BMEcat 2005 files and feeds, custom XML and Excel exports, and you deliver those to a pool or platform in the way it accepts files.

Your ERP stays the system of record for orders, stock and costs. There is no ERP connector: product data comes in from ERP exports as CSV, Excel or XML, uploaded or delivered by link or FTP/SFTP, and the field mapping is saved for the next run. Higher plans add the REST API.

WISEPIM is free up to 100 products. Paid plans are priced by product count, and every plan includes unlimited users and every language. Web research starts on Growth and Quality Guard on Business.

Give every dealer the same declared values.

Start free with one product family, or book a demo and bring one supplier file or one merchant's data requirements.

4.7