Documentation

Find the right guides for your role

Quick answers for the people filling the catalogue, running a project, or wiring Content Hub into a shop: pick your section below.

For catalogue editors

The daily work: adding items, filling fields, picking images, keeping variants straight.

For project leads

Setting the shape: item groups, form layouts, models and layers, duplicating a project.

For integrators & admins

The wiring: the API, the Shoper connector, slugs, caching, organisations and access.

Before you start

The concepts worth having straight before you click anything, including if you are still working out whether Content Hub is for you.

Concepts

Why compositing beats rendering everything

A catalogue's combinations multiply faster than any render farm. Layers are rendered once and assembled on request, and identical results share one cached image.

Read →
Integrations

Connect a shop

Content Hub talks to your shop through an integration. Shoper is built in; anything else is a development job, and the shop's own API sets the ceiling.

Read →
Concepts

What is a product record?

One row that says how a product looks, what it costs and what it is made of, and that every channel reads instead of keeping its own copy.

Read →
Concepts

Variants or configurations, where is the line?

A variant is a thing you could stock. A configuration is a thing you build on demand. Treating one as the other is the most expensive catalogue mistake there is.

Read →
Concepts

Do I need a PIM as well as Content Hub?

Often you already have one and it is not the thing that is failing. The honest answer depends on which half of the problem hurts.

Read →
Concepts

How many images does one product variant need?

Fewer than a photoshoot suggests and more than a catalogue usually has. The number follows from what the buyer is unsure about.

Read →
Concepts

Prerendered visuals or a 3D engine on the page?

Two ways to show a configurable product, with different failure modes. Most catalogues need the first and are sold the second.

Read →
Concepts

What stays in your ERP?

Most of it. The catalogue layer owns what the customer sees; ownership of everything else does not move.

Read →

If they can't see it, they won't buy it. Let's show them.

Leave your details and we arrange a free consultation with the people who have spent years helping brands sell customised products. You bring the catalogue and the questions. We bring what has worked, what has not, and what it would take for you.

1Mvariants from one source
Same dayprice changes live in the shop
No-codeconfigurators the client runs
No demo booking, no sales sequence. We reply by email and take it from there.