Skip to main content
All articles
Catalog operations

Inside Youzu: what follows a product from supplier file to storefront?

Follow a supplier record through category mapping, variant and offer review, and the handoff to photo search, room previews, and product media.

Published by Youzu · Editorial policy

Published
Updated
Reading time
3 min read

What changed: Revised article and supporting media

In this article

Youzu starts with a product record. Catalog Intelligence reads supplier or seller data alongside product photos and proposes a category and the attributes that belong in it. Discover, Visualize, and Product Media use the catalog for different jobs. What connects them is the identity of the item: which product is pictured, which version the shopper chose, and which seller’s offer goes with it.

Original illustration of a two-door cabinet in natural and dark finishes.
One design, two finish variants. The photograph and SKU belong to the chosen finish; seller availability belongs to the offer. Illustrative example.

What stays together, and what stays separate

Imagine a maker’s sheet for a two-door cabinet. It lists the natural and black finishes under one model, with a different SKU and photo for each. Two stores carry the black cabinet. One has stock, and the other is taking backorders. This is an illustrative record, not a customer catalog.

There’s one cabinet design, two finish variants, and two independent offers for the black one. The door count can travel with either finish because the maker specifies it for both. The photos cannot be interchanged. Neither store should inherit the other’s availability. If a third seller submits a similar-looking cabinet with no model reference, resemblance alone doesn’t justify merging it with this one. The Catalog Intelligence overview explains which relationships are kept separate and which findings go to review.

You can see part of that handoff in the supplier-record walkthrough. It uses a track jacket: the original supplier information appears beside separate specifications, and changing the selected color changes the photo. That’s a visible test of the variant link. It doesn’t tell you a seller’s current stock.

Where each product uses the record

For Discover, the cabinet photo is something to search against. A shopper’s reference photo might lead to a similar cabinet with a different finish; the returned item needs its own details. For Visualize, the selected cabinet is the one to preview in a room. For Product Media, its photos are the inputs for a new background or a rotatable model. The platform overview lays out those inputs and what each product returns. A generated view isn’t new evidence of dimensions, materials, or a side the photographer never saw.

A useful integration check is to follow just the black SKU. Start with the approved record, select the black finish in the storefront, and follow its photo through the experience you’re testing. Then change one seller’s availability in your test data. The correct outcome is a change to that offer, not a new cabinet, a different photo, or a stock change at the other store. Confirm it in the receiving system; preparing a record and applying it there are separate steps.

Follow a product through the catalog pipeline · Watch on its own page · Open MP4
Read the captions

Messy data in. A clean product record out. One path in your category tree. Home > Clothing > Jackets Similar products sit close together. The new product joins its cluster. See it with your catalog. Book a demo

Next step

Automate Commerce. Make shopping personal.

Bring your catalog, listing flow or shopping idea. Let's find the right place to start.

Book a demo

Tell us about your catalog and we will get back to you.