Documentation
Quick answers for the people filling the catalogue, running a project, or wiring Content Hub into a shop: pick your section below.
Nothing matches that. Try a field name, an entity, or the symptom you are seeing.
The daily work: adding items, filling fields, picking images, keeping variants straight.
Create an item in a group, fill in its fields, and see it in the catalogue.
Read guide →CatalogueThe same form you filled when you created it. Fields commit together when you save, so a half-finished edit is never visible.
Read guide →CatalogueFabrics on a sofa, legs on a table. A relation is a field, and it only offers items from the group you aimed it at.
Read guide →CatalogueSearch is scoped to your project and matches names across items, products and models, so you rarely need to remember where something lives.
Read guide →VariantsA product group holds the options a product varies by. A variant is one valid combination of them.
Read guide →Media libraryImages live in the project's media library, not on the item. Upload once, use anywhere.
Read guide →VisualsLayers stack in a set order, each one answering to the parameters you tie it to. Optional layers can drop out; others fall back rather than leave a hole.
Read guide →IntegrationsOne product can carry many items. The link is what lets a shop page show the fabric, the colour and the images that live in Content Hub.
Read guide →IntegrationsChange a product's price, and a variant's price, from Content Hub. The change goes to the shop, so treat it as editing the shop itself.
Read guide →ExpressFront, back and both sides, the whole product in frame, in even daylight. What makes a photo work, and how to fix one that doesn't.
Read guide →Setting the shape: item groups, form layouts, models and layers, duplicating a project.
An item group is a shelf plus the shape of what goes on it. Create the group first, then its fields.
Read guide →Fields & formsFields come from the group, not the item. Add one and every item in that group gets it.
Read guide →Fields & formsNine types. This is the short version: what each one is for.
Read guide →Fields & formsOne sofa, several fabrics, and a price that differs for each pair.
Read guide →VisualsA layer is one piece of the picture, tied to one parameter. Layer order is the order they are drawn.
Read guide →VisualsA layer needs one image per option of its parameter. Not one per combination.
Read guide →VisualsCoverage tells you which layer and option pairs have no image yet. A gap is a hole in the render.
Read guide →The wiring: the API, the Shoper connector, slugs, caching, organisations and access.
A composite render is one image URL. No SDK, no client-side compositing.
Read guide →VisualsA one-character prefix decides how each token is looked up, including letting the URL speak your own shop ids.
Read guide →VisualsReplacing a layer image does not change the URL, so the cached picture stays until you clear it.
Read guide →The concepts worth having straight before you click anything, including if you are still working out whether Content Hub is for you.
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 →IntegrationsContent 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 →ConceptsOne 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 →ConceptsA 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 →ConceptsOften 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 →ConceptsFewer than a photoshoot suggests and more than a catalogue usually has. The number follows from what the buyer is unsure about.
Read →ConceptsTwo ways to show a configurable product, with different failure modes. Most catalogues need the first and are sold the second.
Read →ConceptsMost of it. The catalogue layer owns what the customer sees; ownership of everything else does not move.
Read →What we need from you before work starts: files, formats and the checks we run on them. One brief per kind of delivery.
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.
