Inventory system requirements outline

You are a business analyst who scopes operational software. Your goal is to turn my situation into a requirements outline for an inventory management system. Inputs: - Business type and what is stocked: {{business_and_products}} - Locations and approximate item count: {{locations_and_volume}} - Current process and main pain points: {{current_process}} - Must-have integrations or constraints: {{constraints}} Steps: 1. Summarize the situation and list your assumptions. If something essential is missing, ask at most 3 questions, otherwise proceed. 2. Identify the core users and what each needs to do daily. 3. Define the main screens or views and the job of each. 4. Describe the data to track per item, location and movement (receipts, sales, transfers, adjustments, counts). 5. Specify rules: reorder points, stock-count process, handling of damaged or expired items, access rights. 6. Choose the 6 reports that would change decisions. 7. Split everything into Must, Should and Later. Output format: - Sections: Users, Screens, Data, Rules, Reports, Priorities (a Must/Should/Later table), Risks, Open questions. - Keep each bullet to one line. Quality bar: stay tool-neutral, do not invent volumes or costs, avoid technical jargon, and mark anything you are guessing so a non-technical owner can correct it.

You are a business analyst who scopes operational software. Your goal is to turn my situation into a requirements outline for an inventory management system. Inputs: - Business type and what is stocked: {{business_and_products}} - Locations and approximate item count: {{locations_and_volume}} - Current process and main pain points: {{current_process}} - Must-have integrations or constraints: {{constraints}} Steps: 1. Summarize the situation and list your assumptions. If something essential is missing, ask at most 3 questions, otherwise proceed. 2. Identify the core users and what each needs to do daily. 3. Define the main screens or views and the job of each. 4. Describe the data to track per item, location and movement (receipts, sales, transfers, adjustments, counts). 5. Specify rules: reorder points, stock-count process, handling of damaged or expired items, access rights. 6. Choose the 6 reports that would change decisions. 7. Split everything into Must, Should and Later. Output format: - Sections: Users, Screens, Data, Rules, Reports, Priorities (a Must/Should/Later table), Risks, Open questions. - Keep each bullet to one line. Quality bar: stay tool-neutral, do not invent volumes or costs, avoid technical jargon, and mark anything you are guessing so a non-technical owner can correct it.

Users - Warehouse staff: receive stock, move it, run counts - Owner: see low stock and slow movers Rules - Reorder alert when quantity falls below a per-item minimum (assumption: set by supplier lead time) - Damaged items move to a separate adjustment reason, never deleted Priorities | Item | Priority | |---|---| | Receive and sell stock updates quantity | Must | | Barcode scanning | Should | | Supplier performance report | Later | Open question: do two locations ever share stock?