Seller name is the required product-feed field that identifies the business supplying each offer you submit to OpenAI for discovery and advertising inside ChatGPT. It differs from the brand field, which names the product's manufacturer or label instead of the merchant fulfilling the sale.
If you run product ads in ChatGPT, the seller name you submit decides whether OpenAI accepts the row and which merchant identity sits behind your listing. Submit a placeholder or leave it blank, and OpenAI rejects the feed row, so the product never becomes eligible to appear beside a relevant ChatGPT answer.
Within OpenAI's product feed specification, seller name records the merchant responsible for a given offer, one of the nine fields every row must carry before OpenAI will accept it for discovery or ads in ChatGPT. OpenAI's documentation instructs advertisers to use real brand and seller names instead of placeholders, so the value has to be accurate and genuine.
The field sits beside related merchant data and has a specific job. Brand names the product's maker, seller name names who supplies the offer, and the optional seller_url points to that seller's storefront. For a third-party marketplace listing, seller name identifies the specific seller, while a separate marketplace_seller field names the marketplace where checkout happens.
Seller name is feed data, so it governs the product listings ChatGPT can surface and stays separate from the account-level advertiser name shown on every ad card. AirOps tracks how your brand and products appear across ChatGPT answers and ads, so you can confirm your seller identity is surfacing the way you intended.
Resources: how to meet OpenAI's creative specs and ad policy for ChatGPT ads
Seller name works as a required attribute on every product row in the feed you send to OpenAI, read during ingestion and used to attribute each offer to a supplying merchant.
Populate: Add a seller name to each row alongside item_id, title, brand, price, and the other required fields in the product feed.
Distinguish: Set brand to the product's maker and seller name to the merchant supplying the offer, since OpenAI treats the two as separate required fields.
Handle marketplaces: For third-party offers, keep seller name as the individual seller and add marketplace_seller for the marketplace where checkout occurs.
Validate: OpenAI ingests the feed and rejects any row that carries a placeholder such as "unknown" or "n/a" in place of a real seller name.
Attribute: Accepted rows become eligible, and the seller identity travels with the product data ChatGPT can show inside a relevant answer.
The field tells OpenAI who stands behind each offer. It does not control the advertiser name printed on the ad card, which you set once in your account settings.
Seller name is a gate on a new paid channel. Get it wrong and products drop out of ChatGPT's shopping surfaces before you can bid on them, so the field shapes whether your catalog is buyable through ChatGPT at all. Treat it as part of launching the channel, something you settle before ads are already running.
Eligibility depends on it: A row missing a real seller name is rejected at ingestion, so the product never reaches a ChatGPT answer no matter how strong the rest of the feed is.
It sets merchant trust: The seller name tells shoppers and OpenAI who fulfills the order, which carries weight when the brand and the selling merchant are not the same company.
It keeps marketplace catalogs clean: When you resell or operate a marketplace, an accurate seller name separates individual sellers from the checkout marketplace and prevents listings from being attributed to the wrong party.
Growth marketers use seller name to qualify their product feed for ChatGPT ads so new listings become eligible to appear beside relevant answers.
SEO managers use seller name to keep merchant identity consistent between their existing shopping feed and the OpenAI product feed.
Demand gen leads use seller name to confirm that marketplace offers are attributed to the correct selling entity before paid spend ramps up.
Brand names the company that makes or labels the product, while seller name identifies the merchant supplying the specific offer; OpenAI stores them as two separate required fields, so you populate both and never let one stand in for the other.
For third-party listings, seller name marks the individual seller and the separate marketplace_seller field marks the marketplace where checkout happens; keeping the two distinct lets platforms attribute each offer to the right party and send shoppers to the correct checkout.
A product becomes eligible for ChatGPT discovery and ads only when every required field, seller name included, carries a real value; placeholder or empty cells cause OpenAI to reject the row, so eligibility starts with a complete, accurate feed where no required field is left empty.
Qualifies your products to appear in ChatGPT product ads and shopping surfaces.
Satisfies a required field OpenAI checks on every feed row, keeping listings from being rejected at ingestion.
Clarifies who fulfills an order when the brand and the selling merchant differ.
Separates individual sellers from the checkout marketplace on third-party listings.
Builds shopper trust by naming a real, recognizable merchant.
Use your real, legal seller name: Match the merchant name shoppers already see on your storefront, because OpenAI's spec rejects placeholder values.
Keep seller name separate from brand: Populate both fields with their correct values so OpenAI can tell the maker from the merchant.
Pair marketplace offers with marketplace_seller: For third-party listings, name the individual seller in seller name and the marketplace in marketplace_seller, so checkout attribution stays accurate.
Apply one seller name across variants: Use the same seller name on every variant row of a listing, since they share a single supplying merchant.
Add a seller_url: Point to the storefront or seller profile so the identity is verifiable by OpenAI and by shoppers.
Recheck after feed changes: Confirm the field survives each re-export from your shopping platform into the OpenAI format.
Avoid stuffing the brand name into the seller field to save a step; when the maker and the merchant differ, that collapses two distinct identities and can get the row rejected or misattributed.
AirOps: Tracks how your brand and products surface across ChatGPT answers and ads, so you can confirm your seller identity is appearing on the prompts you care about.
OpenAI Ads Manager: The advertiser platform where you set up the account and upload the product feed that carries seller name for ChatGPT ads.
Google Merchant Center: Manages the shopping feed many teams maintain as the source for merchant and seller data before mapping it into OpenAI's product feed format.
Audit your feed: This week, open your existing product feed and check whether every row has a real seller name or is quietly relying on a placeholder value.
Separate brand and seller: Decide the correct supplying merchant for each offer and make sure the seller name is a genuine value, never just a copy of the brand field you already filled.
Map marketplace offers: For any third-party listings, add marketplace_seller next to seller name so checkout attribution resolves to the right selling party and the right marketplace.
Add supporting fields: Include seller_url to make the identity verifiable, then confirm the other required fields on each row are complete before you upload anything.
Upload and verify: Submit the feed in OpenAI Ads Manager and confirm the rows pass ingestion without seller-name rejections, fixing any flagged values and re-submitting.
Seller name is the required feed field naming the merchant that supplies each offer submitted to OpenAI for ChatGPT.
You set it per product row, keeping it separate from the brand and, for marketplaces, from the marketplace_seller field.
The main constraint is that it must be a real value, because placeholders or empty cells get the row rejected.
The main risk is losing eligibility silently, since a rejected row simply never appears in ChatGPT.
The biggest opportunity is a clean, accurate feed that qualifies more of your catalog for ChatGPT's shopping surfaces.
Seller name identifies the merchant supplying an offer, while brand identifies the company that makes or labels the product, and OpenAI treats them as two separate required fields. The distinction matters most when the maker and the merchant are different companies. A boutique that resells a shoe brand would list the manufacturer under brand and its own store under seller name. A direct-to-consumer business that makes and sells its own goods often puts the same company in both, but OpenAI still expects each field to be filled with its correct value, never left blank or copied blindly from the other. Mixing the two up, or stuffing the brand into the seller slot, can lead OpenAI to reject or misattribute the row. The simplest test is to ask who actually fulfills the purchase: that answer belongs in seller name, and the name on the product itself belongs in brand.
Update the seller name whenever the supplying merchant actually changes, which for most catalogs is an occasional event tied to real business changes. The field describes who sells the offer, so it stays stable as long as the same business fulfills the product. You would revise it if you restructure your storefronts, move products to a different selling entity, or bring a marketplace listing in-house. Beyond those events, the practical rhythm is to recheck the value every time you re-export or regenerate the feed from your shopping platform, since a mapping change can silently drop or overwrite the field. If you run a marketplace with many third-party sellers, treat seller name as part of each seller's onboarding so new offers arrive with an accurate value from the start. The goal is accuracy at the moment of ingestion, so tie your checks to feed uploads instead of a calendar.
On a marketplace listing, seller name differs from brand because the business selling the item is not the business that made it. The brand field carries the manufacturer or product label, and the seller name carries the individual third-party seller fulfilling that particular offer. OpenAI's feed also supports a separate marketplace_seller field that names the marketplace where checkout happens, so a single product can involve three identities: the brand that made it, the seller that supplies it, and the marketplace that processes the sale. This separation lets OpenAI attribute each offer correctly and route shoppers to the right checkout, especially when several sellers offer the same branded product. If your marketplace listings show the same value in brand and seller name, that usually signals a mapping gap worth fixing, because it hides who actually fulfills each offer and can confuse attribution across competing sellers.
Yes, you set the seller name directly, because it is a field you populate on every row of the product feed you submit to OpenAI. You control the value, so you choose the exact merchant name that travels with each offer into ChatGPT's shopping surfaces. What you do not control is whether a given product then appears in any particular answer, since OpenAI decides placement based on relevance and its own ranking. Your job is to supply an accurate, real seller name and keep it consistent with your storefront, which keeps the row eligible and the identity trustworthy. Note the difference from the advertiser name on the ad card: that name comes from your account settings and is set once, while seller name is per-product feed data. If you want a specific merchant identity shown with your catalog, the lever is the feed value, entered correctly and verified at upload.
A good seller name is the real, recognizable name of the merchant that fulfills the offer, written the same way shoppers see it on your storefront. OpenAI's specification is explicit that the value should be a genuine seller name instead of a placeholder, so anything like "unknown," "n/a," or a blank cell fails the bar and risks rejection. Beyond being real, a strong value is consistent: the same seller name across every variant row of a listing, and stable from one feed upload to the next. For marketplaces, a good entry names the specific selling business instead of the marketplace itself, with the marketplace captured separately. There is no character-count target that makes a name "good"; the measure is accuracy and recognizability. If a shopper could read the seller name and immediately understand who they are buying from, and OpenAI can match it to a verifiable storefront, the value is doing its job.