Thyris Merchant Services as a Procurement Platform
Thyris Merchant Services is the operating platform between inventory demand, suppliers, procurement teams, payment approval, and receiving operations. It supports human-operated workflows and controlled agent assistance without giving an agent unrestricted authority over supplier or financial decisions.
When to use this scenario
Use this model when a merchant needs to:
- Maintain procurement inventory and reorder information.
- Manage supplier identity and capability records.
- Request and compare quotes.
- Create and track purchase orders.
- Connect an ERP, supplier system, email workflow, or AI client.
- Separate request preparation from commercial approval.
- Track shipping, receipt, and reconciliation as distinct states.
Platform composition
| Capability | Merchant Services role |
|---|---|
| Procurement inventory | Holds purchasable inputs, target stock, reorder points, and supplier relationships. |
| Suppliers | Maintains supplier identity, contact, lead time, status, and supported goods. |
| Requests and quotes | Structures demand and supplier responses for comparison and review. |
| Orders | Records the approved purchase and its lifecycle. |
| Shipping and receipt | Tracks dispatch, transit, receiving, and completion signals. |
| Agentic Payment | Connects an approved provider or wallet to the payment stage. |
| REST, webhooks, UCP, MCP, and email | Connect external systems and controlled automation. |
Reference flow
AI clients prepare requests, search suppliers, and summarize quotes through approved tools. The platform keeps the approval boundary explicit for supplier selection, high-value orders, payment, and material changes.
Implementation journey
1. Define systems of record
Decide which system owns procurement inventory, supplier data, order status, and financial records. Document which fields Merchant Services may create or update.
2. Prepare procurement data
Create or synchronize inventory inputs and suppliers. Use stable external identifiers and establish rules for duplicates, inactive suppliers, missing cost data, and unit differences.
3. Select integration channels
Use REST for direct system integration, webhooks for event-driven exchange, UCP for compatible protocol clients, MCP for controlled agent tools, supplier email, or an extension for a supported adapter.
4. Model approval points
Define thresholds and roles for quote acceptance, supplier selection, order creation, changes after approval, and payment. Apply passkey or another supported control where required by the deployment.
5. Test the lifecycle
Validate normal replenishment alongside no supplier response, conflicting quotes, expired commercial terms, duplicate requests, payment failure, split shipment, damaged receipt, cancellation, and reconciliation mismatch.
6. Introduce agent assistance
Begin with read and preparation capabilities. Add write tools only when permissions, review, idempotency, audit evidence, and recovery behavior are proven.
Enterprise operating model
| Team | Primary responsibility |
|---|---|
| Procurement | Supplier selection, quote evaluation, and commercial approval. |
| Inventory operations | Demand signals, stock thresholds, and receiving accuracy. |
| Finance | Payment authorization and financial reconciliation. |
| Integration engineering | ERP contracts, event delivery, identifiers, and retries. |
| Security and governance | Credential scope, approval policy, evidence, and retention. |
Success measures
- Time from demand signal to approved order
- Supplier response and quote completion rate
- Percentage of orders requiring manual correction
- Late, partial, or unmatched shipment rate
- Payment and reconciliation exception rate
- Agent-prepared requests accepted without rework
Production controls
- Verify supplier identity and destination before dispatch.
- Treat inbound email and webhook content as untrusted input.
- Do not infer payment success from order state alone.
- Reconcile payment, shipment, receipt, and inventory independently.
- Prevent duplicate orders with idempotency and stable identifiers.
- Record who approved the commercial terms and when.