Define the item and its units
List products, sellable variants, SKUs, barcodes where used and units such as each, box or length. Specify whether a supplier pack can be split and which conversions are allowed. Keep supplier codes separate from the business's stable item identity when they serve different purposes.
Illustrative example, not a client result: a box contains several units, but orders may be fulfilled individually. A receipt of two boxes must not be interpreted as two individual units. Save expected calculations before selecting screens.
Record why stock changes
Describe receiving, put-away, transfers, reservation, picking, dispatch, returns, damage and count adjustments for the actual business. Identify the location and person responsible at each step. Define on-hand versus available quantities; an allocated item may still be physically present.
Decide which actions can be corrected, reversed or approved and retain enough history to explain the balance. A dashboard should summarize those rules rather than conceal adjustments in an editable total.
Choose the authoritative stock system
If an online store, warehouse tool or accounting package already owns stock, document that responsibility. For every integration, specify direction, identifiers, update frequency and what happens when the provider is unavailable. Two systems should not independently overwrite the same balance without a tested conflict policy.
Where existing tools cannot support the agreed stock rules, explore a custom web application for inventory workflows.
Plan imports with reviewed mappings, rejected-row reports and repeat-run checks. Establish how a physical count is compared with the same system snapshot and how differences are approved.
Test simultaneous work and exceptions
Use examples such as two staff allocating the last available unit, a partial shipment, a returned item, a repeated import and a count during receiving. Agree what may be promised and which cases require review. Do not assume a successful single-user demo proves concurrent allocation is correct.
If stock updates also go to a storefront or warehouse tool, scope the inventory integration and test what happens when the two systems disagree.
Django provides constraints, transactions and database-dependent locking tools. Their implementation must be tested against the actual backend and the agreed stock rules; a framework does not automatically prevent overselling.
Make the first release usable for staff
Choose the smallest set of daily movements, searches and reports that staff need. Check labels, scanning if in scope, permissions, correction paths and exports. Name who maintains product data, investigates exceptions, tests restores and approves future rule changes.
The Django ecommerce guide explains the connection to catalogue and order rules. An inventory workflow assessment should begin with existing records and responsibilities, not an assumption that a full custom system is necessary.
Related service scope
- Business automation: Review movements, ownership and exceptions.
- Ecommerce development: Scope catalogue/order integration where relevant.