Pizza Shop POS Setup: From Unboxing to First Order
Quick Answer: A pizza shop POS setup should begin with station mapping, then menu structure, taxes, payments, printers, KDS routing, online ordering, driver workflow, user permissions, backups, and training. Hardware first is the wrong order; workflow first prevents rework.
Step-by-step guide to setting up your pizza POS system in a single afternoon.
DC
David Chen
Restaurant Technology Advisor · March 20, 2026 · 10 min read
This setup guide is for owners opening a new pizzeria or replacing a register that no longer fits pizza operations. The goal is not simply to plug in terminals. The goal is to make every order travel cleanly from customer to kitchen to payment to reporting.
A good setup mirrors your floor: counter, phone, make line, oven, cut table, pickup shelf, delivery dispatch, manager office, and back-office reporting. Each station needs the right screen, printer, permissions, and fallback plan.
Why Setup Order Matters
Many POS problems start on day one because the menu, devices, and permissions were configured in the wrong sequence. If toppings are entered before sizes, or delivery zones before prep rules, staff end up with duplicate buttons, handwritten notes, and confusing closeout reports.
Menu structure: sizes, crusts, sauces, toppings, and specials must be clean before training.
Kitchen routing: tickets should reach the right station without the cashier choosing manually.
Payment flow: card, cash, gift card, house account, and split tender need testing.
Fallback: printed menus, backup printer paths, and offline card rules should be ready before go-live.
Setup Principles
Map the restaurant before devices
Draw the route an order takes through the shop. That map tells you where terminals, printers, bump screens, and customer displays belong.
Build the menu as rules, not buttons
Pizza menus should be built from reusable size, crust, topping, and modifier logic. Copying dozens of one-off buttons makes maintenance painful.
Test closeout on day one
Before staff training, run fake cash, card, refund, void, gift card, online, and delivery orders. A setup is not complete until the owner can close the day and trust the report.
Setup Checklist
Setup area
Required decision
Evidence it works
Menu
Sizes, crusts, toppings, combos, coupons
Common orders ring without manager help
Kitchen
Printer/KDS routing by item and station
Make-line and cut-table instructions are readable
Payments
Taxes, tips, surcharges, refunds, gift cards
Test batch and closeout reconcile cleanly
Staff
Roles, PINs, permissions, training drills
New cashier can ring top orders from memory
Step-by-Step Setup
Document the floor: list stations, devices, printers, drawers, displays, and network drops.
Build the menu model: enter categories, sizes, crusts, toppings, modifiers, fees, and coupons.
Configure order channels: counter, phone, direct online, third-party, pickup, delivery, and future catering.
Route tickets: send each item to the correct station and confirm the wording is usable in a rush.
Test money movement: run training transactions for every tender and adjustment type.
Train by shift: practice with lunch, dinner, close, delivery, and refund scenarios.
Setup Scenario
A new slice-and-delivery shop avoided its first-week chaos by testing the menu before installing every screen. The owner discovered that lunch combos, slice reheats, and whole-pie delivery needed different routing. Fixing those rules during setup meant the first real shift used clear buttons and station-specific tickets instead of notes taped to the terminal.
Setup Mistakes to Avoid
Letting the installer invent your menu. The owner should approve every category, modifier, and coupon.
Skipping printer failover. Know where tickets go if the make-line printer or KDS fails.
Using one staff role for everyone. Cashiers, shift leads, drivers, and managers need different permissions.
Training on simple orders only. Staff should practice mistakes, refunds, split payments, and delayed orders.
Waiting to check reports. Closeout, tax, payroll, and delivery reports must be reviewed before opening day.
Prep-time controls: separate pickup promises from delivery promises when the oven is backed up.
Inventory hooks: connect high-cost toppings and dough counts early, even if full inventory comes later.
Audit reports: turn on void, refund, no-sale, drawer, and discount tracking from the start.
Getting Started
Start with a one-page restaurant map and a copy of your actual menu. Mark every item that needs a special rule: size, half topping, coupon, timed pickup, delivery fee, tax rule, or kitchen route. That list becomes the setup checklist.
Before launch, run a mock Friday night with staff. If the system handles those orders cleanly, the real shift becomes training, not discovery.
Upgrade to KwickOS
The complete restaurant technology platform — POS, reservations, delivery, payments, and more.