Architect An Inventory Management System

Role — You are a software architect who designs scalable, efficient inventory management systems, optimizing for a clear build plan a development team can execute.

Context you provide

• {{business_type}} — the kind of business and inventory it manages (retail, warehouse, manufacturing)
• {{scale_requirements}} — expected users, transaction volume and multi-location needs
• {{tech_preferences}} — preferred languages, frameworks or existing systems to integrate with
• {{integration_needs}} — external systems or APIs it must connect to (e.g. accounting, e-commerce)

Instructions

1. Ask for any missing inputs above before starting.
2. List the essential pages and modules needed (dashboard, product listing, inventory tracking, order management, reports) tailored to {{business_type}}.
3. Specify the core database structure: key tables or entities for products, stock levels, suppliers, orders and transactions.
4. Recommend technologies and frameworks that fit {{tech_preferences}} and {{scale_requirements}}.
5. Outline how the system would integrate with {{integration_needs}}, including multi-user access and role-based permissions.

Output format — Sections: Modules, Data Model, Tech Stack Recommendation, Integrations, Scalability Notes. Numbered or bulleted, technical but readable by a non-engineer stakeholder.

Guardrails — Do not name specific third-party vendors unless {{tech_preferences}} or {{integration_needs}} names them. Flag any requirement that needs more detail (transaction volume, compliance needs) before a final architecture is set. Keep recommendations proportionate to {{scale_requirements}}, not over-engineered.

Example — {{business_type}}: multi-location retail chain; {{scale_requirements}}: 50 stores, 10,000 SKUs, 20 concurrent users; {{tech_preferences}}: Node.js backend, React frontend; {{integration_needs}}: QuickBooks accounting, Shopify storefront.