Vertical Reference Architecture Comparison¶

Cross-vertical analysis of UC-BoK Reference Architectures — structural differences, capability priorities, and architectural trade-offs across retail verticals.

Available Reference Architectures¶

Code	Vertical	Status
RA-001	Fashion Retail	Active
RA-002	Grocery Retail	Active
RA-003	Specialty Retail	Active

Structural Comparison¶

Dimension	Fashion	Grocery	Specialty
Avg basket value	£80–200	£20–35	£100–2 000+
Transaction frequency	1–2×/month	2–3×/week	1–6×/year
Returns rate	25–35% online	< 2% (fresh non-returnable)	10–20% (often serialised)
Primary operational KPI	Clienteling conversion, basket size	Transaction throughput, queue time	Conversion rate, attach rate, NPS
Associate role	Styling & clienteling	Operational (picking, checkout)	Expert selling & configuration
Top loyalty driver	Personalised styling, early access	Personalised price, multi-buy offers	Community / Co-op / Pro tier
B2B exposure	Low	Medium (catering, foodservice)	High (trade, professional accounts)
Configuration complexity	Low–Medium	Low	High (CPQ, compatibility rules)
Post-purchase service	Returns & exchanges (high volume)	Minimal (FMCG)	Service, repair, rental (high value)
MVP maturity target (UCMI)	2.0 – 2.5	2.5 – 3.0	2.0 – 2.5
BIC maturity target (UCMI)	3.5 – 4.0	3.5 – 4.0	3.5 – 4.0

Capability Priority Comparison¶

Mission-Critical Capabilities¶

Capability	Fashion MVP	Fashion BIC	Grocery MVP	Grocery BIC	Specialty MVP	Specialty BIC
`basket-management`	🟩 3	🟦 4	🟦 4	🟦 4	🟩 3	🟦 4
`checkout`	🟩 3	🟦 4	🟦 4	🟦 4	🟩 3	🟦 4
`promotions`	🟩 3	🟦 4	🟦 4	🟦 4	🟧 2	🟩 3
`payment-processing`	🟩 3	🟦 4	🟦 4	🟦 4	🟩 3	🟦 4
`order-management`	🟩 3	🟦 4	🟩 3	🟦 4	🟩 3	🟦 4
`inventory-visibility`	🟩 3	🟦 4	🟩 3	🟦 4	🟩 3	🟦 4
`fulfillment-execution`	🟩 3	🟦 4	🟩 3	🟦 4	🟧 2	🟦 4
`returns-management`	🟩 3	🟦 4	🟨 1	🟧 2	🟧 2	🟦 4
`catalogue-management`	🟩 3	🟦 4	🟩 3	🟦 4	🟩 3	🟦 4
`loyalty`	🟧 2	🟦 4	🟩 3	🟦 4	🟩 3	🟦 4
`clienteling`	🟧 2	🟦 4	🟥 0	🟨 1	🟩 3	🟦 4
`customer-profile`	🟧 2	🟦 4	🟧 2	🟩 3	🟩 3	🟦 4
`exchange-management`	🟧 2	🟦 4	🟥 0	🟨 1	🟧 2	🟩 3
`store-inventory`	🟧 2	🟩 3	🟩 3	🟦 4	🟧 2	🟩 3
`store-operations`	🟧 2	🟩 3	🟩 3	🟦 4	🟩 3	🟦 4
`pricing`	🟧 2	🟩 3	🟩 3	🟦 4	🟧 2	🟩 3
`subscription-management`	🟥 0	🟧 2	🟨 1	🟩 3	🟧 2	🟦 4

Critical Process Coverage by Vertical¶

Process	Fashion	Grocery	Specialty
Checkout	🔴 Critical	🔴 Critical	🔴 Critical
BOPIS	🔴 Critical	🔴 Critical	🔴 Critical
Customer Registration	🟠 Important	🟠 Important	🔴 Critical
Loyalty Enrollment	🟠 Important	🟠 Important	🔴 Critical
Clienteling Sale	🔴 Critical	—	🔴 Critical
Endless Aisle	🔴 Critical	—	🟠 Important
Ship from Store	🔴 Critical	—	🟠 Important
BORIS	🔴 Critical	—	🟠 Important
Return Anywhere	🟠 Important	—	🟠 Important
Exchange Anywhere	🟠 Important	—	🟠 Important
Self-Checkout	🟡 Standard	🔴 Critical	🟡 Standard
Scan and Go	🟡 Standard	🔴 Critical	—
Voucher Redemption	🟡 Standard	🟡 Standard	🟡 Standard

Unique Architectural Requirements by Vertical¶

Requirement	Fashion	Grocery	Specialty
Size × colour matrix (SKU explosion)	✅ Required	—	—
Seasonal markdown cascade	✅ Required	—	—
Weighted / variable-measure items	—	✅ Required	—
Perishable inventory (batch/lot, FIFO)	—	✅ Required	—
Fresh markdown (near-expiry automation)	—	✅ Required	—
Age verification interrupt	—	✅ Required	—
Multi-buy rule engine (BOGOF, 3-for-2)	—	✅ Required	—
Scale integration at POS/SCO	—	✅ Required	—
Food stamp / EBT tender	—	✅ Required (US)	—
CPQ / product configuration	—	—	✅ Required
B2B/Pro account split at checkout	—	—	✅ Required
Field Service Management integration	—	—	✅ Required
Post-purchase service order line	—	—	✅ Required
Serialised / high-value item tracking	—	—	✅ Required
Subscription (protection plan, rental)	—	—	✅ Required
BNPL tender (Klarna, Afterpay)	✅ Required	—	✅ Required
Clienteling associate app (mobile)	✅ Required	—	✅ Required

Architectural Decision Pivot Points¶

When selecting a Reference Architecture baseline for an implementation, the following decision questions identify the correct vertical starting point:

Question	Fashion	Grocery	Specialty
Is transaction throughput the primary KPI?	No	Yes	No
Is associate knowledge the primary conversion lever?	Partially	No	Yes
Are products sold in size/colour variants?	Yes	No	Sometimes
Are products perishable with batch/FIFO tracking?	No	Yes	No
Does the product require configuration before purchase?	No	No	Yes
Is post-purchase service a significant revenue stream?	No	No	Yes
Do you serve professional/B2B accounts?	Rarely	Occasionally	Often
Are returns > 15% of revenue?	Yes	No	Sometimes

UC-BoK Reference Architecture Library — v1.0-alpha