A consistent view.
Keep the approved product image, dimensions, revision, and review state attached. Image consistency and product fidelity need their own evidence.
The product standard Version 1.0
A consistent image. Facts with sources. A clear next step to purchase. Every product joins the same system, so an assistant can help someone decide without a long sales page.
The product’s decision record carries its identity, imagery, facts, sources, and purchase options together. The same information can support an AI conversation, a compact product card, or a catalog export.
Keep the approved product image, dimensions, revision, and review state attached. Image consistency and product fidelity need their own evidence.
Keep a concise description, selected variant, relevant attributes, and source records. Mark extracted or inferred values. Preserve what is unknown.
Identify the seller, offer, and available handoff when documented. Show what still blocks a reliable purchase. A link is separate from a checkout.
The public /api/products/:asset_id/decision endpoint returns the decision record. /api/products/:asset_id/purchase-options returns an available official-page handoff and purchasing blockers. Use the exact asset ID returned by search.
Readiness is computed from the available evidence. These are Shelfhelp.ai states, not a certification or a promise of acceptance by another platform. The live contract defines the exact requirements and blockers.
| State | Meaning |
|---|---|
image_record | An image record exists. Product facts and purchasing evidence may still be incomplete. |
decision_ready | The required identity, imagery, and sourced decision information meet this standard’s readiness rules. |
offer_ready | The record also meets the rules for a documented seller-specific offer. Review its freshness and market scope. |
checkout_ready | Reserved for a working, authorized merchant checkout. Native checkout is currently disabled. |
Schema compliance and evidence are separate. A valid profile can still have unknown facts. Passing the profile validator does not verify a claim, grant image rights, or establish a merchant relationship.
Use the approved product-shot workflow. Keep the final image unchanged and record its review state.
Start with the profile template. Replace example values with documented facts. Keep unknown values explicit and attach sources to the claims you provide.
New ingestion requires a valid versioned profile. A missing or invalid profile returns HTTP 422 with validation details. The record’s readiness remains limited by its evidence.
Existing records are mapped into the decision format without replacing their images or IDs. Their migration status stays explicit. Missing evidence is carried forward; migration does not certify identity, imagery, licenses, offers, or checkout.
Profiles allow up to eight facts, six sources, and four sourced caveats within a 5,120-byte budget. An offer’s purchase_unit records what the seller actually sells: quantity, unit size, and merchant identifiers. Its price is the total for that unit. A single-can image can accompany a case offer, but the two must stay distinct.
Image approval is tied to the digest of the published image. Replacing the pixels requires a matching review; an older approval cannot silently carry over to a new render. Conflicting official facts remain visible in decision.caveats.
New evidence can update a product’s profile without uploading its image again. Each recorded revision keeps a reason, a recording date, and a link to the previous revision. The product’s image and public URLs stay the same.
Source dates still matter. A profile saved today can contain an older observation, and an expired offer does not become current just because the profile was updated. The same evidence and readiness rules apply after every change.
Use get_product_evidence_history through MCP, or /api/products/:asset_id/evidence-history, to inspect recorded revisions. Owner updates are validated and protected against conflicting writes. The developer guide explains the update workflow and its capacity limits.
A refresh path is not a live feed. Merchant data still needs an authorized source and an actual new observation. Automatic feed polling, license confirmation, and native checkout remain separate work.
Product pages keep the image and concise decision facts visible. Structured data describes that same content. MCP and API responses preserve sources and unknowns so assistants can explain a recommendation.
Clean URLs, crawlable pages, accurate text, imagery, and matching metadata support discovery. They do not guarantee indexing, ranking, or AI recommendations. Google does not require a special AI schema or llms.txt file for its generative search features.
External product feeds and native checkout have their own requirements and onboarding. This standard provides a foundation for those integrations; it does not claim that they are connected.
search_products_for_intent lets a connected assistant send a shopper’s requirements and receive relevant candidates, source evidence, stable product links, and unresolved constraints. A matching title does not establish a product fact. Missing price, stock, or variant evidence stays unknown.
For broader ChatGPT discovery, OAI-SearchBot access and approved product-feed onboarding are separate from connecting this MCP. Public page crawling is allowed by this site’s robots rules; actual indexing and external recommendation placement have not been verified.
Versioned profiles, ingestion validation, recorded evidence updates, explicit blockers, and compact product pages form the current foundation.
Establish product and image permissions, exact variants, current offers, stock, shipping, and returns. Refresh changing facts from authorized sources and measure their freshness.
Onboard merchants and checkout providers. Add reliable cart, payment, and order handling. Validate external feeds, then measure discovery, recommendation quality, completed purchases, and service reliability.
Reviewed 7 November 2026. These external standards inform the data model; each integration still needs its own validation and setup.
Schema.org Product and product identity Schema.org Offer and seller-specific commercial facts Google structured data quality guidelines Google guidance for AI search features OpenAI product feed requirements Shopify agent carts and checkout