Overview
Learn how Commerce Graph structures products, services, offers, prices, policies, locations, availability, sources, and action paths for AI systems.
- It differs from a website page because it is structured, versioned, and approval-aware.
- It differs from a product feed because it can model services, policies, locations, sources, packages, and action paths.
- Unapproved and private fields stay separate from published public outputs.
What it contains
A Commerce Graph can contain client identity, locations, services, offers, packages, menus, spaces, policies, action paths, sources, published outputs, issues, and fixes.
- Products and services with descriptions, prices, durations, capacity, and availability.
- Policies for cancellation, refunds, deposits, eligibility, and fulfillment.
- Locations, contact paths, operating hours, regions, and source URLs.
- Action paths tied to offers, packages, services, and buyer intent.
Unapproved, approved, and published
Akii separates unapproved graph work from approved and published outputs. Public output should only include the approved public fields of a published graph version.