Shopify POS Local Delivery: Set Up a Promise You Can Keep

Shopify POS Local Delivery: Set Up a Promise You Can Keep

Shopify POS local delivery now lets staff sell an item in-store and arrange delivery during the same checkout. For a customer who can't carry a bulky purchase home, that removes an awkward reason to leave without buying. For the merchant, it creates a practical question: can your stock records and dispatch process support the promise? Two Shopify releases dated 28 September 2026 bring that question into focus. Here's how we'd use them together, without turning your shop floor into an improvised delivery depot.

What changed in Shopify POS local delivery?

According to Shopify's local delivery announcement, staff can now create local delivery orders at checkout in POS. Customers no longer need to reorder online, and staff don't have to rely on an order note as a substitute for a delivery method.

The feature uses the delivery zones and rates already configured for the online store. When staff add shipping to a cart and the customer's address falls within a delivery zone, local delivery appears alongside the other shipping rates. Staff select it, confirm the phone number and add delivery instructions before checkout.

The delivery address and fee appear in the cart, on the receipt and on the customer-facing display. That gives both parties a chance to catch an incorrect address or unexpected charge before the sale ends.

Our view: the useful change is the removal of a second transaction. Asking someone standing at your till to buy again online introduces unnecessary work and another opportunity to abandon the purchase. But checkout convenience doesn't create delivery capacity. Treat the release as a reason to review your operating model before you promote the service.

Stock counts belong in the same rollout

A separate release, stock counts in Shopify POS, lets store staff run cycle counts and full stock counts directly in POS. Planning, review and approval remain in Shopify Admin.

Users with the required permissions create and schedule a count in Admin, select its location and choose the products. The count then appears under Products > Stock counts in POS at that location. Staff with the inventory permission record quantities through barcode scans or manual entry, then submit the completed count for review.

A cycle count checks a selected portion of inventory rather than the entire location. We'd start with products likely to generate delivery orders, particularly bulky items and products with frequent stock discrepancies.

These releases address different jobs. One records the customer's delivery choice; the other helps establish what is physically available. Together, they support a better process, but neither announcement establishes automatic stock reservation or a complete dispatch workflow. Test those behaviours in your own configuration.

Landscape 3:2 realistic editorial photograph in a sunlit Scandinavian homewares shop: a large charcoal ceramic planter b

Configure Shopify POS local delivery around real capacity

Audit the zones you already use online

Because POS uses your existing local delivery zones and rates, start there. A rate that works for small online parcels may be unsuitable for heavy goods sold on the shop floor. Check representative addresses near each boundary and compare the displayed fee with the actual cost of serving that address.

Don't assume a geographic boundary matches a practical route. A nearby address might involve restricted vehicle access or a ferry crossing. Staff need a clear escalation path when an address qualifies in checkout but the delivery requires special arrangements.

Separate delivery eligibility from delivery timing

An address can qualify for local delivery without qualifying for delivery today. The supplied announcement describes zones and rates; it doesn't establish time-slot booking, route optimisation or vehicle capacity management.

Write down the delivery promise staff are authorised to make. For example, a pilot might offer delivery on selected weekdays, with a dispatch cut-off agreed internally. That's an operating recommendation, not a built-in scheduling claim.

If you need booked appointments or capacity limits, verify whether your existing delivery system covers POS-created orders. A system that works for online checkout may need a different integration path for these orders.

Check the customer's details while they're present

Use the customer-facing display to confirm the address and delivery fee. Ask for the phone number needed for delivery contact, rather than assuming an older customer record is current. Capture access instructions that help the driver, while avoiding unnecessary personal information.

Keep the script short: confirm where the order is going, then explain when the customer should expect it. A receipt with the correct address still doesn't tell someone whether they need to stay home on Thursday.

Give the sale a clear handoff to fulfilment

The most dangerous gap is often between payment and picking. A staff member completes the sale, assumes somebody else will handle it, and leaves the item on a shelf where another customer can buy it.

Before launch, assign an owner to the next step. Decide how that person sees new delivery orders, how quickly they check availability and where they stage picked goods. Confirm what your inventory settings do at each stage rather than relying on habit.

  • At checkout: staff confirm the delivery method, contact details and permitted delivery promise.
  • After payment: a named role checks the order and assigns the picking work.
  • Before dispatch: staff verify the physical item against the order and check any access instructions.
  • When something goes wrong: one owner contacts the customer and records the agreed resolution.

Run a test order all the way through your actual fulfilment process. Look at what the picker sees, not just what the cashier sees. If a delivery instruction appears on the order but never reaches the driver, the process still needs work.

Use stock counts to investigate discrepancies

Don't turn the new counting feature into a race to approve adjustments. A mismatch can reflect an unprocessed return, a damaged display item or stock placed in the wrong location. Changing the number without understanding the cause leaves the next delivery exposed to the same problem.

We'd schedule a small count before the pilot starts, then repeat it for the products that cause exceptions. Count sellable units carefully. A floor sample that isn't available for sale shouldn't support a delivery promise simply because it's physically in the building.

Shopify's split between POS counting and Admin review offers a useful division of responsibility. The person with the item in front of them records the quantity; the reviewer checks unexpected differences. For a small team, those roles may overlap, but the review should still be deliberate.

Agree how to handle sales and stock movements during a count. The announcement doesn't describe every concurrency rule. Test your workflow and brief staff so a unit sold mid-count doesn't become an unexplained adjustment.

Landscape 3:2 realistic editorial photograph of a tidy homewares stockroom adjoining a bright shop floor. Matching charc

Where native Shopify ends and another tool may help

Shopify's native local delivery checkout is a sensible starting point for a shop with a manageable delivery area and a simple dispatch process. Its immediate advantage is that staff use the existing sale instead of sending the customer to another channel.

It isn't evidence that you can retire specialist delivery software. Merchants with booked installation visits, multiple vehicles or strict appointment windows should assess those requirements separately. Ask prospective app vendors to demonstrate a POS-created local delivery order through to completion. A feature list is weaker evidence than that test.

Also distinguish local delivery from mixed fulfilment. The fresh Shopify changelog guide from Huptech lists a separate June update for shipping and pickup within one order on Plus and Enterprise. That's a different use case. Don't infer that September's local delivery release supports every combination of take-home and delivered items in a single sale. Verify the exact basket your staff need to sell, along with current plan and location requirements.

Run a pilot before extending the delivery area

We'd begin at one location with a limited product selection. Use the first week to inspect exceptions rather than chase a conversion uplift. Low order volume won't support confident claims about increased sales, but it can expose missing delivery instructions immediately.

Before launch, test an address inside the zone and one outside it. Check a boundary address too. Put through an order with access instructions, then verify where those instructions appear downstream. Rehearse a stock discrepancy and a cancellation so staff know who owns the customer conversation.

Track the share of orders delivered within the promised window and the share that require manual correction. Record delivery cost per completed order, including staff time where practical. Keep failed delivery attempts visible rather than burying them in general operating costs.

If customers like the service but each delivery loses money, revisit the fee or service area before expanding. If stock exceptions dominate, fix counting and picking first. A larger delivery radius will usually make those failures more expensive.

Takeaways

  • Shopify POS local delivery uses your existing online delivery zones and rates. Audit them before staff start offering the service.
  • Use POS stock counts to check the products you intend to deliver, with deliberate review of discrepancies.
  • Assign responsibility for the handoff from checkout to picking. Don't assume a completed sale has entered a working dispatch process.
  • Test specialist requirements separately, then expand only when delivery reliability and costs justify it.

Sources

Want this handled for you?

We're a Shopify Premier agency and this is the work we do every day: performance, CRO, and store builds that pay for themselves. Book a free store review and we'll show you the three fixes we'd ship first.

Frequently asked questions

Can you create local delivery orders in Shopify POS?

Shopify's 28 September 2026 release lets staff create local delivery orders during POS checkout. When shipping is added and the customer's address falls within a configured delivery zone, local delivery appears alongside other shipping rates.

Does Shopify POS local delivery use online store delivery rates?

Yes. Shopify says POS local delivery uses the delivery zones and rates already configured for the online store. Review those settings before offering the service in-store.

Can store staff run inventory counts in Shopify POS?

Yes. Authorised users create and schedule counts in Shopify Admin. Staff with the inventory permission can open the count under Products > Stock counts in POS, scan barcodes or enter quantities manually, and submit the count for review.

Does Shopify POS local delivery include route planning?

The September 2026 announcement describes delivery selection at checkout, not route optimisation or capacity-based appointment booking. Merchants that need those capabilities should verify their delivery software supports POS-created orders.

YOUR JOURNEY STARTS HERE!

To replicate the showcased functions or optimize your websites, connect with us via the form for bespoke solutions.

Complimentary Discovery Call.