Business Software / POS
AYOS POS
AYOS Technologies business software connecting point-of-sale and back-office operations as one system.
- Role
- Co-Founder · Primary Developer
- Status
- Active development / system design
- Stack
- React · TypeScript · Vite
- Provenance
- AYOS Technologies · company software · primary development role
AYOS POS is company software being designed and developed around AYOS Terminal and Back Office workflows: catalog, inventory, sales, payments, shifts, cash, reporting, permissions, devices, and offline/sync behavior. The architecture is intended to be business-profile-driven and capability-composed rather than a vape-specific or one-industry codebase.
00 / System
How the work connects.
- 01Terminal→
- 02Back Office→
- 03Catalog→
- 04Inventory→
- 05Sales / Payments→
- 06Shifts / Cash→
- 07Reports / RBAC→
- 08Offline / Sync
The project is AYOS Technologies company software, not a personal demo.
AYOS POS sits inside the broader AYOS Technologies company rather than defining the whole company. My role centers on primary software and product development while the portfolio keeps company ownership and the active implementation stage explicit.
Earlier Vape POS work became domain reference material, not the architecture for the new system.
The earlier Vape POS exposed practical retail, inventory, lookup, and sales workflows. AYOS POS carries forward that domain learning while being designed as a new system that is not limited to vape-specific operations.
Terminal, Back Office, permissions, and local resilience are being designed together.
The architecture is multi-tenant in direction, business-profile-driven, capability-composed, and locally resilient. Catalog, inventory, sales, payments, customers, purchasing, shifts, cash, reporting, devices, permissions, and synchronization are treated as connected operational concerns instead of separate page features.
Architecture is locked in direction while implementation remains active.
The portfolio does not claim a production customer rollout, completed deployment, ERP replacement, full restaurant suite, payroll/HR system, or arbitrary industry-specific feature set. AYOS POS is presented as active company software whose operational scope is being implemented and verified.
Media / Selected Evidence
Evidence from the work.
The strongest project surfaces, system artifacts, QA output, and technical evidence stay curated here.
Real POS terminal implementation or approved design evidence when ready.
Actual product, stock, or catalog workflow evidence.
Verified transaction-flow implementation when available.
Real reporting, shifts, cash, permissions, or management surfaces.
Architecture or data-flow evidence from the AYOS POS build.
Real test, device, offline, or business-workflow verification evidence.