WooCommerce Distance Rate Shipping prices orders based on the Google Maps distance from a store origin to the shipping address. The plugin saves the resolved distance and the chosen rate on the order as meta (typically _distance_km or _distance_miles and _distance_rate). For a local-delivery operator that's the operational backbone of the business, and yet WordPress treats it as a single-order detail field.

SleekView reads wc_orders with the distance and rate meta joined, plus the shipping address for postcode and city, and renders one row per delivery order. Filter to orders over 10km to triage the long-haul runs. Sort by distance descending to assemble the most-distant cohort. Filter by postcode for the per-neighbourhood review. Group rows by distance band for the catchment-shape audit. The data the chart view aggregates becomes a row-level surface for dispatch ops, driver routing and growth.

The plugin keeps owning the distance calculation and the rate engine. The table view owns the audit surface so the distance-priced operation becomes something the team can review row by row.

When shipping is priced by distance, distance becomes the most important business variable nobody on the team is looking at directly. The plugin saves the resolved distance on every order, which is the foundation for an operational audit, but the WordPress order list treats it as a single-order field. SleekView reads the same distance meta and renders one row per delivery order with distance, rate, postcode and status.

The dispatch team gets a sortable sequencing list, the routing team gets a postcode-grouped audit, and the growth team gets a catchment-shape table. The plugin keeps owning the geometry, and the team finally gets the per-row visibility the geometry was always producing.