Square's official WooCommerce extension persists each paid order's Square transaction ID and location ID in WooCommerce order metadata. Location ID is the channel signal: it distinguishes the Berlin POS register from the online store from a second physical Square location. Product sync also writes location IDs to product meta so inventory can be routed correctly.

SleekView Charts reads wc_orders_meta on HPOS or postmeta on legacy and exposes those Square keys as groupBy columns. A chart card grouped by Square location ID shows order volume per channel. A chart grouped by Square card brand shows which payment paths customers actually use. Refund-state meta becomes a slice on the same dashboard.

Multi-location retailers gain the most. Instead of a CSV export per location plus a manual pivot in a spreadsheet, the saved dashboard renders every location's slice automatically. The gateway keeps owning Square API calls and refunds; SleekView owns the chart layer over what Square already writes.

Square for WooCommerce is unusually rich about writing per-order metadata, including location IDs that distinguish each POS register from the online store. That signal is exactly what multi-location retailers need for finance and operations work, but the WooCommerce admin does not chart it. SleekView Charts reads the same wc_orders_meta the gateway writes and exposes Square location ID as a chart axis, so per-store revenue and channel split land on one saved dashboard.

Reconciliation against Square's settlement reports stops requiring a spreadsheet round trip. The gateway still talks to the Square API, processes refunds, and syncs products; SleekView just charts what Square already writes.