# Hosted URL and SFTP Product Feeds for ChatGPT

> Hosted HTTPS URL, SFTP or manual upload for a ChatGPT product feed? A decision guide to what each delivers, what breaks, and what OpenAI documents, as checked 18 November 2026.

Canonical: https://revnu.com/blog/hosted-url-and-sftp-product-feeds-for-chatgpt
Published November 19, 2026 by George Jefferson, Co-founder and CEO, Revnu

# Hosted URL and SFTP Product Feeds for ChatGPT

Use a hosted HTTPS URL for your ChatGPT product feed if your catalog lives on a platform that can publish a stable file link, use SFTP if you export from a system that can only push files, and use manual upload only for one-off or occasional updates. Hosted URL and SFTP are the two recurring-delivery options, and both beat a person uploading a CSV every week.

This guide covers how each method works, what OpenAI documents for Business Hub versus Ads Manager, and why feeds quietly stop updating. Beta details below are as checked 18 November 2026. Recheck them before you build anything on them. The programme is new and the screens change.

## Short answer: which delivery method to use

Pick the hosted HTTPS URL by default, SFTP when your export job can only push, and manual upload for occasional files. The deciding question is who or what produces the file and how often it changes.

| Method | Best for | Recurring | Main risk |
|---|---|---|---|
| Hosted HTTPS URL | Platforms or scripts that can publish a file at a stable link | Yes | URL moves, auth wall, stale file behind the link |
| SFTP | ERPs, warehouse systems and exports that push files on a schedule | Yes | Wrong credentials, or using Ads credentials for Business Hub |
| Manual upload | Small catalogs, first test, rare changes | No | Nobody remembers to re-upload |

The hosted URL versus SFTP question matters less than people expect. Both deliver the same file, so the file format and hygiene rules in the later sections apply either way. If you have not built the file yet, start with the [CSV setup guide](https://revnu.com/blog/chatgpt-business-hub-product-feeds-csv-setup-guide), then come back here to decide how it travels.

One caveat before you commit. The commerce overview tells merchants to submit a feed so ChatGPT can use the catalog for product discovery ([OpenAI Commerce](https://developers.openai.com/commerce)). A feed supplies catalog data.

## Hosted HTTPS URL: when it fits and how to set it up

A hosted HTTPS URL fits when something on your side can regenerate a file and serve it at an address that never changes. In Business Hub, you open your business profile, go to the product section, verify your identity, choose Upload products and select a delivery method. For a hosted feed, you enter an HTTPS URL that serves the feed file itself, not a web page that links to it.

This works well for Shopify-style exports, a nightly job that writes to object storage, or a route on your own server. It fails when the URL sits behind a login, redirects to an HTML page, or points at a file that a cron job stopped refreshing months ago.

Setup checklist:

1. Serve the file over HTTPS at one permanent path. Do not put a date or version in the filename.
2. Make it fetchable without cookies or a session.
3. Return the raw feed, in the format the schema asks for, with UTF-8 encoding.
4. Regenerate it on a schedule you control and monitor, not on a manual habit.
5. Open the URL in a private browser window and confirm you see data, not a page.

The current product feed specification describes a CSV format with one row per purchasable item or variant, not JSONL records ([OpenAI product feed schema](https://developers.openai.com/commerce/specs/feed)). Build to that schema first. The delivery method is the easy part.

## SFTP: when it fits, how it works, and the Business Hub vs Ads Manager caveat

SFTP fits when your catalog system exports files and can push them to a server on a schedule but cannot publish a public link. You create a feed, configure access with a password or an SSH public key, then upload a UTF-8 product CSV to the feed's SFTP root and check upload status under Monitoring Uploads.

This caveat trips people up. The SFTP walkthrough OpenAI publishes sits in the Ads documentation and is for Ads Manager: you configure SFTP for a feed inside the ad account and use the connection details it returns. The Business Hub help article describes hosted URLs and file uploads, but does not give SFTP credential instructions. Do not assume credentials from an Ads Manager feed work for a Business Hub feed. If you need SFTP specifically for Business Hub, confirm what your Hub screen offers before you wire up automation.

The Ads guidance also says items expire after two weeks, which is why it recommends automated SFTP or a hosted URL over manual uploads. That is stated for Ads feeds. Do not treat the two-week figure as a documented Business Hub rule.

If you use SFTP, treat the connection like any production credential. Prefer an SSH key to a shared password, scope it to one feed, and rotate it when a developer or agency leaves.

## Manual file upload: when it is still the right call

Manual upload is the right call for your first test file, a small catalog that rarely changes, and any moment you want to validate a schema before automating. In Business Hub you upload a CSV that follows the product-feed specification, and you can fix validation errors after processing.

Use it deliberately, not by default. A manual upload is a snapshot with no schedule behind it. If prices or stock move weekly, a person has to remember, and people forget. The practical pattern is to upload by hand until the file validates cleanly, then switch to a hosted URL or SFTP and stop touching it.

Don't run a manual upload and an automated feed against the same catalog without deciding which one wins. Two sources with different prices is a good way to publish the wrong number.

## Refresh cadence and file hygiene (stable IDs, UTF-8, full snapshots, price and stock)

Send a complete, current snapshot at least daily, keep item IDs stable, encode in UTF-8 and update price and availability whenever they change. The commerce overview recommends full snapshots at least daily, and that is the safest baseline for a catalog where stock moves.

The rules that prevent most problems:

- **Stable IDs.** The schema separates the item ID for a specific item, the group ID for a parent listing and the offer ID for a seller's offer ([OpenAI product feed schema](https://developers.openai.com/commerce/specs/file-upload/products)). Never regenerate IDs on each export.
- **Full snapshots, not deltas.** Send the whole catalog each time so removed products don't linger.
- **Money format.** Write amounts as a decimal in major units, a space, then an uppercase ISO 4217 code, for example 79.99 USD.
- **Availability on every row.** The schema asks you to submit current stock status with each row.
- **UTF-8.** A stray encoding breaks product names with accents or symbols.

Note the geography: the standard OpenAI-format upload currently targets the US, per the schema. If you sell elsewhere, recheck eligibility before assuming coverage. Providing a feed also means following OpenAI's specifications and applicable policies under the [Businesses in ChatGPT Terms](https://openai.com/policies/businesses-in-chatgpt-terms/).

## Failure modes and how to debug a feed that is not updating

A feed that is not updating almost always fails at one of four points: the file is stale, the file is unreachable, the file fails validation, or the wrong credentials are in use. Debug in that order.

1. **Stale file.** Open the hosted URL yourself. Is the data from today? A broken export job behind a perfectly healthy URL is the most common cause.
2. **Unreachable.** The hosted URL returns a login page, a redirect or a 403. Test from a network outside your office.
3. **Validation errors.** Review the errors after processing. Missing required fields, bad price strings and non-UTF-8 text are the usual culprits.
4. **Wrong credentials.** For SFTP, confirm you are using details generated for that feed, and not Ads Manager credentials for a Business Hub feed.
5. **ID churn.** If products vanish and reappear as new items, your IDs changed between exports.
6. **Mixed sources.** A manual upload and an automated feed are overwriting each other.

Only after those check out should you suspect the platform. This is a beta, so behaviour and screens can change. Keep a dated note of what you configured and when. The [metrics and weekly reporting guide](https://revnu.com/blog/chatgpt-business-hub-metrics-and-weekly-reporting) covers how to watch results once the feed is flowing.

## Where Revnu fits after the feed is live

Revnu is an AI agent that finds customers and grows revenue across SEO, AI search, outbound, LinkedIn and paid ads. It doesn't deliver or host your product feed, and it has no native Business Hub connection.

Once the catalog is live, Revnu tracks how your business appears in ChatGPT, Claude, Perplexity and Gemini answers and in Google, publishes the pages that close the gaps, and runs outreach and ads within your approvals. It reports back in Slack or iMessage. That is the work a feed can't do for you. Pro is from $99 a month, self-serve, with no sales call.

For the next step, read [Turn ChatGPT Business Hub Data Into Revenue Decisions](https://revnu.com/blog/turn-chatgpt-business-hub-data-into-revenue-decisions) and keep any Hub figures within OpenAI's sharing limits.

## Automate delivery once, then spend your time on demand

Choose a hosted HTTPS URL unless your system can only push files, validate by hand first, and send full daily snapshots with stable IDs. Treat the Ads Manager SFTP walkthrough as Ads-only until your Business Hub screen says otherwise. Then turn to what happens after the feed is live: start Revnu on the Pro plan at revnu.com and let it track your AI answer visibility and run the growth work that turns product discovery into customers.

## Related Business Hub guides

- [ChatGPT Product Feed Fields Explained One by One](https://revnu.com/blog/chatgpt-product-feed-fields-explained-one-by-one)
- [WooCommerce and BigCommerce Product Feeds for ChatGPT](https://revnu.com/blog/woocommerce-and-bigcommerce-product-feeds-for-chatgpt)
- [ChatGPT Business Hub for Shopify Stores: Setup Guide](https://revnu.com/blog/chatgpt-business-hub-for-shopify-stores-setup-guide)

## Frequently asked questions

### Should I use a hosted URL or SFTP for my ChatGPT product feed?

Use a hosted HTTPS URL if your platform or a script can publish the feed file at a stable address. Use SFTP if your system can only push files on a schedule. Both are recurring options, and the file format and hygiene rules are the same either way.

### How often should a ChatGPT product feed refresh?

OpenAI's commerce overview recommends full snapshots at least daily. Update price and availability whenever they change, keep item IDs stable, and send the whole catalog each time. Ads feeds add that items expire after two weeks, so automate rather than relying on manual uploads.

### Do Ads Manager SFTP credentials work for Business Hub?

Do not assume so. The SFTP setup guide is in OpenAI's Ads documentation and is for Ads Manager, using the connection details that feed returns.

### What file format does a ChatGPT product feed need?

Follow OpenAI's product feed schema: UTF-8 encoding, all required fields, stable item IDs, prices written like 79.99 USD, and current availability on every row.

### Does Revnu deliver my ChatGPT product feed?

No. Revnu does not host or deliver feeds and has no native Business Hub connection. It tracks how your business appears in ChatGPT, Claude, Gemini and Perplexity answers, publishes pages, and runs outreach and ads within your approvals.
