Ship To Store · STS / Click to Store¶
Customer places an online order for collection at a chosen store while stock is sourced from a warehouse or distribution centre rather than local store inventory. The scenario coordinates payment, warehouse fulfillment, inter-node movement, and store handover so the collection experience remains consistent with unified commerce.
| Domains | order · fulfillment · store |
| Actors | customer · warehouse-operator · store-associate · store-manager |
| Process | Ship To Store |
| Capabilities | 7 |
| Steps | 10 |
| Events | 16 |
| Lifecycles | 5 |
| Min UCMI | 2.7 |
⚙️ Step-by-Step Flow¶
| # | Step | Actor | Lifecycle | State Change | Event |
|---|---|---|---|---|---|
| 1 | Confirm ship-to-store checkout | customer | basket-lifecycle |
ready-for-checkout → locked | basket-checkout-started |
| 2 | Authorise payment | system | payment-lifecycle |
pending → authorised | payment-authorized |
| 3 | Create customer order | system | order-lifecycle |
draft → confirmed | order-created · order-confirmed · basket-converted |
| 4 | Allocate warehouse inventory | system | fulfillment-order-lifecycle |
created → allocated | inventory-allocated |
| 5 | Route fulfillment to source and destination nodes | system | fulfillment-order-lifecycle |
allocated → released | order-routed · fulfillment-order-created |
| 6 | Pick order at warehouse | warehouse-operator | fulfillment-order-lifecycle |
released → picking | picking-started |
| 7 | Pack and dispatch to store | warehouse-operator | fulfillment-order-lifecycle |
picking → dispatched | picking-completed · shipment-packed · fulfillment-order-dispatched |
| 8 | Receive and stage at collection store | store-associate | fulfillment-order-lifecycle |
dispatched → ready-for-collection | store-task-completed |
| 9 | Capture payment and notify customer | system | payment-lifecycle |
authorised → captured | payment-captured · customer-communication-sent |
| 10 | Hand over order and close transaction | store-associate | order-lifecycle |
in-fulfilment → completed | order-closed |
⚡ Event Sequence¶
basket-checkout-started → payment-authorized → order-created → order-confirmed → basket-converted → inventory-allocated → order-routed → fulfillment-order-created → picking-started → picking-completed → shipment-packed → fulfillment-order-dispatched → store-task-completed → payment-captured → customer-communication-sent → order-closed
🔄 Lifecycles Involved¶
basket-lifecycleorder-lifecyclepayment-lifecyclefulfillment-order-lifecycletill-session-lifecycle
🧩 Capabilities Required¶
| Capability | |
|---|---|
checkout |
Checkout |
order-management |
Order Management |
order-orchestration |
Order Orchestration |
fulfillment-execution |
Fulfillment Execution |
inventory-allocation |
Inventory Allocation |
store-operations |
Store Operations |
payment-processing |
Payment Processing |
🖥️ Application Coverage¶
Applications that implement the capabilities required by this scenario.
| Capability | Implementing Applications |
|---|---|
checkout |
POS · eCommerce Platform · Associate Workspace |
order-management |
OMS · eCommerce Platform |
order-orchestration |
OMS |
fulfillment-execution |
SIM · WMS · FMS · POS · Associate Workspace · Carrier Platform |
inventory-allocation |
WMS · Inventory Service |
store-operations |
POS |
payment-processing |
POS · Payment Hub |
📊 Readiness by Profile¶
Capability readiness across assessment profiles.
| Profile | Capabilities Met | Avg Score | Ready? |
|---|---|---|---|
| Acme Electronics | 5/7 | 1.9 | ❌ |
| BuildPro Trade | 7/7 | 2.7 | ✅ |
| Flash Delivery | 7/7 | 3.1 | ✅ |
| Luxe Maison | 3/7 | 1.7 | ❌ |
| Metro Fresh Group | 6/7 | 2.4 | ❌ |
| Stella Fashion Group | 6/7 | 2.3 | ❌ |
| Reference Tier 2 Non-food Retailer | 7/7 | 2.9 | ✅ |
✅ Preconditions¶
- Customer has selected a store that accepts ship-to-store collections
- Warehouse or DC inventory is available for the requested item
- Inter-node transfer service and store receiving processes are active
- Payment method can be authorised online before fulfillment starts
🎯 Success Criteria¶
- Order is fulfilled from warehouse stock and staged at the chosen store within SLA
- Customer receives clear pickup notification only after the item is ready for collection
- Payment is captured without requiring a second checkout journey
- Order and fulfillment audit trail show both source node and collection node clearly
⚠️ Failure Modes¶
- Warehouse allocation fails after checkout, requiring re-route or cancellation
- Transfer shipment arrives late, causing missed collection promise
- Store receives damaged or incomplete goods and cannot release the order
- Customer notification is sent before store staging is completed
- Payment capture fails after arrival at store, forcing manual intervention
UCMI Requirements¶
Minimum UCMI Score: 2.7
| Capability | Minimum Level |
|---|---|
checkout |
🟠 2 |
order-management |
🟠 2 |
order-orchestration |
🟠 2 |
fulfillment-execution |
🟠 2 |
inventory-allocation |
🟠 2 |
store-operations |
🟠 2 |
payment-processing |
🟠 2 |
UC-BoK Scenario Catalog · All Scenarios · Scenario Catalog