Merchant Self-Service Config for OACP Commerce

Summary

This article describes the repository's merchant-owned commerce configuration design. Route and feature availability still depend on deployment, tenant enablement, credentials, external approvals, and readiness evidence.

The configuration model covers source connector intent, buyer channel readiness, provider-owned payment rails, public catalog publishing, and Offline POS metadata. Its intended isolation boundary is tenant, merchant, and seller agent; deployments must verify that boundary before promotion.

What Merchants Configure

The reference configuration includes display profile, seller and buyer agent identifiers, commerce categories, source connector intent, source location, channel approvals, provider type, credential references, publishing preference, and POS store references.

The security design keeps secret values out of the returned configuration and stores references or redacted metadata instead. This is a design boundary, not a certification; each deployment must verify storage, logging, and response behavior.

Shopify Connector Scope in This Repository

The repository includes a read-only Shopify connector path for selected catalog and inventory fields. It should be described as available only after tenant configuration, credential validation, integration tests, and readiness promotion; it is not a claim of universal Shopify availability.

WooCommerce, ERP, PIM, OMS, WMS, and custom API entries represent connector intent or pending adapters unless a deployment has separate evidence that a specific adapter is promoted.

Payment Providers Stay Provider-Owned

The repository contains a Pine Labs Plural/P3P capability-verification path. Provider use remains non-executing until the applicable adapter, contract, sandbox evidence, webhook verification, and production approval exist for that tenant.

AgenticOrg may prepare a provider-owned handoff when configured. It does not capture payment, create mandates, create orders, reserve inventory, or claim paid status from cache. Payment success must come from provider, bank, POS, or merchant systems.

Public Publishing Is Merchant-Controlled

Public seller profile, catalog JSON, product pages, Schema.org JSON-LD, sitemap, and llms.txt surfaces require the merchant to enable public publishing in commerce config. A platform kill switch can still disable all public commerce publishing.

Safe Outcome

The intended journey is: configure, validate a promoted source connector, sync, request authority artifacts where applicable, cache scoped artifacts, publish only when enabled, show source and freshness, and prepare a provider or POS handoff only when the required evidence allows it.