/vendor/zalando/AgentRouting.json or
/vendor/zalando/AgentContext.json directly.
zalando.com
Overview
Does zalando.com support MCP?
No confirmed MCP support was found for zalando.com as of 2026-06-30.
What agentic protocols does zalando.com support?
As of 2026-06-30, zalando.com has confirmed support for UCP and openai_apps_sdk.
Is zalando.com's API publicly accessible or partner-gated?
Access varies by protocol: platform mediated, open.
Does zalando.com explicitly prohibit automated access?
Yes. zalando.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is zalando.com agent-ready?
Partial. zalando.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence found that Zalando has adopted or implemented the Agent2Agent (A2A) protocol. Search results surfaced Google's A2A launch announcement (naming partners such as Salesforce, SAP, and Atlassian) and an agentic-commerce overview that mentions Zalando only in the context of UCP (Universal Checkout Protocol), not A2A. No Zalando-specific A2A documentation, partnership announcement, or endpoint was identified.
No evidence found that Zalando has adopted or plans to adopt the Agentic Commerce Protocol (ACP, co-developed by OpenAI and Stripe). The initial ACP launch partners are Etsy and Shopify-ecosystem merchants (Glossier, SKIMS, Spanx, Vuori), with Walmart subsequently added. Zalando was identified in search results only as a supporter of Google's UCP — a separate, unrelated protocol — and does not appear in any ACP partner or merchant announcement.
Zala ndo appears as a named endorser of UCP (Universal Checkout Protocol), not AP2. AP2's known payment-layer backers are Visa, Mastercard, Adyen, and PayPal. No vendor-specific evidence found linking Zalando to AP2 adoption or implementation.
No evidence of an official Zalando MCP server was found across searches covering Zalando's developer documentation, GitHub presence, and the official MCP registry. The only MCP-labeled results for Zalando were third-party Apify scrapers (e.g., apify.com/jupri/zalando/api/mcp) — unauthorized scraping wrappers, not vendor-sanctioned interfaces. Zalando's own developer surface (REST APIs for partners and merchants) shows no MCP integration announced or documented.
MPP was co-authored and launched by Stripe and Tempo in March 2026, with Visa as a named design partner for card-based extensions. No evidence found of Zalando.com appearing in any MPP launch partner list, implementation announcement, or developer documentation. Zalando was not identified in any search result related to MPP adoption.
Two searches found no evidence that Zalando has adopted or is implementing NLWeb. Named NLWeb early adopters ("pioneers") include Tripadvisor, Shopify, Chicago Public Media, Common Sense Media, DDM (Allrecipes/Serious Eats), O'Reilly Media, Milvus, Snowflake, and Inception — no retail or fashion e-commerce brand matching Zalando. Zalando was not mentioned in any NLWeb launch materials or pioneer profiles. Not confirmed_absent because Zalando has made no public statement about NLWeb; evidence is simply absent.
Merchant participant exposing product discovery and checkout via UCP-powered surfaces in Google AI Mode (Search) and the Gemini app; first use case is agentic checkout for Zalando's catalog
Zalando publicly confirmed adoption of Google's Universal Commerce Protocol at NRF (January 2026), with checkout via Google AI Mode and the Gemini app as the initial use case. The integration is platform-mediated through Google's surfaces rather than a directly callable public endpoint. As of March 2026, UCP-powered checkout on Google's surfaces was rolling out for eligible US retailers, with Zalando named as a participating merchant.
No evidence that Zalando has implemented or been listed as a launch partner for WebMCP. The protocol is a Google/Microsoft browser-native early preview (Chrome 146 Canary), with Cloudflare, HubSpot, and Stripe-adjacent ecosystems appearing in early adopter coverage — not Zalando. Zalando's own AI-related developer surface centers on its internal AI fashion assistant and partner portal tooling, with no connection to the WebMCP window.AICommands surface.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Third-party-built ChatGPT GPT for Zalando fashion product discovery — not built or operated by Zalando itself, but by a third party (Heimat24 GmbH); provides conversational fashion search and recommendations within the ChatGPT platform, requiring ChatGPT Plus subscription.
A GPT named 'Zalando' exists at chatgpt.com/g/g-WjbNiEvsU-zalando, but its listed builder is Heimat24 GmbH, not Zalando SE — this is a third-party app, not an official Zalando-published integration on OpenAI's ChatGPT Apps platform. Zalando's own OpenAI partnership (documented at openai.com/index/zalando/) is an internal deployment of GPT-4o mini within Zalando's own platform, not a ChatGPT App. No evidence of an official Zalando-published GPT on the ChatGPT Apps platform was found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No llms.txt, AGENTS.md, /.well-known/agent, or similar self-declaration files were found on zalando.com. Direct URL checks could not be performed due to network timeout constraints in this environment. Web searches returned no evidence of Zalando publishing any such files; Zalando was mentioned as an endorser of the UCP protocol (a Shopify-led initiative) in a third-party article, but that is evidence of a third-party platform strategy, not of Zalando itself publishing a self-declaration file at a predictable location on its own domain. The distinction between confirmed_absent and not_found applies here: no vendor-specific statement or deprecation notice was found, and no successful check of the actual endpoints was possible, so not_found is the appropriate status.
Summary
Has agent interface: partial
Verify Zalando's UCP integration status directly with Google's UCP partner program or Zalando's business development team, as the only confirmed agent-callable surface is platform-mediated through Google (UCP) and not directly accessible; also confirm whether Zalando has published or plans to publish any official MCP server, given that only unauthorized third-party scraping wrappers were found.
AgentContext
Verified discrepancies
Vendor claim: Zalando's stated policy offers free returns (within 30 days in applicable markets) with no disclosed upper limit on how many returns a customer may make, and its terms present returns as a standard, unconditional right for eligible items.
What actually happens: Since March 7, 2025, Zalando enforces a tiered account-restriction regime for customers it deems to have 'excessive' returns: first a warning email, then restriction of account functions, and finally a 12-month account pause — meaning an agent or user who relies on the documented free-returns policy to complete return-heavy purchases may find the account suspended mid-use, with no prior contractual notice at point of purchase.
Agent guidance: Before completing any return-heavy transaction or multi-item order on Zalando, an agent must: (1) confirm the applicable market's current return window (30 days in DE/NL/IT as of Jan 2025, not 100 days); (2) be aware that accounts with high return rates may be restricted or suspended without upfront contractual warning — if managing an account with a history of frequent returns, verify account standing before placing new orders; (3) do not represent free returns as unconditional to the user, since Zalando reserves the right to restrict or pause accounts for what it unilaterally defines as excessive return behaviour.
- FashionUnited reports that Zalando introduced measures in March 2025 to temporarily suspend accounts of customers who return 'a disproportionate amount,' including a warning step and then a 12-month account pause for persistent cases.
- Cross-Border Magazine reports that from January 7, 2025, Zalando reduced its return window from 100 days to 30 days in Germany, the Netherlands, and Italy — a material reduction that affects any agent or workflow operating under the older documented policy.
Vendor claim: Zalando presents itself as an open e-commerce platform where any registered customer can browse, add items to a cart, and complete a purchase. Its public-facing shopping experience does not display account-level ordering restrictions prior to checkout.
What actually happens: Since March 7, 2025, Zalando enforces a tiered penalty scheme against customers it classifies as 'excessive' returners: first a warning email, then restriction of certain account functions, and finally a full 12-month ordering suspension. These restrictions are applied at Zalando's discretion based on undisclosed return-rate thresholds and are not surfaced to the customer (or an agent acting on their behalf) at the point of browsing or initiating checkout. An agent could navigate the entire product-selection and cart flow, then encounter a hard block at the payment/confirmation step due to an account-level suspension it had no prior visibility into.
Agent guidance: Before initiating any checkout flow on behalf of a user, attempt a lightweight account-status check (e.g., verify cart submission or payment method acceptance on a test/low-value item if the platform allows). If a hard block is encountered at checkout with no prior warning displayed, treat this as an account-level restriction and surface the error message to the user immediately rather than retrying. Do not assume product availability or cart readiness implies ordering ability for that specific account.
- FashionUnited reports that Zalando announced on March 7, 2025 that customers returning a 'disproportionate amount' of items will receive a warning, followed by account function restrictions, and ultimately a 12-month account pause for persistent excessive returners.
- EcommerceGermany confirms the policy update, noting that Zalando restricts ordering capabilities for a subset of customers who exceed undisclosed return-rate thresholds, framing it as a sustainability and operational measure.
Human handoff required for
Escalate to a human when a checkout or payment confirmation step returns a hard block or error that was not signaled during browsing or cart-building, as this likely indicates Zalando has applied an account-level ordering suspension under its undisclosed tiered restriction scheme for excessive returners — the agent cannot resolve this programmatically and the user must be informed and decide how to proceed.
- Since March 7, 2025, Zalando enforces a tiered penalty scheme — warning, then function restriction, then 12-month ordering suspension — based on undisclosed return-rate thresholds that are not surfaced at browsing or checkout initiation, meaning a block can appear only at the final payment or confirmation step.
- Reporting confirmed that Zalando began restricting and suspending accounts of customers it classifies as excessive returners from March 2025, with no threshold disclosed publicly at the point of purchase.
Escalate to a human when attempting to process a return on behalf of a user whose account has previously had a high return rate, because Zalando may have issued a warning or restriction that silently limits return functionality — a gap exists between the stated unconditional free-returns policy and actual enforcement of account-level penalties.
- Zalando's stated policy presents free returns as an unconditional right for eligible items, but since March 2025 it enforces account warnings, function restrictions, and 12-month suspensions for what it unilaterally deems excessive return behaviour, with no upfront contractual disclosure at point of purchase.
- Zalando's March 2025 account-restriction rollout was reported as applying to customers with high return rates, with the first stage being an email warning and subsequent stages progressively blocking account capabilities including returns.
Escalate to a human when a user asks whether their return window is still 100 days, because Zalando reduced the standard return window from 100 days to 30 days in key markets (DE, NL, IT) effective January 2025 — representing the agent as confirming an extended window based on outdated policy could cause the user to miss their actual deadline.
Five discrepancy categories were checked for zalando.com. Pricing (hidden fees, advertised-vs-checkout gaps): searched and found no documented regulatory actions, settlements, or verified patterns of deceptive pricing specific to Zalando. Availability (ghost inventory, bait-and-switch): searched and found no independently verified evidence of systematic availability discrepancies at checkout for Zalando-listed products. Identity (merchant-of-record ambiguity, counterparty confusion): searched and found no documented evidence that Zalando misrepresents its legal counterparty role or deflects liability to third-party partners in a deceptive manner. Policy (stated vs. enforced return/refund terms): findings present — two material policy shifts in early 2025 were identified, including a return-window reduction to 30 days in key markets (effective January 2025) and a March 2025 rollout of tiered account suspensions for excessive returners that are not disclosed at point of purchase. Undisclosed constraints (hidden checkout or ordering blocks): findings present — Zalando's March 2025 tiered restriction scheme can silently block a user's ability to complete a purchase based on historical return behaviour, with no visibility to the agent or user until the final checkout step. No scan was blocked, but all findings rely on press reporting and Zalando's own policy pages rather than primary regulatory filings, as no enforcement actions were located.