What You Actually Need Before You Can Send a Product Feed to ChatGPT

Every store we've taken through OpenAI's product-feed setup completes the Shopify side without trouble, then stops at the same place: the handover to OpenAI Ads Manager. Here is what that step actually requires, and the traps that cost us a working feed the first three times.

There is a lot of writing about why you want your products in ChatGPT. There is almost none about the twenty minutes where you actually try to do it.

We've run this setup across our merchant base. The pattern is consistent enough to be worth publishing: the store-side work — seller identity, shipping terms, target countries, product data — gets finished by everyone who starts it. Then the process stops dead at one step, for almost everyone, and it isn't a step that happens in your Shopify admin.

This article is that step, written out.

The shape of the thing

OpenAI does not pull your catalog. You push it. Specifically:

1. You create a product feed inside OpenAI Ads Manager.
2. Ads Manager issues you SFTP credentials — a host, a username, a password, and a feed identifier.
3. Something on your side generates a compliant file and delivers it to that SFTP endpoint on a schedule.

Step 3 is what a feed app does for you. Steps 1 and 2 are yours, and they happen entirely outside Shopify. That's the gap nobody warns you about: your store can be perfectly prepared and still have nothing to connect to.

Prerequisite one: an OpenAI Ads account that can create feeds

This is the real gate, and it's worth checking before you fill in a single setting anywhere else.

Product-feed access lives inside OpenAI's advertising product, not your regular OpenAI account. Having a ChatGPT subscription does not give it to you. Access has been rolling out in stages, so the honest answer to "can I do this today?" is: open Ads Manager and find out, before you invest an hour elsewhere.

Two things we can tell you from having done it:

• Billing setup is separate from feed access, and the two get confused. A billing prompt in Ads Manager is not automatically the thing blocking your feed.
• The account is associated with a domain. Make sure that's your storefront domain, not a parent company or corporate domain. We've seen a merchant set up their account under a corporate domain that wasn't attached to their Shopify store at all, and then spend weeks unable to work out why nothing connected.

That last one is the single most expensive mistake in this process, because everything appears to work until it doesn't.

Prerequisite two: product data that survives ingestion

Once you're delivering, the file has to be accepted. Three findings from our first successful ingests, all of them learned the hard way:

item_id must be a plain number. If your feed emits Shopify's global ID format — gid://shopify/ProductVariant/123456 — every row fails. Not some rows. All of them. The same applies to group_id. This is the single most common reason a technically-valid feed ingests zero products.

Unpublished products still ingest. Drafts and unpublished items will go through if your feed includes them. Exclude them deliberately; don't assume the pipeline filters for you.

Format validity is not eligibility. These are two separate judgements made by two different systems. In one of our ingests, 33 rows were accepted as well-formed and 3 were then rejected as not meeting OpenAI's ads policy — without naming which products or which rule. Any tool that tells you your feed is "valid" is telling you about format. Whether OpenAI will actually serve those products is decided afterwards, elsewhere, and largely opaquely.

Plan for that gap. A feed that validates clean can still lose rows on the other side.

Prerequisite three: the fields that describe you, not your products

Most feed guidance focuses on product columns. The seller-level fields get skipped, and they're the ones that quietly break things:

• Seller name — required on every row. If your tool falls back to your myshopify handle, shoppers see something like quickstart-72eb4431.
• Store URL — must be a real, resolving address, and it should be the same storefront your product links point to. A file that names one seller and links to another is a file nobody can verify.
• Shipping terms — country, region, service class, price. Merchant-entered, because no API knows what you actually promise.
• Return terms — if you have a generous policy, this is where it becomes machine-readable. Most stores leave it blank and get judged as if they had no policy at all.

What "done" looks like

You'll know it worked when a delivery lands and comes back with a row count that matches what you expect. Our first clean merchant delivery was 174 rows and about 51 KB, over SFTP, on a schedule. That's the whole finish line: a file, on their server, on a timer.

Everything before that is prerequisites.

The order that saves you the most time

1. Open Ads Manager first. Confirm you can create a product feed at all, and confirm the account's domain is your storefront.
2. Create the feed there and capture the SFTP credentials — host, username, password, feed ID.
3. Only then configure your store side: seller identity, shipping, returns, exclusions.
4. Deliver, then check the row count on OpenAI's side, not just yours.

Doing it in that order means you find out in five minutes whether you're blocked, instead of after an hour of settings.

FoundGPT generates and delivers OpenAI-format product feeds from your Shopify catalog, and fixes the product-data gaps that cost you rows before they're sent. The prerequisites above are still yours — we can't create your Ads Manager account for you — but everything after them is automated.