Everything you need to
run your store better.

Depending on your account and enabled modules, the dashboard may show sales totals, purchase totals, payment summaries, stock alerts, charts, recent activity, or quick links. Dashboard cards are a summary, not a replacement for checking the detailed record or report.

How to use the dashboard each day

1. Check the date range and active warehouse or location filters.
2. Review pending items, stock warnings, and recent activity.
3. Open the detailed report when a number looks unexpected.
4. Record the issue and relevant transaction reference before making a correction.

Open the Settings area and look for business or general settings. Menu labels can vary by release and user permissions.

Recommended order

1. Confirm business information and the correct time zone.
2. Choose a base currency before entering live activity.
3. Configure taxes and payment accounts.
4. Review invoice and receipt layouts.
5. Save, reload the screen, and verify the settings persisted.

Add or select a currency

1. Open Settings, then find Currency or the equivalent currency list.
2. Choose Add Currency if the currency is not listed.
3. Enter the currency name/code and the required rate fields.
4. Save and verify the currency is active and appears in the list.
5. When recording a transaction, select the correct currency and confirm the displayed rate and total.

Taxes

1. Open the tax settings or tax-rate list.
2. Create each tax rate required for your business and jurisdiction.
3. Confirm whether it is a percentage or fixed amount and whether it applies to the intended products or transactions.
4. Apply the tax to relevant products or sales/purchases, depending on your configuration.
5. Test with a sample transaction and verify the line tax, total, invoice, and report.

Payment methods versus payment accounts

A payment method describes how the customer paid (for example, cash, card, bank transfer, or an online provider). A payment account identifies where the received money is recorded. Configure both concepts where the system asks for them.

• Use the actual provider and account configured for your business.
• Do not treat a browser message as proof that an online payment settled; verify the provider transaction and reconciliation record.
• For cash and bank accounts, check the correct account is selected before posting.

Create a role first

1. Open the user, role, or permissions area in Settings.
2. Create a role such as Cashier, Inventory Staff, Purchasing Staff, or Manager.
3. Start with view permissions and add create, edit, delete, payment, export, or reporting permissions only as required.
4. Enable access to optional modules only for staff who need them.
5. Save the role and then create or edit the user's account.

Create a staff user

1. Open Users and choose Add User (or the available equivalent).
2. Enter the person's name, login/email, and other required details.
3. Assign the correct role and, when applicable, a warehouse or branch.
4. Save and test the account with the staff member's actual login.

Always test the role. Check the menu, the actions available on a page, and warehouse restrictions. Hiding a menu item alone is not a substitute for server-side permission controls.

Stock is often tracked by warehouse, not just by company-wide product totals. The warehouse selected on a purchase, sale, count, or transfer can determine which inventory is used.

Create a warehouse

1. Open Settings → Warehouse or the matching location menu.
2. Select Add Warehouse.
3. Enter a clear name and the required contact or address information.
4. Save, then assign user access if your system supports warehouse-level restrictions.
5. Confirm the warehouse is selectable on the transaction forms where it should be used.

Before posting a transaction

• Check that you selected the correct source or receiving warehouse.
• Confirm stock is available in that warehouse, not only at another branch.
• For tracked stock, select the right batch, variant, IMEI or serial number.
• After a transfer, verify both the sending and receiving warehouse ledgers.

Recommended order

1. Create product categories and brands if your workflow uses them.
2. Create units of measure (for example, piece, box, kilogram or litre). Configure conversion units carefully, if supported.
3. Open Products → Add Product (or your equivalent menu).
4. Enter the product name, code/SKU, category, brand, unit, product type, and description if required.
5. Enter cost and selling-price details, tax defaults, barcode, and stock-tracking fields as applicable.
6. Save and check the product appears in the catalogue and can be selected on a test transaction.

Common product types

Product quality checklist

• Use a unique and readable product code.
• Do not create duplicate products for the same item without a clear reason.
• Use the correct purchase and sale units.
• Review cost and selling price before starting live sales.
• Attach a product image if your storefront or product screens use images.
• For an existing live product, use the supported edit process rather than creating a duplicate.

• Variants: use for options such as size, colour, storage capacity, or model. Confirm each variant can be identified separately.
• Batch and expiry: use for goods where lots and expiration dates matter, such as food, medicine or cosmetics.
• IMEI/serial number: use for individual devices or equipment that must be traceable one by one.
• Barcode: use a unique code/label for rapid lookup and scanning. Check that the scanner reads the code expected by the product record.

Good traceability habits

1. Enable the correct tracking type on the product before recording stock.
2. Capture the batch, expiry date, IMEI or serial data when stock is received.
3. At sale, select the exact tracked identity the customer receives.
4. Use stock ledger and expiry/serial reports to investigate movement.
5. Do not create missing historical batch or serial data by guessing after the stock has already moved.

Customer dues, supplier dues and deposits

Use the customer or supplier profile and transaction history to understand balances. A credit sale may leave money due from the customer; an unpaid purchase may leave money due to a supplier. Deposits, instalments, refunds and payment reversals should be recorded through their dedicated workflows where available.

• Check that payment records are attached to the correct customer/supplier and invoice.
• Do not create a duplicate customer simply to change an address or phone number.
• Reconcile balances against transaction histories before making opening-balance corrections.

Before making a purchase, ensure the supplier, receiving warehouse, products, purchase units, currency, taxes and payment accounts are configured.

Create a purchase

1. Open Purchase → Add Purchase or the matching purchase form.
2. Select the supplier and the warehouse receiving the items.
3. Set the purchase date, reference/invoice number, currency and rate where required.
4. Add each product, quantity, unit cost, discount, tax, shipping or other configured charges.
5. For tracked goods, enter the correct batch, expiry, IMEI or serial identities.
6. Review subtotal, taxes, discounts, additional costs, total and any initial payment.
7. Save/complete the purchase according to your workflow.
8. Open the purchase details and confirm the status and received quantities.

Purchase order versus purchase

If purchase orders are available, they are commonly used to plan or authorize a purchase before stock is received. A purchase/receiving record represents the actual goods and costs entered into the system. Do not assume creating a draft or pending record has already updated stock—check the status and ledger.

Before saving, verify

• Correct supplier and warehouse.
• Correct product, quantity and purchase unit.
• Unit cost, tax, discount and freight/shipping.
• Currency and rate, if foreign currency is used.
• Payment amount, due amount and the correct payment account.

Record a supplier payment

1. Open the purchase or supplier account and select the payment action your screen provides.
2. Choose the correct supplier and related purchase/invoice when requested.
3. Enter payment date, amount, method and receiving/issuing account.
4. Add the bank reference or note, if useful.
5. Save and verify the paid amount and remaining supplier balance.

Record a purchase return

1. Find the original purchase and confirm which items and quantities are being returned.
2. Open the supported purchase-return workflow.
3. Select the items, quantities and any applicable reason or reference.
4. Review the effect on stock, supplier balance, taxes and accounting before confirming.
5. Verify the returned quantity and supplier balance afterwards.

Freight, duty and other landed costs

Some businesses need to add freight, customs duty, insurance or other costs to the cost of imported goods. Where a landed-cost allocation feature is enabled, follow its allocation rules and verify the resulting product/batch costs and profitability reports.

Standard checkout

1. Open the POS screen and verify the active warehouse/register if shown.
2. Select the customer, or use the default/walk-in customer where permitted.
3. Scan a barcode or search by product name, code, variant, or serial identity as supported.
4. Confirm each item, quantity, selling price, discount and tax.
5. Review the subtotal and total due. Check that the right currency is selected.
6. Select a payment method and account, then enter the amount received.
7. For split payments, enter each part separately and confirm the combined amount covers what is due.
8. Complete the sale and print, email, or share the receipt using the options available.
9. Verify the sale appears in transaction history and stock changed as expected.

POS tips

• Use a barcode scanner if configured; test one barcode before the sales rush.
• Check the selected warehouse when stock exists in multiple branches.
• Use discount and price-edit permissions carefully.
• For credit sales, deposits, instalments, gift cards or rewards, use the specific controls provided rather than entering an arbitrary payment.
• Do not refresh or resubmit repeatedly if a save is still processing. First check transaction history to avoid a duplicate sale.

Record a standard sale outside the POS

1. Open the Sales list and select Add Sale.
2. Choose customer, warehouse, biller/agent, date and currency if requested.
3. Add products and confirm quantities, unit prices, discounts and taxes.
4. Enter the initial payment only if one is being made now.
5. Review the total and balance, then save using the correct status/action.
6. Check the sale detail, invoice and payment history.

Credit sale

For an approved credit sale, record the full sale and the payment actually received. The unpaid portion should remain due against the customer when the workflow is configured that way. Check the customer's credit limit and terms before confirming.

Installments and down payments

• Confirm the agreed total, first down payment and any configured instalment plan.
• Record each subsequent payment as a separate payment against the correct outstanding sale/invoice.
• Check the balance after every payment and provide a receipt.
• Use supported refund/reversal workflows if a payment was posted in error.

Review a sale

Use the Sales list to filter by date, customer, reference, warehouse or status. Open a specific sale for the detailed items and payment history. If totals look wrong, compare the saved line values and payment records with the invoice.

1. Find and open the original sale. Confirm the sale reference and returned items.
2. Start the sale-return or exchange action supplied by your account.
3. Choose the specific products and quantities being returned. For tracked items, select the exact batch/serial/IMEI where applicable.
4. Check whether the returned stock is fit to restock or needs to be marked damaged according to your process.
5. Review the calculated return value, tax treatment and any refund or customer credit.
6. Confirm the return, then verify stock, payment/credit balance and the return record.

For exchanges, verify the returned product and the replacement product are both represented accurately. If a refund is due, check the refund method and payment-account record. If the original sale is already involved in later accounting or stock activity, follow any system warning and request assistance rather than forcing the transaction.

Record an expense

1. Open the Expenses area and choose Add Expense.
2. Select an expense category, date and paying account.
3. Enter amount, reference, payee and a useful note.
4. Attach an invoice or receipt if uploads are supported.
5. Save and confirm the expense appears in the list and relevant reports.

Examples can include rent, utilities, delivery charges, office supplies or other business costs. Follow your accountant's policy for classifying costs such as freight that may need to be allocated to product cost rather than recorded as a routine expense.

Reconcile cash and bank activity

• Use the correct cash/bank account for every transaction.
• Enter a bank or payment reference where helpful.
• Compare the system balance with bank statements and cash-count records at a regular cadence.
• Use a supported reversal or correction if an expense was recorded on the wrong date, category or account.

Stock count or adjustment

1. Select the correct warehouse and count date.
2. Physically count the items using the same unit and variant/identity as the system.
3. Compare physical quantity with recorded quantity.
4. Use the approved count or adjustment workflow and select a clear reason (for example, damage, loss, or verified count correction).
5. Have a manager approve changes if required by your policy.
6. Save and verify the stock ledger and warehouse quantity.

Transfer between warehouses

1. Open Transfer → Add Transfer where available.
2. Select different source and destination warehouses.
3. Add products and quantities available in the source location.
4. Enter the required batch or variant details where applicable.
5. Save and complete the transfer status according to the system workflow.
6. Check the stock ledger at both locations. Company-wide total should generally remain the same for a simple transfer.

Stock Ledger

The Stock Ledger is useful for tracing when and why quantities changed. When stock looks incorrect, filter the correct product, time period and warehouse, then compare the sequence of purchases, sales, returns, adjustments and transfers.

Where accounting is enabled, business transactions may feed into double-entry journals. Correct account setup matters: sales, purchases, customer receipts, supplier payments, returns, expenses and cash/bank activity need to map to the intended accounts.

Common accounting areas

Safe activation and review

1. Review the Chart of Accounts and required mappings.
2. Complete any accounting readiness checks shown in your version.
3. Run one test purchase and one test sale, including payments.
4. Inspect their journals and compare the amounts with transaction detail.
5. Review Accounting Health or diagnostic screens if available.
6. Only rely on reports after discrepancies have been investigated and the setup has been reviewed by the person responsible for your accounts.

How to investigate a number

1. Record the report name and filters used.
2. Open the detailed transactions behind the total when available.
3. Compare invoices, payments, refunds, returns and ledger entries.
4. Repeat the report using the same date and warehouse filters before comparing with another report.
5. Export a copy for review where permitted, and protect the file because it may contain customer or financial information.

Print or share a sales invoice/receipt

1. Open the saved sale from transaction history.
2. Choose Print, Invoice, Receipt, or the available share option.
3. Check the business name, document number, customer, items, quantities, taxes, discounts, total and payment status.
4. Select the appropriate printer or paper layout if your system offers a choice.
5. Preview before printing or sharing.
6. Confirm the document was delivered or printed successfully.

Printer and barcode notes

• Thermal receipts commonly use 58 mm or 80 mm rolls; choose the matching layout if supported.
• For standard paper, verify page size and margins.
• Barcode-label printing depends on label size and printer settings.
• If printing fails, check browser print settings, the selected printer, paper size and pop-up blocking.
• Email or WhatsApp sharing is available only when the relevant integration and account settings are configured.

Before importing

1. Take a fresh backup before changing large amounts of data.
2. Download the current import template from the relevant module, if offered.
3. Keep the column headings and required formats intact.
4. Check required names, codes, units, categories, tax values and other references already exist.
5. Try a small sample first and review the result for duplicates or errors.
6. Import the remaining rows only after the sample is correct.

Common causes of import failures

• Missing required columns or renamed headers.
• Duplicate product codes or customer/supplier identifiers.
• Invalid dates, decimal formats, tax names, units or category references.
• Incorrect warehouse, unit conversion, batch or serial details.
• Opening balances or historical rates that are not verified.

Export only the data you need. Store exported files securely and delete temporary copies according to your business privacy policy. A spreadsheet import is not a safe way to recreate historic traceability or reverse posted accounting without a planned migration process.

In the documented Mysale.pk package, the eCommerce module may need to be enabled by an administrator before use. Availability on MySale.pk depends on your edition, subscription and setup.

Typical setup order

1. Ask an administrator to enable the module and grant appropriate access.
2. Configure store identity, domain, currency, stock/warehouse rules, delivery areas and shipping rules.
3. Choose which products are published online and verify names, prices, descriptions, variants, images and stock.
4. Configure storefront layout, categories, menus, pages, banners and other visual content.
5. Configure email and payment providers only after credentials and provider-side requirements are verified.
6. Test registration/login, product search, product detail, cart, checkout, delivery, payment success/failure and order history.
7. Confirm an accepted test order appears in the back office and that stock, payment and order status match.

Online order checklist

• Is the product published and available in the correct stock location?
• Are price, variants, tax and delivery fees correct?
• Does the checkout show the correct order total before payment?
• Has payment been verified through the configured provider—not only a browser message?
• Can staff find, process, fulfil and track the order?

Where integration is included and enabled, it can connect the physical-store back office with a sales channel. WordPress hosting, , provider accounts and credentials are separate services and must be configured independently.

1. Confirm the integration is available for your account and enabled by an administrator.
2. Back up both systems before making the first synchronization.
3. Follow the current connection screen to enter the required site URL and API credentials securely.
4. Map products, SKUs, variants, stock locations, taxes and order statuses as required by your version.
5. Run a small controlled test or manual synchronization.
6. Compare a sample product and order on both systems, including stock and payment/status information.
7. Only then run the normal workflow; monitor errors and duplicate records.

Typical dine-in workflow

1. Confirm tables, floor/area, menu products, modifiers, add-ons and preparation stations are configured.
2. Open the restaurant POS and select a table or order type.
3. Add menu items, quantities, modifiers and special instructions.
4. Send the order to the kitchen/KDS using the available workflow.
5. Track preparation and order status on the Kitchen Display System, if configured.
6. When the customer is ready to pay, review the order total and apply supported split payments if needed.
7. Close the order, issue the receipt and check the sales/stock records.

Order types and supporting features

Depending on the enabled module, workflows may include dine-in, takeaway, delivery, waiter assignment, reservations, kitchen tickets, multiple preparation stations, QR menus and WhatsApp ordering.

Test how modifiers, add-ons, order cancellation and refunds affect stock and reports. For delivery orders, verify the delivery details and status before marking the order complete.

HRM features can include employee records, departments, attendance, leave, holidays and payroll. Exact screens and calculations depend on the installed version and your configuration.

1. Create departments or staff groups if your setup uses them.
2. Add employees with accurate identifiers and contact details.
3. Configure work schedules, holidays and leave policies before recording attendance.
4. Review attendance entries before running payroll.
5. Check salary components, deductions, approved overtime/leave and payroll period.
6. Review payroll output carefully before posting or paying it.

Manufacturing and production

Where production features are available, configure the recipe or bill of materials (BOM) to define component quantities for a finished product. Record production through the supported production workflow, then check that ingredient stock and finished-goods stock changed as expected.

Repair and service jobs

Use repair records for service jobs when enabled. Capture the customer, item/device identifiers, reported issue, work status, used parts, labour/service charges and payment details. Verify any parts used are deducted correctly from inventory and are attached to the intended repair record.

Projects and tasks

Use the project module to organize project records, tasks, assignments and progress if included. Agree team ownership and status meanings before entering work, and keep financial invoices or sales records in the correct dedicated workflow.

• Test the full module flow before moving active work into the system.
• Limit edit/delete permissions for completed production, repair, or project records.
• Review both operational status and associated stock/payment/report effects.

The Mysale.pk documentation describes a business-focused assistant that can summarize supported data using predefined skills. It is not necessarily a general-purpose chatbot, and the exact skills depend on the installed release and accessible data.

Example questions to try

Selecting an example copies it to your clipboard when browser permissions allow. It does not submit anything to your MySale.pk account.

How to use answers responsibly

• Confirm the date range and warehouse scope of the answer.
• Open the related detailed report to verify important amounts.
• Do not share private customer or employee data outside the authorized business context.
• Use a normal report or ledger when an auditable, transaction-level record is needed.

Depending on your setup, supported communication workflows may include email, WhatsApp receipt/order sharing, reminders or system notifications. They may require sender credentials, an approved provider account, templates, and correctly formatted customer contact data.

1. Identify the exact feature you want to use: invoice email, receipt sharing, order alert or another workflow.
2. Configure the required provider/sender details in the intended settings page.
3. Use a test recipient or internal address first.
4. Confirm delivery status with the email/messaging provider where available.
5. Check spam folders, phone number formatting and provider restrictions when delivery fails.

Do not place passwords, API secrets or provider tokens in screenshots or public support posts. If the credentials may have been exposed, rotate them.

Backup routine

• Take regular database backups and include uploaded files/documents where required.
• Keep a copy separate from the live application/server.
• Protect backup files with suitable access controls and encryption where practical.
• Test restoring a backup into a safe test environment; a backup is only useful if it can be restored.
• Before a bulk import, update or structural change, take a fresh backup and record the change.

Security basics

• Use HTTPS for the live site.
• Keep user access limited and review staff accounts periodically.
• Do not publish .env files, database credentials, API secrets or license keys.
• Use the official update process for your installation; do not edit protected updater files.
• Monitor storage space and server health if you manage the hosting.
• Configure scheduled tasks/cron only for features whose documentation requires them.

Before updating

1. Review the release notes and prerequisites.
2. Back up the database and files.
3. Apply the update in a test or maintenance window according to the official instructions.
4. Test login, POS, purchases, reports, integrations and critical modules.
5. Retain a recovery plan until the update is verified.

Support ticket checklist

• Store URL and affected module/page.
• Exact steps that reproduce the problem.
• Transaction or record reference (remove sensitive customer data where possible).
• Exact error text and time it occurred.
• Screenshot with passwords, tokens, phone numbers and private details hidden.
• Browser/device details and recent changes, if relevant.