Connect Square from Settings and takings arrive every half hour. Eight weeks of them make a forecast for each site. Four weeks make an hour-by-hour picture of demand under every day on the rota, drawn from up to thirteen.
Four places the takings show up, none of which you have to type into
Up to thirteen weeks of takings become a strip of colour under each day on the rota, hour by hour, darker where the site is busiest. Shifts sit on top of it, so a gap at seven on a Friday is visible before it is a problem. Ask Paddy to suggest a week and it drafts one against the same band. Nothing publishes until you say so.
When you set the time on a check, the routine editor points out the quiet windows in that site's day. When a task is missed, the record says whether it fell in the busiest hour. It stops a fridge check being scheduled for the middle of the lunch rush and then blamed on the person who was serving.
A published shift with nobody on it is already flagged 48 hours out. With the till connected the alert is weighted by what that hour is expected to take, so an empty Friday bar shift at seven is louder than an empty Tuesday at three, and the message says which hour and why.
Once a site has eight weeks of daily takings, a forecast builds overnight: an expected figure and a likely range for each of the next 14 days, from the site's own history, the calendar and the weather. It tells you how accurate it has been, and it says no when it does not have enough to go on.
Five steps, one of which is waiting
The account owner opens Settings > Integrations and presses Connect Square. Square asks them to sign in and approve. Nobody else in the business can start this, because a till gives access to every site's takings.
Square lists its locations and you pick which Paddl site each one feeds. A location you leave unmapped is ignored. One Square location per site.
The last thirteen months of completed orders come in behind the scenes. You can carry on working; the Integrations page shows when the history is complete.
From then on each day fills in through service. A day keeps settling for three days, because a till that was offline can send its orders late, and Paddl marks it as settling until then.
At eight weeks of daily takings a site gets its forecast. At four weeks of till takings the demand band appears under the rota. With Square's history both usually arrive the first night, and both rebuild every night from whatever came in that day.
Grouped by what the connection feeds. Status pills mean what they say.
Square is live. The others are on the list, and the form below is how you tell us which one matters to you.
Connected by the account owner from Settings > Integrations. Every completed order from each mapped Square location comes into Paddl, including the last thirteen months, so a forecast has history to work from on the first night.
Common in pubs and cafés. Not connected yet. Ask for it below and you will hear from us when it is.
Card readers and a till app used by small sites, kiosks and pop-ups. Not connected yet.
A UK till found in a lot of independent restaurants and bars. Not connected yet.
A restaurant till used by larger sites and groups. Not connected yet.
Till hardware from Fiserv, often supplied through a bank. Not connected yet.
A UK hospitality till with a strong footing in pubs and multi-site groups. Not connected yet.
A restaurant till that has been arriving in the UK. Not connected yet.
Reviews come in, are read for sentiment and for anything that looks like a food safety or licensing complaint, and are matched to who was on shift.
Reviews come in from TripAdvisor, are read for sentiment and anything that looks like a food safety or licensing complaint, and are lined up against who was on shift that day.
Shows up inReputation
Reviews from your Google listing, read the same way as TripAdvisor and matched to who was on shift.
Shows up inReputation
Ratings and comments left on Deliveroo orders, read the same way as other reviews. Being built.
Shows up inReputation
Bookings would tell the demand band about tomorrow before the till can. None connected yet.
Bookings would tell the demand band about tomorrow before the till can. Not started; tell us if this is your system.
Shows up inRota
Bookings would tell the demand band about tomorrow before the till can. Not started; tell us if this is your system.
Shows up inRota
Bookings would tell the demand band about tomorrow before the till can. Not started; tell us if this is your system.
Shows up inRota
Delivery orders counted as takings, so a busy night on the apps shows up as a busy night on the rota.
Delivery orders counted as takings alongside the till, so a Friday of deliveries is not a quiet Friday on the rota. Not started.
Shows up inRota
Delivery orders counted as takings alongside the till. Not started.
Shows up inRota
Delivery orders counted as takings alongside the till. Not started.
Shows up inRota
Paddl already exports approved hours in these formats. A direct connection would send them without the download.
Paddl already writes a BrightPay file from approved timesheets. A direct connection that sends the hours without a download is on request.
Shows up inRota
Paddl already writes a Xero Payroll file from approved timesheets. A direct connection that sends the hours without a download is on request.
Shows up inRota
Paddl already writes a Sage Payroll file from approved timesheets. A direct connection that sends the hours without a download is on request.
Shows up inRota
Tell us which till you use and how many sites run it. That list helps decide which till we build next, and you will hear from us when yours is ready, not before.
Completed orders: the time, the net amount after refunds, the order count and the card or cash split, per Square location. That is enough to build takings by the half hour and nothing more. It reads the last thirteen months when you connect and every half hour after that.
Only the account owner can connect or disconnect a till. Sales figures and the forecast are owner-only until the owner turns them on for managers under Settings > Sales, and even then a manager sees only the sites they manage. Labour cost has its own switch under Settings > Labour cost. Staff never see takings.
No card numbers, no customer names or contact details, and nothing from Square that is not a completed order. Paddl does not write anything back: it cannot create, change or refund an order, and it cannot touch your Square settings.
Press Disconnect on the Integrations page. Takings already pulled stay in Paddl, because they are your history and the forecast keeps working from them. Nothing new arrives until you reconnect. If access is removed from the Square side instead, Paddl shows the connection as revoked and raises a Till disconnected alert, so it is never a silent stop.
Yes. Each Square location is mapped to one Paddl site, and everything downstream is per site: the forecast, the demand band, the labour figure and the alerts. A site with no mapped location carries on with entered or imported takings. One Paddl site cannot take feeds from two Square locations.
It tells you. Once a site has enough history the forecast page shows "typically within N%", measured by forecasting six past weeks the site already knows the answer to and comparing. The figure is per site and moves as the site does. Before it has been measured the page says so rather than showing a number, and a site with fewer than eight weeks of daily takings gets no forecast at all.
Start your free 30-day trial, connect Square from Settings, and the history pulls in while you set up the rest. Card required.
Full access to all features · Dedicated onboarding support · Cancel anytime