For merchants
Pizza x402 is for takeout-first shops that want fewer phone interruptions, clearer orders during rush hours, and a self-serve owner path from signup to live QR without pretending to be a full marketplace or POS replacement.
Merchant reality
The product framing follows the real merchant problem: fewer phone interruptions, less payment friction at pickup, and a direct ordering channel that does not feel like another operational burden.
Who it fits
The product is being shaped around rush-hour reality: small teams, existing kitchen flow, and no appetite for a heavy system change just to take direct orders.
Pickup has to matter enough that phone-order chaos is a real daily cost worth fixing.
The value is operational relief during busy windows, not another system someone has to babysit.
The restaurant keeps the ordering relationship instead of renting it from a marketplace.
What setup looks like
The public site can describe the current setup path honestly even without approved product screenshots. It should stay specific about what the merchant will actually do first.
Start with owner name, email, and password in the merchant app.
Source: AGENTS merchant signup route
Launchpad captures the shop profile, pickup details, and storefront basics with save-and-resume.
Source: AGENTS merchant routes
Stripe is the launch payment rail. After Launchpad, the one-pizzeria workspace keeps Stripe readiness, storefront review, business details, and operational edits in one place.
Source: ADR-0018 + AGENTS
Current guidance already covers stable storefront URLs, copy/open actions, QR downloads, print sizes, and practical placement ideas for a first rollout.
Source: QR Code Setup Guide + AGENTS QR Kit
Public screenshots of merchant setup, storefront review, and QR Kit assets are not approved yet. This section stays step-based until real public-safe visuals exist.
Source: Merchant routes + QR setup guide
Merchant readiness checklist
A credible launch starts with a few operational basics being clear before the QR goes out to customers.
Someone has the time and authority to create the account and finish the first setup steps.
Current setup starts with the owner signup path, not a long sales process.
The shop name, pickup address, phone number, and opening hours are ready to enter accurately.
Source: Merchant bootstrap + Launchpad basics
The owner already knows whether managers need Merchant Console access and which staff should stay in Order Desk only.
The current merchant app already separates owner, manager, and staff roles.
Source: AGENTS authenticated merchant surface
The team already knows what “ASAP” should mean in practice and how pickup windows should feel during service.
Source: Vision pickup-first scope
A live storefront requires a valid Stripe account with required payment capabilities enabled. Pizza x402 should not claim availability outside Stripe-supported countries, currencies, and capabilities.
Source: ADR-0018 + AGENTS Stripe posture
The first placement is already chosen: counter, window, printed menu, flyer, or pizza box.
Source: QR Code Setup Guide
Common objections
If the product adds work, needs special hardware, or complicates rush hours, it fails the test. The page should say that plainly.
The point is to move repeatable orders off the phone, not create another heavy workflow during service.
The launch path assumes the restaurant can use its existing phone, tablet, laptop, or printer plus a QR code.
Structured paid orders should reduce call bottlenecks during busy windows. The site should not promise automation it does not have.
This is a merchant-aligned direct channel, not a marketplace handoff where the shop loses the customer touchpoint.
V1 is focused on takeout and pickup flow. It does not sell itself as a delivery network.
The normal path is self-serve owner signup, Launchpad, workspace, payments, and QR rollout, not a long founder-managed implementation project.
What merchants get now
Start with the ordering flow that matters most for takeout, then expand later from a stable base.
Clear boundaries make the rollout easier to trust, especially for a first-time merchant visitor.
Merchant FAQ
The point is to reduce reasons to hesitate, not hide them behind generic sales copy.
It should do the opposite. The intended gain is fewer phone interruptions and clearer prepaid orders, not another dashboard someone has to watch all day.
The current public promise is about reducing phone interruptions and pickup friction, not adding a second ops system.
Source: Vision
No special hardware is assumed. The launch path is meant to work with the devices and browsers the restaurant already uses, plus a printable QR code.
The current QR guidance assumes existing devices plus printed QR placement, not a hardware rollout.
Source: Vision + QR Code Setup Guide
Rush hours are the real use case. Structured paid orders should reduce call bottlenecks and back-and-forth, but the site should not promise kitchen automation that does not exist.
No. The direct ordering surface stays aligned with the restaurant, so the customer relationship does not default to a marketplace middleman.
V1 is for pickup and takeout. That narrow scope is deliberate so the product can solve the first operational problem clearly.
Source: Vision
The intended setup path is lightweight and self-serve: create the owner account, complete Launchpad, review the storefront, connect payments, and start sharing the QR code.
Support is available, but the current merchant routes already define signup, Launchpad, workspace, and QR Kit as the normal path.
Source: AGENTS merchant routes + QR Kit
Current public evidence
The public site can name historical pilot context and current Stripe-only rollout posture, but it should not imply approved metrics or storefront screenshots that do not exist yet.
Au Comptoir à Pâtons in Lyon remains historical pilot context. Public metrics and merchant-ready screenshots are not published yet, so this page stays grounded in setup clarity, Stripe readiness, and current scope.
Au Comptoir à Pâtons in Lyon, France is historical pilot context, not the launch market constraint.
Source: README + ADR-0018
Stripe is the only launch payment path, with pickup-first scope and merchant activation gated on Stripe readiness.
Source: ADR-0018 + AGENTS
No public pilot metrics, no testimonial quotes, and no approved storefront screenshots are published on this page yet.
Source: Current evidence inventory
When public-safe pilot visuals or measured case-study facts exist, this block can absorb them without changing the page structure.
Source: Vision + README + AGENTS
The first goal is a direct prepaid pickup flow that merchants can actually test in the shop.
The site should stay credible by using source-backed facts and setup clarity until richer approved evidence exists.
The restaurant keeps pickup timing, status handling, and a direct customer-facing ordering path.
Ready when you are
Start setup when you are ready. If you want to talk through your current pickup flow first, use the contact page, but normal onboarding should stand on its own.