Before you send campaign traffic to a Shopify store with local pickup, local delivery, and shipping, decide whether every fulfillment promise survives the real buying path. A method is not traffic-ready because it is enabled in Admin. It is ready when the right buyer can see it, understand the cost and timing, complete payment, receive the correct confirmation, and hand the order to a team that can fulfill it.
- Treat each fulfillment method as an end-to-end promise across inventory, eligibility, timing, cost, payment, confirmation, and staff handoff.
- Shopify's current ship-and-pickup mixed-order capability is restricted; local delivery still cannot share one order with shipping.
- Accelerated payments, address eligibility, product locations, and third-party shipping apps can change which methods appear.
- Run a cart-and-address test matrix before BFCM, a local campaign, a delivery-zone expansion, or any shipping-threshold change.
Audit Shopify local pickup, local delivery, and shipping as three complete buyer journeys. For each method, verify the eligible product, inventory location, buyer address, cost, timing, checkout visibility, payment path, confirmation, and staff workflow. Test incompatible carts explicitly. On Shopify today, local delivery cannot be combined with shipping in one order, while ship-and-pickup in one checkout is a limited Plus and Enterprise feature test rather than a universal capability. If the store cannot state what each cart can do before payment, pause campaign traffic and fix the promise first.
What must be true before you send traffic?
The founder-level decision is whether the store can safely promote local pickup, local delivery, and shipping at the same time. The expensive failure is not a disabled setting. It is paying for traffic that reaches a promise the cart, checkout, payment method, notification, or fulfillment team cannot keep.
This guide is for an established merchant with real orders, local customers, campaign traffic, a seasonal pickup window, or a delivery-zone expansion. It is not a developer tutorial for forcing every method into one checkout. The commercial objective is to prevent wrong orders, hidden options, avoidable support work, and damaged trust before a high-intent buyer pays.
Thankik's point of view from 100+ ecommerce projects is that fulfillment is part of the offer. If the product page says available today, the cart implies free pickup, checkout hides shipping, and the confirmation gives a different timeline, the store has turned internal operations into buyer uncertainty.
Use a five-gate traffic-readiness test
| Gate | Owner question | Pass condition |
|---|---|---|
| Inventory | Can the chosen location fulfill every physical item? | The tested cart maps to stocked inventory at the intended location. |
| Eligibility | Does the method appear for the right product, address, market, and customer? | Eligible buyers see the method; ineligible buyers get a clear alternative. |
| Promise | Are cost, location, cutoff, and timing clear before payment? | PDP, cart, checkout, and confirmation describe the same promise. |
| Payment | Does the method survive the real wallet and device path? | Mobile, desktop, accelerated checkout, and returning-customer paths behave as intended. |
| Operations | Can staff recognize, prepare, notify, and hand off the order? | Order data, notifications, routing, and staff steps match the selected method. |
A single failed gate blocks the promise. Better cart copy cannot repair missing inventory. A correct delivery zone cannot repair a wallet path that makes local delivery disappear. An app cannot repair a staff process that sends pickup orders to the wrong location.
Where does fulfillment confusion usually start?
| Symptom | Commercial meaning | First check |
|---|---|---|
| Customers choose pickup when they needed shipping. | The default or cheapest option is overpowering the real choice. | Checkout labels, option order, cart notice, and whether free pickup looks like free shipping. |
| Shipping disappears for some buyers. | Eligibility or delivery-method setup may be hiding a valid path. | Shipping profiles, zones, products assigned to profiles, local delivery settings, and address tests. |
| Local-delivery and shippable items enter one cart. | The cart may imply one order where Shopify requires two. | Product grouping, pre-checkout messaging, and whether the buyer must split the purchase. |
| Pickup-only event orders still show shipping language. | The checkout copy does not match the operational reality. | Pickup settings, product shipping requirement, checkout language, order notifications, and cart messaging. |
| Support calls increase after checkout changes. | The store has moved the decision burden from UX to customer service. | Recent theme/app/checkout changes and the exact method selected on wrong orders. |
Can one order mix pickup, delivery, and shipping?
Not universally. Shopify's current ship-and-pickup in one order capability is a feature test for Shopify Plus and Enterprise organizations, with broader Plus availability documented for July 1, 2027. It works in checkout, not on the product page or cart, and it creates separate fulfillments under one order. It also does not support local delivery or pickup points, and a buyer can select only one pickup location per order.
| Combination | Current native boundary | Design implication |
|---|---|---|
| Ship + pickup | One checkout order is limited to the current Plus and Enterprise feature test; separate fulfillments are created. | Do not promise this flow to an unsupported store or treat a roadmap date as current availability. |
| Local delivery + shipping | Cannot be combined in one native order; the customer must place two orders. | Explain the split before checkout or separate the buying paths. |
| Pickup + local delivery | The buyer chooses a method based on the eligible cart and location rules. | Keep location, timing, and cart eligibility visible before payment. |
| Multiple pickup locations | The mixed ship-and-pickup flow allows one pickup location per order. | Do not imply that one order can be collected across several stores. |
This boundary should determine the store design. If the business needs local delivery and national shipping for different products, the honest solution may be two orders, separate collections, a pre-checkout selector, or an app-supported workflow. Do not present an impossible mixed promise and hope checkout explains it.
What should the PDP and cart explain?
The product page should state the fulfillment fact that changes the buying decision: pickup-only, available at selected locations, local delivery within a defined area, or shippable to the buyer's market. The cart should resolve product combinations and show the cost or timing condition that checkout will enforce.
| Cart situation | Buyer needs to know | Useful message objective |
|---|---|---|
| Pickup-only item | Where and when collection happens | State the location, readiness timing, and pickup requirement before checkout. |
| Local delivery item | Whether the address is eligible | Invite a postal-code or area check before the buyer invests payment effort. |
| Shippable item with pickup active | That shipping is still available | Keep shipping visible; do not let free pickup read like free shipping. |
| Incompatible mixed cart | Why one checkout cannot fulfill everything | Ask the buyer to split or change the cart before payment. |
| Campaign offer | Whether thresholds and cutoffs differ by method | State the method-specific condition next to the offer, not only in a policy page. |
The goal is not more policy copy. It is to remove the one surprise that would otherwise appear after the buyer commits. A precise notice near availability, subtotal, or the checkout button is more useful than a generic delivery FAQ below the fold.
Which Shopify settings can change eligibility?
For local delivery, Shopify requires the physical products in the cart to be fulfillable from one location that has inventory and local delivery enabled. The shipping address must fall within the location's postal-code or radius zone. A third-party shipping app can conflict, and B2B checkout does not support local delivery.
Payment path matters too. Shopify documents that local delivery works with Shop Pay, but the option may disappear if the buyer starts with Apple Pay, Google Pay, Amazon Pay, or PayPal. That is why an Admin preview and one desktop checkout are not sufficient campaign QA.
| Fix option | Use it when | Risk |
|---|---|---|
| Native settings | Pickup locations, delivery zones, shipping profiles, rates, and inventory locations express the rule. | Correct configuration can still leave weak buyer guidance. |
| Theme or cart copy | The method works, but the buyer meets the promise too late. | Copy cannot repair an eligibility or routing defect. |
| Pickup or delivery app | Scheduling, cutoffs, conditional display, or local operations need stronger controls. | App logic can drift from Shopify profiles, theme messaging, and notifications. |
| Internal operations | The storefront is clear but staff routing, preparation, or handoff fails. | A UX change alone will not fix the fulfillment process. |
| Ecommerce CRO | The issue spans offer, PDP, cart, checkout, payment, support, and campaign readiness. | The scope needs diagnosis, acceptance criteria, implementation, and handoff. |
When is an app, internal fix, or CRO engagement rational?
Stay native when the business rule is simple and the gaps are configuration or copy. Use a specialist app when scheduling, conditional visibility, pickup slots, or delivery controls are genuinely required. Use the internal team when ownership and order handling are the only defects. Choose Ecommerce CRO when several buyer-facing surfaces disagree or the team cannot isolate whether the leak is eligibility, messaging, checkout behavior, payment, or operations.
Doing nothing is defensible only when the method is not being promoted and wrong selections are rare and cheap. Before BFCM, a paid local campaign, a store-opening push, or a shipping-threshold change, that risk changes. Shopify's own peak-season guidance recommends testing BOPIS and local-delivery workflows before the weekend, and its ecommerce testing guidance calls for testing before sales events and after integrations or platform changes.
How should the team QA pickup, delivery, and shipping?
QA should follow buyer paths, not Admin sections. Use representative products, inventory locations, buyer addresses, devices, and payment entry points. Record expected and actual behavior at PDP, cart, checkout, confirmation, notification, and staff handoff.
- Test a pickup-only product from PDP to confirmation on mobile and desktop.
- Test a local-delivery product with an eligible and ineligible address.
- Test a normal shippable product where pickup is also active.
- Test an incompatible local-delivery and shipping cart and confirm the buyer is asked to split it before payment.
- If the store has access, test the ship-and-pickup feature with one pickup location and confirm separate fulfillments.
- Test a cart where free pickup appears beside paid shipping.
- Test Shop Pay and each enabled accelerated wallet because local delivery can disappear when a wallet starts the checkout.
- Confirm order tags, fulfillment method, notifications, staff workflow, and customer-facing copy after purchase.
What acceptance criteria prevent wrong orders?
Acceptance criteria should be written in buyer-visible terms. Do not stop at pickup enabled or rates configured. Define what a buyer with a specific cart and address can see, choose, understand, and complete.
- Pickup availability, location, and readiness timing are visible before the buyer commits.
- A shippable product still shows shipping when pickup or local delivery is also active.
- A local delivery option appears only when the address or area is eligible.
- An unsupported mixed cart clearly asks the buyer to split or change the order before payment.
- Free pickup never reads like free shipping in subtotal, delivery method, or confirmation context.
- Pickup date, pickup location, delivery window, shipping cost, and shipping speed are visible before final payment.
- Cart, checkout, confirmation email, staff order view, and customer support language describe the same method.
- The internal team knows who owns future changes to products, rates, locations, pickup windows, and notices.
The first-party signal here is directional, not proof of conversion impact: the existing article received 15 US Search Console impressions with no clicks and an average position of 14.93; the query local pick up Shopify received five impressions at an average position of 15.2. That supports refreshing the answer around the merchant's readiness decision. It does not prove that fulfillment confusion caused lost sales.
Need pickup, delivery, and shipping to stop confusing buyers?
Thankik can audit the complete fulfillment promise across offer, product pages, cart, checkout, payment paths, notifications, and staff handoff, then turn the findings into prioritized fixes and launch acceptance criteria.
FAQ
Can Shopify show local pickup, local delivery, and shipping together?
Yes, a Shopify store can offer all three methods, but they are not universally compatible in one order. Eligibility depends on products, inventory locations, addresses, shipping profiles, delivery zones, checkout capability, payment path, and apps.
Why do customers choose pickup by mistake on Shopify?
Customers often choose pickup by mistake when free pickup appears beside paid shipping, delivery options are collapsed, labels are unclear, or the cart does not warn that the product is local-only before checkout.
Can Shopify combine local delivery and shipping in one order?
No. Shopify documents that local delivery cannot be combined with shipping in one order, so the customer must place two separate orders. The store should explain or prevent the incompatible mix before payment.
Can Shopify combine shipping and pickup in one order?
Only in Shopify's current ship-and-pickup feature test for Plus and Enterprise organizations. The choice happens in checkout, supports one pickup location, creates separate fulfillments, and does not include local delivery or pickup points.
Why can local delivery disappear in Shopify checkout?
Local delivery can disappear when the cart is not fulfillable from one eligible location, inventory is unavailable there, the address is outside the delivery zone, a third-party shipping app conflicts, or the buyer starts checkout with an unsupported accelerated wallet.
Is a pickup and delivery app always needed?
No. Native Shopify settings are enough when locations, zones, profiles, rates, inventory, and simple messaging express the business rule. An app is rational for scheduling, cutoffs, conditional visibility, or local operations Shopify cannot express cleanly.
When is this an Ecommerce CRO issue?
It is an Ecommerce CRO issue when unclear fulfillment options cause wrong orders, checkout hesitation, support calls, or abandoned carts. The problem then spans buyer confidence, cart messaging, checkout clarity, and operational handoff.
Sources and verification notes
- Shopify Help Center, Setting up pickup in store for online orders, retrieved 2026-09-28
- Shopify Help Center, Setting up local delivery for online orders, retrieved 2026-09-28
- Shopify Help Center, Delivery methods, retrieved 2026-09-28
- Shopify Help Center, Ship and pickup in one order in Shopify Checkout, retrieved 2026-09-28
- Shopify, BFCM campaigns: test BOPIS and local delivery before the weekend, retrieved 2026-09-28
- Shopify, Ecommerce testing guide, retrieved 2026-09-28