Skip to content

Click-and-Collect with Store-Level Stock Visibility

An anonymised engineering account of location-level availability, collection eligibility and staff handoffs, including what to do when stock changes after checkout.

NetSuiteCeligoCustom APISystem IntegrationArchitecture Design

Make collection promises depend on eligible stock

The challenge

Connecting location availability, collection promises and fulfilment decisions.

An anonymised engineering account. Customer identities, operating figures and engagement dates are withheld. The focus is the problem, design decisions and validation, rather than a claim of commercial improvement.

An aggregate stock figure does not tell a customer whether an item can be collected from a particular location. Stock can exist while being reserved, unavailable for sale or unsuitable for a collection promise. A customer-facing promise needs business rules in addition to an inventory feed.

The handoff continues after checkout. Staff need a clear picking instruction, the customer needs an accurate readiness notification, and the business needs a decision when the selected location cannot supply the order.

The approach

Define eligible availability

Map source locations to the destinations that expose availability. Agree the treatment of reservations, stock status, buffers and stale feeds. Separate physical stock from what can be promised for collection, and assign an owner to each rule.

Revalidate the promise

Check eligibility at the relevant order handoff and protect the reservation against concurrent demand. Define what happens if availability changes between browsing, checkout and order acceptance. Avoid confirming readiness merely because a storefront order exists.

Make exceptions explicit

Agree whether a shortage should lead to an alternative location, a transfer, a different delivery method or a customer-service decision. These are operating choices to validate with the business. Do not silently substitute one fulfilment promise for another.

Separate order acceptance from readiness

Send staff a structured instruction through the agreed operating channel. Capture acceptance, picking and readiness as distinct states where the process needs them. Trigger customer communication from the appropriate confirmed state, with an owner for failed notifications.

Account for location capacity

Collection eligibility may also depend on opening hours, staffing or the ability to handle further orders. Keep these rules configurable and reviewable. A stock feed alone cannot establish that a location can fulfil the promise.

Design outcome and validation

The design connects the customer promise to location eligibility and an explicit staff handoff. Exceptions have defined decisions instead of relying on an aggregate stock status or an untracked message.

Validation evidence to retain

Test available stock, concurrent demand, a stale feed, a location that is unavailable for collection, a failed notification and a cancellation after reservation. Check the customer message and ERP state together. Record which team owns each exception and how an operator can recover safely.

Retain the location mapping, reservation rules, acceptance checks and operating instructions. No pickup times, sales uplift, location counts or other customer operating figures are published.

Related projects

Services behind the approach

Let’s connect

Ready for a more connected business?

Tell us where you are and where you want to go. We'll help you work out the next step.

Book a free consultation