Shop

The Shop section is the user-facing commerce workspace at /<orgSlug>/shop. It is a product surface built from discovered store manifests and normalized catalog metadata.

Core flows

1. Browse stores (/shop/stores) Discover verified or discovered merchants, filter by status/category/country, and open detailed merchant pages.

2. Product browsing (/shop/stores/[domain]) Review catalog capabilities (checkout, orders, identity, payment tokens), product stats, and merchant metadata.

3. Product details (/shop/products/[id]) Inspect product images, variants, attributes, pricing, availability, and add to cart when checkout is enabled.

4. Cart and checkout (/shop/cart, /shop/cart/[cartId]/checkout) Items stay scoped to org + user. Checkout exposes accepted payment handlers from the merchant manifest; unsupported stores disable checkout paths clearly.

5. Orders (/shop/orders) Track recent order lifecycle, item counts, and shipment events.

Store capability model

Each store advertises capabilities in the platform catalog and appears in status tiers such as:

• verified
• not_detected
• invalid
• blocked
• unreachable
• pending

Capability flags drive UI affordances:

• Checkout — allow cart conversion flow
• Orders — allow order history and tracking
• Identity linking — optional cross-domain identity handoff
• Payment tokens — merchant-specific payment handling

Checkout boundary behavior

The checkout flow is intentionally explicit about trust boundaries:

• subtotal is computed from the current cart snapshot
• shipping and taxes are resolved by the merchant domain
• card usage remains at merchant level, with Alumia storing session/intent state for reconciliation

Admin visibility

Shopping data also feeds admin model surfaces so operators can monitor:

• store health and manifest sync status
• product catalog freshness
• order volume and order-state trends

This keeps commerce features manageable as store volume grows.