01
Establishing which path applies
Applies to marketplace onlyown storefronthybrid
Five inputs determine which documented path is available to a given seller: the storefront provider, the account’s eligibility, the product category, the geography, and what the current official documentation states. A hosted catalog connection and a direct feed are different operating models with different requirements.
Establishing these first is a matter of sequence. The field-level question — what a record should contain — has the same answer regardless of path, while eligibility determines whether any of that work reaches a destination. Where one of the five inputs returns an unclear answer, the path is conditional, and recording it with its condition attached preserves the information that the condition exists.
For the Meridian camera, two of the five resolve from documentation alone and one requires a reply from a supplier. That mixed result is the ordinary case, and the sections below cover each path in turn.
02
What the platform documentation states about default syndication
Applies to marketplace onlyown storefronthybrid
Shopify documents agentic storefronts as active by default for eligible stores2 and automatic syndication of eligible products through Shopify Catalog.3 A default-on arrangement is different in kind from an opt-in feed: there may be no enrollment step, which places the seller’s work on review rather than on setup.
Three things are confirmed under that arrangement: which products are eligible, whether the products being syndicated are the intended ones, and where checkout takes place for a given channel. Shopify documents channel availability separately and notes that some channels remain in early access.2
Removal is a distinct operation under the same arrangement. Editing a storefront listing and changing a channel availability setting are separate actions, and confirming that a change is reflected on the destination is a third. For a catalog of single units, that sequence is the one that determines whether a sold item remains purchasable somewhere.
03
Per-surface conditions, recorded with their sources
Applies to marketplace onlyown storefronthybrid
Conditions differ by surface, so the table below records them per row rather than summarizing them into one instruction. Each row carries its own path, eligibility rule, initiator, used-goods handling, quantity behavior, fee position, and removal expectation, together with the primary source and the date it was read. Cells where a public document does not answer the question say so.
| Surface | Path and eligibility | Control and quantity | Fees and removal | Reviewed |
|---|---|---|---|---|
| OpenAI direct product feed | Path: Approved-partner file upload or Products API Eligibility: OpenAI approval and current commerce-policy eligibility Used goods: Condition is represented in the current product payload; category eligibility still applies | Initiator: Approved merchant or integration partner Quantity: Variant availability and quantity are merchant-supplied; unique stock still needs one authoritative state | Fees: Not stated in the reviewed public feed documentation Removal: No public guarantee found; use incremental updates and verify the destination | Primary source ↗ |
| ChatGPT through Shopify Catalog | Path: Shopify Catalog discovery, followed by the merchant online-store checkout in an in-app browser or new tab Eligibility: Eligible Shopify store and product; ChatGPT has Catalog access rather than Shopify direct checkout Used goods: Shopify Catalog eligibility is required; no universal used-goods support is inferred | Initiator: Shopify enables eligible catalog access by default; merchant can manage channel access Quantity: Shopify inventory supplies availability; checkout returns to the merchant store | Fees: Merchant storefront, payment, and Shopify terms apply; this is not the direct-checkout fee posture Removal: No public guarantee found; update Shopify, remove channel access where needed, and verify ChatGPT separately | Primary source ↗ |
| Google AI Mode and Gemini through Shopify | Path: Google & YouTube sales-channel product sync with optional Shopify-powered direct checkout Eligibility: Early access, not available to all stores; store based in and selling to the US, UK, Australia, or Canada, with required product sync, supplemental terms, and policies Used goods: Shopify Catalog and Google channel eligibility apply; no universal used-goods support is inferred | Initiator: Direct checkout is activated by default for eligible stores; merchant can deactivate it Quantity: Shopify inventory and checkout functions control the offered quantity; unsupported customizations must be reviewed | Fees: Shopify states no fees for this direct checkout beyond standard payment processing; ordinary merchant costs still require review Removal: No public guarantee found; update source and verify Google AI Mode and Gemini | Primary source ↗ |
| Microsoft Copilot through Shopify | Path: Shopify Catalog with optional Shopify-powered direct checkout inside Copilot Eligibility: Eligible Shopify stores selling to US customers, eligible products, accepted supplemental terms, and complete policies Used goods: Shopify Catalog eligibility applies; no universal used-goods support is inferred | Initiator: Eligible path is active by default; merchant can remove Catalog access or deactivate direct checkout Quantity: Shopify inventory and supported checkout functions control the offered quantity | Fees: Shopify states no fees for this direct checkout beyond standard payment processing; ordinary merchant costs still require review Removal: No public guarantee found; update Shopify, remove access if needed, and verify Copilot | Primary source ↗ |
| Etsy through named AI shopping surfaces | Path: Etsy-controlled listing discovery and purchasing path Eligibility: Some listings for eligible US shoppers on the surfaces Etsy names Used goods: Listing- and policy-dependent; the help article does not promise all used goods are eligible | Initiator: Etsy controls surface availability; seller maintains the Etsy listing Quantity: Etsy listing inventory controls the purchasable quantity | Fees: Etsy terms and seller fees apply; no additional universal fee claim is made here Removal: No public cross-surface guarantee found; update Etsy and verify the named destination | Primary source ↗ |
| eBay public listings | Path: Public listing discovery only unless eBay grants prior express automation permission Eligibility: Marketplace agreement and any express permission control automation Used goods: eBay listing fields describe condition; they do not grant agent purchasing authority | Initiator: Seller publishes the listing; eBay controls automated access and purchasing permission Quantity: The eBay offer quantity is marketplace state and must not be treated as a cross-channel reservation | Fees: eBay agreement and seller fee schedule apply Removal: No external-agent guarantee; end or revise the eBay listing and verify its state | Primary source ↗ |
Two distinctions run through the table. Checkout location varies by surface: a ChatGPT buyer is returned to the merchant’s own store to pay, while on Google AI Mode and Gemini, on Copilot, and on Meta a buyer may complete payment on the surface once direct checkout is live there. Shopify documents conditions separately for each of those channels,2 so a statement that a platform supports agentic checkout resolves into several different arrangements with different places where money changes hands.
The second distinction concerns who decides. Etsy documents purchasing for some listings through named AI shopping surfaces for eligible US shoppers,4 which is a marketplace making the decision for the listings on it rather than a setting an individual shop controls.
The removal column is the one that determines whether a catalog of single units can be safely exposed on a given surface, and it is also the column public documentation specifies least often. Where documentation does not state a removal guarantee, the merchant’s own verification step is what establishes that an item is no longer purchasable, and that step needs a named owner and an interval.
04
The direct feed path and its stated access condition
Applies to marketplace onlyown storefronthybrid
OpenAI’s direct product-feed documentation addresses approved partners and directs applicants to a form. It describes file upload and API delivery models, recommends a complete daily file combined with intraday API changes where applicable, and documents promotions data as available through the interface only.1 Where approval has not been granted, the documented path is not open, and no unofficial submission workflow creates eligibility.
The two delivery models handle different problems, and the split holds independently of whether either is currently available to a given seller.
| Delivery model | What it handles well | What it leaves to the other model |
|---|---|---|
| A complete file, replaced on a schedule | Removals and accumulated drift, since the new snapshot is the whole truth | Freshness between runs, which is bounded by the schedule |
| Updates through the interface | Freshness, since a change can be sent as it happens | Removals, which occur only if a removal message is sent |
The recommended combination follows from that split: the periodic file establishes the complete state, and intraday updates reduce the interval during which a specific fact is out of date. A daily file with no intraday channel leaves a sold item advertised until the next run; intraday updates with no periodic reconciliation accumulate drift, because a message that fails without raising an error is not corrected by anything else.
05
The product facts that have to arrive intact
Applies to marketplace onlyown storefronthybrid
The same small set of facts has to survive delivery on every path, and each has a different system or person responsible for it. Naming the owner is what makes a later correction assignable.
| Fact | Check for a single-unit item | Owner |
|---|---|---|
| Title | Names the exact edition and the recorded defect | Seller |
| Images | Show the actual unit rather than a stock image | Seller |
| Price and currency | Match the landing page | Commerce system |
| Availability | Carries one state and a timestamp | Inventory system |
| Policies | Resolve at a public URL | Merchant owner |
The middle column is where guidance written for repeatable stock diverges from what a single unit needs. A title naming a model is sufficient when every unit is identical and insufficient for one body with an intermittent shutter, because the defect is among the facts a buyer needs before committing. Stock photography works the same way: efficient for a commodity, and not representative of an object whose condition is specific to that unit.
06
Choosing an update interval
Applies to marketplace onlyown storefronthybrid
A full snapshot reconciles removals and drift; an incremental update reduces the time a changed price or a sold item remains stale. A design with both has an authoritative source and a recovery path. Four values are recorded per run: the export time, the accepted and rejected row counts, the last successful incremental event, and the result of verifying the public destination.
The interval follows from the fastest-moving item rather than the average one. Most of a used-goods catalog is static for weeks, which makes a daily rhythm look sufficient; the item that sells at midday is the one that remains advertised until the next run under that rhythm. Where no faster channel is available, reducing the number of surfaces carrying purchasable state reduces the number of places a sold item can still be bought.
Rejected rows warrant separate attention because they produce no visible symptom. A record refused by a validator is simply absent, and nothing at the destination distinguishes a record that was rejected from one that was accepted and not shown. The rejection count is recorded at delivery time, which makes it the first thing to read when part of a catalog appears nowhere.
07
The stages between delivery and a sale
Applies to marketplace onlyown storefronthybrid
Five stages sit between sending a record and completing a sale. Each is a separate event with its own evidence, and reaching one carries limited information about the next.
- Submission: the merchant sent data through a documented path.
- Acceptance: a validator or platform accepted the record.
- Eligibility: the record is permitted for a given surface.
- Retrieval or display: a platform decision.
- Referral, checkout, and sale: each requires its own observable evidence.
The first two are observable in the merchant’s own logs. The third is generally stated in documentation that can be read and dated. The fourth and fifth belong to the platform and the buyer, and the documented paths do not describe them as outcomes a merchant can produce.
Stated in these terms, the position of a given catalog can be described precisely: which stages have evidence, which do not, and what the evidence consists of. A service offering placement as a deliverable is offering something the documented paths do not describe as available.
08
The completed path record and the correction loop
Applies to marketplace onlyown storefronthybrid
Filled in for the Meridian camera, the path record holds three kinds of entry, only one of which is an available path.
| Path considered | Status on the date read | What follows this week |
|---|---|---|
| Platform syndication for eligible stores | Documented as active by default; eligibility still to confirm | Review of what is being syndicated |
| Direct product feed | Documented as addressing approved partners; form submitted | No reply yet; nothing to act on |
| Marketplace listing | Governed by the venue’s own agreement | No merchant-side setting involved |
| An offered shortcut | No documented basis in the sources | Not pursued |
Every path in that table needs the same correction loop, and its last step is the one that touches what a buyer can still do.
- Keep the source record and the delivery timestamp, so that a correction can be dated against the state it replaced.
- Check the affected field against the live page rather than against the internal database, since the live page is what a buyer acted on.
- Correct the source and send the documented update through the path that owns that field.
- Confirm on the destination that the previous offer is no longer actionable.
09
The record as it stands
Applies to marketplace onlyown storefronthybrid
Shopify documents agentic storefronts as active by default for eligible stores and automatic syndication of eligible products through Shopify Catalog, with per-channel conditions and some channels in early access.2 Eligible products are documented as syndicated automatically through that catalog.3 OpenAI documents direct product-feed onboarding as addressing approved partners, describes file and API delivery models, and recommends combining a complete daily file with intraday changes.1 Etsy documents purchasing for some listings through named AI shopping surfaces for eligible US shoppers.4
The sources do not state placement, display, or traffic outcomes for a merchant who completes any of these paths, and the removal expectations they publish vary by surface and are frequently unspecified. Where a cell in the surface table or the path record has no entry, it reflects the documentation consulted on the date recorded against it.
10
Practice
Exercise
Complete a channel onboarding record
- Find the current official onboarding documentation for one surface and copy the sentence stating the eligibility condition, with the date you read it.
- Compare one item’s title, price, availability, and policy links against its live page, recording any difference.
- Record the next correction check with a timestamp and a named owner, entering “no reply yet” for any status you are waiting on.
Check yourself
Does delivering a product feed establish that an item will be displayed?
No. Submission, acceptance, eligibility, display, referral, and sale are separate events. The first two are visible in the merchant’s own logs, eligibility is generally documented, and display is a platform decision.
A storefront platform syndicates eligible products by default. What work remains?
Review rather than enrollment: confirming which products are eligible, that the syndicated set is the intended one, where checkout takes place, and how a product is removed and the removal verified on the destination.
Which delivery model handles removals, and which handles freshness?
A complete file replaced on a schedule handles removals, because the new snapshot is the whole state, and its freshness is bounded by the schedule. Interface updates handle freshness and only remove an item if a removal is sent. The documented recommendation combines both.
Part of a catalog appears nowhere. What is recorded that would explain it?
The rejection count from the delivery run. A record refused by a validator is absent, and the destination gives no signal distinguishing that from a record that was accepted and not shown.
Is used or single-unit stock handled the same way across surfaces?
The documentation differs by surface, which is why used-goods handling is recorded per row with its source and read date rather than summarized into one rule.
Progress is saved in this browser only. No account, nothing sent anywhere.
11
Common questions
Can a nightly snapshot replace timely availability updates?
Not for items that can sell or change during the day. The interval that matters is the one on the fastest-moving item, not the catalog average.
The documentation addresses approved partners and I am not one. What applies?
That path is not open on the date read. Constructing an unofficial submission workflow does not create eligibility. Recording the path as unavailable with a review date preserves what was checked and when.
Where does checkout happen on these surfaces?
It varies by surface and is recorded per row in the table. A ChatGPT buyer is returned to the merchant’s store to pay; on several other surfaces a buyer may complete payment on the surface where direct checkout is live.
Does a marketplace listing require any merchant-side setup for these surfaces?
Where a marketplace documents agent purchasing for eligible listings, the decision is made at the venue level under its own agreement. There is no individual seller setting described in that arrangement.
What can be stated to someone asking whether a catalog is in ChatGPT?
Which stages have evidence: whether data is delivered through a documented path, whether every row was accepted, and whether the catalog meets the documented eligibility rule. Display is a platform decision the documentation does not describe as a merchant outcome.
12
Research and sources
Rules and platform policies change. These primary sources were reviewed on ; confirm the current position for your jurisdiction and account before acting.
Claim evidence
- OpenAI direct product-feed onboarding is currently limited to approved partners.
- current external fact. Supported by Agentic Commerce: Get started .
- OpenAI recommends a full daily file snapshot plus intraday API updates for applicable integrations.
- current external fact. Supported by Agentic Commerce: Get started .
- Eligible Shopify stores can have agentic storefronts active by default and products syndicated through Shopify Catalog.
- current external fact. Supported by Shopify agentic storefronts , Shopify Catalog and product discovery for agentic storefronts .
- Shopify documents ChatGPT shoppers as completing the purchase on the merchant’s own store checkout, whereas its Google AI Mode and Gemini, Microsoft Copilot, and Meta channels can settle the purchase inside the channel when direct checkout is active, each under conditions set out on its own page.
- current external fact. Supported by Shopify agentic storefronts .
- Etsy documents purchasing for some listings through named AI shopping surfaces for eligible US shoppers.
- current external fact. Supported by Purchasing Etsy items through AI shopping surfaces .
- Agentic Commerce: Get started OpenAI · Tier A · current documentation · unversioned live documentation
OpenAI direct product-feed onboarding and delivery models. Limit: Describes OpenAI’s current direct-feed path. It does not establish eligibility, surfacing, placement, traffic, or sales for a merchant.
- Shopify agentic storefronts Shopify · Tier A · current help documentation · live documentation
Shopify agentic-storefront eligibility, default activation, channel behavior, and checkout posture. Limit: Documents Shopify stores only. Some channels are early access and not available to every store.
- Shopify Catalog and product discovery for agentic storefronts Shopify · Tier A · current help documentation · live documentation
Eligible-product syndication, product-field mapping, hiding, and B2B exclusions. Limit: Shopify controls this catalog path. Automatic eligibility does not guarantee retrieval or display by an AI channel.
- Purchasing Etsy items through AI shopping surfaces Etsy · Tier A · current help documentation · live documentation reviewed 2026-07-31
Etsy listing purchase paths through named AI shopping surfaces for eligible US shoppers. Limit: Documents Etsy-controlled eligibility and purchasing only. It does not establish eligibility for every listing, seller, shopper, country, or surface.