Standard field names
All ecommerce templates share naming patterns like `inventory`, `policies`, `actions`, and `evidence`. Reuse these keys consistently so agents can cross-reference data across pages.
Ecommerce templates
These templates capture the commerce journey from discovery through support. Use them together to give agents consistent answers about products, policies, and calls-to-action.
Need a strategic overview? Jump to the ecommerce industry page.
Template catalog
Each template links to a detail page with fields, JSON examples, and copy-ready scaffolds.
| Template | What it covers |
|---|---|
| Homepage | Brand story, credibility signals, featured categories, and prioritized actions. |
| Collections | Category purpose, merchandising logic, filters, and promotion hooks. |
| Product Pages | Specifications, inventory, pricing, guarantees, and service commitments. |
| Blog Posts | Storytelling content connecting editorial topics with shoppable moments. |
| Static Pages | Policies, FAQs, and operational details agents reference mid-conversation. |
Implementation notes
Keep the following conventions in mind as you adapt each template.
Action payloads
Action objects must include `type`, `label`, and `url`. When possible add `availability` and `tracking` metadata to signal readiness.
Collections & PDP harmony
Collections reference product IDs through `featured_products`. Ensure those IDs are defined within the product page JSON to keep relationships intact.