Domains and Modules

Domains the platform models

• restaurant — recipes, modifiers, menu sections
• boutique — variants by size/color/style
• pharmacy / drugstore — lots, expiration, prescription gating
• retail — assortments, returns, reorder points
• distributor — bulk pricing tiers, multi-warehouse routing
• grocery — unit/weight/package, perishables
• hardware — technical specs, BOMs
• appliance — serial numbers, warranty windows
• mixed — any combination above

Each domain shapes the model: recipes for restaurants, lots for pharmacies, serials for appliances, weight pricing for grocery.

Modules

tenancy, identity, catalog, inventory, ordering, payments, pricing, purchasing, suppliers, customers, audit, graph_sync, reporting.

Each module owns its tables and emits its own outbox events. Cross-module calls go through public service interfaces or domain events — never direct table reads.