Context
Delivery pricing needed to be assessed against the actual distance between warehouse and customer. A flat operational view could show transaction count and fees, but it did not explain where delivery economics turned negative.
Question
How far could an order travel while the observed net delivery margin remained positive under the pricing structure represented in the available data?
Approach
I joined delivery distance with fee and cost components, calculated net margin for each observed delivery, and plotted distance against margin. A zero-margin reference line made loss-making observations visible, while the furthest positive observation provided a concrete threshold for discussion.
This was descriptive analysis rather than a universal pricing rule. Outliers, service area, vendor behavior, and changes in cost structure still required operational review.
Decision support
The analysis reframed delivery performance from a dashboard total into a distance-sensitive unit-economics question. Stakeholders could use the threshold as an investigation point for delivery coverage, pricing bands, and exception handling rather than treating all delivery distances equally.
Privacy boundary
Customer-level records, addresses, phone numbers, and transaction identifiers are not published. The public evidence retains only the analytical relationship needed to explain the method and finding.
What I learned
A threshold becomes useful only when its assumptions remain visible. Operational decisions should pair the observed result with data-quality checks, outlier review, and clear ownership of pricing changes.