Two parts of the same operation
AutoSet Niš sells, installs and repairs automotive glass. The public website guides drivers to the relevant service and contact route, while the internal panel supports inventory search, scheduling and work orders. Customer and operational records remain outside the public presentation.
An inventory of 713 items
The initial inventory came from an export of the accounting system. The same code can belong to different manufacturers, so an item is matched by code and manufacturer. Rows without a name remain usable when they have a code, and a preview shows new and changed records before import.
- Preview before any write
- A backup before every import
- Search fields based on counter staff needs
Controls that protect the records
The panel keeps original decimal values instead of writing rounded table text back to storage. XLSX archives are checked for declared size and compression ratio before parsing, preventing a small upload from expanding into hundreds of megabytes. Permissions and change history belong to the application rather than the browser view.
Testing the task itself
The workflow was checked with real clicks and scrolling at a common laptop height. This exposed an import button below an unreachable modal edge and a status badge intercepting controls underneath. An API test would miss both failures even though either can stop work at the counter.
What the example demonstrates
Useful business software starts with real operating rules: what makes a record unique, who may change it, how a mistake is reversed and what proves completion. This case documents a delivered system; its outcome is not a promise for another project.