WooCommerce Local Delivery and Pickup Plugins Compared

WooCommerce local delivery and pickup plugins fall into three layers that get sold under one search term, and buying the wrong layer is the most expensive mistake in this category: a date picker at checkout, a pickup location manager, and a dispatch tool for whoever drives the van. Most stores need one of the three, some need two, and almost nobody needs all three — yet the roundups list them together as if they were interchangeable.

Below: the three layers separated out, the criteria I judged each option against, a table of versions, install counts and prices checked on 30 September 2026 against WooCommerce 11.1.2 on WordPress 7.1.2, what WooCommerce already gives you free before you buy anything, and the two things that break local delivery stores regardless of which plugin you pick — cut-off times and pickup tax.

The three layers people call "local delivery"

Separate these before you open a pricing page. They solve different problems, they are written by different vendors, and a plugin that is excellent at one is usually indifferent at the others.

1. Scheduling at checkout. The customer picks a delivery date, a time window, or a pickup slot before they pay. This is where the date-picker plugins live. The hard parts are capacity (how many Saturday 10am–noon slots exist), lead time (how many hours of notice you need), and cut-offs (order by 2pm for same-day).
2. Pickup locations. You have more than one place customers can collect from, or products that only exist at one of them. This is a shipping and inventory problem, not a calendar problem, and WooCommerce core covers a thin version of it for nothing.
3. Dispatch and fulfilment. The order is paid; now somebody has to be assigned to it, drive it, and mark it delivered. This layer lives entirely after checkout, has its own user role, and has nothing to say about dates or slots.

What WooCommerce already does for free

Start here, because a surprising number of stores buy a $99/yr extension for something core has shipped for years. WooCommerce 11.1.2 includes Local Pickup as a core shipping method. You add it per shipping zone under WooCommerce > Settings > Shipping > Shipping Zones, give it a name, set its tax status, and optionally attach a cost. Customers in that zone then see it at checkout as an alternative to shipping.

There are two implementations, and knowing which one you are looking at saves an hour of confusion. The legacy method is the shipping-zone one just described. The newer Local Pickup block is configured separately and is what the Cart and Checkout blocks use. If you have migrated to block checkout and your pickup settings appear to have vanished, they have not — you are editing the wrong one.

What core does not do: pickup dates, pickup time slots, delivery dates, capacity limits, or cut-offs. There is no calendar anywhere in it. If all you need is "let people collect instead of paying shipping", you are finished and you have spent nothing. If you need to know when they are collecting, that is the first paid or add-on decision.

One core behaviour to know about before it surprises you at tax time: by default, WooCommerce calculates tax on a local pickup order using your store address rather than the customer’s. That is the correct treatment for plenty of US stores and the wrong one for others, and it is a one-line filter to change.

<?php
// wp-content/plugins/wpfairs-store-snippets/local-pickup-tax.php
// Stop WooCommerce taxing local pickup orders at the store's base address
// and fall back to your normal tax configuration instead.
add_filter( 'woocommerce_apply_base_tax_for_local_pickup', '__return_false' );

// Or keep base-address taxing, but point it at the pickup location
// rather than the address in WooCommerce > Settings > General.
add_filter( 'woocommerce_countries_base_postcode', fn() => '80903' );
add_filter( 'woocommerce_countries_base_city',     fn() => 'COLORADO SPRINGS' );

Put that in a small site-specific plugin, not in your theme’s functions.php, so a theme switch does not silently change how you collect tax. Which of the two behaviours is right for you is a question for whoever files your returns — sourcing rules differ by state and I am not going to guess yours. WooCommerce sales tax plugins compared for US stores covers the automation options once you know the answer.

The six criteria I judged each WooCommerce local delivery plugin on

Stated up front so you can reweight them if your store looks nothing like the one I assumed: a US business doing 50 to 600 local orders a month, one or two pickup points, deliveries inside a metro area, payment taken at checkout, and one person who configures plugins between other jobs.

1. Which layer it actually sits in. Scheduling, locations or dispatch. This decides everything else, and every vendor’s marketing blurs it.
2. Whether capacity limits are in the free tier. A date picker with no cap per slot is a promise generator. Twelve people book Saturday 10am, you have three delivery runs, and you find out on Saturday. This is the single most common reason a free delivery-date plugin gets replaced within a month.
3. Cut-off handling. "Order by 2pm for same-day" is a scheduled comparison, not a static setting, and how the plugin evaluates it decides whether your 2:01pm orders quietly become same-day anyway.
4. Block checkout support, stated explicitly. WooCommerce’s Cart and Checkout blocks need extensions written against the Store API. A plugin that only hooks the classic checkout template will render nothing on a block checkout, and it will not tell you — the field just is not there.
5. Maintenance signals, read strictly. Tested-up-to version, time since last release, install count against review count. This code sits in your checkout and holds customer addresses; a stale delivery plugin is a liability, not just a missing feature.
6. What renewal costs, not what the first year costs. Discounted first years are standard here. A $95.20 first year that renews at $119 is a $119 plugin, and you should budget it as one.

WooCommerce local delivery and pickup plugins compared

Versions, install counts and ratings come from WordPress.org and the vendors’ own listings; prices come from each vendor’s pricing page. All checked on 30 September 2026, against WooCommerce 11.1.2 and WordPress 7.1.2. On a narrow screen this table stacks into one card per option rather than scrolling sideways.

The honest summary of that table: if you need a delivery date with capacity limits and nothing else, the free Tyche plugin does it and you can stop reading. If you need same-day with a cut-off, you are buying something, and the real choice is $119/yr against $149/yr. If you need multiple pickup points, that is a separate $99/yr purchase that does not overlap with either.

Delivery fees: flat, zone-based, or by distance

Scheduling and charging are separate decisions and most stores conflate them. You can have a beautiful delivery calendar and still charge $8 to drive two blocks and $8 to drive eleven miles. Three ways to price it, in order of how much work they are:

• A flat rate inside one shipping zone. Free, core, five minutes. Draw the zone by postcode, attach a flat rate, done. This is right far more often than store owners believe, and the margin you lose on the far edge of the zone is usually smaller than the cost of maintaining anything cleverer.
• Several zones as concentric rings. Still free and still core: zone A is your inner postcodes at $5, zone B the outer ring at $12, everything else gets shipping only. The cost is maintenance — every postcode list is a thing you now own. WooCommerce shipping methods compared for US stores covers how zones, classes and table rates interact once you have more than two.
• Real distance or drive time. WooCommerce Distance Rate Shipping is $99/yr (v1.9.0, updated 16 September 2026, 3.5/5 from just 6 reviews) and prices by road distance or travel time using Google’s Distance Matrix API. It is the only one of the three that reflects what a delivery actually costs you.

Cut-off times are a WP-Cron problem

"Order by 2pm for same-day delivery" sounds like a setting. It is a time comparison that has to be correct at 1:59pm and at 2:01pm, and it fails in two specific ways that no feature list mentions.

The first is the time zone. If your WordPress time zone is set to a UTC offset instead of a city, daylight saving is not handled and your cut-off is an hour wrong for roughly eight months of the year. Fix it under Settings > General by picking an actual city — America/Chicago, not UTC-6. This takes ten seconds and is worth checking even if you think you did it.

The second is scheduling. Anything a delivery plugin does on a timer — rolling the available dates forward at midnight, closing a slot when it fills, releasing a held capacity slot from an abandoned order — usually runs as a WordPress scheduled event, and WP-Cron only fires when somebody visits the site. On a local store with no overnight traffic, a job scheduled for 3am runs whenever your first morning visitor arrives, which might be 7:40am. Your customers see yesterday’s dates until then. The missed schedule error in WordPress covers switching to a real system cron, which is the fix for this and for every other quiet-hours scheduling bug on the same site.

Test the cut-off before you launch, not after the first angry phone call: set it to two minutes from now, place a test order, and check the date options change. Then set it back.

Checkout caching and the delivery date field

A delivery date picker renders live availability: which days are open, which slots still have capacity, whether today is still same-day eligible. That is the same problem a booking calendar has, and it has the same answer — it cannot be served from a full-page cache.

In practice your cart and checkout pages are already excluded by any competent caching setup, so the picker itself is usually fine. The trouble starts when the picker lives somewhere else. If you put the delivery date selector on the product page or in a cart widget — several of these plugins offer a shortcode or block precisely for that — you have just put live availability on a cached page, and customers will pick slots that filled up an hour ago and get rejected at checkout. That reads to them as a broken store.

Either keep the picker on checkout where the cache already excludes it, or exclude every page you put it on and accept the performance cost. WooCommerce caching plugins: what breaks and what works covers which plugins set store exclusions automatically and which need them written by hand.

One more thing worth doing before you migrate anything: find out where your current delivery data actually lives. With High-Performance Order Storage enabled, order meta is in wp_wc_orders_meta, not wp_postmeta, and a plugin swap that does not carry the meta key across loses every scheduled delivery on your open orders.

# Not sure whether you are on HPOS at all? This answers it.
# "yes" means order meta lives in wp_wc_orders_meta, not wp_postmeta.
wp option get woocommerce_custom_orders_table_enabled

# Find the meta keys your delivery plugin writes, most-used first,
# before you change plugins.
wp db query "SELECT meta_key, COUNT(*) AS rows_found
  FROM wp_wc_orders_meta
  GROUP BY meta_key
  ORDER BY rows_found DESC
  LIMIT 30;"

# Then count the orders still open that carry one, substituting the
# key you found above for the placeholder.
wp db query "SELECT COUNT(*) AS open_orders_with_date
  FROM wp_wc_orders o
  JOIN wp_wc_orders_meta m ON m.order_id = o.id
  WHERE m.meta_key = '_your_delivery_date_key'
    AND o.status IN ( 'wc-processing', 'wc-on-hold' );"

If the first command returns nothing or no, you are not on HPOS: your order meta is still in wp_postmeta keyed by post_id, so query that table instead. Change the table prefix in both queries if yours is not wp_, and take a database backup before you run anything that writes.

Dispatch: who actually drives the van

Layer three, and the one most stores reach last. The order is paid and scheduled; now it needs a person attached to it, a status that is not "Processing", and a way for that person to see their runs on a phone without you giving them admin access to your store.

The established free option is Local Delivery Drivers for WooCommerce by powerfulwp — v3.0.1, 800+ installs, 4.3/5 across 18 reviews, tested to WordPress 7.0.6, updated two weeks ago. The free version gives you a driver user role, custom order statuses (Driver Assigned, Out for Delivery, Failed Delivery Attempt), manual assignment, a mobile-friendly driver view and automatic order notes. Route optimisation, live customer tracking, SMS and WhatsApp alerts, proof of delivery with signatures and photos, automatic assignment and driver commissions are in the paid tier.

My own Delivery Manager for WooCommerce does the same job from the other direction — disclosure: I build and maintain it. It adds a Delivery Person role, AJAX driver assignment from the order screen, a visual delivery timeline, automatic order notes on status changes, a driver dashboard inside My Account, and a customer-facing progress view with the expected date and the assigned person. It is v1.2.1, updated three days ago, tested against WordPress 7.1.2 and built for HPOS and block checkout.

Whichever you use, the dispatch layer generates mail: assignment notices to drivers, status updates to customers, failed-delivery notes. WordPress sends that through PHP’s mail() by default, straight from your web server, which is the exact sending pattern mailbox providers treat as suspicious — and a delivery notification that lands in spam costs you a phone call every time. Route it through authenticated SMTP with SPF, DKIM and DMARC before you scale the driver count. WooCommerce SMTP plugins compared for order emails covers the options and what each one verifies.

What to pick for your situation

• One shop, customers collect, you do not care when. Core Local Pickup. Free, five minutes, nothing to maintain. Decide the pickup tax question deliberately and move on.
• You deliver and need a date with a daily cap. Order Delivery Date for WooCommerce, free tier. Capacity limits and time slots are in it, 10,000+ installs behind it, and it costs nothing to find out whether you also need cut-offs.
• You promise same-day with a cut-off. Now you are paying. Tyche Pro Starter at $119/yr on one site is the cheaper route and the one with a public free tier you have already tested. Kestrel’s Order Delivery at $149/yr has the cleaner capacity-and-cut-off model and is bundled with CheckoutWC Pro, so if you already pay for that it is effectively free.
• Two or more pickup locations with different stock. Local Pickup Plus at $99/yr. Nothing free does per-location product availability, and working around it with product visibility rules costs more hours than the licence costs dollars.
• Takeaway, food, or anything with a kitchen. Orderable, with your eyes open about the WordPress 6.9.9 tested-up-to flag. The live order dashboard and printed tickets are worth real money on a busy Friday and nothing else here has them. Test it on staging against your WordPress version first.
• Drivers, not dates. Local Delivery Drivers for WooCommerce, free tier, and buy the pro tier when you need route optimisation or proof of delivery. This is a separate problem from scheduling and you can solve it independently.
• Customers book a service rather than receiving goods. Wrong category entirely. A haircut or a consultation is a bookable product with resources and availability rules, not a delivery date — WooCommerce booking plugins compared is the list you want.

Frequently asked questions

The short version

Name your layer first. Scheduling, locations or dispatch — and then check whether WooCommerce core already covers the thin version of it, because for single-location pickup and flat-rate zone delivery it does, for nothing.

After that the money is easy to predict. A delivery date with capacity limits is free. Same-day with a cut-off is $119 to $149 a year. A second pickup location is $99 a year. Distance-based pricing is $99 a year plus a Google API bill. Drivers are free until you want route optimisation. Nothing in this category should cost you more than that, and if a vendor is quoting more, they are selling you a layer you have not established you need.

Then spend your first week on the two things that actually break local delivery stores: whether your cut-off is correct at 2:01pm in the right time zone, and whether the slot capacity you configured is really being enforced. Neither is on a feature comparison page, including this one, and both cost you a Saturday when they are wrong.