Skip to content

Omnichannel Patterns

Formal patterns for recurring Unified Commerce design problems.

A UC-BoK Pattern documents a proven solution to a recurring omnichannel challenge. Each pattern specifies the context, forces, solution sequence, required capabilities (with minimum maturity level), and trade-offs.


Pattern Library

Pattern Classification Minimum Capabilities
BOPIS fulfillment-pattern basket-management ≥ 3, inventory-visibility ≥ 3
Ship from Store fulfillment-pattern order-orchestration ≥ 3, fulfillment-execution ≥ 3
Endless Aisle commerce-pattern catalogue-management ≥ 3, channel-management ≥ 2
BORIS post-sale-pattern order-management ≥ 3, returns-management ≥ 3
Reserve and Collect fulfillment-pattern inventory-reservation ≥ 3, store-operations ≥ 2
Self-Checkout commerce-pattern checkout ≥ 3, payment-processing ≥ 3

Pattern Structure

Each pattern is documented with:

  • Context — when to apply the pattern
  • Forces — tensions the pattern resolves
  • Solution — the recommended approach
  • Sequence Diagram — Mermaid interaction flow
  • Business Objects — BOs created or modified, with state transitions
  • Capabilities Required — minimum maturity level per capability
  • Trade-offs — benefits, risks, known issues

Capability Prerequisites by Pattern

Use this matrix to assess whether your organisation is ready to implement each pattern, using your Assessment Framework scores.

Pattern Critical Prerequisites
BOPIS basket-management ≥ 3 + inventory-visibility ≥ 3 + checkout ≥ 3
Ship from Store order-orchestration ≥ 3 + store-operations ≥ 3
Endless Aisle catalogue-management ≥ 3 + order-orchestration ≥ 3
BORIS order-management ≥ 3 + returns-management ≥ 3 + payment-processing ≥ 3
Reserve and Collect inventory-reservation ≥ 3 + inventory-visibility ≥ 3
Self-Checkout checkout ≥ 3 + payment-processing ≥ 3 + store-operations ≥ 3