At a glance
The average value of a successful Square payment in the period (total volume divided by transaction count). Square retail typically sits USD 25, USD 60 average ticket; Square Online sits USD 40, USD 90; Square Invoices much higher (USD 200+). Mix-shift between channels moves this number more than any single-channel pricing change.
Calculation
Calculated automatically from your Square data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The Austin bookshop, 30-day window:
Observations:
- Cash drawer drags the average down hard. USD 12.03 cash avg vs USD 22.92 card-present avg. Pure cash is the small-ticket tender (a single magazine, a paperback, a coffee). If the merchant grew online Cash App Pay (USD 33 avg) and shrank cash drawer, the blended figure would rise materially.
- Invoice channel matters more than its count. 14 invoices at USD 342.86 contribute USD 4,800, which is 3.7% of total volume but pulls the blended avg up by USD 0.75. A 50% increase in invoices would lift avg-ticket by USD 0.40 even if no other channel moved.
- Online avg is consistently higher than retail avg. Standard retail-vs-ecom pattern: walk-in customers buy one or two items; online customers buy multi-item baskets to qualify for free shipping.
- Apple/Google Pay avg lower than chip/tap. Express tap is biased toward small-ticket impulse buys (under USD 25); larger purchases sometimes prompt the customer to use chip-and-PIN out of habit.
- Multi-location merchants see different averages per store. A flagship downtown location sees higher avg-ticket than a satellite suburban store; slice by
location_idfor the per-location read.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in the Square Dashboard:Reports → Sales → Sales Summary → “Average sale” tile (with the same date filter).Dashboard’s “Average sale” matches this card when the channel filter is “All”. Why our number may legitimately differ:
Cross-connector reconciliation: avg-ticket is a useful sanity check across PSPs but legitimately diverges by channel mix. A retail-heavy Square merchant (low avg) plus a SaaS Stripe account (high avg) for the same business will show very different avg-tickets, that’s expected.
Known limitations / merchant FAQs
“Why did my avg-ticket suddenly jump 30%?” Almost always channel mix-shift. Opensqu_top_payment_methods and check whether Cash App Pay share dropped, or whether Invoices went up. Pricing changes rarely move blended avg by 30%; mix-shift does.
“Should I exclude cash from this metric?”
Some merchants prefer to. The card defaults to all-tender. If you specifically want card-avg, the underlying field is source_type and you can filter IN (CARD, WALLET, CASH_APP, EXTERNAL) in your own analysis.
“Does this work per-location for multi-location merchants?”
Yes; the card aggregates by default but the underlying /v2/payments rows carry location_id. The location-specific breakdown is on the connector roadmap.
“My subscription business has very stable avg-ticket, is that normal?”
Yes. Subscriptions rebill at the same dollar amount every cycle; if your subscriber base is stable in tier mix, the avg-ticket flatlines.
“USD vs CAD locations, single number?”
No, currency-neutral averaging would mislead. The card returns USD avg and CAD avg separately.
“Square Online sales vs in-store, why is the gap so consistent?”
Online customers are price-aware (free-shipping thresholds, basket optimisation); in-store customers are convenience-driven. The gap exists in every retail-plus-ecom dataset and rarely closes.
“Tipping, does it inflate this metric?”
Yes. Tipped industries (restaurants, bars, salons) running Square see avg-ticket include tip. The tip flows in tip_money separately but the headline amount_money is gross of tip.
“What about refunds, do partial refunds reduce avg?”
No. Refunds are tracked separately. The original payment’s full amount stays in this metric.