How to test click-and-collect availability by branch

Test click-and-collect inventory by branch. Keep IP location, saved store, pickup promise and the retailer’s inventory feed separate in your results.

A shopper checks her phone outside a store marked for order pickup.

A shopper can be sitting in Toronto and still have a Vancouver branch saved from a previous visit. The IP address and the selected store represent different things. A pickup test is only useful when the report identifies them both.

Give each branch a fixture

Choose an owned or participating store with a known item on its local inventory feed. Open a fresh session from the intended market, explicitly select the store and record its branch code. Capture the pickup message and promised collection date. Repeat with a store that should have a different outcome. Test an item that is unavailable as carefully as an item in stock. Google Merchant Center local inventory specification.

Trace a failed promise

If both stores say “ready today,” inspect the selected branch after a page reload. A fallback to a default store can look exactly like stale inventory. Keep the expected feed timestamp alongside the storefront result so the merchant can tell whether the mismatch reached the customer before or after the latest stock update. Ask XtremeProxy for the exit region your release involves.

A useful two-branch control is an item the retailer knows is stocked only at branch A. If branch B also promises same-day collection, save the branch visible at checkout. If checkout quietly changed to A, the problem is location persistence. The inventory system may have been correct throughout.

One postcode, two pickup counters

Two counters share a postcode and the same retailer branding. One carries the test kettle and the other receives it from a warehouse in three days. Open the location chooser, select each counter by its branch identifier and record the promised collection day. If the detail page offers same-day pickup at both but the cart quotes Thursday for the second, verify which branch the cart actually retained. A map pin or postcode alone cannot tell the inventory team which promise to correct.

Check the last reservable unit

Available for collection can mean ready on a shelf, transferable from another store, or reservable for tomorrow. Ask the branch owner which promise the interface makes. Keep closing time and reservation cutoff distinct. A store that closes at eight may stop accepting same-day reservations at six.

Collection slots can fill even while the shelf count stays positive. Prepare a fixture with one unit on hand and no bookable pickup slot. The stock control and the scheduling control should give the customer a coherent explanation. The branch needs to know which constraint prevented the reservation.

When closing time changes the promise

Take a sample branch open until 20:00 with a same-day preparation cutoff at 18:00. At 17:55 the expected message is pickup today, subject to stock. At 18:05 tomorrow can be correct while the branch is still open. Reproduce both times in the merchant's staging clock or historical fixture. Selecting a new regional route halfway through would introduce a second variable just as the time-based rule changes.

Test what happens when the shopper changes the branch after placing the product in the basket. Use a synthetic item that is immediately collectible at branch A and requires a transfer at branch B. Begin at A, add the item, and use the basket's own selector to change to B. Capture the selected branch and pickup promise on the review screen. The initial product-page promise can be perfectly accurate even if the basket fails to recalculate it after the switch.

Ask a store operator for one test item that can be collected only after a transfer from another branch. That item exposes a subtle failure: a page can correctly say “available” while making the wrong promise about today. On the same regional connection, inspect the pickup slot before and after choosing the branch. Stop before confirming the reservation unless test inventory is available. Record the earliest selectable slot alongside the stock badge so the operations team can distinguish an inaccurate lead time from a missing stock record.

Save one branch pair that regularly exercises different pickup promises. It becomes a useful release fixture each time the store chooser or cart changes. Pickup promises by branch follows the branch selection into the basket. If the selected branch stays correct but the quantity looks old, continue with Measuring a store-level stock feed against the shopper’s view to compare inventory propagation times. Compare XtremeProxy network types.

Frequently asked questions

Should a missing pickup time count as zero stock?

Give the missing promise its own state. The unit may still be sellable at the counter while the reservation service is closed. Ask the branch owner for its pickup calendar before interpreting the observation as an inventory error.

Related articles