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). That's the data a delivery-driven store needs to understand its operation: how far the average customer is, how revenue scales with distance, which distance bands are over-served or under-served.

SleekView Charts joins wc_orders with the distance meta so the radius-based business gets a real dashboard. A Number gives the average distance per order across the period. A Bar groups orders by distance band (0-2 km, 2-5 km, 5-10 km, 10+ km). A Pie of revenue share by band reveals which radius is paying the bills. An Area trends orders-by-distance over time so seasonal patterns or expansion campaigns become visible.

The plugin keeps owning the distance calculation and the rate engine. SleekView surfaces the data the engine writes as a screen the local-delivery operator actually reads.

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 dashboard, but no native screen pivots that data into the four shapes a local operator actually needs: average, distribution, revenue share, growth curve. SleekView Charts treats the distance meta as the first-class column it is.

Catchment-trim decisions stop being driven by a single driver complaining about a long run and start being driven by the revenue-by-band Donut. New-location decisions stop being instinct and start being a time-series. The plugin keeps doing the geometry.

The dashboard delivers the visibility the geometry deserves.