Square for WooCommerce writes a Square transaction ID and a Square location ID to every Square-paid order's meta. Storage adapts to HPOS (wc_orders_meta) or legacy (postmeta). Multi-location retailers (an online store plus physical Square locations) have all the data needed to split sales by channel, but the default reports screen surfaces none of it.

SleekView Charts pivots the Square keys and builds a channel-aware dashboard. A KPI card shows Square revenue for the period. A Pie card splits orders by location (online, store 1, store 2). An Area card plots daily revenue stacked by location, so contribution and trend are visible in one shape. A Bar card ranks locations by total revenue.

Filters scope to Square-paid orders only, so multi-gateway stores still reconcile each gateway separately. Drill-through to rows surfaces the Square transaction ID inline for cross-reference against Square's dashboard.

Multi-location retailers running Square plus WooCommerce have all the data they need for channel-aware reporting and almost none of the visibility. Location ID is right there in order meta on every Square-paid order, but the WooCommerce reports screen does not know it exists and the per-order meta panel hides it behind clicks. The result is a monthly export-and-pivot ritual where managers reconstruct per-location performance in spreadsheets.

A four-card dashboard built directly on Square's location and transaction meta collapses that work into one screen. Revenue as a KPI gives finance the gateway-scoped headline. Per-location pie and ranked bar make channel contribution obvious.

Stacked daily revenue plots trend and mix together. Drill-through preserves the transaction ID for instant cross-reference against Square's dashboard. The gateway still owns refunds and the canonical settlement; the chart dashboard owns the WordPress-side queryability that multi-location retail genuinely needs.