End-to-End App Flow

1. Read Requirements and complete Installation.
2. Open Configuration and confirm database, mail, timezone, branding, and runtime defaults.
3. Open Settings and save General, Branding, Security, Inventory Operations, POS, and Payments & Gateways sections.
4. Open Roles & Permissions and assign access for warehouse, quality, compliance, supplier, reports, and POS users.

• Branding, company name, timezone, and app type affect the whole admin shell.
• Inventory Operations settings define warehouse/bin defaults and location-enforcement behavior.
• Payment gateway settings decide which online payment methods appear in POS.
• Saved tax rules are not configured in Settings; they are created in the dedicated Tax Rates module and then reused by transactions.
• Roles and permissions decide which report workspaces, POS screens, and admin modules each user can see.

Release templates are managed from Reports > Operations & Risk > Quality Records. Inside that workspace, the Release Templates section lets the admin define the evidence and approval checklist that a batch must satisfy before it can become usable.

• Create the required quality template first.
• Link it to categories and products through their governance sections.
• Use the same phase to define compliance expectations for the products that need them.

1. Open Purchases and create a purchase against a supplier.
2. Choose the receiving warehouse and bin.
3. Select a saved Tax Rule if the supplier invoice uses one of the shared purchase tax rules; otherwise use manual tax type and tax value.
4. Add transport notes, storage intake notes, and discrepancy notes if needed.
5. Choose whether stock should be quarantined on receive.
6. Upload the supplier invoice, COA, and receiving evidence.
7. Enable label generation if your receiving team prints labels during intake.
8. Complete the purchase so lots and stock records are created.

• The batch becomes usable stock.
• Usable released stock on Dashboard increases.
• Stock outs, scan operations, and POS can now consume that stock subject to FEFO and other controls.
• The batch remains traceable in Batch Dossier, stock movements, and downstream shipment/sale history.

• Recall Center: identify affected lots and downstream traceability.
• Expiry Rescue Board: prioritize lots that must be rescued, consumed, discounted, or escalated.
• Compliance Vault: manage evidence and proof files.
• Batch Dossier: open a single batch's full audit trail.

• Missing or rejected evidence keeps batches in governance queues.
• Near-expiry stock increases pressure on Expiry Rescue Board and Dashboard.
• Recall decisions create visible downstream operational urgency.
• Storage issues, deviations, and CAPA records create management and action-center follow-up.

1. Create the store and map it to its warehouse.
2. Create one or more terminals/registers under that store.
3. Open a register session with opening float.
4. Open POS Suite and select Store, Terminal, and Register Session.
5. Scan barcode or type SKU/name in the barcode-first search field.
6. Select a shared tax rule when the branch should use one of the predefined POS tax rates, or switch back to manual tax type and tax value for exceptions.
7. Add customer, coupon, loyalty, or store-credit context if applicable.
8. Choose a payment method and complete the sale.

• Create or update category/product governance: affects future purchase intake, release requirements, FEFO behavior, and POS eligibility.
• Create or edit a tax rate: changes which shared tax options appear in new POS and purchase transactions, while completed transactions keep their stored tax type and value.
• Complete a purchase: appears in Purchases, receiving documents, batch inventory, and often governance queues.
• Approve quality evidence and release a batch: increases usable stock and makes the batch available for outbound and POS use.
• Record a stock out: appears in stock movement, traceability, branch consumption history, and related reporting surfaces.
• Create an adjustment or deviation: appears in operational correction history, governance follow-up, and management review signals.
• Complete a sale: appears in POS Sales History, receipt view, terminal activity, branch analytics, and inventory movement.
• Process a return or exchange: updates POS history, payment records, and stock state together.
• Raise a recall, rescue, or storage issue: appears on Dashboard, Action Center, and the relevant exception workspace.

1. Install the app and save base settings.
2. Create a quality-enabled category and a matching unit.
3. Create a shared tax rule that applies to purchases and POS.
4. Create a supplier with compliance and recall contacts.
5. Create a warehouse and bin, then create a branch store and terminal mapped to that warehouse.
6. Create a product with barcode, shelf life, FEFO, and release-template behavior.
7. Create the release template inside Quality Records.
8. Create a purchase and receive stock into the warehouse/bin with evidence attached.
9. Use the shared tax rule on the purchase and verify it appears on the invoice output.
10. Open Dashboard and Quality Release Queue to show that the batch is present but not yet freely usable.
11. Approve the required records and release the batch.
12. Return to Dashboard and confirm usable stock changes.
13. Open POS, select the store, terminal, and session, then scan or search the product and reuse the same shared tax rule if the branch policy requires it.
14. Add customer, coupon, loyalty, or payment context and complete the sale.
15. Open Sales History, Receipt, and Terminal Activity to show the retail result.
16. Process a return or exchange and show the inventory and payment trail.
17. Open Branch Replenishment, Drawer Reconciliation, and Analytics to close the operational story.