Skip to main content
Menu
Start a conversation

A storefront humans and AI agents can both check out on.

SwiftShop.pl is a Polish commerce platform built the other way round. Instead of bolting AI, e-invoicing and accessibility onto a 2015 codebase, we start from the four things Poland actually mandates and the one thing the market hasn't caught up with: a checkout any agent can complete.

Warsaw, PolandPrivate beta 2026Launch 2027
Why now

Four deadlines already landed. Almost nobody re-architected for them.

Poland is the rare market where regulation, payments and logistics all changed inside 24 months. Each change is a migration project for an incumbent — and a greenfield for us.

Live surface

An agent completes a purchase in a session you can audit.

Every agent-initiated checkout leaves a signed trail: which agent, which policy ceiling, which payment token, which invoice. You stay merchant of record and you keep the customer.

Checkout — agent session ss_9f2c
Shell jacket RC-01
size L · black
373.98 PLN
Shipping — parcel locker
WAW831M · promise 11 Mar
0.00 PLN
Discount — price history
30-day lowest: 419.00 PLN
−45.02 PLN
ACP 1.0 · session ss_9f2cAgent ready

E-invoicing became mandatory

Every Polish business had to issue structured invoices through KSeF from 1 April 2026, and had to *receive* them from 1 February 2026.[1] Billing is no longer a PDF you email. It is an XML document with a government-issued number.

Online shops became regulated for accessibility

The Polish Accessibility Act has applied to e-commerce since 28 June 2025, supervised by the Minister for Digitalisation, with penalties up to 10% of turnover.[2] Your checkout is now a regulated surface.

Agents started buying

On 29 September 2025 OpenAI and Stripe open-sourced the Agentic Commerce Protocol so an AI agent can complete a purchase for a user.[3] Over 700 million people use ChatGPT weekly. Almost no Polish shop is reachable by any of them.

BLIK ate the online checkout

Poles made 1.4 billion BLIK payments online in 2025 worth 219 bn PLN — roughly triple the estimated value of card payments online.[4] A store that treats BLIK as an optional plugin loses the default.

The platform

Six things a Polish shop needs that no single stack gives it

An agent gateway, not a chatbot

Your catalogue is published as an MCP server and an ACP checkout. Any compliant agent — ChatGPT today, others as they adopt the spec — can search, configure and pay, while you remain merchant of record.[5]

KSeF-native billing

FA(3) structured invoices are generated from the order and submitted to KSeF automatically, with offline24 mode and QR-coded visualisations for the cases where you still must hand a document to a human.[6]

Accessibility as architecture

WCAG 2.2 AA and EN 301 549 are enforced in CI, not audited against once. Your statutory accessibility statement and the 30-day complaint workflow ship with the storefront.

Polish payments as defaults

BLIK, BLIK Pay Later, pay-by-link, Apple and Google Pay, cards and COD — on by default, because 20.7 million Polish accounts already use BLIK twelve times a month.[4]

Logistics that matches reality

Paczkomat picker at checkout, label generation, cash-on-delivery reconciliation and returns — against a network of 30 000 lockers in Poland alone.[7]

A sub-second storefront

LCP under 2.5 s, INP under 200 ms, CLS under 0.1 at the 75th percentile are release gates, not aspirations.[8] 82% of Polish online shoppers are on a phone.

Market

The numbers we are building against

Every figure below is sourced, dated and mirrored as JSON at /data/market-data.json, so an agent can reason over the same numbers a human reads here.

91.971 bn PLNPolish online retail turnover in 2025[9]
9.1 %of all Polish retail now happens online[9]
≈75 kactive online shops competing for that demand[10]
20.7 mactive BLIK accounts at the end of 2025[4]

Sources cited on this page

Every figure above is drawn from the sources listed here. The machine-readable register lives at /data/market-data.json.

  1. Ministerstwo Finansów / Krajowa Administracja Skarbowa. Zakres obowiązkowego KSeF (KSeF 2.0) —
  2. Dziennik Ustaw RP. Ustawa z dnia 26 kwietnia 2024 r. o zapewnianiu spełniania wymagań dostępności niektórych produktów i usług przez podmioty gospodarcze (Dz.U. 2024 poz. 731) —
  3. OpenAI. Buy it in ChatGPT: Instant Checkout and the Agentic Commerce Protocol —
  4. Polski Standard Płatności (PSP). Blisko 3 mld transakcji BLIKIEM w 2025 r. i ponad 2 mln nowych użytkowników —
  5. Agentic Commerce Protocol. An open standard for programmatic commerce flows (Apache-2.0) —
  6. Ministerstwo Finansów. Etapy wdrożenia KSeF 2.0 — mapa drogowa —
  7. Grupa InPost. Grupa InPost ma już 30 000 maszyn Paczkomat w Polsce i 70 000 w całej Europie —
  8. Google / web.dev. Web Vitals — LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1 at the 75th percentile —
  9. Krajowa Izba Gospodarcza (KIG), on GUS retail reporting. E-handel stanowił 9,1% handlu detalicznego w 2025 roku —
  10. Dun & Bradstreet Poland, via Rzeczpospolita. Liczba sklepów internetowych w Polsce rośnie mimo presji globalnych platform —
Plan

What is built, what is next

  1. Architecture and the agent gateway

    The ACP checkout surface, the MCP catalogue server and the KSeF invoice pipeline are the parts that are hardest to retrofit, so they are the parts we built first.

  2. Design-partner beta

    Twenty-five Polish merchants across e-grocery, specialist retail and B2B wholesale run real orders on the platform, with migration support and a named engineer.

  3. Public launch

    Self-serve onboarding, the full fee schedule, the public price-and-stock API and the Cloudflare-edge rendering tier.

  4. Cross-border

    Multi-currency settlement, EU VAT OSS and IOSS handling, and agent-readable catalogues in every locale. Only 4.9% of Polish firms sell online abroad — that gap is the growth story.

Questions

Fair questions, direct answers

Is SwiftShop.pl live?
No. The domain currently resolves to a hosting placeholder page and the company is in KRS registration. This site is the technical and commercial case for the platform we are building.
What does "agent-native" actually mean?
It means the storefront exposes a machine interface as a first-class product surface: an MCP server for discovery and configuration, an ACP checkout for transacting, and an llms.txt plus structured data layer so a language model can read the whole catalogue without scraping HTML.
Do I still need a marketplace?
Probably, for reach. SwiftShop is designed to be the channel you own — where you set the fee, keep the customer data, and where the agent relationship points at you rather than at an intermediary.
How can you promise accessibility when audits are expensive?
Because we put it in the build pipeline instead of the calendar. Automated axe-core and contrast checks fail the build, and every component ships with a manual test script for the parts automation can't judge.

Talk to us before the beta fills

Twenty-five design-partner seats. We would rather have five committed merchants than fifty lukewarm ones.