Merchant Flow
A merchant starts in AgenticOrg by opening the Commerce Runtime settings page, saving tenant/merchant/store config, connecting Shopify with read-only credential custody, running source sync, and requesting Grantex OACP authority artifacts. Shopify remains the source of record, and the merchant can edit source, channel, payment-provider, public publishing, and POS settings later.
Requirements
You need a public myshopify.com domain, read-only Admin API or approved OAuth access, an AgenticOrg tenant, Grantex tenant allowlisting, channel approvals, and provider-owned capability configuration if purchase handoff is offered. WooCommerce, ERP, PIM, OMS, WMS, and custom API configs can be saved now as pending-adapter setup.
What Buyers See
Buyer agents answer from cached OACP artifacts with source and freshness labels. A purchase request becomes a prepared handoff or blocker; payment and order success must come from merchant/provider systems.
Frequently Asked Questions
Does AgenticOrg move my Shopify source of truth?
No. Shopify remains the source of record. AgenticOrg stores public-safe OACP refs and freshness labels.
Can the buyer agent complete payment by itself?
No. Nothing a buyer agent sends approves a payment. A checkout completes only after the commerce arbiter's fixed rules allow that exact checkout and the Plural payment executor carries it out, and that executor is switched off by default. Payment and mandate rails remain provider-owned; bank-owned and other rails require approved adapters before execution.
Topics
Ready to try it?
Evaluate the workflow with your own approved data, integrations, review gates, and success criteria.
Open the OACP flow