← Back to help centre

Use your browser’s “Save as PDF” option from the print window.

Businar · printable usage guide

A safe working order for daily business operations

This document is a short, accurate summary of the flows available in the application. It does not assume a configured integration, automatic payment verification or email delivery.

Sales, inventory, accounts and reportsE-commerce and subscription boundariesReadable on mobile and desktop
  1. 01 · Secure startVerify your business and access firstEvery workspace opens for the selected business and the role verified by the server. A panel option cannot expose another business’s data.

    Recommended order

    1. Sign in through Business sign in and confirm the business you will work in.
    2. On Overview, check the sales, inventory and report areas available to your role.
    3. Change only the business preferences your role permits in Settings.
    • business
    • access
    • role
    • security
  2. 02 · Products and inventoryCreate product cards, then monitor stockA product card is the single record for a name, unit, sale price, product code or barcode, and stock. A new price never rewrites a completed sale.

    Recommended order

    1. Open Products & inventory and complete the name, unit and sale price.
    2. If you use them, save SKU or barcode as a unique, readable value.
    3. For tracked products, check the opening quantity and low-stock threshold.
    4. Record counts and corrections as stock movements, separately from a sale.
    • product
    • stock
    • barcode
    • SKU
    • low stock
  3. 03 · Bulk product importValidate a CSV or .xlsx file firstYou can upload a supported file for many products. When rows are invalid, the system shows an error summary before writing any product record.

    Recommended order

    1. Download the template from Products and preserve the header layout.
    2. Upload CSV or a standard .xlsx file; do not use legacy .xls or formula-filled files.
    3. Correct the row and field errors shown by validation.
    4. Process only a valid file through the confirmed import step.
    • CSV
    • Excel
    • xlsx
    • import
    • product
  4. 04 · Sale workflowSave a cart sale and manage it without deleting historyA sale cart can contain multiple products. The server validates price and stock from the current product card; an entered total is never trusted by itself.

    Recommended order

    1. Find a product by name, product code or barcode and add it to the cart.
    2. Check quantity, payment method and payment status.
    3. For a credit sale, choose an existing customer; a cash sale does not require one.
    4. Save the sale; if you have permission, use the correction, cancellation or restore flow for a mistaken header.
    • sale
    • cart
    • payment
    • barcode
    • cancel
    • restore
  5. 05 · Customers and accountsKeep credit sales and collections as separate entriesA customer record is the account linked to a credit sale. A collection does not change the sale amount; it creates a separate, traceable ledger entry.

    Recommended order

    1. Save the customer name and the needed contact details in Customers.
    2. Choose the correct customer during a credit sale to create the debit entry.
    3. When collecting payment, save the amount and date separately from the customer ledger.
    4. Check the outstanding balance and movement order per customer.
    • customer
    • account
    • credit
    • collection
    • balance
  6. 06 · Reports and exportFilter real records and export with permissionReport charts and summaries use server-verified sales data for the selected business. Sales, products and eligible report views can offer role-based CSV or Excel export.

    Recommended order

    1. Select the date range and the relevant filters in Reports or sales history.
    2. Confirm that charts use only real records from that period.
    3. Export the list you need as CSV or Excel.
    4. Store downloaded files safely; an export is not a complete system backup.
    • report
    • chart
    • CSV
    • Excel
    • export
    • sales history
  7. 07 · E-commerce operationsManage e-commerce as a separate channel operationThe e-commerce area keeps connections, mappings and orders as a distinct business operation. A configured, enabled WooCommerce connection can receive only signed Order created notifications; other provider intake and automatic stock, price or status sync must not be assumed.

    Recommended order

    1. Check connection status and manual-operation notes in E-commerce.
    2. Create channel, product-mapping and order records only from verified information.
    3. Review order statuses against your own fulfilment process.
    4. When provider access or a technical connection is missing, operate manually instead of assuming an automatic delivery.
    • e-commerce
    • order
    • channel
    • connection
    • mapping
    • sync
  8. 08 · Subscription and transferKeep a transfer notice separate from subscription approvalWhen payment infrastructure and plans are configured by an administrator, a business can copy the IBAN for its pending request and submit the bank reference. A notice is not automatic payment approval.

    Recommended order

    1. Check the suitable plan and duration in Subscription & payments.
    2. For a pending request, use only its displayed account name, owner, IBAN and payment reference.
    3. Copy the IBAN and include the displayed reference in the bank-transfer description.
    4. Send the payment notice and wait for the platform administrator’s manual reconciliation.
    • subscription
    • IBAN
    • transfer
    • payment
    • manual approval
    • plan
  9. 09 · Administration and securityKeep the business panel and platform administration separateBusiness users work only with their own business data. Platform administration is a separate, more restricted session for cross-business operations such as subscription and payment review.

    Recommended order

    1. Perform daily product, sale and customer work in the business panel.
    2. Use a properly authorized administrator session for platform plans, payment profiles or business lifecycle actions.
    3. If access looks suspicious, verify the session and selected business rather than repeating the action.
    4. Do not share passwords, IBANs, references or customer data in messaging apps.
    • admin
    • administration
    • permission
    • security
    • business
    • session

Short checklist before starting an operation

This list helps prevent missed critical steps; it does not replace permissions or server validation.

  • The correct business workspace is selected.
  • Product, customer and payment method are up to date.
  • A customer is selected for a credit sale.
  • A record was not deleted to cancel or correct it.
  • The exported file is stored safely.
  • A transfer notice awaits manual approval.