MISAll POS — Complete User Manual

Choose an edition and a learning path

MISAll serves Chinese-owned supermarkets, convenience stores, wholesale businesses and retail shops overseas. POS supports checkout. Back Office manages store operations. MISAll Business Manager (Enhanced Edition) focuses on purchasing, sales documents, inventory and business accounts.

Steps

1. For a shop with tills, train cashiers with the POS manual and owners or managers with the Back Office manual. Cashier accounts and back-office operator accounts are managed separately.
2. For customer orders, wholesale dispatch and stock control, follow the Enhanced Edition path: master data, receiving, delivery, payments and reconciliation.
3. Enhanced Edition does not include POS checkout, membership/promotion management, the Audit Centre or tax-authority integration. Ordinary tax calculation is a separate capability.
4. Choose your edition first, then check company options and permissions. A missing menu can be an edition restriction rather than an installation problem.

Install, launch and update

The installer language and the application language are separate settings. The current installer uses English. A first launch without a saved preference defaults to Simplified Chinese; an existing language choice is preserved.

Steps

1. Obtain the correct installer through your MISAll service channel and verify whether it is POS, Back Office or Enhanced Edition. The icon alone is not sufficient.
2. Before an update, record the current version, server and company database. Confirm a backup exists and reconcile any pending offline sales.
3. Complete the installer. If the application asks for a server, follow chapter 003. POS also needs the correct store and till registration.
4. After updating, sign in, open a historical document, check stock and preview a print layout. If a database upgrade is requested, the responsible administrator should back up before proceeding.

Connect to the server and select a company

The server stores shared business records. A company database contains one set of business accounts. Database credentials are different from operator or cashier credentials.

Steps

1. Open Connection Settings on the sign-in screen. The responsible administrator enters the confirmed server, port and database connection details.
2. Test the connection, then apply it and reconnect. A successful test is followed by checking that the company list and sign-in actually work.
3. Verify the server and company name displayed before signing in. Select the correct company when several independent businesses share a server.
4. Initialize POS online before preparing offline operation. If connection fails, follow chapter 072 while preserving existing local records and settings.

Sign in and separate staff responsibilities

Back-office operators control management functions; cashiers control checkout actions. Use the system administrator for setup and maintenance, and individual accounts for routine work.

Steps

1. In Back Office or Enhanced Edition, select your operator and enter your own password. In POS, use your assigned cashier number and password.
2. Check the active operator, store and warehouse. When cashiers change, use the shift handover process rather than sharing one person’s shift.
3. An administrator assigns module access, editing, approval, export and cost visibility in Operator Permission. POS cashier rights are maintained under the back-office POS menu.
4. If a required action is unavailable, record its name for the responsible manager. Lock the till when leaving it and complete the shift before finishing work.

Switch languages and keep terminology consistent

Interface language, foreign product names and print language affect different content. Switching to English does not translate stored product names, warehouses or remarks automatically.

Steps

1. Use the language selector on the sign-in screen, choose English or Simplified Chinese, and sign in to check the menus.
2. Maintain both the local and foreign product names with consistent units, variants and barcodes. Do not create duplicate stock records merely to represent two languages.
3. For store-specific terms, use System → Custom Translation, find a phrase, edit the intended language and save. Agree on a glossary before changing common terms.
4. Check receipt and label language, fonts and layouts separately. Preview examples containing Chinese, English and long product names before testing physical output.

Work across computers, warehouses and stores

Computers connected to the same company share business records. Warehouses distinguish stock; stores and tills distinguish checkout activity. These concepts serve different purposes.

Steps

1. Use one agreed server/company configuration and individual staff accounts. Verify the company name on each workstation.
2. Create warehouses to match physical stock ownership. Stores needing separate stock must have the correct warehouse mapping, not just different store names.
3. Register each POS workstation against its assigned store and till. Investigate an occupied till before clearing any device data.
4. Filter management queries by warehouse, store, cashier and date. Record inter-store stock movements with transfer documents.
5. For remote or cross-border access, use the controlled network arrangement provided by your service team and test stability and recovery.

Sign in, start a shift and enter the float

Confirm the store, till and cashier before trading. The opening float is cash already in the drawer, not sales revenue.

Steps

1. Sign in with your assigned cashier number and password. Complete online initialization before first use.
2. If Start Shift appears, count the opening cash and enter the actual amount. Investigate an existing open shift instead of creating a duplicate.
3. Check the connection status, cashier and sales mode. Ordinary retail sales must not start in return or customer-delivery mode.
4. Confirm the scan field accepts input and the printer has paper. Use chapter 023 to hand over an earlier shift.

Scan, search, change quantities and sell unbarcoded items

POS accepts barcode scans, text searches and touch selection. Check the selected variant, unit and price every time.

Steps

1. Focus the product input field and scan. Without a scanner, enter a name or item code, press Enter and select the correct result.
2. For multiple identical items, scan again or use the quantity function. Check the merged quantity and keep scans out of numeric editing fields.
3. Before switching units, confirm the conversion and unit barcode are configured. A case and a bottle have different prices and stock quantities.
4. Choose the required colour or size for a variant; its full barcode identifies that variant directly. Use the authorized unbarcoded-sale function for items without a barcode.
5. Delete the incorrect unpaid line. Clear the entire basket only when abandoning that unpaid sale; completed transactions require the appropriate return process.

Worked cash sale: total 7, cash 10, change 3

This verified example sells two bottles of Demo Water at 3.50 each: total 7.00, cash tendered 10.00 and change 3.00.

Steps

1. Enter DEMO500, confirm item DOC-WATER-001 and set quantity to two.
2. Choose Cash, enter the 10.00 actually handed over and verify change of 3.00 with zero remaining.
3. Set receipt printing as required, confirm once and wait for the result.
4. Record the successful sale number, give the change and query that number in sales history.

Open the full illustrated walkthrough →

Card, other methods and split payments

The payment dialog can combine methods. Selecting Card does not by itself prove that every card terminal is integrated or that a charge succeeded.

Steps

1. Open payment, check the amount due, then select each configured method and enter its amount.
2. For a total of 7.00, card 5.00 plus cash 2.00 leaves zero remaining. Non-cash amounts must not exceed the total; excess tender requiring change must come from cash.
3. Bind the correct member before using stored value. Follow chapter 018 for vouchers instead of treating them as unrestricted cash.
4. Verify external payment success before confirming the sale. Where a terminal is integrated, reconcile both its result and the software status.
5. Check the method breakdown in sales history, not only the overall amount received. Maintain method names in the relevant POS settings.

Hold, recall and cancel an unfinished sale

A held sale preserves an unpaid basket while a customer is away. It is neither a completed sale nor a deposit-paid Layby.

Steps

1. Check the basket and member, select Hold and confirm. Serve the next customer after the basket clears.
2. Use Recall and identify the intended basket by its time, goods or note rather than its row position.
3. If another basket is active, follow the prompt to hold it before recalling the target basket.
4. Recheck quantities, member and prices before payment. Use line deletion or clear-sale only for an unpaid transaction and observe permission prompts.

Identify members and verify prices and points

Identify the member before checking the actual price and benefit applied. Member prices, fixed discounts, promotions and points do not necessarily stack.

Steps

1. Use the member function, normally F4, and enter the card number or phone number. Verify the person and card type.
2. Inspect basket prices and discounts. Member-priced, promotional and non-discountable products can follow different rules.
3. If a benefit is wrong, check the member benefit type, product member price and store rules before manually changing prices.
4. After payment, verify the points change and use the points ledger when tracing a discrepancy.
5. Before serving the next customer, confirm the previous member has cleared or select the new member.

Pay with stored value and reconcile top-ups

Stored value is a member balance. Purchases, top-ups and refunds must be reconciled separately.

Steps

1. Bind a stored-value member and verify the card and balance before opening payment.
2. Enter the amount to use. If the balance is insufficient, reduce that amount and complete the remainder with an allowed method.
3. After success, check both the sale and balance movement. Investigate uncertain results before attempting another debit.
4. For a top-up, use the online top-up function and verify the actual payment method and amount before confirming.
5. Have an authorized person handle lost cards, account closure or balance corrections through the appropriate workflow.

Discounts, promotions, rounding and authorization

Price changes, discounts and rounding are different adjustments. Confirm the discount display convention before entering a number.

Steps

1. Scan and inspect the promotional price or gift condition. If it is absent, check dates, store scope and products instead of adding discounts repeatedly.
2. Use line or whole-sale discounts only with permission. A payable rate of 80 means pay 80% of the original price; 20% OFF means reduce it by 20%.
3. Follow cashier permissions for price changes, gifts and rounding. A required supervisor authorization must be completed by the supervisor.
4. Verify the discounted total and rounding before payment, then reconcile them in history and shift reports.

Use vouchers and redeem loyalty points

Voucher payment and points redemption are different workflows. Where voucher numbers are required, validate the actual number instead of typing an arbitrary deduction.

Steps

1. Select Voucher in payment. If a Number button appears, enter the voucher and check the amount and eligibility returned.
2. Complete the remainder using an allowed method and retain the link between the voucher and sale.
3. For points redemption, select the member and redemption item, then verify points, quantity and stock before confirming.
4. Check the points ledger and redemption record afterwards. Use an authorized correction process for mistakes instead of issuing a second gift.

Return goods against the original sale

Use the original sale where possible so products and refund values remain linked to the original transaction. Recording a return and actually refunding money are separate checks.

Steps

1. Open Returns. If original-sale returns are enabled, find the sale by date and number and select the items being returned.
2. Enter the actual returned quantity without exceeding the remaining returnable quantity. Check return mode, negative quantities and the refund total.
3. Verify the refund method. External card refunds require the configured device workflow and original payment evidence.
4. Confirm, retain the return number and inspect the original sale and return in history. Print the return record when needed.
5. If abandoning the return, exit return mode before the next ordinary sale.

Find a sale and reprint its receipt

Sales history is the first place to establish whether checkout completed. No paper does not mean no sale, and reprinting should not create another transaction.

Steps

1. Open Sales Details from Other Functions, normally Ctrl+J.
2. Choose retail or the relevant document type, include the transaction time in the date range and search by document number.
3. Check goods, quantity, amount due, methods, cash tendered and change. Net cash equals tendered cash minus change.
4. Reprint only after identifying the correct original sale. Investigate the printer instead of charging again.
5. If no record appears, check store, date boundaries, connection mode and pending offline uploads.

Sell offline and verify synchronization

Offline selling requires an initialized local data copy. Uploading sales after reconnection is separate from submitting tax invoices.

Steps

1. While online, download and check the local product and store data. Verify till registration and the functions required for offline use.
2. Use the supported offline mode during an outage and confirm the sale is saved locally. Preserve that computer and its data.
3. After reconnection, inspect the pending count and use Upload when needed. Do not clear local data, rebind or reinstall while transactions remain pending.
4. Sample-check uploaded sale and shift records by number in Back Office. Confirm pending sales reach zero and original amounts are preserved.
5. Check and handle tax invoices separately for the configured country. Offline sales synchronization does not automatically submit tax invoices.

Recover an uncertain checkout result

If success was not displayed, establish the original transaction’s state before trying again.

Steps

1. Keep the original screen, payment evidence, time and amount. Look for an uncertain-settlement or sale-saved message.
2. Use Recover Unconfirmed Settlement and follow the prompts with the original store and cashier.
3. If the original sale number is returned, query it. A saved sale needs reprinting or follow-up handling, not another charge.
4. For card payments, check the terminal’s transaction status separately; software recovery does not replace that check.
5. If uncertainty remains, stop further charging for this transaction and give the responsible person the time, amount, reference and error message.

Close a shift and reconcile X/Z reports

An X report reviews the current shift; a Z report records a completed shift. POS shift closure and an Argentine fiscal printer’s day closure are separate actions.

Steps

1. Resolve held sales and uncertain settlements, and upload pending offline sales where possible.
2. Open the shift function from Other Functions and review the X report, including all payment methods.
3. Count the drawer and reconcile opening float, net cash sales, refunds and withdrawals. Enter the actual counted cash.
4. Confirm shift closure and check its completion and Z report. Reprint the existing report when needed.
5. Use Back Office Shift Query to review shifts. After offline shifts upload, generate or reprint their reports using the available function.

Layby deposits, instalments and collection

Layby reserves goods while a customer pays over time before collection. Unlike a held basket, it contains payments and an outstanding balance.

Steps

1. Add goods in POS, choose New Layby in Other Functions, enter the customer details and proceed to the deposit.
2. Enter the payment, check any minimum-deposit requirement and record the Layby number and remaining balance.
3. For another payment, select the original Layby in POS or Back Office → POS → Layby Management. Recheck its current server status and balance.
4. Do not exceed the remaining balance. Once paid, mark collection only when goods are actually handed over and verify the resulting sale and stock movement.
5. For abandonment, have the manager check the store agreement and use the appropriate cancellation/default workflow with the correct refund. Do not record each instalment as a separate goods sale.

Customer delivery, part payment and credit sales at POS

Customer delivery mode records a sale against a customer account. The current confirmation dialog allows a payment now and leaves the unpaid balance as receivable.

Steps

1. Open Sales Delivery from Other Functions, select the customer and check warehouse, customer pricing and quantities.
2. At settlement, compare the amount due with the actual payment. Select a settlement account when receiving money.
3. Use the no-payment/credit option for full credit, or check the outstanding amount after a part payment.
4. After confirmation, verify document approval and the customer balance. If saved unapproved, have the responsible operator resolve it.
5. Collect the remainder in Back Office with a sales receipt allocated to the original customer and outstanding document.

Keyboard shortcuts and touch checkout

Use the shortcuts displayed by the current screen. The same key can perform different actions in the basket and payment dialog.

Steps

1. Common basket defaults are F6 quantity, F7 price, F8 line discount, F10 hold, F11 recall and F12 payment.
2. In payment, F9 toggles receipt printing and Enter/F12 confirms. Inspect the amount before confirming.
3. Adjust workstation keys in Shortcut Settings under Other Functions, avoiding conflicts with staff conventions.
4. In touch mode, choose products by category and verify the selected line before changing quantity, price or deleting it. Check readability after resizing columns or scaling the interface.
5. Lock the till when leaving and resolve unfinished work before handover. Use a bilingual staff reference card for common actions.

Configure receipt printing, drawer, display and scales

POS hardware settings primarily apply to the workstation. Verify the equipment before configuring software. Ordinary receipt printers and fiscal printers have different integration paths.

Steps

1. Install the required official driver or connection and verify the printer’s own test output.
2. Open POS parameters, choose the actual printer, connection, paper width and mode, then preview and print a store test receipt.
3. Connect and test the drawer according to its interface. Distinguish a serial customer display from a second computer screen.
4. Distinguish live serial scales from barcode-label scales. Verify serial settings for the former and barcode prefix, item and weight/amount segments for the latter.
5. Save and recheck after restarting. Reconfigure when replacing a till or printer; a shared layout does not select the local hardware automatically.

Distinguish receipts, barcode labels and fiscal documents

Sales receipts, product labels and fiscal documents serve different purposes. Paper width alone does not identify them.

Steps

1. Decide whether you need a customer receipt, a price label or a country-specific fiscal document.
2. Print ordinary receipts from checkout/history and labels from the product or supported receiving workflow with the correct quantity.
3. Verify the unit barcode and price on labels so a case label does not display a bottle price.
4. Generate fiscal documents through the configured country workflow rather than imitating their appearance in an ordinary template.
5. Record the printer, paper, layout and test result for each output.

Troubleshoot scanners, scales, drawers and displays

Check the device and connection before software settings to separate wiring faults from data issues.

Steps

1. Test the scanner in a plain input field for complete characters and an ending Enter, then return focus to the POS scan box.
2. For label scales, match the barcode format. For serial scales, check port, baud rate and weight unit.
3. Connect the drawer to the specified interface and verify printer/trigger settings; similar-looking sockets are not necessarily compatible.
4. Check serial displays and secondary monitors separately for power, cabling, display mode and software setup.
5. Change one setting at a time, record the original value and test result, and return to a known configuration when needed.

Print layouts, paper, fonts and labels

Layouts determine content and placement; local settings choose the output device. Saving a new layout does not necessarily make it active.

Steps

1. Use the authorized design entry in the print menu or POS layout function, and copy/save a new layout before editing.
2. Set actual paper width, margins, fonts and line columns. Insert data fields rather than typing a single transaction’s amounts.
3. Preview long names, multiple lines, tax, totals and barcodes, checking page breaks and clipping.
4. Save and explicitly check the active layout, then print from the business page. Verify shared layouts and local printer selection separately.
5. Import/export within the matching document type. For labels, check dimensions, gaps, counts and unit prices separately.

Payment succeeded but nothing printed

Establish the transaction state before investigating printing. Do not charge again when a successful sale number exists.

Steps

1. Record the success number and find the original sale, checking amount and methods.
2. Inspect the print toggle, selected printer and active layout, including whether output went elsewhere.
3. Check power, paper orientation, paper/cover warnings, offline status and the system print queue.
4. If the device self-test works, investigate the driver, paper and application output mode.
5. After correction, reprint the original sale. For uncertain fiscal results follow chapter 076 instead of issuing another fiscal document.

Find the cause of slow checkout confirmation

Separate device checking, sale saving, fiscal issuance and ordinary printing to locate the delay.

Steps

1. Record approximate times for confirmation, status changes, success and paper output, together with the sale number.
2. Compare similar simple cash transactions with those using membership, external payment or fiscal issuance while keeping the environment comparable.
3. For device checks, inspect IP and printer state; for saving, inspect server/database connectivity; for delay after success, inspect printing.
4. Give support the version, store, time, amount and relevant status screenshot while omitting unnecessary customer information.
5. Resolve uncertain transactions before experiments. Repeated confirmation, force-closing or charging again is not a performance fix.

Barcode not found or wrong selling price

Check product data, unit, pricing rules and synchronization in that order.

Steps

1. Search the full barcode in Item Data and inspect primary/auxiliary codes, inactive status and variants.
2. Check whether the scan identifies a bottle or case and verify the unit conversion and price.
3. Review customer level, membership, promotions, tiers, manual overrides and validity dates.
4. For offline tills, check the local copy and refresh it online without clearing pending sales.
5. Test one item, the threshold quantity and a quantity below the threshold, recording expected and actual prices.

Troubleshoot server connection failures

Failures can originate in the network, server service, connection details or company. Preserve existing configuration and offline records.

Steps

1. Determine whether one workstation or the whole shop is affected. Check the server first for store-wide failures and the local connection for isolated ones.
2. Verify the server address after router/network changes and confirm the workstation is on the intended network.
3. Test the configured address, port and company, then apply and reconnect. Have an administrator verify credentials privately.
4. Use supported offline operation only where an initialized local copy exists; a newly installed workstation may have none.
5. Record the exact error, time and affected computers for support instead of disabling all protection or deleting database files.

Why sales synchronization and tax issuance are separate

Sales, payment and tax-document results are three states. An uploaded sale does not prove that a fiscal document exists.

Steps

1. First verify the original sale, its amount and payment result in sales history.
2. Then inspect the fiscal status, reference or error for the correct country and originating till.
3. Offline upload preserves the original sale and synchronizes sales data; it does not automatically resubmit tax invoices.
4. Use authorized manual recovery for the applicable country. Reconcile uncertain results before retrying.
5. Maintain the link between sale and fiscal number and review outstanding exceptions.

Connect an Argentine Epson fiscal printer over Ethernet

The current Argentine Epson integration uses Ethernet. USB/serial sockets on the hardware do not mean the current software integration uses them.

Steps

1. Record the model, firmware and self-test network settings. Connect through the store LAN or directly to the computer while avoiding address conflicts.
2. Example only: with printer 192.168.1.1 and mask 255.255.255.0, a dedicated direct Ethernet adapter may use unused 192.168.1.10 with the same mask and blank gateway/DNS; internet access can remain on Wi-Fi.
3. Open the actual printer IP in a browser after checking connectivity. Epson Manager access proves management-page reachability, not completed fiscal acceptance.
4. Enter the actual IP in POS fiscal-printer parameters and test the connection. Verify model, serial number, sales point and training/fiscal mode.
5. Have the responsible person configure real business identity, tax treatment, method codes and registration. Use an approved test environment before live issuance.

Argentine fiscal success, failure and uncertain results

Establish whether the sale was saved, then distinguish fiscal success, definite failure and an uncertain result. Uncertainty is not proof of non-issuance.

Steps

1. After checkout, verify the sale reference and fiscal type, sales point and number.
2. For definite failure, record the device error, resolve paper/cover/network issues and use the original sale’s manual recovery path.
3. For an uncertain result, inspect physical output, device status and software reconciliation before deciding whether a document exists.
4. Recover from the till connected to the original printer using the original sale, rather than recording another sale on a different device.
5. Process refunds from the original sale and verify the corresponding fiscal correction and original reference.

Argentine fiscal closure, open-day queries and reports

A POS shift Z report differs from the printer’s Cierre Z. Epson Manager history may list only closed fiscal days; check open-day sales in software history and current device status first.

Steps

1. Find the sale by number and inspect its fiscal reference. Empty closed-day history is not a reason to issue it again.
2. Use supported status or X-report functions for current-day review instead of forcing closure just to query.
3. In the current Argentine configuration, Back Office fiscal-day records provide date/printer filters, document counts, software/device totals and differences.
4. At business-day completion, follow the responsible person’s closure procedure and retain the Z number. A software shift closure is a separate record.
5. Review unissued documents and downloaded reports, then handle submission and retention with the accountant. Downloaded does not mean submitted.

Missing menus, disabled buttons and hidden fields

Check edition, company options, permissions and document state in that order.

Steps

1. Confirm the installed edition. Enhanced Edition does not gain POS or authority menus merely by granting permissions.
2. Check multi-unit, tax, batch and bin switches; related hidden fields can be normal when disabled.
3. Review operator/cashier rights and have an authorized person inspect masked costs.
4. Approved, unsaved or empty documents can legitimately disable editing, approval or printing.
5. Read the available hint and record the exact entry, state and version before escalating.

Send a useful support report

A useful report identifies the same transaction and a reproducible sequence, rather than only saying “slow” or “wrong amount”.

Steps

1. Record version, edition, language, store and online/offline state.
2. Describe the menu, steps, expected outcome and actual message, with time and document number.
3. For amounts include goods, quantities, units, prices, tax and methods; for stock include warehouse and approval state.
4. Capture relevant screen context while hiding credentials, payment secrets and unrelated personal information.
5. State whether all computers are affected, whether it repeats and what has already been tried. Preserve uncertain payments before further action.