Appearance
Units of Measure
| Backlog field | Value |
|---|---|
| Story ID | INV-DASH-008 |
| Epic | Inventory |
| Story type | Dashboard |
| Review status | Draft - business analyst and business owner review required |
| Source evidence | Inventory MFE route/form, Inventory.Apis controller, application command/query handlers, validators, domain entities, and posting services |
| Last source review | 2026-07-10 |
Purpose
Define measurement units, categories, conversions, and defaults used by items and transactions.
User stories
- As a master-data user, I want to manage units and their category so that quantities are entered consistently.
- As a catalog user, I want to set a default unit and conversions for an item so that buying, selling, and stocking units translate correctly.
- As an auditor, I want to view and export units so that measurement configuration can be reviewed.
Acceptance criteria
- A unit has a unique code and required localized identity.
- A unit belongs to a valid unit category.
- Only one applicable default unit is used for a category/item context.
- Conversion factors must be positive and must not create ambiguous conversions.
- A referenced unit cannot be deleted if doing so would invalidate an item or transaction.
- List, view, add, edit, delete, set-default, and export actions follow permissions.
- Egyptian/ERP logical unit identifiers are retained where required for tax integration.
Data rules
- UOM category localized identity is required and unique in its supported scope.
- UOM code and localized names are required; official/ETA logical codes are conditional for electronic documents.
- Base calculation and item conversion ratios must be greater than zero for any unit used in transactions.
- An item has one base unit. Transaction quantity is multiplied by the configured base calculation to obtain base quantity.
- Prices/costs may be stored per item variant/UOM; posting converts them consistently with quantity.
- Unit usage can restrict where a unit is valid (purchase, sales, inventory, or other configured usage).
Action effects
Setting a default changes future lookup defaults and conversions; it does not rewrite posted transaction quantities. Deleting or deactivating a referenced UOM must preserve history. A missing or zero conversion blocks stock posting with a UOM configuration error.