Glami

Why it is not a price comparison site

A classic comparison site assumes several shops sell the same product and compete on price. In fashion that rarely holds — a particular shirt model often has a single seller, and the shopper is not looking for the cheapest copy of one item but for an item they like.

So Glami builds on the filters fashion actually needs: category, size, colour, material, brand, cut. Browsing replaces comparing. For a shop that means photo quality and complete parameters decide the outcome, not the last unit of currency on the price tag.

What the feed must carry

A fashion aggregator feed is more demanding than a general comparison feed, because it carries attributes an ordinary shop often does not even store as separate fields. If size lives only inside the product name rather than in its own parameter, filters cannot see it and the product drops out of most listings.

• Size as its own parameter, not text inside the name.
• Colour in values the aggregator recognises, not marketing names for shades.
• Brand and category mapped to the taxonomy, or the product lands in the wrong place.
• Variants as separate items with their own availability.
• Photos on a clean background, large enough to zoom.

When it is worth using

Glami makes sense for a shop selling fashion with a catalogue wide enough to browse. For a narrow range or goods outside fashion it is a wasted channel, and Heureka or Google Merchant Center will serve better.

As with every aggregator, measure through to the order and watch returns. Fashion carries a naturally high return rate, so a channel that looks strong on order count can look different once returns are deducted. Generating feeds for several channels from one dataset is what a custom e-shop is for.