Case study · Business systems
Aromata Digital Ecosystem
Aromata combines an internal retail system with a public WordPress experience so product operations and customer-facing content can move together.
Windows / iOS / Android / Web / Fiscal hardware- Status
- Private system
- Industry
- Retail and fragrance
- Timeline
- Private engagement
- Role
- System architecture, cross-platform development, integration and deployment
- Platforms
- Windows, iOS, Android, Web, Fiscal hardware
- Technology
- Flutter, Electron, PHP, MySQL, WordPress, REST APIs
Business challenge
Perfume retail requires fast checkout, dependable inventory, fiscal compliance and consistent product information across stores and the public website.
The problem
Sales, stock, employees, fiscal devices and website products needed to operate as one system rather than separate tools and manual updates.
What the product needed to do.
- 01
Inventory and warehouse management
- 02
Sales and employee workflows
- 03
Fiscal-printer integration
- 04
Cross-platform access
- 05
Offline-aware operation
- 06
Website product synchronisation
A system designed around the operation.
A connected product ecosystem with a custom POS at its operational centre and API-driven synchronisation to the public WordPress catalogue.
POS checkout
Inventory
Fiscal receipts
Multi-role access
Offline-aware sync
Website integration
Reports and exports
04 / System architecture
How the parts work together.
A representative architecture view is shown in place of confidential product screens and operational data.
Technical decisions and trade-offs.
Decisions
- Use a dedicated desktop path for reliable fiscal-device communication.
- Separate local transaction continuity from cloud synchronisation.
- Expose only the product data required by the public website.
Challenges and trade-offs
- Fiscal hardware introduces device-specific testing and recovery paths.
- Operational screens and transaction data are confidential and shown only as system diagrams.