Square's official WooCommerce extension is unusually thorough about persisting transaction metadata: every order paid via Square gets a Square transaction ID written to its meta, plus a location ID that distinguishes the in-person POS register from the online store from any other physical Square location. Products synced with Square also carry location metadata so multi-location retailers can route inventory correctly. The default WooCommerce orders screen surfaces none of it because that's not what core orders shows.

SleekView reads wc_orders_meta on HPOS stores and postmeta on legacy and pivots the Square keys into named columns. Transaction ID becomes the link to Square's dashboard for reconciliation. Location ID becomes a filter chip that splits in-person sales from online sales without any custom report. Refund metadata surfaces inline so support tickets resolve in one screen rather than three.

Multi-location retailers gain the most. The same WooCommerce store often handles sales from two or three physical Square locations plus the website, and the conventional flow forces a manual export per location for finance and inventory work. SleekView turns location into a column and a filter, so 'orders from Berlin store, last week, completed' is one saved view instead of a SQL query. The gateway still owns refunds and the Square API; SleekView owns the audit and segmentation layer over data Square already writes.

Multi-location retailers running Square plus WooCommerce live a particular pain. The website is one Square location; each physical store is another; products sync between all of them; and orders flow through WooCommerce regardless of where the sale happened. The default orders screen shows order ID, status, and total; the location detail that matters most for stock reconciliation, channel attribution, and store-level finance is buried in meta.

The result is a manual export-and-pivot workflow per period or per location, plus a constant cross-reference against the Square dashboard for transaction IDs nobody surfaced. SleekView pivots Square's location_id and transaction_id into proper columns and adds a location filter chip, which collapses the workflow into saved views: 'Berlin store, last week', 'online channel, this month, refunded only', 'all locations, AOV by channel'. Cross-referencing against Square's dashboard becomes a click on the transaction ID column.

Inventory teams audit per-location product sync from a parallel products view. The gateway still owns the API and the dashboard remains canonical; SleekView owns the WooCommerce-side queryability that multi-location retail genuinely needs.