Product feed seller name: why it matters

A product feed seller name identifies the business offering a product. It is normally a merchant-level fact, which makes it one of the simplest fields to fix well: use the name customers see on the shop, keep it consistent across the feed and make sure related policy pages identify the same business.

Why this matters now

Catalogues commonly have strong product detail but weak merchant context. The owner knows who is selling; an external channel only sees rows of data. Supplying a truthful seller name closes that context gap and makes it easier to keep brand, returns and customer support information aligned.

What to check first

A practical way to do it

1. Use the trading name displayed on the public shop and customer communications.
2. Apply it as a store-level default when every product has the same seller.
3. Check that policy and contact pages use a compatible identity.
4. Keep the product brand separate when the merchant sells other brands.
5. Review the value after a rebrand, legal-entity change or marketplace expansion.

Common mistakes

• Putting a product collection name in the seller field.
• Using a different seller identity on every row without a real multi-seller model.
• Confusing a fulfilment partner with the merchant selling to the customer.

What this does not mean

A clean product feed makes your catalogue understandable to a receiving platform. It does not guarantee approval, inclusion, ranking, sales or a particular checkout experience. Those decisions and customer-facing flows remain with the platform and the merchant.

The useful habit is simple: correct the source data, then validate the exported feed. Do not patch a one-off file and assume the next shop sync will remember your fix. That is how a tidy launch turns into a slow drift a fortnight later.