Identify which pickup system the buyer is selecting

Start with the checkout the store actually uses

WooCommerce's Checkout block guide says the checkout page must be assigned in Advanced settings. Record that page's identity and inspect whether it uses the Checkout block, a classic checkout or a different implementation. Editing pickup behavior on a page that is not assigned does not establish what the buyer reaches.

Record the WooCommerce version and any pickup extension used by the store. The core distinction in this guide does not establish the behavior of every extension or customization. If the visible checkout cannot be traced to the expected page, resolve that page assignment before interpreting missing or repeated pickup choices.

Block locations and zone methods have separate settings

Block local pickup depends on enabled pickup locations and the assigned checkout. Inspect the block pickup configuration for the actual locations enabled by the store. A location that exists in those settings is a different configuration record from a Local Pickup shipping method enabled in a shipping zone.

The shipping-zone guide lists Local Pickup among WooCommerce's core zone methods. For zone-based methods, a customer matches the first matching zone in the ordered list and sees that zone's methods. Inspect the matched zone and the enabled Local Pickup method there; checking a similarly named method in a later zone does not explain what this buyer sees.

Do not apply that zone-match rule to block pickup locations merely because both choices contain the word pickup. Keep separate inventories: enabled block locations on one side, and enabled legacy Local Pickup methods with their zone names on the other. Finding one does not establish that the other has been configured, removed or migrated.

Trace the displayed selection to the collection handoff

Use the affected buyer report and available real order records to record the exact pickup label shown, any location selected and the checkout page used at that time. Compare those observations with both inventories. If the label alone does not identify its source, mark it unresolved for the site maintainer instead of deciding from the wording.

Where both systems are configured, inspect the actual presentation for competing or confusing choices. Their coexistence in settings is not proof that every buyer sees two options. Conversely, a single visible label does not prove that all orders use one configuration. Preserve the observation's date and checkout context so the maintainer can trace the choice that was actually offered.

Compare that choice with the handoff staff can carry out: which collection location receives the order, who prepares it, and which genuine instructions the buyer receives. If the order or confirmation does not contain enough information to identify the collection arrangement, record that gap. A selection on checkout is not evidence that staff received usable collection instructions.

Choose the workflow before removing a method

Decide which actual collection locations and handoffs the business intends to support. Then give the maintainer the current checkout type, both configuration inventories and the observed mismatch. A useful change request names the pickup choice to retain or correct, the order information staff need and the buyer instructions that must agree with it.

Do not disable a method merely because it is called legacy, or enable block locations solely because checkout changed. Either decision can alter the choices buyers receive. First identify which configured path is serving the intended collection workflow and account for existing orders that already chose another path. After an authorized change, compare the resulting live display and real order handoff against that agreed requirement.

For a Prism checkout-review consultation, describe the pickup discrepancy and the platform, without sending customer addresses or administrator credentials. Confirm the scope and responsibility for any configuration or implementation work. Pickup functionality does not determine whether a payment provider approves the research-only business or whether a collection arrangement meets applicable requirements.

Pickup-system comparison

Complete both configuration rows even if one system is unused. Record disabled, absent or unconfirmed according to what you actually inspected. The decision is whether the buyer's choice maps to an intended collection handoff, not whether two settings happen to share a label.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.