Swiss edition · Chapter 01

The same category.
A different market.

Agentic Commerce Operations does not work differently in Zurich than in Hamburg. What differs are the payment routes, the languages, the data protection law and the question of which law the commerce data sits under. This page walks through the four points where a Swiss shop has to vet a provider differently than a German one.

The category in one sentence

Quote, not copy.

Category paper v2.0 · 8 September 2026
"The software category for AI agents that run an online shop on the operator side: they observe the real order flow and market signals, diagnose root causes against the source code, and act within defined policies under human oversight with an audit log."

Source: DevQon, category paper v2.0. Full version, origin of the term, boundaries to neighbouring categories and change history: Definition of Agentic Commerce Operations.

Contactless payment with a smartphone at a terminal, next to it a stand with a QR code, a Swiss cross on the counter.
Every payment route has its own failure pattern. The agent knows them all, from QR code to acquirer.
01 · Payment landscape

Six payment routes, one order flow.

Six Swiss payment routes. One order flow.ACO · CH · 01The agent knows the response codes of the Swiss providers.TWINT420 msPostFinanceCard310 msPostFinanceE-Finance38 sCallback missing · 38 sDatatrans280 msSIX Saferpay350 msCredit cardvia acquirer510 msAgentPolicy: fallback active
Response times are typical operating values, not a measurement log. Fallback rule from the operator's policy.

A Swiss checkout usually offers more payment routes than a German one, and they behave differently. TWINT works with sessions that expire. PostFinance Card and E-Finance confirm success through a callback that sometimes never arrives. Datatrans and SIX Saferpay return their own response codes for authorisation, cancellation and timeout. Payrexx bundles several routes behind one interface. Add the card acquirer with 3-D Secure.

For operations this means: the shop can be online, the catalogue can be correct, and orders still get lost because a single payment route stands still. In the admin that looks like a quiet hour. An ACO agent reads the providers' response codes and callbacks in the real order path, recognises the pattern and acts within the policy the operator has set. A typical policy reads: after three timeouts from the same provider within ten minutes, activate the fallback provider, log the action, inform the operator. Without a policy the same case arrives as a proposal with a CHF estimate and waits for a click.

What the agent has to know
  • TWINT · session expiry, cancellation in the app, confirmation back to the shop
  • PostFinance · callback confirmation, missing or late callbacks
  • Datatrans · response codes for authorisation, cancellation, timeout
  • SIX Saferpay · handshake, token expiry, rejection
  • Payrexx · gateway status across several routes
  • Acquirer · 3-D Secure drop-offs, authorisation rate

The agent reads provider signals. It does not replace a payment contract or an integration.

02 · Multilingual

Three languages, one order flow.

Three languages. One order flow.ACO · CH · 03One agent, three store views, the same signal depth.STORE VIEW · DEProduktCHF 84.90In den WarenkorbSTORE VIEW · FRProduitCHF 84.90Ajouter au panierSTORE VIEW · ITProdottoCHF 84.90Aggiungi al carrelloAgentSignal depth:identical
Example with one Magento instance and three store views. Price, tax logic and shipping per store view.
Store views

DE · FR · IT

A Swiss shop usually runs as one instance with three store views. Prices, tax logic and shipping rules are configured per store view. An error in the French configuration stays invisible in the German one.

Signal depth

Equally deep per store view.

The order-flow probe runs per store view through the real order path, cart to order confirmation. Cron, indexer, payment, stock and search are read the same way for all three languages, not only for the main one.

Typical errors

Tax and shipping.

A shipping rule maintained only in the German store view. A VAT class missing in the Italian store view. A payment route not offered in Romandy although it should be active. All cases a probe per store view makes visible.

03 · Data protection law

revFADP instead of GDPR.

Article
Duty
What ACO provides
Art. 7
Data protection by design and by default.
Read-only code access, zero retention, no use of operator data for training.
Art. 19
Duty to inform about the collection of personal data.
Transparency about which data is processed in which zone, as input for the privacy notice.
Art. 22
Data protection impact assessment where there is a high risk to personality.
Two-zone architecture with documented data residency as a building block of the assessment.
Art. 25
Right of access of the data subject.
Audit log per action and exportable records so that access requests can be evidenced.

The revised Federal Act on Data Protection has applied to every Swiss shop since 1 September 2023, supervised by the FDPIC. Shops serving customers in the EU carry the GDPR on top, with a data processing agreement under Art. 28 and an impact assessment under Art. 35. For AI systems the EU AI Act adds Article 14, which requires effective human oversight. A policy framework with an audit log and the ability to abort satisfies that. As for how your shop is classified: check with your data protection adviser, this page is not legal advice.

04 · Buying criterion

CHF evidence as the Swiss buying criterion.

Swiss operators rarely buy on roadmap promises. They want an amount and a date. The reference implementation XEREBROtherefore delivers the first evidenced CHF amount within three months, traceable in the Value Ledger with before-and-after value, date and source. If the evidence does not arrive, the operator cancels without commitment. Each application is booked individually and cancellable monthly after the three-month evidence. That pins the investment to a date and an amount rather than a promise.

That is not a marketing detail but a test for every provider in this category: whoever delivers no evidence in CHF is selling a dashboard. How the category differs from monitoring and AIOps is explained on the comparison page ACO vs. AIOps and APM. Terms such as Value Ledger, order-flow probe and policy are explained in the Agentic Commerce Operations glossary.

Ninety days
  • Day 0 · Health check, thirty minutes, read-only, two to four findings in CHF
  • Month 1 · Baseline running, one or two signal systems, Value Ledger starts
  • Month 3 · First CHF evidence, before and after, with date and source
  • After that · Monthly cancellation, no evidence means no commitment
The market in numbers

CHF 15.8 bn

Swiss online retail 2025

In 2025 Swiss consumers bought goods worth CHF 15.8 billion online, up 6 percent. The domestic share was CHF 13 billion, purchases abroad CHF 2.8 billion. Source: HANDELSVERBAND.swiss, collected with NIQ/GfK and Swiss Post, published in March 2026. Every operational fault in the checkout is a share of that market that quietly goes to competitors.

More on this topic

From Switzerland into practice.