First-day checklist

• Setup completed and saved.
• License activated or grace period intentionally started.
• At least one admin account and one cashier account created.
• Catalog built with products that have batches and selling prices.
• Printer, scanner, and scale tested if hardware is in scope.
• First backup exported after test transactions pass.

Do not skip these

• Do not go live with cash payments until a shift and drawer workflow is confirmed.
• Do not import or restore data over a remote shop unless you are sure whether this device should become the main shop or a terminal.
• Do not install report plugins as loose .zip or standalone .nxrpt files. The runtime now expects .nxpack packages only.

Remote profile fields you should prepare

• Engine: MongoDB, MySQL, or PostgreSQL.
• Host and optional port.
• Optional connection URI.
• Database name.
• Username and secure password.
• TLS, schema, auth database, read preference, application name, and connection timeout where relevant.

QR setup behavior

• QR provisioning is only for remote sync setups.
• The payload stores the remote profile and optional remote password.
• Mobile validation rejects loopback hosts like localhost or 127.0.0.1.
• Private LAN hosts are allowed but raise a warning so operators remember the mobile device must be on the same network.

End-user activation flow

1. Obtain the product key from platform.nexuscloud.uk.
2. Open the setup wizard or the activation screen.
3. Enter the key exactly as issued and click activate.
4. The app verifies the key using the device ID, current platform, and app version.
5. After success, the activation state is saved and the app can proceed normally.

Grace period behavior

• The app supports a one-time 7-day grace window.
• Grace is intended for controlled temporary use while waiting for a real product key.
• Once grace expires, the app can route back to activation until a valid key is entered.
• The home panel shows status, masked key preview, last validation check, and last successful validation time.

Technical build configuration

• Environment keys include NEXUS_LICENSE_VERIFY_URL, NEXUS_LICENSE_APP_ID, NEXUS_LICENSE_APP_SECRET, and NEXUS_LICENSE_APP_VERSION.
• Bundled config loaders also read assets/env/license.debug.json or assets/env/license.release.json.

Validation timing

• Stored license validation is skipped if the last successful check is still fresh.
• The default periodic recheck interval is every 6 hours.
• The app also triggers checks during startup and resume flows.

Main admin areas

• Home and manager dashboard: high-level metrics, shortcuts, license summary, AI tools, and operational insight cards.
• Inventory: departments, categories, subcategories, suppliers, units, products, product batches, stock rules.
• Finance: sales, income, expenses, accounting, coupons, loyalty and gift cards, financial reports, reporting plugins.
• People: customers and account follow-up workflows.
• User accounts: staff creation, roles, permissions, departments, commission, cash drawer overrides.
• Settings: business profile, workflows, templates, integrations, devices, appearance, database, sync, maintenance.

Settings panes

• Business Profile: store info, currency, business type.
• Workflows and Rules: modules, approvals, drawer policy.
• Templates and Design: receipt and invoice layouts, branding, previews.
• Integrations and API: PayHere, digital receipts, AI providers.
• Hardware and Devices: printers, scanners, scales.
• Appearance and Sound: language, typography, accessibility, audio behavior.
• Database and Network: sync, direct DB connection, terminals, setup QR.
• System Maintenance: backup, restore, diagnostics, factory reset.

Cashier account fields you should understand

• Username: must be unique among active users.
• Display name: appears in operational flows and printed documents.
• Allowed departments: limits where the cashier can work.
• Commission enabled and commission rate %: optional extra pay logic for cashiers.
• Cash drawer policy override: use business default, tracked drawer, no drawer tracking, or auto-managed drawer.

Permission tuning basics

• Managers can override a smaller set of sensitive admin permissions such as users, settings, approvals, drawer, customers, customer receivables, and supplier payables.
• Cashiers only edit POS-relevant permissions such as discounts, refunds, save/load cart, split bills, manual price overrides, drawer open, close shift, and stock management.
• Kitchen users are scoped for kitchen operations and should not receive cashier or admin actions unless you have a special workflow reason.

Admin-level permission categories

• User management: create, edit, delete user accounts.
• Settings access: business profile, workflows, templates, device config, database settings.
• Financial approval: approve refunds, customer credits, discounts over limit, manager approvals.
• Drawer management: open/close cash drawer, drawer reconciliation, float adjustments.
• Customer receivables: manage customer credit limits and outstanding balances.
• Supplier payables: approve supplier payments and manage accounts payable.
• Backup and restore: create and restore from backup files.
• System maintenance: diagnostics, factory reset, sync management.

Cashier-level permission options

• Discounts: apply discounts to sales.
• Manual price override: manually override product prices at checkout.
• Refunds and exchanges: initiate refund or exchange workflows.
• Save and load cart: temporarily save and resume cart items.
• Split bills: divide a sale into multiple payments.
• Customer lookup: search and attach customer records.
• Drawer operations: open cash drawer, view drawer status.
• Close shift: finalize and close the shift summary.
• Stock visibility: view remaining stock when scanning products.

Recommended catalog order

1. Departments
2. Categories
3. Subcategories
4. Units
5. Suppliers
6. Products
7. Add-on groups
8. Initial batches and restock records

Useful product fields in the current model

• Name, description, image, barcode
• Department, category, optional subcategory
• Stock tracking type
• Minimum and maximum stock levels
• Tags, active status, variant flag
• Add-on groups
• Batches with batch number, supplier, SKU, expiry, stock, cost, and selling price

Product manager behavior to remember

• The product screen prepares departments, categories, subcategories, units, and suppliers before editing rows.
• The page can keep a preferred batch and sync common fields like SKU, supplier, cost price, selling price, expiry date, and stock totals from that batch.
• Products can start with a seed batch automatically so batch-driven inventory is ready from the first save.

Data quality habits

• Do not leave barcodes and SKUs blank if you expect rapid stock lookup or supplier return work later.
• Keep department and category names short and stable so filters stay readable.
• Deactivate products instead of deleting them when you need sales history to remain consistent.

Core product fields

• Name and description: visible to cashiers and customers.
• Product image: thumbnail display on cashier screen and receipts.
• Barcode and SKU: for fast scanning and supplier tracking.
• Department, category, subcategory: organization and filtering.
• Stock tracking type: whether to track by quantity, weight, volume, or custom units.
• Variant flag: marks the product as part of a variant set.
• Tags: custom labels for filtering and reporting.

Stock and operational settings

• Minimum stock level: triggers reorder alerts when inventory falls below this.
• Maximum stock level: threshold for overstocking warnings.
• Active status: controls whether the product appears in checkout.
• Returnable and refundable: whether the product can be returned or exchanged.
• Markup percentage: automatic pricing calculation from cost.
• Preferred batch: which batch to use for common editing.

Product variants workflow

• Create a base product and mark it as a variant product.
• Create related product SKUs or batch numbers that represent size, color, or other differentiators.
• Link variant products together in the variant group so reporting captures the full family.
• Each variant can have its own batches, pricing, and stock levels.

When to deactivate vs delete

• Deactivate: for seasonal, discontinued, or temporarily unavailable items. Keeps sales history intact.
• Delete: only for data entry mistakes before any sales are recorded.
• Always prefer deactivation to preserve historical transaction accuracy.

Batch-level pricing

• Each batch carries its own cost price and selling price.
• The batch selling price determines the checkout default unless overridden by a promotion or coupon.
• Markup percentage can automatically calculate selling price from cost if needed.
• Tiered pricing by quantity can be set so bulk purchases receive better unit pricing.

Promotional pricing types

• Fixed discount: reduce the price by a fixed currency amount.
• Percentage discount: reduce the price by a percentage (e.g., 25% off).
• Bundle pricing: sell multiple items together at a special rate.
• Tiered pricing: different unit prices for different quantity ranges.
• Seasonal markup: increase prices temporarily for high-demand periods.

Coupon management

• Create coupons in the Finance section with code, discount value or percentage, valid date range, and usage limits.
• Coupons can apply to specific products, categories, or the entire sale.
• Per-use or total-use limits prevent over-redemption.
• Track coupon usage and redemption rates for reporting and analysis.

Discount controls during checkout

• Cashiers can apply per-item discounts if permission is granted.
• Line-level discount percentages override batch prices temporarily.
• Manager approval can be required for discounts exceeding a threshold.
• All applied discounts are logged in the sale record and receipt.

Purchase order workflow stages

1. Draft: create and edit the order before sending.
2. Sent: formally submitted to the supplier.
3. Partially received: some items have arrived.
4. Received: all items delivered and accepted.
5. Closed: fully invoiced and reconciled with payments.

Creating a purchase order

• Open Admin > Stock Operations > Orders.
• Select the supplier.
• Add product lines with quantity, unit price, and expected delivery date.
• Review totals and include notes for special handling or delivery instructions.
• Save as draft then finalize when ready to submit.

Receiving procedures

• Match the delivered products to the purchase order using barcode scanning or manual selection.
• Confirm quantities and inspect for damage or defects.
• If everything matches, mark the line as received.
• Any discrepancies or damaged items are logged in the supplier case flow instead.
• Once all lines are received or disputed, close the receiving process.

Auto-reordering setup

• Set minimum reorder points on products to trigger automatic PO suggestions.
• The system can recommend suppliers and quantities based on historical usage.
• Review calculated reorder quantities and adjust if needed.
• Generate multiple POs at once for selected products and suppliers.

Supplier profile fields

• Company name, contact name, and title
• Phone, email, and website
• Mailing and billing addresses
• Tax ID or registration number
• Payment terms (e.g., net 30, net 60)
• Default delivery lead time
• Account notes and credit limit

Supplier invoice matching

• Receive supplier invoices and match them to your purchase order records.
• Verify quantities, prices, and line items match the PO.
• Log any variance or dispute in the supplier case system.
• Mark as approved once verified or as pending invoice correction if needed.

Supplier payment tracking

• Track all outstanding supplier balances in the Finance > Accounts Payable view.
• Group invoices by supplier and aging bucket (current, 30 days, 60 days, 90+ days).
• Record payment dates and methods for reconciliation.
• Generate aging reports for month-end financial statements.

Supplier performance management

• Review on-time delivery rates from receiving records.
• Track quality issues and damage cases by supplier.
• Maintain supplier scorecard or notes for review meetings.
• Elevate chronic issues to disputes or contract renegotiations.

Damage report fields

• Batch and product: which exact batch is affected.
• Quantity damaged: how many units cannot be sold.
• Damage type: packaging, product defect, dent, leak, breakage, corrosion, etc.
• Discovered date: when the damage was detected.
• Root cause: shipping, handling, storage, manufacturing, or unknown.
• Estimated cost: retail or cost value of the loss.
• Supplier claim status: pending claim, claim submitted, approved, rejected, or not claimable.

Damage workflow steps

1. Discover or receive a damage report from staff.
2. Create a damage record immediately to preserve evidence and timing.
3. Take photos if needed and attach to the record.
4. Determine whether to discard, attempt repair, or donate the items.
5. Reduce stock from the affected batch accordingly.
6. If supplier is at fault, initiate a supplier case or claim.
7. Track claim submission and resolution in the supplier module.

Supplier damage claims

• Link damage records to the original PO or supplier case.
• Calculate claim amount considering restocking fees or partial recovery if applicable.
• Submit claim documentation via email or the supplier portal if integrated.
• Track claim status through approval, payment, or rejection.

Disposal and recovery

• Discarded items should be logged for potential tax deduction or insurance purposes.
• Some damaged goods can be salvaged, sold at discount, or donated.
• Partial recovery reduces the net loss and should be recorded separately.
• Maintain disposal records for audit trails and compliance.

Write-off categories

• Expiration: products past their usable date.
• Obsolescence: discontinued products or replaced models with no further demand.
• Overstock: inventory that has not sold within a specified aging period.
• Shrinkage: unaccounted loss due to theft, miscounting, or handling errors.
• Quality migration: items that have deteriorated in storage but not technically expired.
• Recall: products removed due to safety or regulatory issues.

Write-off procedure

• Identify candidates using stock aging reports and inventory reports.
• Create a write-off batch or journal entry for each category.
• Document the batch numbers, quantities, reasons, and estimated loss value.
• Mark affected batches as inactive or closed after write-off.
• Arrange for disposal or salvage processing where applicable.
• Record the financial impact in expense reports for accounting.

Write-off reporting

• Run write-off summary reports by category, month, or supplier.
• Calculate write-off cost as a percentage of total inventory.
• Use trends to identify problem areas in ordering or demand planning.
• Review with managers to identify systemic issues or training needs.

Financial treatment

• Write-offs are typically expensed rather than capitalized.
• Include write-off values in cost of goods sold or operational expense lines.
• For tax purposes, document the business reason for each significant write-off.
• Work with your accountant to ensure proper treatment in financial statements.

Refund policy configuration

• Refund window: days within which a full refund is allowed (e.g., 14 days).
• Extended returns: whether returns beyond the window are allowed at a discount.
• Restocking fee: percentage deducted if a full window return is allowed but not requested immediately.
• Non-refundable skus: product categories or specific items that cannot be returned.
• Condition requirements: whether items must be unopened, unused, or in original packaging.
• Original or equivalent price: refund based on original receipt price or current price.

Settlement calculation logic

• Even exchange: customer receives exact replacement with same cost.
• Refund to customer: cash or credit returned when original price exceeds replacement.
• Customer top-up: customer pays difference when replacement costs more.
• Restocking deduction: percentage deducted from refund amount based on condition.
• Credit note: refunds can issue store credit instead of cash refund.

Refund workflow execution

1. Locate the original sale via receipt number, transaction ID, or customer record.
2. Verify the item meets refund policy conditions (within window, condition met, not restricted).
3. Calculate the eligible refund amount considering window, restocking fee, replacement item if any.
4. Select settlement method: cash refund, credit note, exchange, or partial refund.
5. Confirm payment allocation and any approvals required.
6. Finalize the refund, which updates stock, accounting, and sales history.
7. Print refund receipt and provide documentation to customer.

Exchange workflow execution

1. Locate and verify the original sale eligibility as above.
2. Select the replacement product and quantity.
3. Calculate whether this is even exchange, requires refund to customer, or customer top-up.
4. Confirm stock availability of the replacement before finalizing.
5. Process the exchange, updating stock for both return and new item.
6. Settle any price difference via cash, credit, or invoice.
7. Print both original refund and new sale documentation.

Daily reconciliation checklist

• Count physical cash against recorded drawer balances.
• Compare cash transactions to checkout records.
• Verify split payments and multi-tender transactions were recorded correctly.
• Check online payment capture logs against batch submission receipts.
• Review refund and exchange entries for accuracy and approval status.
• Confirm all sales documents (receipts, invoices) printed and delivered.

Discrepancy resolution process

• Identify the exact amount and transaction involved.
• Check for duplicate entries, reversals, or missing entries.
• Review corresponding customer or supplier records.
• Consult staff for possible manual entry or processing errors.
• Document the resolution in notes or adjustment records.
• If unresolved, mark for manager or accountant follow-up.

Month-end closing procedures

1. Halt new transactions during a cut-off window or mark period boundary.
2. Run reconciliation of all sales, payments, and adjustments for the period.
3. Close pending customer credit accounts or hold approval for outstanding invoices.
4. Match supplier invoices to purchase orders and received goods.
5. Process and approve all supplier payments for the month.
6. Inventory count and write-off any expiration or shrinkage found.
7. Generate accounting exports or trial balance reports.
8. Review with management and finance before finalizing the period.

Cashier drawer reconciliation

• Each cashier reconciles their drawer at end of shift.
• Count cash physically and compare to system balance.
• Investigate variances immediately: missing sales, over-tenders, counterfeit.
• Document responsibility if shortage exceeds tolerance threshold.
• Manager signs off on drawer reconciliation before cashier leaves.

How add-on groups are structured

• Group name: the visible label, such as Size, Toppings, Extras, or Cooking Preference.
• Selection mode: single or multiple.
• Required: whether the cashier must choose something before continuing.
• Min selections / max selections: the allowed range.
• Options: each option has a name, active flag, default flag, and optional priceDelta.

What the cashier sees

• A modal titled Choose Addons.
• Each group listed separately with its selectable options.
• Validation if minimum or maximum selection rules are broken.
• An apply button that shows the total extra price from the chosen add-ons.

What a batch represents

• Batch ID and batch number
• Supplier and SKU
• Unit, cost price, selling price
• Current stock, last restock date, purchase date
• Expiry date and active state
• Minimum and maximum stock thresholds

How the app chooses batches

• Direct batch ID match is used first if available.
• If only batch number is known, the app looks for active matching batches for that product.
• When multiple active matches exist, batches are sorted using FEFO: earliest expiry first, then earlier purchase or creation timing.
• Soft-deleted or inactive batches are ignored for active stock use.

Stock operations areas

• Orders: purchasing and receiving preparation.
• Supplier cases: supplier issues, credits, exchanges, and refund-now scenarios.
• Write-offs: damaged, expired, or otherwise removed stock.
• Reports: purchase register, receipt register, supplier case register, movement register, reorder alerts, stock transfers, approval history.

Recommended daily batch workflow

1. Review pending purchase orders and receiving tasks.
2. Receive stock into the correct existing batch or create a new batch if the supplier lot is genuinely new.
3. Use supplier case and write-off tools for damaged, expired, or disputed stock instead of silently editing counts.
4. Run report views to watch low stock, reorder alerts, and unusual movement patterns.
5. Clean up finished and inactive batches once they are no longer needed operationally.

Normal checkout flow

• Select or scan products into the cart.
• Choose add-ons when prompted.
• Attach a customer if credit, loyalty, digital receipts, or detailed invoicing are needed.
• Apply discounts or coupons where permission and module rules allow.
• Accept tender using cash, split allocations, online payment capture, or gift card.
• Print a receipt, invoice, or both, and optionally open the invoice PDF.

Special cashier capabilities

• Split bills and split sale parts.
• Customer credit sales, including approval checks and credit limit enforcement.
• PayHere online payment capture when enabled and configured.
• Gift card redemptions and balance checks.
• Coupons, loyalty, saved carts, and sale edits.

Refund and exchange behavior

• Refund policy supports a default refund window, optional refunds after the window, restocking fee %, non-refundable product SKUs, and customer initiation rules.
• Refunds can calculate customer payout, exchange credit, even exchange, or customer top-up depending on the settlement balance direction.
• Refund and exchange flows can touch stock, payment allocations, customer credit, supplier accounting, and sales history.

Sales documents

• Checkout print mode can be receipt, invoice, or both.
• Receipts are optimized for 80mm thermal output.
• Invoices can open as PDF or print through system printer support.
• Add-ons, taxes, discounts, settlement status, and payment allocation summaries can appear in the document layout.

Document template blocks

• store_header
• document_meta
• customer_summary
• items
• totals
• payment_summary
• notes_terms for invoices
• footer

Digital receipt options

• Email receipts use SMTP host, port, username, password, sender name, and sender email.
• SMS receipts use a configurable HTTP base URL and related account credentials.
• Receipt delivery jobs are stored with status such as pending, processing, sent, failed, or skipped.

Report Plugins Center workflow

1. Open Finance > Report Plugins Center.
2. Click Install Package and select a .nxpack file.
3. If the same version already exists, choose whether to force replace it.
4. Enable or disable installed plugins as needed.
5. Run a plugin, fill its parameter sheet, and generate the report.
6. Use Download Template to export a starter plugin package.

Strict import rule

• Supported install format: .nxpack.
• Unsupported legacy formats: standalone .nxrpt, standalone .nxrpt.json, and generic plugin zip files.
• Package name must match the internal plugin folder name.

Current supported plugin runtime surface

• Parameter types: text, number, integer, bool, date, dateTime, dateRange, select, radio, multiSelect, json
• Data sources: sales, income, expenses, purchases, inventory, supplierBalances, customerReceivables
• Layout blocks: title, header, section, text, condition, divider, spacer, metricsRow, table, list, formatShowcase, iconShowcase, footer, pageBreak
• Formats: currency, percentage, date, dateTime, number, decimal, badge, text
• Auto-fill sources: departments, suppliers, customers, categories, subcategories, units, products, salesStatus, paymentMethods, expenseTypes, incomeSources, and table:<name>

Validation rules that often fail first

• Missing plugin.manifest.json at the archive root.
• Missing README.md, package.json, or required asset directories.
• Manifest plugin ID, report ID, report name, or version mismatch.
• Report schema version outside the package requirement range.
• Re-importing the same version without force replace, or importing an older version than the installed one.

Sales and revenue reports

• Daily sales summary: total revenue, item count, payment method breakdown, by hour or by cashier.
• Product sales analysis: top sellers, bottom performers, sales trends by product or category.
• Sales by department: revenue and margin by department for store layout optimization.
• Cashier performance: sales volume, average transaction size, payment methods handled, customer count.
• Discount and promotion impact: how much revenue was given away versus retained.
• Payment method analysis: cash vs card vs online, tender processing efficiency.

Financial reports

• Income statement: sales, cost of goods, gross profit, operating expenses, net profit.
• Cash flow mapping: when money moves in versus out across payables and receivables.
• Expense tracking: categorized operational expenses for cost control.
• Tax liability calculation: sales tax, VAT, or other withholdings collected or owed.
• Margin analysis: gross and net margins by product, department, or time period.
• Budget vs actual: compare planned revenue and expenses to actual results.

Inventory and stock reports

• Stock-on-hand: current quantity by product or batch.
• Stock aging: how long items have been in inventory, useful for identifying obsolescence.
• Reorder alerts: products that fell below minimum levels during the period.
• Stock movement: inbound receives, sales, adjustments, and write-offs by product.
• Overstock analysis: slow-moving items that tie up cash.
• Batch expiry calendar: upcoming expirations by date range.
• FEFO compliance: verify that oldest stock is being sold first.

Supplier and payables reports

• Supplier invoice register: all invoices by supplier with dates, amounts, and payment status.
• Accounts payable aging: outstanding balances by age bucket (current, 30, 60, 90+).
• Supplier performance: on-time delivery, quality issues, average order value.
• Purchase register: all received goods with cost and receipt date for cost accounting.
• Supplier case register: damaged goods, returns, and disputes by supplier.
• Cost price trends: track how supplier pricing changes over time.

Customer and receivables reports

• Customer lifetime value: total purchases by customer over time.
• Accounts receivable aging: outstanding customer credit sales by age.
• Customer credit limit utilization: who is near or over their credit limit.
• Transaction history: all purchases by customer for follow-up or pattern analysis.
• Gift card and loyalty: balance reports and redemption analysis.
• Customer segmentation: high-value, frequent, lapsed, or one-time customers.

Refund and exchange reports

• Refund register: all refunds by date, product, reason, and amount.
• Refund rate by product: which products have high return rates, indicating quality or fit issues.
• Exchange tracking: items swapped and price adjustments made.
• Refund impact on revenue: gross sales minus refunds to get net revenue.
• Approval tracking: refunds requiring manager approval and their resolution.

Reporting best practices

• Run daily sales and cash reports to spot issues the same day.
• Review inventory reports weekly to stay ahead of stockouts.
• Month-end financial reconciliation should match sales, refunds, and payments exactly.
• Use custom date ranges and filters instead of generic monthly snapshots.
• Benchmark performance month-over-month and year-over-year.

Operational decision examples from reports

• Product reordering: check reorder alerts and aging stock before placing POs.
• Staffing and scheduling: use sales by hour to plan cashier coverage.
• Pricing adjustments: review margin by product and compare to market.
• Promotional planning: analyze discount impact on revenue to justify future campaigns.
• Supplier negotiations: use performance reports as basis for terms discussions.

What Sync Center shows

• Pending outbox count
• Retry queue count
• Dead-letter and unresolved issue count
• Outbox item details and queue flow
• Repeated requeue diagnostics
• Background helper status on Windows

Manual controls you should know

• Push Now to send local changes immediately.
• Pull Now to fetch remote changes immediately.
• Retry or discard unresolved local copies in the dead-letter area.
• Pause or resume the Windows background helper if closed-app sync must be suspended temporarily.

Background helper summary

On Windows, a helper mode can continue conservative sync activity after the main UI is closed. It focuses on outbox push, checkout queue recovery, issue recovery, and incremental pulls of changed records. Use it when you need background continuity but still want safety-first sync behavior.

When to open Sync Center immediately

• After a network outage
• Before exporting a backup
• Before restoring to a remote shop
• When terminals appear out of date
• When a plugin or report seems to miss fresh transactional data

What a backup can include

• Collections and local store data
• App settings
• Setup configuration
• Admin and cashier databases
• Sync metadata
• Users, business profile, and business config data if present

What can block a backup

• Pending outbox entries
• Retry queue entries
• Dead-letter conflicts not yet resolved
• Database integrity validation failures
• In remote mode, terminals that cannot be safely locked for the operation

Restore planning checklist

• Analyze the restore source first.
• Decide whether the target remote shop should be erased or whether this device should switch to terminal mode instead.
• Make sure users understand terminal reset notices after restore actions.
• Expect remote shop safety prompts if the destination already contains entities.

Remote restore safety

• The app can lock other terminals during backup operations.
• Restore and backup operations both benefit from a clean sync queue.
• If unresolved sync issues remain, backup can stop on purpose instead of producing a misleading snapshot.

Hardware and document issues

• Printer not found: confirm the selected printer mode is supported on the platform and rerun discovery or manual target entry.
• Print test fails: connection details are wrong, printer is offline, or reconnect logic is pointed at the wrong device.
• Wrong receipt fields: review the template block visibility rather than editing the product or sale data first.
• Scanner input is messy: fix prefix and suffix trimming in scanner settings.

Inventory and stock issues

• Stock looks wrong: verify the correct active batch is being used and that expired or inactive batches are not misleading the operator.
• FEFO not working: check batch expiry dates are set correctly and no forced batch overrides are interfering.
• Product not appearing at checkout: ensure the product is marked active and is assigned to an accessible department and category.
• Batch expiry not triggering reorder: set minimum stock levels and use the reorder alerts report.

Purchase order and supplier issues

• Cannot receive completed purchase order: confirm the PO is in sent or partially received state, not draft or closed.
• Receiving quantity mismatch: if actual received quantity differs from PO, create a supplier case instead of forcing the receive.
• Supplier invoice not matching PO: check that line items, pricing, and tax match exactly before approving. Document any variance in supplier notes.
• Accounts payable aging looks wrong: verify payment dates are recorded for all paid invoices and no double-counted amounts.

Refund and exchange issues

• Refund amount seems incorrect: check the original sale price, applicable restocking fees, and any promotional discounts from the original sale.
• Exchange not updating stock: ensure the system correctly reduces stock from the returned batch and increases stock for the replacement.
• Refund outside window blocked: this may require manager approval. Check your refund policy settings and user permissions.
• Cannot refund non-refundable item: this is by design. Contact management if an exception is needed.

Damage and write-off issues

• Damage report not reducing stock: confirm the damage record is saved and approved, not just drafted.
• Write-off batch not creating: ensure you have the required permissions and the batch records exist for the items you're writing off.
• Supplier damage claim not visible: verify the damage record is correctly linked to the supplier and the claim status is set appropriately.
• Disposal/salvage tracking missing: add notes to the damage or write-off record to document where items ended up.

Data and sync issues

• Terminal seems out of date: open Sync Center and inspect pending outbox, retry queue, and unresolved issues.
• Backup is blocked: the sync queue is not clean, database validation failed, or unresolved damage/write-off records exist.
• Remote restore warning: stop and confirm whether the target should be erased or whether the device should switch to terminal mode.
• Reconciliation totals don't match Sync Center: wait for background sync to complete or manually push/pull to refresh remote data.

Reconciliation mismatches

• Cash drawer balance off: review each cashier's recorded sales and refunds in the report. Check for voided transactions or manual overrides.
• Sales total mismatch: compare POS sales to payment batches. Missing items usually indicate unrecorded offline sales or sync delays.
• Payment method sums don't match: verify that split payments and multi-tender transactions are recorded completely.
• Accounts payable total wrong: check no duplicate invoices were entered and all payment postings are recorded.
• Accounts receivable total wrong: verify all customer credit sales are accounted for and refunds/payments are allocated correctly.

Plugin and reporting issues

• Install rejected: check the package root structure, matching names, README, package.json, icons path, and schema version range.
• Same version already installed: decide whether force replace is justified.
• Generated report looks empty: review parameters, data source filters, and whether the underlying shop data exists in the chosen date range.
• Report shows incomplete data: confirm Sync Center is clean and all remote terminals have pushed recent data.

License and permissions issues

• Activation failed: verify the key, internet access, and device entitlement.
• Grace already used: you now need a valid key.
• Config missing: the build lacks the required license API configuration.
• User cannot access feature: verify the user's role and individual permission settings. Managers may have restricted access to certain functions.

Consolidated source material

• Former user guide merged into this single index
• Former stock guide merged into this single index
• Former report plugin API and quick-start notes merged into this single index
• Current settings, setup, licensing, report plugin, backup, stock, cashier, and sync modules in the app code

Useful auto-fill sources for plugin authors

• departments
• suppliers
• customers
• categories
• subcategories
• units
• products
• salesStatus, paymentMethods, expenseTypes, incomeSources