For merchants
A simpler pickup ordering flow for independent pizzerias.
Pizza x402 is for takeout-first shops that want fewer phone interruptions, clearer orders during rush hours, and a direct prepaid channel that stays aligned with the restaurant.
Merchant reality
Built for rush-hour simplicity.
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
Best for shops that want a practical rollout, not a platform migration.
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.
Takeout-first pizzerias
Pickup has to matter enough that phone-order chaos is a real daily cost worth fixing.
Small teams under service pressure
The value is operational relief during busy windows, not another system someone has to babysit.
Shops that want a direct channel
The restaurant keeps the ordering relationship instead of renting it from a marketplace.
What setup looks like
From owner account to live QR code in a few concrete steps.
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.
Create the owner account
Start with owner name, email, and password in the merchant app.
Source: AGENTS merchant signup route
Fill in the pizzeria basics
Launchpad captures the shop profile, pickup details, and storefront basics with save-and-resume.
Source: AGENTS merchant routes
Connect card payments and review the storefront
Card is the launch-safe default for the current pilot posture. Onchain remains optional and secondary.
Source: Vision + AGENTS
Open the QR Kit and place the code where orders begin
Current guidance already covers stable storefront URLs, 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
Plain-language checks before you go live.
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 team already knows what “ASAP” should mean in practice and how pickup windows should feel during service.
Source: Vision pickup-first scope
The launch-safe default is card checkout, so payment readiness should not be left as a vague later step.
Source: Vision + AGENTS card-default posture
The first placement is already chosen: counter, window, printed menu, flyer, or pizza box.
Source: QR Code Setup Guide
Common objections
The main merchant hesitations should be answered directly.
If the product adds work, needs special hardware, or complicates rush hours, it fails the test. The page should say that plainly.
Fewer interruptions, not more work
The point is to move repeatable orders off the phone, not create another heavy workflow during service.
No special hardware
The launch path assumes the restaurant can use its existing phone, tablet, laptop, or printer plus a QR code.
Rush hour is the real test
Structured paid orders should reduce call bottlenecks during busy windows. The site should not promise automation it does not have.
The restaurant keeps the relationship
This is a merchant-aligned direct channel, not a marketplace handoff where the shop loses the customer touchpoint.
Built for pickup, not delivery
V1 is focused on takeout and pickup flow. It does not sell itself as a delivery network.
Setup stays lightweight
The goal is a practical starting point with setup, payments, and QR rollout, not a long custom implementation project.
What merchants get now
A focused V1 that solves the first problem clearly.
Start with the ordering flow that matters most for takeout, then expand later from a stable base.
What merchants get
- A direct QR and web ordering flow for pickup
- Mobile-friendly customer checkout
- Prepaid checkout with card-first default
- Order notes, pickup timing, and status handling
- A merchant setup path with storefront review and QR kit support
- A direct channel the restaurant controls
This is not promising everything at once.
Clear boundaries make the rollout easier to trust, especially for a first-time merchant visitor.
- No delivery marketplace or dispatch network
- No promise of replacing an existing POS on day one
- No heavy custom hardware install
- No customer ordering app built in this repo
- No broad AI or voice-ordering promise as the main launch story
Merchant FAQ
Practical answers before you commit.
The point is to reduce reasons to hesitate, not hide them behind generic sales copy.
Will this create extra work for me?
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
Do I need new hardware?
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
What happens during rush hours?
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.
Do I lose control of my customer relationship?
No. The direct ordering surface stays aligned with the restaurant, so the customer relationship does not default to a marketplace middleman.
Is this for delivery or takeout?
V1 is for pickup and takeout. That narrow scope is deliberate so the product can solve the first operational problem clearly.
Source: Vision
How complicated is setup?
The intended setup path is lightweight: create the owner account, set up the shop, connect payments, review the storefront, and start sharing the QR code.
The current merchant routes already define signup, Launchpad, workspace, and QR Kit boundaries.
Source: AGENTS merchant routes + QR Kit
Current public evidence
Use the named pilot carefully, not as theater.
The public site can name the current pilot context and current rollout posture, but it should not imply approved metrics or storefront screenshots that do not exist yet.
evidence pending
Public pilot evidence is still limited on purpose.
The current named merchant focus is Au Comptoir a Patons in Lyon. Public metrics and merchant-ready screenshots are not published yet, so this page stays grounded in setup clarity and current scope.
The current public merchant focus is Au Comptoir a Patons in Lyon, France.
Source: README + AGENTS
Card is the default launch path today, with pickup-first scope and merchant-configurable rails.
Source: Vision + 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
Focused first rollout
The first goal is a direct prepaid pickup flow that merchants can actually test in the shop.
Evidence-first public story
The site should stay credible by using source-backed facts and setup clarity until richer approved evidence exists.
Merchant-first control
The restaurant keeps pickup timing, status handling, and a direct customer-facing ordering path.
Ready when you are
Want to see if Pizza x402 fits your shop?
Start setup when you are ready. If you want to talk through your current pickup flow first, use the contact page.