Vendventory Documentation
v1.0.0 Changelog

Vendventory Documentation

Vendventory is an all-in-one inventory and POS management system. It brings purchasing, stock control, supplier coordination, retail checkout, reporting, and daily operations into one workspace.

Recommended reading order: Requirements, Installation, Configuration, Settings, Roles and Permissions, End-to-End App Flow, Dashboard, Reports, POS Overview, POS Payments & Card Machine, Register Sessions & Drawer, POS Errors & Fixes, POS Demo Flow & Logins, then the CRUD pages for Categories, Units, Tax Rates, Products, Suppliers, Purchases, Stock Outs, Stock Adjustments, and Users and Profile.
Media placeholders included: the final documentation pass now leaves explicit image placeholder blocks on the key flow, dashboard, reports, POS, purchase, product, settings, and access-control pages so reviewer or marketplace media can be captured later without guessing what to record.
What the current documentation focuses on
  • The operations dashboard that acts as the main day-to-day control center.
  • The expanded report suite for release, recall, rescue, compliance, replenishment, supplier risk, and operational workspaces.
  • The POS section for sales, returns, exchanges, customers, pricing, loyalty, gateways, register control, and branch operations.
  • The plain-language POS payment page that explains cash, card machine, manual card, wallet, bank transfer, and hosted gateway flow.
  • The shared Tax Rates module that creates reusable flat or percentage tax rules for POS and purchase transactions.
  • Separate POS pages so overview, register sessions, drawer work, common errors, and demo logins are easier to find.
  • Simple POS notes that explain the main rules in plain language instead of technical wording.
  • Screen-by-screen explanations across dashboard, reports, and the main CRUD pages so each visible section is described in plain operational language.
  • The modernized CRUD surfaces that now follow the shared select, date, loader, confirm, and toast contract.
  • The operational flows that connect receiving, release, traceability, exceptions, and retail checkout.
Current operating pillars
  • Inventory control: stock, purchasing, adjustments, and movement records stay centralized and reviewable.
  • Traceable operations: purchases, stock outs, sales, adjustments, transfers, recalls, and returns stay auditable.
  • Operational reporting: dashboard and reports prioritize action queues, risk signals, and readiness.
  • Location-aware workflows: warehouse, bin, store, terminal, and register context matter across core flows.
  • Shared UI discipline: updated pages reuse the same modern form controls, loaders, confirms, and notifications.

Start here

Fastest way to understand the whole app
  1. Read End-to-End App Flow first.
  2. Open Workflow Guide & Demo Logins before screenshots or buyer review so you use the correct role for each story.
  3. Open Dashboard to understand the governance cockpit.
  4. Open Reports Overview to understand the intelligence and operations suite.
  5. Open POS Overview, POS Payments & Card Machine, Register Sessions & Drawer, POS Errors & Fixes, and POS Demo Flow & Logins for the retail layer.
  6. Then review the CRUD pages for how the master data, tax controls, and transaction flows feed the governance story.
What the new flow page explains
  • What the user should configure first after installation.
  • When categories, units, tax rates, suppliers, warehouses, products, stores, and terminals should be created.
  • How a purchase enters the app, where it appears, and when it becomes usable stock.
  • How shared tax rules appear in Purchases and POS, and when manual tax entry should still be used.
  • Which pages show release pressure, recalls, rescue actions, compliance evidence, and outbound activity.
  • How the POS branch flow works from store selection and barcode search through sale completion and returns.
  • How register sessions, drawer counts, and demo logins work in plain language.

System overview

Vendventory is no longer only about "how much stock do we have?" The more important question the live system answers is: which stock is usable, what is blocked or risky, what needs review, what must be replenished, and how should branch sales consume inventory without breaking governance rules?

Current operating model
  1. Secure the system, save core settings, and assign correct roles and permissions.
  2. Create the foundation data: categories, units, tax rates, suppliers, warehouses, bins, products, stores, terminals, and customers.
  3. Record purchases and receive stock with notes, evidence, warehouse/bin placement, quarantine choice, and label intent.
  4. Review release templates, quality records, compliance evidence, and release queues until stock becomes usable.
  5. Use dashboard, intelligence, action queues, supplier scorecards, and scheduled briefs to decide what to act on next.
  6. Run outbound operations through stock outs, transfers, scan console, adjustments, and storage monitoring.
  7. Sell branch stock through POS with customer, pricing, loyalty, payment, and traceability context.
  8. Handle returns, exchanges, replenishment, branch transfers, reconciliation, and end-of-day review.

Documentation map

Platform and operations pages
  • End-to-End App Flow: one continuous setup-to-operations walkthrough.
  • Dashboard: governance cockpit, KPI strip, risk charts, queues, workspaces, and activity feed.
  • Reports: intelligence, release, recall, rescue, compliance, supplier risk, and operational workspaces.
  • Copilot: read-only analytical assistance layered on top of dashboard and report context.
CRUD, POS, and support pages
  • Products, Categories, and Tax Rates: governance defaults, templates, expiry, FEFO, storage, barcode behavior, and reusable commercial tax rules.
  • Suppliers and Purchases: compliance identity, receiving workflow, warehouse/bin, tax rules, notes, evidence, and quarantine.
  • Stock Outs and Adjustments: location-aware outbound and correction workflows.
  • POS pages: overview, register sessions, assisted orders, manager inbox, branch replenishment, end of day, a plain-English errors page, and demo logins.
  • Release and QA pages: install, release checklist, buyer ZIP audit, manual QA, and changelog.

What changed in this documentation refresh

Primary areas updated in the current docs pass
  • Flow documentation: added a dedicated End-to-End App Flow page for setup, daily operations, and branch POS execution.
  • Dashboard: documented as an inventory governance cockpit, not a generic stock summary.
  • Reports: documents Intelligence Hub, Action Center, Replenishment Planner, Supplier Scorecards, Scheduled Briefs, Recall Center, Quality Release Queue, Expiry Rescue Board, Compliance Vault, Batch Dossier, and the operations workspaces.
  • POS: documents branch-aware checkout, customers, pricing, loyalty, sessions, returns, exchanges, and payment gateways.
  • Tax Rates: documents the reusable flat and percentage tax-rule module used by both Purchases and POS.
  • CRUD pages: align with the live forms and validations for categories, units, products, suppliers, purchases, stock outs, stock adjustments, and users.

Who should read what first

Implementers and reviewers
Start with End-to-End App Flow, Dashboard, Reports, POS Overview, and Changelog. Those pages explain the live product story fastest.
Operators and admins
Start with End-to-End App Flow, then read Settings, Roles and Permissions, Products, Suppliers, Purchases, Stock Outs, Stock Adjustments, and the POS pages.