Invio Project Reference

Shared details page for the full Invio team. Use this as the project baseline for architecture, scope, repository responsibilities, and current implementation conventions.

Status: Active Build Domain: Inventory Management Last Updated: February 26, 2026

Project Snapshot

  • Purpose

    Build a reliable inventory platform for small and multi-store retailers.

  • Primary Users

    Store operators, inventory managers, and admin teams.

  • Core Capability

    Product/barcode catalog + immutable stock movement ledger + offline scan sync.

  • Design Principle

    Fast operation on the floor, strict traceability in the backend.

Domain Entities

  • Product

    SKU identity, barcode mappings, and category metadata.

  • Store

    Per-location inventory scope and threshold settings.

  • Stock Movement

    IN / OUT / ADJUST events as append-only records.

  • Scan Event

    Mobile-captured event batch for offline-first synchronization.

  • User + Role

    RBAC rules for product updates, stock edits, and reporting access.

Repository Map

Repo Responsibility Key Focus Run Command
backend API and inventory domain logic Product catalog, stock movements, RBAC, alerts, sync ingestion uvicorn app.main:app --reload
frontend Admin dashboard for management workflows Products, stores/users, stock summary, reports, optional supplier module (app-specific frontend command)
mobile Store-floor scanning companion app Fast barcode scan, stock actions, offline capture + background sync (mobile project runner)
pages Project references and documentation Shared team docs, project overview, links and guidance Static hosting

System Flow

1

Capture

Scan or enter stock actions from mobile/web interfaces.

2

Validate

Apply RBAC, product/store checks, and movement rules.

3

Persist

Write immutable movement records and audit-relevant metadata.

4

Sync + Alert

Update views and emit low-stock signals for operations teams.

Operational Notes

  • Data Integrity

    Stock ledger should remain append-only to preserve audit history.

  • Offline Behavior

    Mobile batching must be idempotent to avoid duplicated stock movements.

  • Security

    RBAC required for stock adjustment, catalog edit, and user management.

  • Observability

    Keep health endpoint and structured logs available in all environments.

Reference Commands

Backend API

uvicorn app.main:app --reload --host 0.0.0.0 --port 8000

Suggested Team Convention

branch: feature/<module>-<short-desc>
commits: feat|fix|docs(scope): message

Current Build Plan

  • Phase 1
    Stabilize core inventory APIs and movement ledger behavior.
  • Phase 2
    Finalize dashboard flows for stock operations and user management.
  • Phase 3
    Harden offline mobile sync and production-grade retry strategy.
  • Phase 4
    Publish internal analytics and low-stock operational playbooks.