Pizza shops

Half-and-half pizzas the kitchen can read.

One ticket from cart to cut table. Per-side toppings, four-quarter builds and driver dispatch all carry through, so the box matches the order and leaves while the cheese is still hot.

Specials

Half / Half

Gluten Free

Left half

Pepperoni · hot honey

Right half

Margherita · basil

Select a size

SmallMediumLargeFamilyKing
Add to Order$31

Higher-half pricedautomatically · fires as one ticket

Split builds

Half / half, four-quarter, higher-half rule on the same ticket.

Tap whole, half / half or four-quarter. The pizza, the POS total and the kitchen docket update together so owners see how pricing and prep stay in sync across every order channel.

PIZZA HQ

Collins St · Friday · 7:04 PM

Order #4412Web
1× LG HALF / HALF
L · Margherita
R · Funghi
+ bacon (Funghi side)
Higher-half base$28.00
Bacon · Funghi side$3.00
TOTAL$31.00

Promised by 7:32 PM· +2 min split

Kitchen station 1 · printed at 7:04 PM

Toppings, removals and size-aware extras that protect food cost

Pizza margin leaks in small increments: extra cheese on a family pizza, premium meat on half the pizza, removals buried in notes. Structured modifiers and an ingredient library turn those choices into line items the kitchen can execute.

  • Ingredient library with categories your saucing line already uses
  • Default ingredients per pizza so removals mean something on the ticket
  • Size-aware extra pricing (small / medium / family premiums for the same topping)
  • Required modifier groups so half/half cannot submit half empty
  • Kitchen-visible removals (no onion, no olives) on printer and KDS

Worked leak

$19 mushroom pizza, $4 of prawns and double cheese riding for free.

When extras live in notes, staff end up writing them off or discounting after the fact. When extras are modifiers with prices that scale by size, the POS charges before the dough hits the peel. Sales-by-ingredient later names which toppings paid their way and which ones dragged margin, so price changes ride on evidence.

Deals you can run on Tuesday and survive on Wednesday

Bundles and two-for offers only help if margin survives the week. Auto-detect on POS and web applies eligible specials when the order qualifies, and half/half-in-specials stays under your control when premium halves should not count.

Auto-detect

Eligible deals apply at POS and web without staff memory.

Two large traditional pizzas plus garlic bread and a 1.25L drink can price as a family pack the moment the order hits the rule. Staff do not hand-key the discount during the rush, and customers online see the deal without having to enter a voucher code.

  • Manual pause when stock or margin pressure hits mid-service
  • Voucher lookup with redemption tracking for flyer and SMS campaigns
  • Custom label so "Specials" can read as "Deals", "Combos" or "Family Packs"

Half/half-in-specials

Decide whether split pizzas count toward Tuesday two-for.

Leave the toggle on when split pizzas should count. Turn it off when one half is gourmet and you do not want that build inside the promo. Channel-aware specials can push pickup on your site without matching the same offer on a marketplace.

  • Size-aware specials so a large-pizza deal never lands on small items by mistake
  • Deal reporting by item and category so you see lift versus discount-only volume at month end
  • Channel-specific deals so direct pickup wins without giving margin away on a marketplace

Friday dispatch

Oven promise, driver list and guest ETAs on the same screen.

When the queue backs up, you throttle web, stretch prep time for big orders, or pause a marketplace. Guests still see current delivery time that matches what dispatch just set.

Every order on one live orders view

Web, phone, marketplace, counter and dine-in land on one screen with promised times, on the POS tablet. Split builds bump prep so a driver is never handed a box that is still in the oven.

Next Order
All OrdersPickupDeliveryDine-in
Actions
PreparingExpected Time
Search
Katie BellVIP2$62.50
Overdue 12 minsTable 32RESY
Cho Chang$73.25
Due in 2 minsDelivery #5623
Johnny Appleseed$105.10
Due in 10 minsDelivery #4302Web
Romilda Vane$94.60
Due in 13 minsPickup #6452Uber
Lee Jordan$24.40
Due in 22 minsDelivery #9830DoorDash
Collection 20 mins Delivery 45 mins
UpcomingPreparingReadyHistory

Driver list with overflow rules

Own drivers first, partner courier when your drivers are full. Fees, tips and handoff timestamps stay on the ticket for payroll and disputes.

Drivers · Collins StLive

Pickup time

22 min

Delivery time

40 min

  • Alex

    On delivery

    21A Gheringhap St

    En route
  • Sam

    Returning

    Arriving · 10 min

    Returning
  • Priya

    In store

    Waiting · 13 min

    Ready

Order delivered · 602 Mount Waverly Rd

Arrived in store · Jane · ready for delivery

Guest ETA matches what dispatch set

En route updates pull from kitchen handoff and live driver position, not a static footer promise from last month.

Order #4413 · Family meatlovers

Phone · prep bump applied

ETA 7:14
A

Alex · own driver

2 stops left · live position

En route

Illustrative route. Your store uses your zones and driver names.

Throttle

Order throttling per slot

Cap web orders per fifteen-minute slot so the makeline keeps the promised times honest.

Prep bump

Order-value prep time

Add minutes when a large party order lands next to singles, before drivers are assigned.

Zones

Delivery zones + radius pricing

Far drops carry the right fee or fall outside coverage, so far runs do not eat your hour.

Pause

Store online / offline per channel

Pause Uber while the oven is buried without hiding direct ordering on your own site.

Channel economics

Same order, three prices, zero duplicate menus.

You set pickup, delivery and marketplace prices from the same item. Customers see the right number at checkout. You see which channel paid for the labour.

Best margin

Direct web

$39

Average pizza order · pickup

No marketplace fee on this ticket. Push pickup when drivers are thin.

Own delivery

Own delivery

$43

Same order · delivery fee on the ticket

Delivery charge and zone rule attach to the ticket, not a sticky note on the monitor.

Marketplace

Uber Eats

$47

Or DoorDash, Menulog

List price covers the marketplace fee so margin survives the channel.

On a $30,000/month direct pickup channel, the gap between $39 direct and a 30% marketplace cut is ~$9,000/month retained. Illustrative example based on a typical pizza shop volume.

  • Hide a sold-out gourmet pizza on Uber while it still sells for direct pickup, with variant-level sold-out on the topping that ran out.
  • Item availability by channel keeps risky builds off marketplaces while your POS still sells them.
  • Take the store online / offline per channel when the oven is buried, without killing your web channel.
  • Menu and price updates push to Uber Eats, DoorDash and Menulog from one admin save — publish to every marketplace the moment you are ready.

Direct ordering and the regulars who used to call

Branded ordering on your domain, custom DNS, mobile checkout with Apple Pay where configured, scheduled pre-orders for parties, and loyalty enrolment that keeps repeats on a channel you own.

Branded direct ordering

The complex pizza they used to phone in, ordered on your domain.

  • Online half/half and deep modifier flows so guests stop phone-ordering complex pizzas
  • Order review before checkout catches topping mistakes before the oven fires
  • Pickup and delivery toggles with realistic earliest times during the rush
  • Custom closed messaging when you pause a mode without sounding like a dead site

Caller ID to SMS

The phone regular becomes the direct-order regular.

Friday: caller ID matches a regular, you greet by name, their last half/half loads with crust, sauce and both halves. Tuesday: the same mobile gets an SMS dinner offer; they reorder on your site and the full build replays with their saved card on file. Loyalty points earn on spend you configure, redemptions run at the POS without a second queue, and branded loyalty keeps the programme under your shop name.

Reporting that names the leak

Pizza owners need more than nightly sales totals. These reports answer the questions you ask after service, by name.

Sales-by-size

Which size pays?

Volume and revenue per small, medium, large and family so you stop underpricing family extras and start designing deals around the sizes customers buy.

Sales-by-ingredient

Which topping is bleeding margin?

Topping usage tied to price so prawns, double cheese and premium meats show their real cost across thousands of split builds.

Suburbs report

Which suburb earns the next driver?

Suburb-level volume and fees so you tune zones, fees and marketing on evidence, not guesswork on the wall map.

We have run our pizza business on Next Order for years. Great value and great service, with the attention to detail and professionalism you want behind a busy kitchen.

MP
Margaret Preston
Pizza restaurant · Australia
Google

Frequently asked questions

What operators ask us before they sign.

    • How does half/half pricing work? Do I lose money on the cheap side?

      You set the rule in admin. The higher-half rule prices the pizza at the more expensive half, then extras attach to the side that earned them. Worked example: a half-and-half at the higher base, with bacon added only to the Funghi side bumping that half (not the whole pizza) by the bacon modifier price. The POS shows the customer-facing breakdown; the kitchen docket names each side so saucing stays honest.

    • Can deals apply automatically to half/half builds?

      Yes. Auto-detect on POS and auto-detect on web can apply eligible specials when the order meets your rules, so staff are not memorising Tuesday bundles during the rush. Half/half-in-specials is a toggle: leave it on when split pizzas should count toward a two-for, or turn it off when one half carries premium toppings you do not want inside the deal. Channel-aware specials can run on direct pickup without giving the same margin away on a marketplace.

    • Do drivers see marketplace orders next to direct orders?

      Third-party orders can land in the same operational queue as web, phone and counter, with channel labels on each ticket. Dispatch works off the same driver board and the same status rail the kitchen pushed. Current delivery time per integration can be extended when the oven is buried, and store online/offline per marketplace stops new third-party tickets without hiding your direct channel.

    • What happens to a regular's saved build when a topping is sold out?

      Variant-level sold-out marks the topping unavailable without hiding the whole pizza, so you keep selling the item on the halves that still work. Channel-specific sold-outs can remove a gourmet line from Uber while it still sells for pickup on your site. Default ingredients per item mean removals like no onion stay structured, and the guest sees what changed before they pay.

    • How fast can I push a price change to every marketplace?

      Direct ordering picks up admin saves within seconds. Most marketplace integrations update automatically, but each one still processes the change on its side, so allow a short window for the public menu to match yours. Some integrations need one button push from admin when you are ready to publish the catalogue change. Admin shows status per channel so managers know when each channel is updated.

Walk your menu on a Friday-night timeline

Bring a split build, a marketplace price bump and a driver shortage. We will run POS, web, dispatch and loyalty in one pass.