Gapfill — building-product attributes the supplier never sent
Chapters
On this page

Where normalised data could actually go

If the thesis is normalise-once/publish-many, the destinations matter as much as the source. Nine specification platforms were researched independently across two continents, and t
Gapfill — building-product attributes the supplier never sentresearchingChapter 8 of 13

If the thesis is normalise-once/publish-many, the destinations matter as much as the source. Nine specification platforms were researched independently across two continents, and the finding is blunt: not one of nine accepts a product feed.

  • Material Bank: no API (api.materialbank.com returns 403, no developer subdomain). Ingest is an "MB New SKU Template.xlsx" emailed in, after which their staff enrich it. Updates mean requesting an export, editing it, and sending it back, taking one to five days. On the physical side, ship 30–40 samples per SKU to their hub with an advance shipping notice.
  • Archello: a manual self-serve wizard, one product at a time. No API, no feed.
  • Archiproducts: managed only; robots.txt disallows /api. Furniture-weighted — a design marketplace with a building-products wing.
  • NATSPEC, Masterspec, EBOSS, ArchiPro, Archify: all account-managed or done-for-you.
  • Only ARCAT (MasterFormat) and NBS Source (Uniclass) are standards-based. Every AU/NZ platform uses a proprietary taxonomy.

The incumbent already sells the normalisation layer. Material Bank offers manufacturers "PIM Lite" — automatic attribute mapping plus a per-product data health score — with a next-generation PIM upsell to push enriched data to your other channels. That is this idea's product, sold by the platform.

Material Bank's economics are order-of-magnitude only. Forbes (2021) reported manufacturers "pay a monthly fee in the thousands… and additional fees when their items are ordered". Business of Home records that Material Bank declined to disclose, with sources suggesting "in the realm of $25 per order" — trade-press estimate, not a rate card. The only published numbers are penalties: barcode $0.15 per piece, missing ASN $250, missing packing list $125. And it does not reach this market at all: Material Bank ships to the contiguous US and Canada only, with hubs in Olive Branch, Mississippi and Crépy-en-Valois, France.

The load-bearing unknown

BIMobject's write API is unverified, and the evidence conflicts. One thread documented an active OAuth2 Publish API at publish-publicapi.bimobject.com behind gated approval. Another found the public content API returning 410 Gone / permanently shut down, while developer.bimobject.com still advertises "the most powerful BIM content API" and serves no endpoints. These are plausibly two different APIs — a withdrawn read API and a live partner write API — but nobody completed an OAuth handshake against either.

This is the load-bearing assumption in the spec-library feasibility verdict. If BIMobject has no working write API, then not one of nine platforms accepts programmatic ingest and the specification-channel pivot is a services business by construction. Test this before any build decision: request BIMobject partner API access and attempt an authenticated publish.

Relatedly, whether ARCAT, NBS, Archbase, BIMsmith or Archify run private partner APIs under NDA is not researchable by search. That is a sales call. Absence of public documentation is not proof of absence.

Consolidation, and which company actually matters here

An earlier entry recorded Anguleris acquiring Concora Spec in February 2025, adding it to a portfolio holding BIMsmith, Swatchbox and Modlar — one owner across research, content, sampling and specification, meaning fewer integration targets and an incumbent with obvious motive to build ingestion itself.

That framing is right in kind but wrong in company for this market. The consolidation that matters for AU/NZ is Hubexo, which owns NBS UK, NBS Australia, Archify across APAC, and Uniclass. The local channel and the only free, API-accessible classification system have the same owner. A dependency on Uniclass in a product competing for the same manufacturer budget as Archify is a single point of commercial failure.

Two further constraints on any "normalise between taxonomies" play:

Uniclass is CC BY-ND — no derivatives. NBS publishes a native REST API returning JSON/XML notation, title and children trees, registration-gated, with quarterly table downloads — better access than previously recorded. But the licence is Creative Commons Attribution-NoDerivatives 4.0. A cross-taxonomy mapping table (ETIM class to Uniclass notation) is exactly the artefact this idea would build and might sell, and it is a derivative work. Publishing or distributing it is likely a licence breach. Internal use is probably fine; the mapping as a product is not. Get legal advice before treating taxonomy mappings as a saleable asset.

And bSDD gives mapping capability but not the dataset — it contains no OmniClass and no MasterFormat at all, so a mapping to the US taxonomies cannot be built from it. Only 2 of 14 platforms accept data programmatically.

The compliance layer is where the published prices are

The one part of this research with fully published prices and a mandated machine-readable format is the environmental-declaration layer.

  • EPD Australasia fees are entirely public: joining AUD 1,075–1,600, annual AUD 720–4,300, and the first 150 EPDs are free. Critically, publication requires "an approved MS Excel template for machine-readable EPDs" — a structured-data obligation with real consequences, unlike anything the spec libraries impose.
  • A live destination with a price: EPD Australasia's July 2026 partnership with Rosella Street puts verified Australasian EPDs into the AU/NZ DPP database at AUD 105 per EPD for members or AUD 300 standard, with no ongoing cost. Caveat: that platform's APIs are described as "upcoming", not shipped.
  • Eco Choice Aotearoa is fully public: NZD 1,000 application plus NZD 1,000–61,000/yr scaled by turnover.
  • CodeMark cost is explicitly "a commercial arrangement between the applicant and the CodeMark Conformity Body" — unquotable by design.
  • GBCA does not certify products at all. It recognises third-party initiatives and assigns a Responsible Products Value your product inherits. Anyone pitching "GBCA product certification" has misread it.
  • NABERS is buildings and tenancies only — nothing a manufacturer can obtain.
  • The NCC itself is published as XML with a schema on data.gov.au under CC BY 4.0. The code is machine-readable; the products are not.

That asymmetry — machine-readable code, unstructured products — is the gap the Australian common data template exists to close, and an EPD obligation that already demands a machine-readable Excel template, free for the first 150 products, is a cheaper wedge into a supplier's data than asking them to care about a taxonomy.

Australia already has an industry-agreed schema, and it is not in a BIM library

This inverts the premise of the specification-channel pivot and is the strongest strategic finding in the dossier.

The NBPC Common Data Template, in the National Building Products Coalition's Building Product Information Traceability and Digitalisation Guide V4.1 (February 2026). Its lineage runs from the 2018 Building Confidence Report to the ABCB National Building Product Assurance Framework (2021), Element 3.

What it mandates per product:

  • A globally unique identifier per AS ISO/IEC 15459.6 — in practice a GTIN.
  • Name, brand, description, model number, net content, unit of measure, variant.
  • Manufacturer and supplier contacts with URLs.
  • A statement of application and intended use naming the NCC edition, building classification, construction type and the specific NCC clause.

Crucially, product classification is explicitly optional, with Uniclass, OmniClass and ETIM all named as acceptable. So in Australia the taxonomy war this research has been fighting is not the binding constraint — identity and intended-use are.

And there is a programmatic destination waiting. GS1 Australia runs a Building & Construction programme partnered with the NBPC, buildingSMART Australasia (MOU), BPIC, the Australian Steel Institute, Standards Australia and the ABCB. Its National Product Catalogue is a GDSN-certified data pool — genuinely machine-to-machine. Construction is not yet a live vertical on it. GS1 membership fees are published (AUD 225 joining, 675–22,895/yr); NPC subscription is not.

The reframe: the spec libraries are manual, but Australia's identifier-and-compliance layer is standards-based, GTIN-anchored, and has a real data pool with an empty construction vertical. If the thesis is normalise-once, the schema to normalise to in this market is the NBPC template — not any platform's field list, and not necessarily ETIM. That makes the ETIM extension work optional in Australia rather than unavoidable.

New Zealand adds the cleanest gap-shaped finding in the entire dossier: the Building Product Information Requirements have been mandated in law since December 2023, specifying required fields with no mandated machine-readable format. A statutory obligation with no schema.