Login
I

ivendnext_handheld

iVendNext Handheld

iVendNext Handheld

A barcode-driven warehouse / store back-office inventory Progressive Web App for iVendNext retail. It runs in the browser on rugged Android mobile computers and BYOD phones/tablets, and posts against the shared ivendnext_pos engine's native inventory documents — goods receipt, stock transfers, counts, issues, returns-to-vendor, item lookup with label printing, and pick / pack / deliver. The engine does the stock, valuation and document work; the Handheld app is the scan-first staging front-end on top of it. It is not a till — it takes no tender and posts no fiscal document.

  • App: ivendnext_handheld/ — a root-level iVendFramework app (installable via bench get-app).
  • Scope: this repo is Handheld-only. (The mPOS selling app is a separate product line in its own repo.)
  • Status: all 30 screens are built and on the shared beta site with testers, in English plus five more languages. The first implementation chain finished on 2026-08-29; the product has been hardening since, through full walks, tester reports and planned fix lanes, and those lanes are now finished. There are no customers yet. Full picture: docs/STATE_OF_THE_PRODUCT.md.
  • Ownership: the product is being handed to the engine team. Taking it over? Start at docs/HANDOVER.md.
  • License: Proprietary — © CitiXsys. Internal to the ivendnext org; not open-source.

Repository layout for developers

Folder What's in it
docs/ All developer documentation — start at docs/README.md.
dev/ The walk-bench seeds. A bench from nothing: docs/onboarding/DEV_SETUP.md. (The seeded operator and how to sign in as it: docs/onboarding/README.md step 2b.)
design_system/ The component library you compose UI from (this repo's vendored copy).
ivendnext_handheld/translations/ The five language catalogues. Every operator word ships in all of them, and a test enforces it: docs/onboarding/README.md step 5.
ivendnext_handheld/ The app itself (repo root — hooks.py, modules.txt at top level).
ci/, docker/, .github/ The CI harness: the stages the hosted merge gate (server-tests.yml) and the local preflight both run.

New here? Start with the docs.

→ docs/README.md is the one page to read first. You do not need to read the whole docs/ tree to be productive.

The product specs are in docs/specs/ (BRD, PRD, scoping, engine-seam dossier) and docs/reference/ (screen map, code map, API, data model); docs/README.md routes to everything.

User Reviews

Write a review

No reviews yet, be the first to review.