Thyris Merchant Services as the Agentic Commerce Readiness Platform
This document explains what Thyris Merchant Services is, what it is not, which customer-facing capabilities it contains, and how it relates to the Thyris Agentic Commerce platform.
Executive Summary
Thyris Merchant Services is the merchant readiness platform for agentic commerce and agentic procurement. It prepares merchant systems so AI agents, MCP clients, UCP-compatible clients, and customer-facing commerce experiences can safely discover products, create carts, complete order handoffs, request supplier quotes, process procurement orders, and observe operational outcomes.
Thyris Agentic Commerce provides the agent orchestration layer: agent experiences, policy-controlled tool access, session continuity, usage reporting, and operational observability.
Thyris Merchant Services provides the merchant-side operating layer: merchants, stores, sub-merchants, API keys, catalog data, cart and order APIs, procurement suppliers, inventory, quote workflows, purchase orders, webhooks, MCP tools, UCP-compatible endpoints, extension adapters, diagnostics, dashboard operations, and security controls.
Together, they make a merchant ready for agentic commerce procurement: the agent experience can safely use merchant-approved business capabilities to search, transact, replenish, approve, pay, and reconcile.
What It Is Not
Thyris Merchant Services is not a replacement for the merchant's ERP, PIM, commerce backend, warehouse system, supplier system, or payment provider. It does not require the merchant to expose private business logic, source code, database design, or internal operating procedures.
The platform focuses on secure integration contracts, readiness checks, operational controls, and approved commerce/procurement capabilities. Customer documentation should describe what each integration surface does and what data is required, not how Thyris implements those capabilities internally.
Platform Relationship
Thyris Agentic Commerce should be treated as the orchestration boundary for agent behavior. Thyris Merchant Services should be treated as the merchant readiness and operational boundary for merchant data, tools, and workflows.
What Merchant Services Contains
| Capability | Description |
|---|---|
| Merchant account model | Merchant, sub-merchant, store, team member, role, and account settings model for multi-tenant operations. |
| Store setup | Store creation, store-level configuration, store IDs, store-scoped keys, and store-specific catalog/procurement data. |
| Developer access | Developer API keys with merchant, store, sub-merchant, and custom-store scopes. |
| Catalog management | Product upsert, listing, search, deletion, variants, images, prices, stock state, inventory quantity, flexible metadata, and searchable attributes. |
| Cart and order flow | Cart creation from agent-facing catalog IDs, cart clearing, checkout IDs, and order completion/handoff data. |
| Catalog webhooks | Inbound product synchronization and outbound product, cart, checkout, and order event delivery. |
| Procurement suppliers | Supplier records, contact data, supported currencies, capabilities, endpoints, reliability, lead-time, and status fields. |
| Procurement inventory | Reorder inputs, procurement item IDs, target stock levels, reorder points, auto-reorder flags, thresholds, cost, currency, and policy metadata. |
| Quote and purchase order workflow | Order requests, supplier quote intake, approvals, payment request state, supplier order dispatch, shipment, receipt, and completion statuses. |
| Procurement webhooks | Inbound supplier/inventory/order synchronization and outbound procurement lifecycle events. |
| MCP tools | Remote MCP access for controlled catalog and procurement tools, including list/search/create/update flows where allowed by API scope. |
| UCP-compatible APIs | Protocol-compatible catalog and procurement endpoints backed by the same merchant data and authorization model. |
| Extension and adapter layer | Adapter patterns for connecting commerce platforms, ERP/PIM systems, supplier systems, and custom backends into normalized Merchant Services contracts. |
| Diagnostics and operations | Store diagnostics, integration health views, operational dashboards, audit/activity records, API key controls, and visibility settings. |
| Security controls | HTTPS-only integration posture, server-side API keys, webhook secrets, least-privilege scopes, two-factor authentication, and credential rotation guidance. |
Readiness Outcomes
A merchant is considered ready for agentic commerce when it can provide:
- Structured product data with stable IDs, price, currency, stock state, product URLs, images, and variant information.
- A clear cart and checkout model, including which system owns checkout, payment authorization, inventory deduction, and final order creation.
- Operational webhooks or APIs for product updates, order status updates, and reconciliation.
- Secure API keys, scoped access, staging and production separation, and a documented credential rotation process.
- MCP or UCP access when agents or protocol clients need controlled tool access.
A merchant is considered ready for agentic procurement when it can also provide:
- Supplier records with contact, capability, lead-time, currency, and endpoint details.
- Procurement inventory records with reorder policy, target stock level, thresholds, unit cost, and preferred supplier mapping.
- Quote request and approval rules.
- Supplier order, payment, shipment, receipt, cancellation, and completion states.
- Monitoring and replay processes for failed supplier email, webhook, quote, or order events.
Reusable Commerce Adapter Pattern
Merchant Services is designed so commerce-specific source systems do not need to appear in customer documentation. A source platform or custom backend can be represented as an adapter that maps its native capabilities into normalized Thyris contracts:
| Source Capability | Thyris Contract |
|---|---|
| Product search or product export | Catalog products and MCP product search tools. |
| Add-to-cart or basket API | Cart creation and cart update/handoff flow. |
| Checkout page, checkout API, or order API | Checkout ID, order completion, or merchant checkout handoff. |
| Customer address and delivery data | Checkout customer, shipping, and billing fields. |
| Supplier or purchasing module | Procurement suppliers, inventory, quote requests, and purchase orders. |
| Platform event stream | Inbound webhooks and outbound reconciliation events. |
This keeps customer-facing documents focused on Thyris Merchant Services, Thyris Agentic Commerce, and the merchant's own integration responsibilities.
Recommended Rollout
- Confirm merchant account, stores, and team ownership.
- Create staging API keys with the narrowest scope required.
- Synchronize a small catalog and validate search, cart, and order handoff.
- Add inbound catalog webhooks or scheduled REST synchronization.
- Add outbound webhook destinations for reconciliation.
- Configure procurement suppliers, inventory inputs, reorder policies, and quote workflows if procurement is in scope.
- Enable MCP or UCP access for agentic commerce channels.
- Connect the Merchant Services capabilities to Thyris Agentic Commerce flows.
- Run POC, integration, and production readiness checks.
- Move to production with monitoring, support ownership, and credential rotation in place.