If you already run local delivery as a real channel — not a test, but a steady stream of orders going out in your own metro — you have lived inside this dashboard. You know the status flow cold. What you probably do not have is a clean read on whether those local orders out-earn the same products shipped by carrier. This guide covers what the dashboard does, then fills the gap it leaves: the per-order profit math.
What the Shopify local delivery dashboard actually is
The dashboard is a filtered slice of your existing orders. When a customer at checkout picks a local delivery rate instead of shipping, the order gets tagged with the Local delivery delivery method and shows up under the Local delivery filter in both the web admin and the Shopify POS app.
From there you move each order through its statuses. Shopify's order workflow runs Unfulfilled, then Ready for delivery, then out for delivery, then Delivered, after which the order flips to Fulfilled, per Shopify's local delivery fulfillment documentation. Each order also carries the delivery instructions your customer typed at checkout, so your driver knows the gate code or the "leave at side door" detail.
That is the whole feature. It is good at what it does — keeping a day's route organized and statuses honest. It is silent on economics.
How the delivery zones and fees are set
Before the dashboard fills up, you define where you deliver and what you charge. This is where most of the profit leaks hide, so it is worth stating the limits precisely.
You build local delivery around zones. Shopify lets you set a delivery area either by a distance radius or by a list of postal codes, with a cap of up to ten delivery zones per location and a maximum radius of one hundred miles, or one hundred sixty kilometres. Postal-code lists can run up to three thousand characters.
Each zone gets its own pricing, and this is the lever operators under-use. Shopify supports up to three additional conditional price rules per zone, so you can charge full freight on small baskets and drop the fee as order value climbs — for example a delivery fee on orders over one threshold, a lower fee over a higher one, free above a third. Those rules are the difference between local delivery subsidizing your margin and quietly eating it.
The one number the dashboard never shows: profit per order
Here is the trap. The dashboard shows an order as Delivered and marks it green. Green reads as "done." It does not read as "profitable," and for local delivery the two are often not the same.
A carrier-shipped order has a clean, known shipping cost. A locally delivered order replaces that line with something fuzzier: a driver's hourly wage split across the stops on a route, fuel, the van, and — if you drive yourself — the hours you did not spend on the business. None of that flows into the Local delivery view. You see status, not cost.
So the channel can look busy and healthy while a chunk of orders lose money, because short routes, one-off addresses on the edge of a zone, and under-priced delivery fees all show up as the same cheerful "Delivered."
A worked example: is your local route paying?
Say you run an operating store doing 1,000 orders a month at a $40 average order value, and roughly 150 of those are local delivery in your city. Your product economics are steady: a $40 order carries $16 in product cost (blanks, print, base fulfillment), leaving $24 of gross profit, with another $3 in payment and pick-pack costs. Call that $21 before the delivery line.
For a carrier order you'd pay about $6 to ship, landing near $15 of contribution. Now price the local version honestly. You pay a driver $20 an hour, and on a tight suburban route they clear six stops an hour, so labor is $20 ÷ 6 = $3.33 per stop. Add fuel and vehicle wear of roughly $1.50 per stop and your real local delivery cost is about $4.83 an order.
If you charge a $5 local delivery fee, the customer covers it: $21 − $4.83 + $5 = $21.17 of contribution, better than the carrier version. Now break the route. On a thin day your driver clears only three stops an hour, so labor doubles to $6.67 and cost per stop climbs to about $8.17. That same $5 fee no longer covers it: $21 − $8.17 + $5 = $17.83, still positive here — but on a lower-AOV basket, or a longer edge-of-zone drive, that gap closes and then inverts. The dashboard shows all of these as "Delivered." Only the math tells them apart.
The takeaway is not "stop doing local delivery." It is that route density and your conditional fee rules are the two dials that decide whether the channel earns, and neither one is visible in the view you stare at all day. This is the same gap that shows up across fulfillment choices, which is why operators lean on dedicated ecommerce business intelligence rather than reading profit off an operations screen.
Native dashboard vs delivery apps vs actual profit
When the native view gets tight, most operators reach for a delivery app. Tools like Zapiet, Shipday, and Dropit add route optimization, driver apps, time-slot picking, and live customer tracking on top of Shopify. They are a real upgrade for logistics.
But notice what they optimize: time and stops, not margin. A route optimizer makes the $4.83 cost smaller by packing stops tighter — genuinely useful — yet it still reports success in minutes saved, not dollars kept. You are back to needing the profit layer somewhere else.
That "somewhere else" is a reporting question, not an operations one. If you want to compare local delivery against carrier shipping and against pickup, you are comparing contribution margin by fulfillment method over time — the kind of view a Shopify overview dashboard starts to approach and that true transaction analytics in ecommerce are built to deliver. Picking the right tool for that job is its own decision, which is why it helps to know what the best ecommerce analytics platforms actually measure before you commit.
Where PodVector AI fits
PodVector AI runs Victor, an AI employee for your store. Victor is not a delivery dashboard and will not plan your route — the native view and the delivery apps do that job well. What Victor does is close the money gap those tools leave open.
Victor sees every order in Shopify, every ad dollar in your Meta Ads and Google Ads accounts, and every supplier cost from Printify, Printful, and Gelato in one place, so he can compute the true per-order profit on your local deliveries and compare it against your carrier-shipped orders. He delivers that read to you as a report in Google Drive, so the profit answer lives next to the operations view instead of in your head.
And because Victor can take action — with your approval on every write — he can do more than report. If your local delivery fee is under-priced against your real route cost, Victor can propose and, once you approve, change prices and discounts in Shopify and adjust your Meta and Google Ads campaigns to steer spend toward the orders that actually clear. Nothing executes until you say go.
If you want the profit truth behind every "Delivered," you can put Victor to work on your store and see the per-order math the delivery dashboard was never built to show. From there it is a short step to the full ecommerce performance analytics picture across every channel you run.
FAQs
Does the Shopify local delivery dashboard show profit per order?
No. The Local delivery view shows fulfillment status, the delivery method, and customer instructions. It does not pull in your driver wages, fuel, vehicle cost, or your own time, so it cannot tell you whether a delivered order earned a profit. You get the operational state of the order, not its margin.
What is the maximum delivery radius and how many zones can I set?
You can set a delivery area by distance or by postal codes, with a cap of one hundred miles or one hundred sixty kilometres and up to ten zones per location. Each zone can carry its own pricing plus up to three conditional price rules, which is the main tool you have for making the fee match the real cost of reaching that zone.
Should I charge for local delivery or make it free?
It depends on your route density and basket size. Free delivery lifts conversion but only pays if your contribution per order still clears the real delivery cost — which, as the worked example shows, swings hard with how many stops your driver clears per hour. Use Shopify's conditional pricing to make delivery free only above an order value where the margin covers the drive, and charge below it.
Do I need a delivery app on top of the native dashboard?
If you are running more than a handful of local orders a day, an app like Zapiet, Shipday, or Dropit earns its keep through route optimization and driver tracking. Just remember those tools optimize time and stops, not margin — they make the route cheaper, but they still do not tell you which orders are profitable. That profit read has to come from your reporting layer.
How is local delivery profit different from carrier shipping profit?
A carrier order has a single, known shipping charge. A local order swaps that for a variable cost that depends on route density, wages, and distance, so two identical products can have very different delivery costs on the same day. That is why you cannot assume local delivery is cheaper just because there is no carrier label — you have to price the route and measure it per order.