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: a Berlin POS register, a Hamburg POS register, and the online store each carry distinct values. The default WooCommerce orders screen treats them identically, with no column for location, no filter to split POS from online and no saved per-store view.

SleekView reads wp_wc_orders joined with wc_orders_meta and exposes Square location ID, transaction ID and refund references as columns on every row. Filter to a single POS location for a monthly per-store finance review. Sort by Square transaction ID to match against Square settlement reports. Saved views per location replace the CSV export per store the finance team used to do every month.

The plugin keeps owning the Square API and product sync. The table view owns the audit surface, so the location signal Square already writes stops hiding inside per-order panels and becomes a sortable, filterable workspace.

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 standard orders screen leaves it inside per-order panels with no column, no filter and no saved view. SleekView reads the same wc_orders_meta the gateway writes and renders Square location ID, transaction ID and refund state as audit columns, so the Berlin POS, the Hamburg POS and the online store stop competing for the same row.

The plugin keeps owning the Square API, refunds and product sync, while finance, store managers and support each land on the slice their work actually needs.