Specialty Retail Reference Architecture¶

RA-003 | Unified Commerce end-to-end model for specialty retail
Classification: reference-architecture · Vertical: Specialty Retail

Industry Profile¶

Specialty retail is architecturally distinct from both fashion and grocery in four defining ways:

Representative brands: Apple, Best Buy, MediaMarkt, IKEA, REI, Decathlon, Sephora, Ulta, Home Depot, Lowe's, B&Q, LEGO, GameStop, Barnes & Noble, L'Occitane.

Capability Map¶

Maturity levels: 0 Absent · 1 Aware · 2 Fragmented · 3 Integrated · 4 Optimised

Critical Capabilities (MVP ≥ 3)¶

Important Capabilities (MVP 2, scale to 4)¶

Standard Capabilities (MVP 1–2)¶

Critical Processes¶

graph TD
    subgraph "Revenue & Conversion"
        CLI[Clienteling Sale]
        ENL[Endless Aisle]
        CHK[Checkout]
    end
    subgraph "Fulfilment"
        BOP[BOPIS]
        SFS[Ship from Store]
    end
    subgraph "Post-Purchase Service"
        RET[Return Anywhere]
        EXC[Exchange Anywhere]
    end
    subgraph "Customer Lifetime Value"
        LOY[Loyalty Enrollment]
        REG[Customer Registration]
    end

    CLI --> CHK
    ENL --> CHK
    CHK --> BOP
    CHK --> SFS
    CHK --> RET
    RET --> EXC
    REG --> LOY
    LOY --> CLI

Application Landscape¶

graph LR
    subgraph "Customer Touchpoints"
        MOB[Mobile App]
        WEB[eCommerce]
        POS_[POS / mPOS]
        KIOSK[Product Kiosk]
    end

    subgraph "Commerce Core"
        OMS[OMS]
        CPQ[CPQ / Configurator]
        CRM[CRM / Clienteling]
        PRICE[Pricing Engine]
        PROMO[Promotions Engine]
        LOY_[Loyalty Platform]
    end

    subgraph "Supply Chain & Fulfilment"
        WMS[WMS]
        INV[Inventory Visibility]
        FSM[Field Service Management]
    end

    subgraph "Customer Data"
        CDP[CDP]
        ID[Customer Identity]
    end

    MOB --> OMS
    WEB --> OMS
    POS_ --> OMS
    KIOSK --> CPQ
    CPQ --> OMS
    CRM --> POS_
    CRM --> MOB
    PRICE --> OMS
    PROMO --> OMS
    LOY_ --> CRM
    OMS --> WMS
    OMS --> FSM
    WMS --> INV
    CDP --> CRM
    ID --> CDP

Application Role Map¶

Integration Topology¶

graph TD
    POS_["POS / mPOS"]
    OMS_["OMS"]
    CPQ_["CPQ"]
    CRM_["CRM/Clienteling"]
    INV_["Inventory Visibility"]
    FSM_["FSM"]
    ERP_["ERP / Finance"]
    ECOM_["eCommerce"]

    POS_ -->|order.created| OMS_
    CPQ_ -->|configuration.confirmed| OMS_
    CRM_ -->|customer.context| POS_
    OMS_ -->|inventory.reserve| INV_
    OMS_ -->|service.scheduled| FSM_
    OMS_ -->|payment.settled| ERP_
    INV_ -->|atp.updated| ECOM_
    INV_ -->|atp.updated| POS_
    FSM_ -->|service.completed| OMS_
    ECOM_ -->|order.placed| OMS_

Canonical integration events for Specialty Retail:

Operational Experience View¶

Specialty retail involves the highest associate skill density of the three verticals. The Operational Experience Layer maps five actor types across eight priority journeys.

Actor Types¶

Priority Journeys by Maturity¶

Specialty-Specific Operational Patterns¶

1 — Guided Configuration at POS The Expert Advisor uses a tablet CPQ to walk the customer through compatibility and customisation choices (processor, RAM, colour, fabric, accessory bundles). The configured item is added directly to the POS basket with locked pricing. Associates cannot override CPQ rules — validation happens at configuration, not at checkout.

2 — Trade Account Fast Lane B2B/Pro customers bypass standard loyalty enrollment and enter a verified trade account flow. Identity verification (trade card, account code) unlocks a separate price list, purchase order reference field, and invoicing checkout path. CRM flags the account type and Pricing Engine switches rule-set in real time.

3 — Post-Purchase Service Continuity Installation, repair, and rental bookings are created as service order lines on the original OMS order. FSM receives the job schedule; CRM shows the service status alongside purchase history. When the service is completed, FSM writes service.completed → OMS updates the order → Loyalty awards post-service points. The customer sees one timeline, not separate product and service records.

Architectural Patterns¶

Pattern A — Expert Selling Engine¶

sequenceDiagram
    participant A as Expert Advisor (mPOS)
    participant CRM as CRM/Clienteling
    participant CAT as Catalogue/CPQ
    participant INV as Inventory Visibility
    participant OMS as OMS

    A->>CRM: Look up customer profile
    CRM-->>A: Purchase history + preferences
    A->>CAT: Search compatible products
    CAT-->>A: Product options + bundle rules
    A->>INV: Check real-time ATP
    INV-->>A: In-store + warehouse stock
    A->>CAT: Confirm configuration
    CAT-->>OMS: configuration.confirmed
    OMS-->>A: Basket updated

When to apply: Any sub-vertical where associate knowledge drives conversion (electronics, sports, beauty, DIY). Requires CRM integration on the POS/mPOS and real-time inventory access.

Anti-pattern: Locking the associate to a desktop POS — mobile-first associate tooling is mandatory for floor-based guided selling.

Pattern B — Product Configuration at Checkout¶

sequenceDiagram
    participant C as Customer
    participant POS_ as POS/eCommerce
    participant CPQ as CPQ/Configurator
    participant PRICE as Pricing Engine
    participant OMS as OMS

    C->>POS_: Select base product
    POS_->>CPQ: Open configuration session
    CPQ-->>C: Present options (spec, accessories, warranty, service)
    C->>CPQ: Confirm selections
    CPQ->>PRICE: Calculate bundle price
    PRICE-->>CPQ: Locked price
    CPQ->>OMS: configuration.confirmed (line items)
    OMS-->>POS_: Basket updated
    C->>POS_: Proceed to payment

When to apply: Electronics, furniture, garden/outdoor, DIY — any product requiring specification choice or accessory selection before purchase. Configuration rules in CPQ prevent invalid combinations and enforce manufacturer constraints.

Pattern C — Post-Purchase Service Loop¶

sequenceDiagram
    participant OMS as OMS
    participant FSM as Field Service Mgmt
    participant TECH as Technician (Mobile)
    participant CRM as CRM
    participant LOY as Loyalty

    OMS->>FSM: service.scheduled (installation/repair)
    FSM->>TECH: Job assigned
    TECH->>FSM: service.completed
    FSM->>OMS: Update service order line
    OMS->>LOY: Award post-service points
    OMS->>CRM: Update customer service history
    CRM-->>Customer: Service completion notification

When to apply: Electronics (installation, repair), furniture (delivery + assembly), sports (bike service, boot fitting), DIY (tool hire return).

Pattern D — B2B/B2C Account Split¶

graph LR
    ID[Customer Identity] -->|account-type: B2B| B2B_FLOW[Trade Checkout]
    ID -->|account-type: B2C| B2C_FLOW[Consumer Checkout]
    B2B_FLOW --> PRICE_B2B[Trade Price List]
    B2B_FLOW --> INVOICE[Invoice / PO Reference]
    B2C_FLOW --> PRICE_B2C[Consumer Price List]
    B2C_FLOW --> LOYALTY[Loyalty Earn]
    PRICE_B2B --> OMS_[OMS]
    PRICE_B2C --> OMS_

When to apply: Home Depot Pro, Best Buy for Business, B&Q Trade — any specialty format serving both consumers and professionals. Customer Identity must resolve account type before pricing or checkout rules are applied.

Comparison with Other Verticals¶

This architecture is one of three canonical UC-BoK Reference Architectures. See the Cross-Vertical Comparison for a structured comparison across Fashion, Grocery, and Specialty Retail.