From setup to service
How OvenShift works for pizza popups
See how a pizza service moves from a menu and pickup window to a clear list of orders for the team.
OvenShift is in development and general access is not open yet.
One simple rhythm
Plan the service before the orders arrive.
OvenShift is being built for independent pizza popups that sell a limited menu for a specific night. The planned workflow brings the service date, menu, pickup times, and order list into one place.
In this guide, a drop means one service with a date, a menu, and a pickup window. The exact screens and availability will be validated as OvenShift moves through early access.
The operator workflow
From Friday idea to ready for orders.
-
1
Set up the service
Start with the details customers need: the service date, pickup location, pickup window, and ordering deadline. A clear service gives the team a shared starting point before the link goes out.
-
2
Add the menu and limits
Add the pizzas available for that service, then decide how many orders the team can handle in each pickup period. Keep item availability and pickup capacity separate: one limits what can be ordered, the other spreads arrivals across the evening.
-
3
Share one ordering link
Share the service link wherever customers already find the popup. The intended customer flow is a mobile-friendly ordering page without a required customer account.
-
4
Prepare from the pickup view
Work from orders grouped by pickup time so the next batch is visible. The service team can use the list to see customers, items, notes, and status together instead of reconciling separate messages and sheets.
The customer workflow
A short path from menu to pickup time.
- Open the link The customer lands on the service menu from a shared popup link.
- Choose the order They select the available pizzas and provide the order details requested by the service.
- Select an available time Pickup periods show the remaining room for the service as capacity changes.
- Confirm the pickup The customer receives the order and pickup information supported by the final product.
Payment, confirmation channels, and changes after submission are still part of the product details to validate during early access. This page will be updated when those behaviors are confirmed.
A concrete example
A calmer Friday night starts before Friday.
Friday pizza service
The operator sets the service date, publishes a limited menu, and opens pickup periods from 17:00 to 20:00.
See what is next
Orders stay connected to their pickup periods, giving the team a clearer view of the next batch to prepare and hand over.
Questions operators ask
What to know before early access.
- Who is OvenShift for?
- It starts with independent pizza popups and small teams selling food in batches for a specific service.
- Do customers need an account?
- The planned customer flow is designed around a simple ordering link and no required customer account.
- Is OvenShift available now?
- OvenShift is in development. General access is not open yet; contact us if you want to share how your popup works.
Have a real service to plan?