> This page is for Product Documentation. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.navipartner.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server. # NP Retail Emergency mPOS (reference guide) > This article contains details on all setup pages in the NP Retail Emergency mPOS app. ## NP Retail Emergency mPOS home page As soon as you open the app, you are presented with the following options: | Action Name | Description | | ------------ | ------------------------------------------------------- | | **New Sale** | Begin a new sale or resume an existing sale on the POS. | | **Sync** | Synchronize unsynchronized sales. | | **History** | Open a list of completed sales. | | **Setup** | Open the setup menu. | ![emergency\_1](/_fern-files/_img/85b50e0c0d0e1fb954e62c89d16dc27b0c3fa857fd0f98e433cc40db7836c715.webp) ## Setup page The **Setup** page is opened by tapping **Setup** on the home screen. It contains the following options: | Action Name | Description | | --------------- | ---------------------------------------------------------------------------------------------- | | **Quick Setup** | Perform basic setup. | | **BC** | Configure Business Central options. | | **Payment** | Configure payment. | | **Scanner** | Choose between **Camera** and **HID** (Hardware Input Device/keyboard simulator) for scanning. | | **Items** | Manage products and pricing. | | **Help** | Access troubleshooting guides. | ## BC setup The Business Central setup page is used for connecting to Business Central and synchronizing sales. Most of the available fields it contains are used for targeting specific Business Central environments. The SMS and Email Template codes refer to special setups that are used when sending out receipts. ![emergency\_4](/_fern-files/_img/d82e6e26f4b92c2107340271b27b0bf245705a2a78b47570c11b54e5bf40c256.webp) ## Payment setup The payment setup page specifies all configurations related to sales and payments. | Action Name | Description | | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Sale POS ID** | References the POS unit. Each POS unit should be linked to only one device. This setup allows the emergency POS to share the same cash drawer as the regular POS. | | **EFT Payment Method** fields | All EFT payment method fields are related to the POS payment method. When sales sync with NP Pay, card details are automatically mapped. | | **Cash Payment Method** fields | Specify configuration details for handling cash transactions. | | **EFT Payment Method: Monetary Unit/Cash Payment Method: Monetary Unit** | Defines the smallest accepted payment unit. For example, a value of 0.50 means valid payments are 1.00, 1.50, 2.00, but not 1.33 or 1.25. | | **Payment Integration** | Configures payment processing options: - Adyen Tap to Pay – Uses the Adyen Payments app for Android devices. - LAN Terminal – Uses the NP Pay device’s built-in payment functionality. | | **Encryption Details** | Stores security credentials (ID, password, and version) at either the terminal or store level. When using the [Tap to pay](/product/np-pay-tap-to-pay) feature, configuration must be done at the store level, as the **Terminal List** does not include these details. | | **Tap to Pay** | After configuring Encryption Details and Adyen Merchant Setup, you can establish a connection with the Adyen Payments app (a process called Boarding). If the app is uninstalled or unregistered, the Boarding process must be repeated. | | **Local Terminal** | The **POI ID** uniquely identifies an NP Pay device using the format: \[Device Model]-\[Serial Number]. This applies only to NP Pay devices and is usually auto-filled. | ![emergency\_5](/_fern-files/_img/c578ab20080c8ca8d3c6b2fa1a76e4dac6abecd94dcb5a5f893e5485ca781195.webp) ## Scanner setup For scanning, you can either use the camera together with the **Binary Eye** app for barcode scanning, or the HID (Hardware Input Device), which is keyboard simulated events. The latter is typically used with devices that have built-in laser scanner functionality. ![emergency\_6](/_fern-files/_img/281b99d64588a520def42751cc3fa3a353c15cd03e935e992315b272f965ff7d.webp) ## Help page The **Help** page is used for troubleshooting the app. It contains **Logs** and **Data** sections. ![emergency\_7](/_fern-files/_img/a23d457529b386dc0fd05c9280094fa731804fc151fe075e896d60359ea7c83d.webp) ### Logs Error and crash events are automatically collected, but enabling the **Logs** feature extends the info written to a local file. The upload logs can upload the log file to a NaviPartner online storage, so a developer can identify issues with the app. ### Data The database is another type of local storage that keeps track of all sale and item data. In case of data corruption, the database can be uploaded and inspected to identify issues within the sale data. > **Note:** The **Delete Database** button should be used with extreme caution, as it will delete all data, and this will not be recoverable. ## Item page The **Item** page contains a list of all created items. The items can contain the following information: * Name * Barcode * Price If a user scans a barcode and the barcode is registered in the app, the app will automatically fill the information when inserting the sale line. ![emergency\_8](/_fern-files/_img/2d858ce62a0f936af8d4fbc73bce5b1105feaae5bea3ec96bebe38c999919553.webp) ### POS page The **POS** page contains the list of items in sale lines. The sale lines can be created in one of the following ways: * Scanning a barcode * Creating a new empty line * Creating a new item * Adding an existing item ![emergency\_9](/_fern-files/_img/43adb9dde01fdfc03038d3fed81c5091e6d4f8d1e4a09fea04a204c851869570.webp) You can also take the following actions: * Cancel the entire sale if no payments have been made. * Proceed to the **Payments** page, by pressing the green cart button. * Edit or remove lines with the buttons that appear from swiping the item to the right and left respectively. ![emergency\_10](/_fern-files/_img/d316eaeef55f85662e3b625944bbcf7f64bdf75fd0a61f2a12e6e7af0d41472b.webp) > **Note:** Updating lines in the edit mode does not update the **Item** itself, only the sale line. ### Payment page On the **Payment** page, you can create new payments either with cash or electronic payments that use the NP Pay setup. It also contains the overview of the sale total, the amount paid and the remaining amount. If the sufficient amount has been paid, the user is prompted with the **End of Sale** pop-up window, where the phone number and email can be collected, as well as information on whether the customer wishes to receive an electronic receipt when the sale is synchronized to Business Central. After you click **End Sale**, the sale is finished and you will be redirected back to the home screen. ![emergency\_11](/_fern-files/_img/c999a9b8d297c1dc2aaf50541fd220b4c6b64784d1c1b5f0349dc0fbf1ad1466.webp) ### History page The **History** page contains all sales made with the app in reverse chronological order. If you press on a sale, you will be presented with its details. ![emergency\_12](/_fern-files/_img/03a5b93b2763eab248753a475329b4ba98f80492678fae023f5aa9aafa30fa02.webp) ![emergency\_13](/_fern-files/_img/4ad3d5313e6a506fc90f4b3be7f7069d9fa86e165e77bdd422f934609680a2ca.webp)