Skip to content

Industries · Food and beverage

Payments for pizzerias, from the oven queue to the driver settlement

A pizzeria is two businesses sharing one make table. One of them ends at a counter and the other ends in somebody's driveway, and the second one is where the accounting gets interesting.

The night, end to end

What a delivery night asks of the system

Six places a pizzeria's software either helps or gets in the way.

Toppings with a placement and a portion

Left, right, quarter, double on one side. On a pizza POS that is one readable line. On a general restaurant POS it becomes modifier items the make table has to interpret.

The oven queue sets the promise

A flat quote at six and the same flat quote at nine is a guess made twice. The queue already knows the answer if the system is asked to use it.

Dispatch that records who took what

A clipboard works until a driver takes four runs and comes back with three receipts. Dispatch in the POS makes the shift settle itself.

Zones drawn as polygons

A radius includes the far side of the interstate and excludes the street you have delivered to for nine years. Polygons are the difference between the map and the drive.

Caller ID against the order history

The regular who orders the same thing every Friday should not be asked for their address again. That is thirty seconds a call in a business where the phone never stops.

Dough par against tomorrow

Dough made today is sold tomorrow, so the par is a forecast. Sales history by day and weather-shaped Fridays are the inputs, and most systems already hold the first one.

Buying guide

Before you sign anything for a delivery store

Seven questions worth asking any provider, us included.

  1. Build a half-and-half with a double topping in the demo.

    Then read the ticket the make table would read. That single test separates a pizza POS from a restaurant POS.

  2. Where does the promise time come from?

    Ask whether it reads the oven queue or a setting. If it is a setting, you will be adjusting it by hand all night.

  3. Can zones be drawn as polygons, and who can redraw them?

    A manager should be able to change a boundary on a Friday without a support ticket.

  4. How does the system record dispatch and driver return?

    Ask to see a shift settled, including one cash run and one card run.

  5. Which third-party channels inject into your ticket stream?

    Get the list by name and by market. This is the biggest accuracy fix available to most stores.

  6. Does caller ID match to history, and how far back?

    Ask what happens when a regular calls from a new number.

  7. What is the export when you leave?

    Customer addresses and order history are the asset here. Ask for the format up front.

Questions

Pizzeria questions we get asked most

Can toppings be applied to one half or one quarter of a pizza?

On a POS built for pizza, yes: the topping carries a placement and a portion, so left, right and quarter builds print as one line the maker can read. On a general restaurant POS it is usually done with separate modifier items, which works at the register and produces a ticket the make table has to interpret. Ask to see a half-and-half with a double topping on one side.

How is a promise time calculated when the oven is already full?

From the oven queue, not from a fixed number. Each order carries a make time and a bake time, the queue holds what is already in and ahead, and the promise is the sum plus the drive. A store quoting a flat forty-five minutes at both six o'clock and nine o'clock is quoting a guess twice a night.

How do drivers settle at the end of a shift?

Against what was dispatched to them. The driver takes out orders with known totals, brings back cash for the cash ones, and the card ones were already captured. Settlement is the difference, plus whatever your mileage reimbursement policy pays. What makes this clean is dispatch recording which orders left with which driver at what time, which is a POS function and not a clipboard.

Are delivery zones drawn by radius or by street?

A radius is a circle and a delivery area is not. Polygon zones let you exclude the far side of a highway, follow a river, and stop at a boundary a driver actually cannot cross quickly. If your system only supports a radius, the workaround is a shorter radius, which costs you the streets you could have served.

Do third-party delivery orders have to be re-keyed into the register?

Not where injection is available for that channel and that POS version. Injection puts the order into the same ticket stream as a phone order, so the make table works one queue and the sales report has one total. Where injection is not available, the tablet stays and the re-keying stays with it, which is worth knowing before you sign rather than after.

Talk to someone who has worked a make table

Tell us about your store

Four fields. A person reads it, looks at what you are running now, and comes back with what they would actually change.

The promise

We will implement whatever is right for you — including keeping what you have. If your dispatch board works and the only real gap is one channel that still lives on a tablet, we will fix that one thing and leave the rest alone.

Payco · Industries · Food and beverage · Pizzeria

Two free tools, before you talk to anybody

Both are open to anyone, and both can be done between the lunch and dinner rushes.

Last updated: 2026-08-17