Stock-Aware Checkout and Store Collection

Solution design

Collection promises backed by store confirmation

The collection service connects stock reservations, store picking, payment activity and handover through one order reference. Availability includes existing holds and the freshness of stock information. Each item retains its own fulfilment state, so a shortage or partial collection has an explicit next action. Staff confirm the goods physically set aside before sending the collection message.

Online availability accounts for reservations and stock freshness. Store teams receive a clear picking task, customers hear when their items are physically ready, and support can see what happened to each order line.

• Availability that reflects fulfilment rules
• Clear picking and collection responsibilities
• Item-level handling of shortages and refunds

Business context

A retailer serving shoppers through an online store and physical locations, with collection and delivery options.

Core capability

Software Development

An available item still has to reach the counter

A stock count describes inventory, but collection is a promise about a particular item at a particular place. Display stock, damaged goods, existing reservations and items awaiting receipt affect that promise differently. A location can show a positive balance and still be unable to fulfil the next online order.

The checkout therefore uses a defined availability rule for each fulfilment method. It considers saleable stock, active reservations, any agreed buffer and the age of the latest update. A stale feed is visible to the availability service. It does not silently carry the same confidence as a recent store update, especially when only a small quantity remains.

The same item needs the same identity everywhere

The integration maps the product variant, store location and stock movement across the commerce platform, inventory system and point of sale. Similar descriptions are insufficient: a size or colour mismatch can turn an apparently valid reservation into an impossible picking task. Unmatched identifiers go to review instead of being guessed from names.

Inventory states also have agreed meanings. On-hand, saleable, reserved and in-transit quantities remain distinct. Retail owns the stock adjustments, commerce owns the customer promise, and finance owns the treatment of payments and reversals. These responsibilities define which system can change each fact and how the other systems learn about it.

Payment, picking and collection move at different speeds

A stable order reference links the customer request, line items, reservations, payment activity and fulfilment tasks. Each has its own state. A payment may be authorised while picking is still pending; one line may be ready while another is unavailable. A single status such as processing conceals those differences and makes partial orders difficult to handle.

Reservations protect accepted quantities for a defined period. Expiry and cancellation release them through repeat-safe operations, so a retried event cannot release stock twice. The system retains event identifiers and timestamps for reconciliation. Store staff see the task they can act on, while support can inspect the wider history when a customer asks about a delay.

The ready message follows a physical check

Checkout confirms the selected location and service before reserving the items. Once the order is accepted under the payment rules, the store receives a picking task with variant details and an expected action. Staff locate the goods and confirm the quantity actually set aside. That confirmation triggers the collection message, including the location and reference needed at handover.

At collection, staff verify the order reference and mark the handed-over lines. Inventory and order history update without re-entering the transaction elsewhere. A partial collection leaves the remaining lines open with their own next step. Customer communication reflects that distinction, rather than describing the entire order as complete because one bag has left the counter.

A missing item creates a decision, not a silent substitution

The picking screen records a shortage when an item is damaged or cannot be found. The customer-facing team can offer an approved alternative, another location or a cancellation according to the retailer's policy. The system retains the original request and the customer's choice. Reservations and payment adjustments follow that choice instead of being released by an unrelated stock update.

Duplicate payment callbacks, disconnected store devices and expired holds are tested as part of the same workflow. An uncertain payment is reconciled before staff repeat a charge or refund. Picking, handover and financial actions have separate permissions, and payment details remain with the payment provider. Exception records include enough context for recovery without exposing unnecessary customer information.

Collection starts with a controlled assortment

The first release covers selected locations and products whose identifiers and stock rules can be reconciled. The team checks the complete promise from checkout to counter before adding more fulfilment choices. Store rehearsals include an item sold just before picking, a customer cancellation and a payment update arriving late.

Parallel reconciliation compares accepted orders, reservations, stock changes and payment records. Differences are investigated at line level, where partial fulfilment becomes visible. Staff training includes the exception actions as well as the normal pick. A new location joins through a readiness checklist covering stock mapping, notifications and ownership, rather than a copy of another branch's settings.

The exception queue has named owners

Store teams own picking and physical handover. Commerce owns the availability rules and customer-facing status. Finance handles payment discrepancies, while technical operations maintains event delivery and integration recovery. The order record routes each unresolved issue to the team able to change it, with escalation when that action does not happen.

A daily operational review separates stock inaccuracies from missed picking tasks, identifier errors and payment delays. They can produce the same customer complaint but need different fixes. Recovery tools replay an event with its original reference and show the effect before another attempt. Replaying a failed update must not send another ready message or issue a second refund.

Every accepted line should reach a known outcome

The core check follows each accepted order line to collection, delivery or a recorded cancellation. It compares that outcome with the availability shown at checkout. Shortages are grouped by cause and location, so the team can distinguish an overly generous promise from a store inventory problem or a delayed feed.

Picking wait, collection readiness and unresolved financial differences provide complementary views. Faster picking does not help if ready messages are premature, and a successful payment does not prove the item was handed over. Reviewing these records together shows where the collection service breaks down and which owner can make the next practical correction.

The choices behind the solution

How the solution is evaluated

These measures define the evaluation criteria for the workflow, its controls and the quality of completed tasks.