Summary
This is a reference sequence. Each step depends on tenant configuration, a promoted connector, valid credentials, authority status, and external channel approvals; the sequence does not claim tenant readiness.
In this design, Shopify remains the operational source of record; downstream systems should receive scoped evidence rather than raw private payloads.
Gated Reference Journey
1. Reference step: prepare tenant-, merchant-, and store-scoped configuration in `/dashboard/commerce-runtime`.
2. Merchant creates or updates a Seller Commerce Agent onboarding packet.
3. Merchant stores Shopify credential custody through the approved AgenticOrg path.
4. AgenticOrg runs read-only Shopify Admin GraphQL sync and webhook-triggered refresh marking.
5. AgenticOrg sends public-safe evidence refs, hashes, timestamps, and source ids to Grantex.
6. Grantex issues or refuses OACP artifact families.
7. AgenticOrg caches artifacts by buyer agent, seller agent, tenant, and merchant.
8. Buyer channels answer from valid cache with source/freshness labels.
9. Purchase intent becomes a prepared provider/POS/merchant handoff or a blocker.
Intended Buyer Experience
A promoted buyer channel should support non-binding product, price, availability, policy, and discovery questions with source and freshness labels. Stale, missing, revoked, or mismatched evidence should produce a refresh requirement or refusal.
What Stays Blocked
No buyer channel can invent price, inventory, delivery, warranty, refund, tax, or payment facts. No channel creates checkout, captures payment, creates orders, reserves inventory, or marks a payment successful from OACP cache alone.
Topics
Ready to try it?
Explore the public playground, or create an account to evaluate an agent with your own approved data and controls.