Toast Pulseone short weekday brief across every store

Numbers on this page come from the agent that built and runs the routine, which re-checked them against its own files on 2026-10-28. They are not independently audited.

Problem

One POS (Toast), many locations. Nobody opens every dashboard every morning. A store down 30% on a weekend, delivery prices drifting from in-store prices, or a pile of comps and voids with no reason only showed up days later, if at all. The goal: one short weekday brief that stays silent when nothing is wrong.

Stack

• A read-only Toast connector: store sales summaries, an operations overview, menu price audits, cross-store comparisons.
• A read-only Toast web session for voids, comps and discounts, which the connector does not expose.
• Later, the Toast API with read-only credentials for order-level data.
• Email, to send a daily note to the owner’s team.
• A small hosted dashboard, redeployed each morning.
• A scheduled routine, weekdays at 8:00 AM local, with some timing flexibility.

Steps

1. Pull yesterday’s numbers for every store. Compare to the same weekday last week and the week before.
2. Convert to a trustworthy net sales figure (see Misfires).
3. Check delivery-app price markup and cross-store menu price drift. Mondays only: a config parity check across stores.
4. Pull voids, comps and discounts from the web session, with reasons and approvers.
5. Archive the day’s digest as a markdown file and redeploy the dashboard.
6. Apply thresholds. A big swing, a price drift, a config mismatch or an outage becomes a one-line escalation. A clean day sends nothing.
7. Write the daily note to the owner’s team: why each store moved, and which exceptions are worth a look.

Real numbers

Source for every number below: the owning agent’s build summary and its corrections, 2026-10-28. Not independently verified.

• Every store in the group is covered by one routine.
• The connector’s raw “net sales” ran about 16 to 22% too high, because it includes tips and gratuity.
• The fix: derive net from tax. Net equals the tax collected divided by the sales tax rate, and the rate is checked per store before it is trusted.
• One night’s order count came out as 265 by one method and 277 by another.

Time before and after

• Now: the routine runs unattended on weekday mornings and the owner reads a short brief. A clean day sends nothing.
• By hand: nobody timed it, so no time-saved figure is claimed.
• Escalation counts were not tracked as a metric, so none are quoted.

Misfires

• Overstated sales. Early digests used the connector’s net and ran high until the owner caught it. Every digest before the fix was overstated. The tax rule now lives in a shared note every agent reads.
• Unverified tax rates. A store’s tax rate is labeled “unverified” until it is proven from order-level data.
• Order counts differ by method. A business-date pull and a modified-time pull disagreed, so some figures are labeled approximate.
• Redundant recaps. Toast already emails sales totals, so the daily note now covers only reasons and exceptions.
• No voids or comps in the connector. It needs a signed-in web session. When the session expired, voids went out as a same-day follow-up.
• Noise. The first versions reported daily. Escalate-only-on-threshold made the brief worth reading.
• Hidden gaps. The connector has no item mix, covers or close report. They are marked unavailable rather than guessed.

Copy-paste template

Routine prompt:

Every weekday morning, pull yesterday's Toast data for every store, compute net sales the approved way, compare to the same weekday last week, check delivery markup and price drift, archive the digest, refresh the dashboard, and escalate only if a threshold is crossed. Stay quiet if everything is clean. Read-only: never change anything in Toast.

Daily note prompt:

Write a short, warm note covering every store. Don't repeat sales totals, because Toast already emails those. Explain why each store moved, and list any voids, discounts or comps worth a look.

Rules to keep: read-only everywhere, nothing published without the owner’s yes, no wages or guest personal information. Validate every metric against a source you trust before it goes in a report. Keep “quiet when clean” a hard rule. Write the net sales formula in one shared file.

What’s next

• Time one manual morning and one routine run, to replace the rough figures.
• Start tracking escalations (count and how many were real) so a number can be shared later.

Live link or demo

No public live link. The recorded demo at the top of this page shows it end to end. Screen recording of the dashboard fed made-up sample stores and concepts. 31 seconds, no sound.