Appearance
Customers and Categories
| Backlog field | Value |
|---|---|
| Story ID | AP-SAL-003 |
| Epic | Sales |
| Story type | Master data / configuration |
| Review status | Draft - business analyst and business owner review required |
| Source evidence | AppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available |
| Last source review | 2026-07-10 |
User story
As sales users, I want to maintain customers, categories, tax data, credit data, and commercial defaults so that sales documents use valid customer information.
Acceptance criteria
- Only authorized users can view or execute the feature's actions.
- Required business data, active dependencies, tenant/branch scope, and current document state are validated.
- Invalid requests return actionable validation errors without applying a partial change.
- Search, list, view, print, and export operations use the same authorized business scope.
- Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
- Financial or stock effects are applied atomically and no more than once.
Business rules
Required
Customer/category localized identity and active state are required; legal/tax/currency data are required by enabled sales.
Optional or conditional
Contacts, addresses, credit limits, payment terms, salesperson, price policy, and account overrides are conditional.
Action behavior
Customer Receivable/Sales/Return/Discount accounts override category values.
Blocking rule or downstream effect
Credit or master changes affect future documents; history retains posted snapshots.