Daily sales summary
By Toolspoke
Totals the day's Square sales per location every evening, compares with last week and posts the top items and refunds to Slack.
Needs a Toolspoke account. You choose which project it installs into.
- Square + Slack
- Required integrations
- Runs on a schedule
- Every day at 9pm by default
- Post one message
- What its last step does
- Some actions can delete
- 3 of 39 actions in its tools
On this page
The short version
- What it is
- A ready-made Toolspoke agent that tells you each evening how the day went at every Square location.
- What it reads
- The day's payments, completed orders and refunds at each location, and the same weekday last week.
- Where it posts
- One Slack channel, chosen when you set it up.
- What it reports
- Gross sales, number of payments and average sale per location, the change from last week, the top five items and the refunds.
- How often
- Every day at 9pm once you switch it on.
- What it never does
- Refund, cancel or change a payment, or post a buyer's details.
- What you need
- A Toolspoke account, a Square access token and a Slack workspace.
What Daily sales summary will never do
Daily sales summary is told never to refund, cancel or change a payment, and never to post a buyer's details. It counts, and a person acts.
Daily sales summary will never
- Refund, cancel or change a payment.
- Create or change a customer, an item or an order.
- Post a buyer's name, email address, phone number or card details to Slack.
- Add two currencies together.
Why it never refunds
A refund moves money back to a buyer and cannot be undone. It belongs to the person who spoke to the customer, not to a report.
What it keeps out of Slack
A sales channel is often read by the whole team. The post has totals and item names, and nothing that identifies a buyer.
Why you may still want a lock
No instruction is a perfect lock, and a Square token can refund. Allow this agent Square reads only, and refunding is impossible for it.
These are written into Daily sales summary's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
Daily sales summary reads Square and posts one message. Every refund and every cancelled payment is a person's.
What Daily sales summary does
Daily sales summary is an AI agent that reads Square every evening, totals the day for each location, compares it with the same weekday last week and posts one Slack message with the top items and refunds.
Most shop and cafe owners find out how the day went by opening the Square dashboard on their phone, one location at a time, and comparing it with a week they half remember.
Daily sales summary does the comparing. For each location it totals the day's completed payments, adds up what sold from the orders, reads the refunds, and puts the same hours of the same weekday last week beside it.
It only reads and reports. It is told never to refund or cancel a payment, and you can allow it Square reads only, so it cannot.
In practice, every evening at 9pm you get:
- Gross sales, payments and average sale for each location
- The change from the same weekday last week, as a percentage
- The five best selling items by amount
- The day's refunds, with the largest and its reason
How it works
Daily sales summary works in four steps each evening: it reads your locations, totals the day, compares it with last week and posts one message. All of it comes from the agent's written instructions, which you can read and edit after you install it.
Step 1: Read the locations
Each location's timezone fixes where its day starts.
Step 2: Total the day
Payments, completed orders and refunds since midnight.
Step 3: Compare with last week
The same weekday, over the same hours.
Step 4: Post one message
A line per location, then top items and refunds.
It counts the day in each location's time
It reads list_locations first. A location's day runs from midnight in its own timezone to the time of the run, so two shops in different cities are each counted fairly.
It adds up what sold
It reads completed orders with search_orders and adds up quantity and amount per item name, keeping the top five. Payments come from list_payments and refunds from list_refunds.
It compares like with like
A Thursday is compared with last Thursday over the same hours, not with yesterday. Weekdays and weekends sell differently, and the comparison should not hide that.
It keeps buyers out of Slack
The post has totals and item names only, never a buyer's name, email address, phone number or card. The limits are listed under what it will never do.
What an evening message looks like
A message from Daily sales summary is a single Slack post: a line per location, then the top items, then refunds, then the total.
Copper Kettle
Channels
- # daily-sales
- # ops
- # rota
- # general
# daily-sales
Thursday 22 October, midnight to 9 PM at each location.
Locations
- Harbour Street, 4,982.50 USD, 238 payments, average 20.93. Up 15% on last Thursday.
- Station Road, 3,106.20 USD, 174 payments, average 17.85. Down 4% on last Thursday.
Top items
- Flat white, 186 sold, 744.00.
- Almond croissant, 121 sold, 508.20.
- Breakfast bap, 64 sold, 448.00.
Refunds and total
3 refunds, 41.70 USD. Largest 18.50 at Station Road, reason recorded: wrong order. Total 8,088.70 USD, up 7%.
- Locations
Each location's day, with the change from last week, so a quiet shop stands out the same evening.
- Top items
The five items that brought in the most, across all locations, with quantity and amount.
- Refunds and total
How many refunds, how much, and the largest with the reason Square recorded. Then the day's total.
Why it posts every day
A daily summary is only useful if it is daily, so the agent posts every evening. A location that took no payments gets one line saying so, rather than being left out.
If Square cannot be read, it posts that once, so a missing summary is never mistaken for a day with no sales.
Who uses Daily sales summary
Daily sales summary suits any business that takes payments through Square at one or more locations. The examples use made-up names.
A cafe owner with two sites
Nadia Haddad runs two cafes and works in one of them. The evening post tells her how the other did without a phone call.
An area manager comparing shops
Owen Davies looks after four shops. The line per location, with the change from last week, shows him where to visit tomorrow.
A head chef planning prep
Maya Lindqvist uses the top items to plan the next morning's prep. When the croissants sell out by noon, the numbers say so.
An owner watching refunds
Carlos Mendes wants to know when refunds are creeping up. The largest refund and its reason are in the same post every night.
What Daily sales summary connects to
Daily sales summary connects to two tools: it reads Square and posts to Slack. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.
Square
RequiredRead payments, orders, customers, the catalog, inventory and invoices, and issue refunds.
Authentication: Access token
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
| Tool | What Daily sales summary does | What it cannot do |
|---|---|---|
| Square | Reads locations, payments, orders and refunds (list_locations, list_payments, search_orders, list_refunds). | Change an item or an order: the connector has no action for either. It can refund or cancel a payment and create a customer, and this agent's instructions forbid all three. |
| Slack | Posts one message with send_message, to a channel. | Delete messages: the connector has no delete action. |
A Square access token carries every permission of the account, so the connection itself can refund. Daily sales summary is told never to, and that is an instruction. To make it a lock, allow this agent Square reads only in your project: refunding and cancelling are destructive actions and creating a customer is a write, so none of them is reachable. The access control guide explains how.
The activity log records each call, but Square payment and order reads keep only that the call happened. The message posted to Slack is stored.
When Daily sales summary runs
Daily sales summary runs every day at 9pm, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.
- Each run counts from midnight at each location to the time of the run.
- It compares with the same weekday last week, over the same hours.
- A location with no payments gets one line, not silence.
- If Square cannot be read, it posts that once.
Each run uses model credit from your workspace balance, so it makes seven runs a week. The Square and Slack calls themselves are free.
Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, change the time (later if you close late) and edit its instructions. The agent's page lists recent runs and their cost.
How to set up Daily sales summary
To get the day's sales every evening, add Daily sales summary to a Toolspoke project, connect Square and Slack, allow Square reads only and switch on the schedule. It takes a few minutes, and nothing runs until the last step.
Step 1: Create a Toolspoke account or sign in
Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.
Step 2: Add it to a project
Pick the project it should live in. You get your own editable copy, and you can see the two tools it brings before anything connects.
Step 3: Connect Square
In the Square Developer Console, copy your application's production access token and paste it. It is stored encrypted and the agent never sees it.
Step 4: Allow Square reads only
In the project's access settings, allow this agent reads only on Square, so refunding and cancelling are out of reach.
Step 5: Connect Slack
Choose Sign in with Slack and approve the Toolspoke app. For a private channel, add the Toolspoke bot to it first.
Step 6: Choose the channel
Name the channel in the instructions, and any locations to leave out.
Step 7: Switch on the schedule
The schedule arrives switched off. Run it once to see a message, then switch it on.
Make Daily sales summary fit your business
Daily sales summary's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.
Paste any sentence below into the builder chat, or say the same thing in your own words.
Run every day at 11pm instead of 9pm.
This changes when the agent wakes up, so the builder edits its schedule, not the instructions.
List the top ten items, not five.
Mention @nadia if any location is more than 20% down on last week.
Compare with the average of the same weekday over the last four weeks.
Only report on Harbour Street.
None of these edits needs more access or touches the Never rules. They change what Daily sales summary is told, not what the connections allow.
How it compares to other options
Daily sales summary beats the alternatives when you want every location's day, the comparison with last week and the top items in one message, and loses to them when you want live numbers during the day.
| Compared on | Daily sales summary | Square's dashboard | Square's daily email | Adding it up yourself |
|---|---|---|---|---|
| Every location in one message | Yes | One view at a time | Depends on settings | If you do it |
| Compared with the same weekday last week | Yes, same hours | If you set the range | Sometimes | If you keep notes |
| Arrives where the team talks | Yes, in Slack | No | Email only | No |
| Live during the day | No, once each evening | Yes | No | No |
| Can refund a payment | Told not to; allow reads only | Yes | No | Up to you |
| Setup effort | Connect two accounts | None | A setting | Every evening |
Square's dashboard is the better choice when you want to watch sales as they happen. Daily sales summary is one considered message at the end of the day.
Square's own emailed reports are fine for one location and one person. Daily sales summary suits a team that wants every site side by side, in Slack, with last week next to it.
Frequently asked questions
Can Daily sales summary refund a payment?
It is told never to. A Square token can refund, so allow this agent Square reads only in your project if you want that enforced (how access works).
Which hours does it count?
From midnight in each location's own timezone to the time of the run, 9pm by default. Last week's figure covers the same hours.
Does it handle more than one location?
Yes. Each location gets its own line, then a total across them in each currency.
What if I close after 9pm?
Tell the builder to run it after you close. Sales after the run time are not counted in that day's summary, so a 9pm run misses a late evening.
Does it post customer details to Slack?
No. It reports totals and item names only, never a buyer's name, email, phone number or card.
Where do the top items come from?
From the line items of the day's completed orders, added up by item name across all locations.
Is Daily sales summary free?
It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.
Know how the day went before you lock up
Connect Square and Slack, allow Square reads only, choose the channel and switch on the schedule. Your first summary lands tonight at 9pm.