Start with the problem you can see
Find the right guide, skill, playbook, or reference for the commerce issue in front of you.
The Commerce Fieldbook covers the awkward gaps between storefronts, catalogs, analytics, ad platforms, search engines, and AI shopping tools.
Begin with the symptom. A merchant usually arrives with a stale price, a broken checkout path, conflicting revenue reports, or a product that never appears in shopping answers. SEO, GEO, CRO, accessibility, analytics, and reliability help explain the issue later.
Pick the right page
Open a problem guide when you know what is wrong but not why. It tells you what to capture, what to check first, and which conclusions are premature.
Open an agent skill when the task is repeatable. Each skill lists the inputs, output format, checks, and limits.
Open a playbook when the work crosses teams or systems and needs an agreed sequence.
Open projects and references when you need the official rule, specification, or tool behind a recommendation.
New to the vocabulary? The glossary defines the technical terms (PDP, feed, structured data, attribution window, and the rest) in plain language.
Page status
Every page has a review date and status:
- Stable: ready for routine use.
- Emerging: useful, but the platform or practice is still moving.
- Experimental: suitable for testing, not for treating as a standard.
A sensible reading order
- Read the evidence model.
- Skim the glossary if the vocabulary is new.
- Review the rules for agent skills.
- Find the problem closest to yours.
- Follow the linked skill or playbook.
- Check platform requirements against the official source.