Short answer: in building and plumbing materials, four things strain an ERP: variants, units, price lists and documents
A pipe, a fitting or a valve looks like one product, but by diameter, length, material, pressure class and packaging it turns into hundreds of separate stock items. The same product is priced differently by dealer group, quantity and project; it converts between meters, lengths, boxes and pallets; and for some construction products a declaration of performance and CE marking travel with the goods. A general-purpose ERP handles each of these alone, but with all four at once the data model becomes decisive.
The table below summarizes the four areas to probe in a demo. It is our own list, not a standard.
| Area | Why this sector makes it harder | Question for the ERP |
|---|---|---|
| Variants | The product of the attributes creates many separate stock items | Does it keep the parent product and its variants apart and report stock per variant? |
| Units | Sales, warehouse and production work in different units (pieces, meters, lengths, boxes, pallets) | Is unit conversion defined per item and visible on documents? |
| Price lists | Dealer group, quantity, project and date stack up | Is the conflict rule written down, and can a list be updated in bulk? |
| Documents and traceability | Technical documents travel with the product; batch and certificate tracking | Can documents be tied to a product and a batch? |
We covered general wholesaler criteria (multiple warehouses, credit terms, credit limits) in our wholesaler ERP article and the manufacturing side in our manufacturing ERP article. If you are both a manufacturer and a wholesaler, both apply. This article stays on what is specific to the sector.
Variant products: parent, variant and the number of combinations
A good ERP stores a product in two layers: a parent product that carries the shared attributes (for example "PPR pipe") and a separate variant for each combination (for example "PPR pipe, 25 mm, 4 m"). Odoo's variants documentation illustrates the model: a product with four colors and five sizes has twenty variants, and each variant keeps its own inventory count, sales totals and similar records. The documentation also shows that price can differ by attribute value (in its example the red color adds three to the template price) and that pricelist rules can apply to the template or to individual variants.
In plumbing, the numbers grow quickly. This is an example calculation, not a real catalog: a pipe family with 6 diameters, 3 lengths, 2 materials and 2 pressure classes makes 6 × 3 × 2 × 2 = 72 variants. So in the demo, ask for:
- Matrix entry: choosing variants from a diameter-by-length grid on an order line rather than searching one by one. Odoo's sales features page calls this "variant grid entry"; what is the equivalent in your ERP?
- Stock and barcode per variant: each combination needs its own barcode and warehouse stock; seeing "diameter 25" stock only as a total is not enough.
- Bulk variant generation: when a new diameter is added, are variants opened by hand across the whole family, or automatically?
- Inactive variants: combinations you do not make or sell should be closable so they do not clutter the catalog.
- Attribute search and filters: a sales rep should be able to find an item by typing "32 mm, 6 m".
Units: meters, lengths, boxes and pallets
A pipe may be sold by the meter, counted in the warehouse by the length and shipped by the pallet. According to Odoo's sales features, products can be sold in multiple units of measure with the system managing conversion; look for the same in your ERP. Ask:
- Is the conversion ratio defined per product? (The same "length" equals a different number of meters on different products.)
- In which unit is the price given and the invoice issued, and how does rounding work if they differ?
- Is cut or broken-unit selling supported? (If you sell a pipe by the meter, what happens to the leftover piece in stock?)
- Are unit codes carried correctly on waybills and e-invoices? (For the document flow see our 2027 readiness article.)
Multiple price lists: rule order and bulk updates
In building materials, price is rarely a single number. Odoo's description says pricelists compute the right price from customer conditions such as region and price tier, or order conditions such as quantity and time. The typical mix in this sector is dealer group (A, B, C), quantity breaks (pallet, truckload), project price, time-limited campaign and a list renewed because raw material prices moved.
First ask how rules conflict: if a dealer qualifies for a "group B list", a "project price" and a "campaign" at once, which one wins, and are discounts added, multiplied or merged? We described how to set that order up on a B2B site in our wholesaler B2B site article; if the ERP and the portal do not follow the same order, the same order gets two different totals.
Our suggestion is to model price lists like this (an example model, not a standard):
| Table | What it holds | Example fields |
|---|---|---|
| Product (parent) | Shared attributes | Name, category, base unit |
| Variant | Each combination | Diameter, length, barcode, stock unit |
| Price list | A set of prices | Name, currency, validity start and end |
| List line | One combination's price | Variant, unit price, minimum quantity |
| Dealer group link | Which dealer sees which list | Dealer, list, priority |
Test it in the demo with three things:
- Bulk update: when a raw material price moves, how many steps does it take to raise a thousand variants by a percentage and publish a new list, and is the old list preserved?
- Validity date: if a new list starts tomorrow, do today's orders close at the old price?
- Price history: can you later see which price a dealer was shown last month?
The dealer network: portal, credit limit and order flow
Companies with a wide dealer network take orders by phone, WhatsApp and Excel, which is the main source of price-list errors and double entry. We described the way out in our move from WhatsApp and Excel to a B2B portal and how to connect a portal to an ERP in our dealer portal and ERP integration article. In this sector, ask in particular:
- Does a dealer see only their own list price in the portal, or is there any risk of seeing another dealer's price?
- Does the variant matrix work in the portal too, or does the dealer key in line by line?
- Is stock shown to the dealer as "in/out" only, or with warehouse and estimated delivery?
- Are dealer credit limits and overdue balances checked at order time? (Detail in our wholesaler ERP article.)
Documents and traceability: declaration of performance and batches
Some construction products fall under a product regulation, and documents travel with the goods. In Turkey the Construction Products Regulation (305/2011/EU) has been in force since 1 July 2013 (according to the Türkiye İMSAD guide); for a construction product covered by a harmonized standard the manufacturer draws up a declaration of performance (DoP), and the CE mark cannot be affixed without it. The Ministry of Trade's Product Rules Database explains that the manufacturer draws up the declaration in the format of Annex 3 of the regulation and places the product on the market with the CE mark.
For a manufacturer-wholesaler, the consequences on the ERP side are:
- Importers and distributors are responsible too. Under Article 15 of the regulation, an importer must guarantee before placing the product on the market that the manufacturer has carried out the required assessment and drawn up the technical file and the declaration of performance (regulation text). The Türkiye İMSAD guide says that an importer or distributor who places a product on the market under their own name or brand is treated as the manufacturer. If you sell under your own brand, this concerns you directly.
- There is a retention period. The same guide says the manufacturer must keep the technical documentation for 10 years from the date the product is placed on the market and must keep complaint records. Keeping the document tied to the product and batch makes those records easier to find.
- Linking batch and document. Our recommendation: attach the declaration of performance to the product card and to the batch or production-date range it applies to, and make it reachable from the dispatch document. If a recall is needed, you should be able to work out which batch went to which dealer.
This section is not legal advice: whether a product falls under the regulation, which standard it follows and which documents it needs vary by product. Check the scope in the Ministry of Trade's Product Rules Database and your sector's standards, and consult a conformity adviser if necessary.
Ready-made ERP or custom adaptation?
A variant matrix, per-item unit conversion and layered price lists come ready in most standard ERPs, but your sector's special rules (for example recalculating a project price per dealer, or linking documents and batches) often call for adaptation. We described the decision framework in our off-the-shelf vs custom software decision matrix and the total cost of an ERP in our 5-year cost article.
Demo-day checklist
- ☐ Have a product family with four attributes (diameter, length, material, pressure) opened with its variants and count how many appear
- ☐ Add an order line using matrix entry
- ☐ Sell the same product by the meter, by the length and by the pallet and follow the stock decrease
- ☐ Define two conflicting price rules for a dealer and have the result explained
- ☐ Raise a thousand variants by a percentage and publish a new list
- ☐ Set the new list's start date to tomorrow and ask for today's order price
- ☐ Tie a declaration of performance to a batch and trace backwards which dealer received it
- ☐ Try to see another dealer's price in the dealer portal
Frequently asked questions
What is the difference between a variant and a separate product card?
With variants the shared information (name, category, description) sits in one parent product and each combination carries only its own stock, barcode and price difference. If you open a separate card for every combination, a shared change (a description, a category) has to be applied to hundreds of cards by hand. Both work for a small catalog, but in this sector the variant model scales.
Should price lists live in the ERP or the B2B portal?
Name one owner for the data; in most businesses that is the ERP, and the portal reads it and applies the calculation rule exactly. Keeping separate prices in two places is the most common reason the same order shows two different totals. There is more detail in our wholesaler B2B site article.
Is it mandatory to keep the declaration of performance and CE record in the ERP?
The regulation requires that the document is drawn up and kept, not that it is kept in the ERP. Keeping it in the ERP makes the document linked to the product and batch and easy to search; that is our recommendation. Settle with a conformity adviser which documents apply to you.
How do I move hundreds of variants from Excel into an ERP?
First clean the attributes (diameter, length, material) into one naming convention, then bulk-load the parent products and variants using code rules. To plan the move in stages see our 90-day Excel-to-ERP plan.
If you want to assess your sector-specific product, price and dealer processes together from an ERP and B2B angle, see our custom software development service or get in touch.
Sources: Product variants (Odoo 20.0 documentation), Sales features (Odoo), Yapı Malzemeleri Yönetmeliği (305/2011/AB) text (Alomaliye.com), Yapı Malzemeleri Yönetmeliği (305/2011/AB) text (Ministry of Environment, Urbanization and Climate Change website), Yeni Yapı Malzemeleri Yönetmeliği Rehber Kitap (Türkiye İMSAD), Yapı Malzemeleri (Turkey Product Rules Database, Ministry of Trade)