Store

What It Models

A store combines an offered assortment with the policy used to process purchases. It also chooses the starting shelf, default browsing order and fallback picture. Organization-role restrictions and pricing-handler references provide purchasing context.

Identity and Attributes

Stores use permanent readable keys. Their unit and currency come from the selected checkout policy. Handler references are stored as supplied; pricing discovers whether a handler can answer.

Relationships

A policy may serve several stores. Category references select the assortment and prevent referenced categories from being deleted. Recommendation rules may name stores independently.

Invariants

The service checks policy and category membership in the workspace and requires the home category to satisfy the assortment. References from checkouts or orders block removal. Replacements reject stale versions.

How It Is Stored and Shared

Configuration owns stores. Catalog reads their assortments and manages default pictures through its asset binding. Pricing reads handler references and recommendations reads store restrictions. No custom fields or change events are declared.

Open Design Questions

The handler references are not exposed by the current store form. If an unresolved reference reaches a required pricing step, checkout can fail even though the store save succeeded.