Skip to main content

Introducing Loss Radar: see which shift cost you money.Learn more

All posts

StationPro playbook

Field-tested workflow
Operator review
9 minute read
Playbooks9 min readPublished

Multi-store gas station reporting: what owners should review every morning.

A ten-minute morning routine for multi-store owners: portfolio sales, EOD compliance per store, top variance events, lottery exceptions, fuel margin band per grade. With a per-store ranking framework and what should trigger a follow-up.

Written by
StationPro Editorial
Reviewed by
StationPro operator team

What multi-store reporting should give an owner

Multi-store reporting isn't a 60-page PDF. It's the answer to one question every morning: which stores are running normally, and which one needs my attention today. The right answer fits on a phone screen with one line per store.

The discipline is comparing each store to its own baseline first, then peer-comparing. A high-volume urban store and a low-volume rural store have different "normal." A $50 cash variance is noise at one and signal at the other. Peer comparison after baseline comparison is the right order.

≈10 minutes
Multi-store morning review when nothing flagged
One line per store on a phone screen. 30+ minutes only when an investigation is needed.

The seven-item morning review

1. Yesterday's sales by store

Total sales per store vs. the store's same-day-of-week average for the prior month. A 15% drop at one store on a non-holiday day is a flag. A 15% rise might be a flag too if it's out of pattern.

2. EOD compliance per store

Which stores closed yesterday with under-tolerance variance? Which had an over-tolerance variance with a reason code? Which never closed (missed EOD)? Missed closes are the highest-priority signal: either the clerk left without closing, or the close failed and nobody noticed.

3. Cash variance per store

Variance amount, reason code, on-shift clerk. Above the warning band, this should already have generated an SMS to the owner last night, the morning review is the second pass. Look for patterns: same clerk multiple days, same time of day, same store.

4. Lottery exceptions

Missing scratcher serials, settlement mismatches, draw-game terminal vs. POS sync issues. Each exception ties to a shift; same-day investigation preserves attribution.

5. Fuel margin per grade per store

Realized vs. target margin band per grade per store. Persistent gaps over 3¢/gal flag for pump-calibration check, supplier-cost audit, or wet-stock investigation. Don't react to a single day's outlier; look for the second-day pattern.

6. Inventory anomalies

SKU-level variances from yesterday's cycle counts. Tobacco outliers prioritized (highest dollar exposure per unit). Vendor short-shipments from yesterday's receiving, flagged at receiving, escalated if not resolved.

7. Unresolved manager notes

Yesterday's shift-handoff notes that flagged something but weren't resolved. Equipment issues, customer incidents, delivery anomalies. These compound if ignored, review them weekly even if the daily review is quick.

Store ranking by exposure

Once you have the per-store data, rank stores by daily exposure, the sum of unresolved variance across all categories. This becomes the prioritization layer: the top-exposure store gets attention first.

Exposure is not the same as sales. A store with $4,000/day sales and $400/day unresolved variance has 10% exposure, a much bigger operational issue than a $20,000/day store with $500/day variance (2.5% exposure). Track exposure as a percentage of sales, not as absolute dollars.

What should trigger a follow-up

Not everything in the brief needs same-day action. The triage framework:

SignalActionBy when
Missed EOD closeCall store manager immediatelySame morning
Cash variance > $50 over warningManager talks to clerk before their next shiftWithin 24 hours
Lottery serial gapInvestigate before settling the packSame day
Fuel margin gap > 4¢/gal (one day)Monitor; flag if second-day repeatNext morning
Tobacco shrink pattern (SKU + shift)Pull camera, schedule conversationWithin 48 hours
Vendor short-shipmentCharge-back negotiation with vendorWithin 1 week
Sales drop > 20% off baselineCheck competitor pricing, weather, foot trafficSame week

How to avoid spreadsheet chaos

Multi-store operators almost universally start with a master spreadsheet, one tab per store, a roll-up tab, columns for yesterday's metrics. It works at three stores. At six it becomes a part-time job. At ten it's the bookkeeper's full-time job.

The break points are usually:

  • Adding a new store requires re-jiggering the spreadsheet structure. New tab, new column references, new formulas. Onboarding cost per store grows non-linearly.
  • Regional managerscan't share the spreadsheet without seeing all stores. Either you over-share (manager sees the owner's portfolio) or under-share (manager can't see anything).
  • Manual data entry creates lag. By the time the spreadsheet is updated, the morning when the variance happened is gone.
  • Cross-store queriesrequire a person to run them. There's no "ask anything" layer.

Example: a multi-store morning brief

STATIONPRO MORNING BRIEF. Tuesday, June 3 2026, 7:00 AM PT

PORTFOLIO
  Total sales yesterday:   $48,210
  Sales 30-day avg (same DOW): $51,400 (-6.2%)
  Stores closed normally:  6 of 8

ATTENTION REQUIRED
  Store #5. EOD short $-87, reason: "missed cash drop"
    Clerk: Maria (overnight shift)
    → Manager review before her Tuesday shift

  Store #3. Lottery serial gap on pack #B-024
    Two scratchers missing ($10 exposure)
    Overnight shift, same store, same clerk pattern
    → Investigate before settling pack

  Store #2. Fuel margin regular 13.1¢ vs 18¢ target (4.9¢ gap)
    Second day of gap; first day was 14.3¢
    → Pump calibration check ordered

LOW-PRIORITY NOTES
  Store #7. Vendor short-ship: Marlboro Box, 2 cartons short of invoice
    → Receiving flagged at delivery; charge-back to McLane filed

  Store #1. Manager note: pump 3 slow to authorize all weekend
    → Service ticket open

ALL OTHER STORES, clean.
View full brief →

Comparing managers across locations

With per-store data, manager performance becomes comparable across objective KPIs:

  • EOD compliance % (closes done on time, on procedure).
  • Average close time per shift.
  • Variance frequency (closes with over-tolerance variance).
  • Lottery accountability (settled packs with zero shrink).
  • Vendor invoice approval lag (how quickly invoices clear the queue).
  • Void rate vs. store baseline.

Compare managers monthly, not daily, daily fluctuations are noise. Tops to thank and learn from (what are they doing differently?); bottoms to coach (process, training, or fit). The data takes the subjectivity out without removing the human judgment.

Exception-based reporting

The default mode of POS reports is "show everything that happened." The default mode of multi-store reporting should be the opposite: "show only what's anomalous." Exception-based reporting tags every event against the store's own baseline and surfaces only the events outside the band.

At eight stores, a typical operator would have ~50 individual signals (sales, voids, variance, lottery, fuel margin, inventory) per store per day = 400 data points to review. Exception-based reporting compresses that to the 5–15 anomalous events worth looking at. The owner reviews 15 things instead of 400.

Frequently asked questions

What should gas station owners review every morning?

Seven lines per store: yesterday's sales vs. baseline, EOD compliance, cash variance, lottery exceptions, fuel margin per grade, inventory anomalies, and unresolved manager notes. Each ties to a same-day action when flagged. The whole review takes about ten minutes when nothing is anomalous.

How do you compare store performance across locations?

Compare each store to its own historical baseline first, then peer-compare across the portfolio. Use percentage-based KPIs (margin %, variance % of sales) rather than absolute dollars, absolute dollars confuse volume with efficiency. A high-volume urban store and a low-volume rural store have different "normal."

What is exception-based reporting?

Reporting that tags every event against the store's own baseline and surfaces only events outside the band. Instead of "show everything that happened," exception-based reporting shows "what's anomalous today." Compresses 400 daily data points across 8 stores to the 5–15 worth reviewing.

When should I add a regional manager?

Typically around 6–8 stores under one owner. Below that, the owner can manage directly and the morning brief plus weekly deep-dives are enough. Above that, the daily attention demand exceeds the owner's bandwidth, a regional manager scoped to a store subset becomes the next layer.

How do you avoid spreadsheet chaos with multi-store reporting?

Move from per-store spreadsheets to a back-office system that aggregates automatically. The spreadsheet works at weekly cadence and breaks at daily cadence. Software runs daily without adding labor and scales linearly with store count, adding the 16th store costs the same as the 2nd.

What's the difference between sales and exposure?

Sales is daily revenue. Exposure is unresolved variance, cash, lottery, fuel margin gap, inventory shrink, as a percentage of sales. A $4,000/day store with $400/day exposure (10%) is a bigger operational issue than a $20,000/day store with $500/day exposure (2.5%). Track exposure ratios, not absolute dollars.

How do you handle regional manager scoping?

Role-based access at the user level. A regional manager is scoped to a specific list of stores; every view, query, alert, and report inherits that scope. Cross-store comparisons return only stores in scope. The owner sees everything; managers see only their stores. Bookkeepers and accountants are similarly scoped.

Sources & methodology

This playbook draws on operator workflows observed in StationPro pilot stations and on anonymized product data from live pilot tenants. Figures are illustrative examples, not promises about your stores. Procedures were reviewed against the workflows of the StationPro operator team before publication. Questions or corrections: talk to the team.

Written by

StationPro Editorial

The operator team behind StationPro. We write the procedures we ship: every playbook comes from real close, reconciliation, and loss-attribution workflows in pilot stations.

See where your station is leaking money.

A 30-minute call. We build the demo around your stations, not a generic deck.