One Master, a Thousand Catalogs: How Brandhubify Makes the Segment the Real Unit of B2B Catalog Management

Every Brand Already Runs a Thousand Catalogs. Most Just Don't Know It.

Ask a brand how many catalogs it maintains and the answer is usually "one." Ask the sales team the same question and the honest answer is closer to "one per important account." There is the distributor price file with the discontinued SKUs removed. The regional line card that only shows what is certified for that market. The trade-show sheet with the new launches on page one. The key-account PDF with negotiated prices and no MSRP column. The spreadsheet a broker asked for last quarter, which has quietly become that broker's source of truth.

None of these were designed. They were exported. Each one began as a copy of the product master on a specific day, was edited by a specific person for a specific buyer, and has been drifting away from the truth ever since. The brand thinks it has one catalog because it has one product database. In practice it has as many catalogs as it has commercial relationships — and almost none of them are governed.

This is the real catalog management problem for brands, manufacturers, and distributors, and it is a different problem from the one most catalog management software was built to solve.

What the Procurement World Got Right — and Who It Was Built For

Catalog management as a software category grew up on the buy side. Procurement suites help large organisations control what their employees are allowed to purchase: supplier catalogs are loaded or punched out to, content is normalised, contract pricing is enforced, and a requisitioner sees only the items their organisation has approved. Buyer's guides to catalog management software tend to rank tools on exactly these criteria — supplier onboarding, content quality, search, contract compliance, and the user experience of the person ordering.

ERP-grade product catalogs, of the kind SAP S/4HANA has offered for years, add structure on top. A catalog has a layout. The layout is divided into areas — a hierarchy of sections and sub-sections. Products are assigned to those areas, catalogs can carry variants for different languages or currencies, and the result can be transferred onward to a web shop or a print process. It is a rigorous, governed model, and it reflects a hard-won insight: a catalog is not a list of products. It is a curated, structured view of products, built for a purpose.

Both traditions got the core idea right. Where they leave a gap is in who they serve. The procurement view helps the buyer control what comes in. The ERP view helps the enterprise publish what it has. Neither was designed around the question a brand asks every single day: how do I give each of my buyers exactly the catalog that is right for them, keep every one of those catalogs current, and see what each buyer does with it?

The Seller-Side Problem: Same Products, Different Truths

On the sell side, the catalog is not a single published artifact. It is a relationship. A national distributor should see the full range with trade pricing. A boutique retailer in a different region should see only what ships to them, priced in their currency, with the launch line held back until the embargo lifts. A media partner needs images and descriptions but no prices at all. An architect needs the compliance documents and BIM files but not the case-pack data.

These are not different products. They are different truths about the same products — different subsets, different fields, different assets, different commercial terms. Every brand handles this somehow. Most handle it with exports, because exports are the only tool that lets you cut the master differently for each audience. The cost is that every export is a fork, and every fork is a future data-quality incident: a buyer ordering a discontinued SKU, a retailer publishing last year's ingredient panel, a distributor quoting a price that changed two months ago.

The question is not whether to cut the master differently for each buyer. Every brand has to. The question is whether that cut is a copy or a view.

The Segment: A Catalog That Is a Query, Not a Copy

In Brandhubify, the unit that answers that question is the segment. A segment is a named, curated set of products drawn from the governed product master — and it comes in two forms, because brands need both.

A static segment is a hand-picked list: the twelve hero SKUs for a pitch, the exact assortment agreed with a key account, the products featured in a seasonal campaign. It changes only when someone deliberately changes it.

A dynamic segment is a rule. It is defined by filters on the product record itself — category, status, brand, price, or any custom attribute the brand has defined — combined with an all-of or any-of match. "Every active product in the outdoor category under a certain price." "Everything carrying the organic claim attribute." "All SKUs where the market availability attribute contains this region." When a new product is approved into the master and meets the rule, it appears in the segment. When a product is discontinued, it leaves. Nobody re-exports anything.

This is the shift that matters. The procurement and ERP traditions taught us that a catalog should be structured and governed. The segment adds the missing property for the sell side: a catalog should be computed from the master, not copied out of it. A dynamic segment cannot drift, because it does not store a stale snapshot of the truth. It asks the master for the truth every time.

From Segment to Share: Who Sees What, Field by Field

A segment decides which products are in a catalog. A Brand Share decides how that catalog is presented, to whom, and on what terms. A share combines one or more segments into a single portal with its own clean URL, and every share carries its own configuration rather than inheriting one global setting.

Attribute visibility is the clearest example. Each share can allow every attribute, include only a named list, or exclude a named list. The distributor share can expose case-pack, pallet configuration, and trade pricing. The media-kit share built from the very same segment can expose descriptions, claims, and imagery, and nothing commercial. The data is not duplicated to achieve this. The field-level policy simply sits on the share.

Assets follow the same logic. A share decides whether downloads are allowed at all, whether a downloader must leave an email first, and which tagged assets are visible — so the retailer portal shows packshots and lifestyle images, while the spec-sheet portal shows certificates and technical drawings, and a restricted document tag never leaves the building. Pricing can be shown or hidden per share. Branding, colours, and the portal's headline can be set per share, so a distributor sees a catalog that looks built for them, because it was.

Then come the controls that turn a link into a governed channel: a share can be public or password-protected, can expire automatically on a date with a visible countdown, and can sit behind a gate that captures the visitor's name, company, and consent text before the catalog opens. The procurement world calls this access control. On the sell side, it is also lead capture.

The Catalog That Takes Orders

A catalog that cannot be acted upon is a brochure. The most expensive gap in most sell-side catalog processes is not the catalog itself — it is everything that happens after a buyer decides they want something. They email the rep. The rep re-types the SKUs into a quote template. Someone else re-types the accepted quote into the order system. A third person raises the invoice. Each hop is a chance to get a price, a quantity, or a SKU wrong.

Because a Brand Share is a live view over governed data rather than an exported file, it can carry the transaction too. Each share chooses its call to action — request a quote, check out directly, or browse only. In quote mode, a retailer on their phone adds products to a basket and submits a quote request; the brand responds, the quote becomes an order, and an invoice can be raised manually or automatically on response or submission, with a configured payment term. Product, segment, share, quote, order, invoice: one chain, one source of truth, no re-keying at any hop.

This is where the segment earns its keep commercially. The assortment the buyer was allowed to see, the fields they were allowed to read, and the prices they were shown are the same records the quote and the invoice are built from. There is no reconciliation step between what was offered and what was ordered, because they were never two different data sets.

Closing the Loop: Every Catalog Reports Back

An exported PDF goes dark the moment it is sent. You do not know whether it was opened, forwarded, or ignored, and you certainly do not know which products the buyer lingered on. A share reports back. Each portal tracks views, unique visitors, asset downloads, and quote requests, and can notify the right people — by email, WhatsApp, or SMS, depending on where the team actually works — when a share is viewed, an asset is downloaded, or a quote arrives.

That turns catalog management from a publishing chore into a source of commercial signal. The distributor share that has not been opened in six weeks is a relationship risk worth a phone call. The regional share where the same three SKUs keep getting downloaded is a demand signal worth a stocking conversation. The share that generated quote requests within a day of a launch tells you the segment rule was right. None of this is visible when your catalogs are files.

One Engine, Every Kind of Catalog

The segment-and-share model was built for brands sharing product catalogs with retailers and distributors, but the structure is deliberately not tied to physical SKUs. A record in the master can be a product, a property listing, a menu item, or a service, and the same engine renames itself to match. A real estate team curates portfolios and sends property packs. A restaurant group publishes a digital menu. A healthcare practice shares a curated set of records with a specialist. A digital asset team builds collections and sends them as a governed link.

The vocabulary changes. The mechanism does not: a governed master, a segment that defines a curated subset, a share that defines who sees which fields and assets on what terms, and a feedback loop that reports what happened. That is also why the model holds up across regions. A share for a buyer in Europe can carry consent text on its gate; a share for a buyer in the Gulf or India can be pushed over WhatsApp, where that buyer actually opens links; a share for a US distributor can lead with email. The catalog logic stays the same while the commercial and legal context around it changes per audience.

A Practical Way to Start

Brands moving from exported catalogs to segments rarely need a big-bang migration. A sequence that works:

Start with the master. Segments are only as trustworthy as the product records they query, so the first job is getting the attributes that matter — status, category, region availability, pricing, compliance claims — complete and owned by someone. Attribute templates per category make this enforceable rather than aspirational.

Next, replace your most-exported file first. Find the spreadsheet or PDF that sales regenerates most often, express it as a dynamic segment rule, and publish it as a share to the buyers who currently receive the file. Retire the file. This one change usually removes the largest single source of stale data in the business.

Then layer the controls. Set field-level visibility per audience, turn on the gate where lead capture matters, set expiry on time-bound offers, and switch on the call to action that matches how that buyer actually buys — quote for trade accounts, checkout for repeat replenishment, browse-only for media.

Finally, watch the signal. Review share analytics alongside your pipeline. The catalogs that are opened, downloaded from, and quoted against are telling you which assortments work; the ones that sit unopened are telling you something too.

The Catalog Was Never the Product. The Relationship Is.

The procurement and ERP worlds established, correctly, that catalogs deserve structure and governance. What the sell side adds is the recognition that a brand does not have a catalog — it has a catalog per relationship, and each one has to be right, current, and accountable on its own terms.

Treating the segment as the unit of catalog management is how a brand gets there without multiplying its data. One governed master. As many curated views as the business has buyers. Every view live, every field governed, every link reporting back, and every order traceable to the exact catalog it came from. That is not a better way to export. It is the end of exporting.