Skip to main content

Sanitary ware, heating and ventilation

PIM for Plumbing, Heating and HVAC

ETIM data, specs and documents ready before buyers check

For manufacturers, suppliers and wholesalers of sanitary ware, heating and ventilation products. WISEPIM turns manufacturer files and ERP exports into ETIM-classified articles and BMEcat feeds.

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

Key features

  • ETIM classes and features

    Adopt ETIM classes as families and see which features are missing.

  • Documents and accessories

    Datasheets and certificates as file attributes, with accessories and successors linked.

  • Feeds for wholesale

    BMEcat 2005 with ETIM, CSV, Excel, XML and Brand Portals.

Who it's for

Built for installation catalogs like yours

WISEPIM fits manufacturers, suppliers and wholesalers that pass technical product data on to wholesale, installers or their own B2B shop.

Built for you if

  • You carry 5,000 to 250,000 articles with connection sizes, pressure ratings, materials and approvals.
  • Wholesalers or a data pool ask you for ETIM-classified data, or you need it from your own manufacturers.
  • Manufacturer files arrive as BMEcat, Excel or PDF price lists, each in its own layout.
  • You supply 25 or more wholesalers, buying groups or installers, or run your own B2B portal.
  • Your wholesalers or installers sit in 3 or more countries, or need your data in 3 or more languages.
  • You run Magento 2, Shopify Plus, Shopware or Akeneo, or an ERP with a webshop on top.

Probably not yet if

  • You need a direct 2BA connection or a ready-made DATANORM or FAB-DIS file. WISEPIM offers neither today; it exports BMEcat 2005, CSV, Excel and custom XML.
  • You have under 2,000 articles with few specs. Start on the free plan and grow into it.
  • You just started a PIM migration. Finish it first, then add WISEPIM as a layer next to it.

Not sure? Send one manufacturer file to the free data readiness check, or book a demo and bring it along.Check one file free

Why installation suppliers look for a PIM

Where installation product data breaks

A valve, a radiator or a pump carries more specs than most products, and every link in the chain from manufacturer to wholesaler to installer wants them in a different shape.

  1. ETIM classes nobody has assigned

    Wholesalers and data pools expect an ETIM class with features and values per article. Your ERP holds a line like Ball valve 1/2" FF PN25 brass.

  2. Specs installers cannot filter

    Connection size, thread type, pressure class, temperature range and material arrive in mixed units and spellings. One wrong value hides the article from a filtered search.

  3. Short texts with hard limits

    German SHK wholesale works with two short text lines of 40 characters each. Marketing names do not fit, and every manufacturer abbreviates differently.

  4. Spare parts and successors drift

    When a boiler or mixer tap is discontinued, the successor, accessories and spare parts have to follow. In spreadsheets those links break first.

  5. Documents spread over shared drives

    Installation manuals, datasheets and declarations of conformity sit in folders. Wholesalers publish whichever version they received last.

  6. Every market, every language

    Belgian, German and French buyers need the same specs in their own language, and they need them again after every change.

How WISEPIM solves it

What a plumbing and HVAC PIM does

Six jobs WISEPIM takes off your product data team, each backed by a feature you can open today.

  • ETIM classes on your own families

    WISEPIM suggests the ETIM class for each product family and the ETIM feature for each of your attributes. Nothing is adopted until someone confirms it, and each article then shows a conformance score against its class.

    Wholesaler ETIM requirements become fields you can check.

  • Specs with units and permitted values

    Typed attributes, option lists, ranges and unit of measure code sets per family. Value merging turns spelling variants of the same material or thread type into one value.

    Installers can filter on every spec in your range.

  • Manufacturer files in one shape

    BMEcat imports read ETIM features into your attributes and fill only empty fields, so next month's file adds what is missing without overwriting your team's corrections. Your own supplier glossary decodes terse codes such as FF or MS, and an import that went wrong can be rolled back.

    Re-import next month's manufacturer file without losing your own edits.

  • Short texts that fit the limit

    Template strings build short texts from your attributes, and a Quality Guard rule with a maximum length flags every text that runs over, so you can fix it before the feed goes out.

    You find an over-long short text before your wholesaler does.

  • Documents and successors per article

    Keep datasheets, manuals and certificates as file attributes. Link accessories, replacement items and related products, and the BMEcat feed writes them as article references.

    A discontinued model points buyers to its successor.

  • One catalog for every buyer format

    Feed Hub builds BMEcat 2005 with ETIM features and custom XML on a schedule. Export templates give each buyer its own CSV or Excel layout, and Brand Portals add a browsable catalog with a PDF datasheet per product.

    A new wholesaler means a new feed, not a new spreadsheet.

In the product

Every ETIM class, feature by feature

Open a class to see every feature ETIM defines for it, in ETIM's own order: which ones are required, the data type, the unit and the permitted values.

An ETIM class in WISEPIM: required features, data types, units and permitted values. Every plumbing and HVAC class in ETIM 10.0 opens the same way.

Compared

WISEPIM next to ERP and Excel

Your ERP stays the system of record for orders, stock and costs. The question is where sellable technical data should live.

Plumbing and HVAC PIM compared with ERP article data, Excel files per wholesaler and enterprise PIM suites
What you needWISEPIMERP article dataExcel per wholesalerEnterprise PIM suites
ETIM classificationETIM 10.0, confirmed suggestions, conformance scoreRarely built inTyped in by handUsually, sometimes as a module
Short texts with limitsBuilt from attributes, length-checkedOne text field, often cut offRewritten per buyerPossible with configuration
Accessories and successorsLinked, written as BMEcat referencesPartly, in the article masterLost when files are copiedUsually supported
Buyer formatsBMEcat with ETIM, CSV, Excel, XML, portalsCustom exports per partnerOne file per buyer, by handThrough syndication modules or partners
PriceFree up to 100 products, then plans with public pricesAlready paid forFree, but paid in hours of workUsually quoted on request

WISEPIM has no ERP connector, no 2BA connection, no ETIM xChange export and no DATANORM or FAB-DIS template. ERP data comes in as CSV, Excel or XML files, or through the REST API on the Pro plan and up.

Compare PIM systems side by side

Setup path

From manufacturer file to wholesale feed

Most teams start with one product group, such as valves or radiators, and one buyer format. How fast it goes depends on how clean your source data is.

  1. Import a manufacturer file or ERP export

    First day

    Upload CSV, Excel, XML or BMEcat. WISEPIM suggests the column mapping, and a BMEcat file brings its ETIM features into your empty fields.

  2. Classify one product group in ETIM

    First week

    Adopt the ETIM classes you sell as product families. You confirm the class once per family and each feature once per attribute, not once per article. Then let AI fill the missing features on every article in that family.

  3. Publish the first wholesale feed

    First weeks

    Set up a BMEcat 2005 feed with ETIM features in Feed Hub, or open a Brand Portal for your buyers. Put it on a schedule and add the next buyer from the same data.

The standards

What your buyers' systems expect

Installation wholesale runs on shared data standards. These are the figures behind them, from the organisations that publish them.

new classes in ETIM 10.0, the current ETIM release
119
ETIM International, 2024
characters for an SHK short text: two lines of 40, no marketing language
80
SHK data quality guideline DQR 11.0, 2025

FAQ

Plumbing and HVAC PIM questions

What manufacturers and wholesalers in installation technology 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

Yes. WISEPIM ships the ETIM 10.0 model, the current release. You adopt the classes you sell as product families, WISEPIM suggests the matching class per family and feature per attribute, and you confirm them. Each article then gets a conformance score. ETIM International plans ETIM 11.0 for 1 December 2026; a project can switch its adopted classes to a newer release once that release is available in WISEPIM.

Take the ERP line Ball valve 1/2" FF PN25 brass. The article sits in the product family you linked to the ETIM class for ball valves, so it carries that class's features. You or AI fill them from the source line and the manufacturer file: 1/2 inch for the connection size, internal thread on both ends, PN 25 for the pressure rating and brass for the body material. A template string builds short text 1 from those values, and a Quality Guard length rule confirms it fits in 40 characters. The datasheet sits on the article as a file attribute, and the BMEcat feed writes it all out with the ETIM codes.

ETIM codes are the same in every language, so a value you pick once means the same thing in every market. When you adopt a class, its features and values come in with the descriptions the loaded ETIM release carries for your project's language, with English as the fallback. National translations come from the ETIM organisation in each country, so ask us in a demo which languages are loaded for your release.

Yes. Feed Hub writes BMEcat 2005 with the ETIM class and features per article, plus order units, prices and images, and article references for accessories and successors. You set the supplier and catalog header once, pin the ETIM release and run the feed on a schedule. After every run, Feed Hub shows how many articles the feed wrote and warns you when articles were skipped because their family has no ETIM class yet, so you know what to classify next. The importer also reads BMEcat files from your own manufacturers.

Not today. There is no 2BA connector, no ETIM xChange export and no ready-made DATANORM or FAB-DIS template. WISEPIM exports BMEcat 2005 with ETIM features, CSV, Excel and custom XML. Ask your data pool or wholesaler which format they accept, and bring their specification to a demo so we can check how close an export gets.

Yes. Keep short text 1 and 2 as attributes, build them from your specs with a template string, and add a Quality Guard rule with a maximum length of 40 characters. Every article that breaks the rule is flagged, so you can shorten the text before the feed goes out instead of a wholesaler cutting it off.

Link them on the article. Accessory, replacement and related are relation types, and bundle items carry a quantity. The BMEcat feed writes accessories as accessories and replacements as follow-up articles. For a spare part that fits several models, a multi-value attribute such as Fits model keeps the list structured and checkable.

Yes. Add file attributes for datasheets, installation manuals, declarations of conformity or approval certificates, and keep media in the media library. Each document then sits with its article instead of in a shared folder, and a Quality Guard rule can flag every article that has no datasheet yet.

Send them a Brand Portal link. They browse your catalog and download it as CSV or Excel, or as a PDF datasheet per product, and when you allow it, dealers who use WISEPIM can import it into their own project. Every download comes from your current data, so nobody works from last year's file. Wholesalers that need a fixed format get a scheduled feed instead.

No. WISEPIM works as a layer next to it. Akeneo syncs both ways. Other PIMs and ERPs exchange data with WISEPIM by file or through the REST API on the Pro plan and up. Your ERP stays the system of record for orders, stock and costs.

AI never adopts an ETIM mapping on its own: every suggestion waits for a confirmation. When AI fills missing features, it can only choose values ETIM permits for that feature, and it leaves a feature empty when the product data does not say. Quality Guard rules check the result, and you can send changes through the Review queue before anything is exported.

That depends on your source data. Most of the time goes into confirming the class mapping and reviewing specs for the first product group. Your current exports keep running while you move. To see how much work your data needs, send one file to the free data readiness check.

Give every wholesaler the same specs.

Start free with one product group, or book a demo and bring one of your own manufacturer files.

4.7