RetailSelf-serviceHow to

Deploy a self-service POS unit

Record the required setup details, configure the self-service POS unit and its device, and verify the deployment with an end-to-end test sale.

Deploying a self-service POS unit involves four areas that need to be configured and verified together: digital receipts, the self-service POS configuration in Business Central, the device and its installed software, and the self-checkout URL that customers land on.

Use this article as a commissioning checklist. Record the values marked as placeholders (for example, <POS unit>) for the installation you’re working on, complete each configuration step, and then run through the verification checklist before handing the unit over.

Note: This article ties together the individual setup articles rather than replacing them. Each step links to the detailed procedure it relies on.

Prerequisites

  • A Fiskaly Dashboard account with permission to create API keys.
  • Access to the Business Central environment that the self-service POS unit belongs to.
  • The Zebra device, payment terminal, scanner, and printer are physically installed and connected to the network.
  • A master POS unit already exists, so the self-service unit can be attached to it for end-of-day balancing.

Step 1: Set up digital receipts

Digital receipts replace printed receipts on an unattended unit, so they need to be working before the unit goes live.

  1. Create an API key in the Fiskaly Dashboard, and record the credentials:

    DetailValue
    Fiskaly Dashboard API key<API key>
    Fiskaly Dashboard API secret<API secret>

  2. Complete the digital receipt setup in Business Central.
    Enable the feature, enter the API key and secret, and click Test API Credentials. The Credentials Test Success toggle needs to be on before you continue, because digital receipts can’t be enabled without a successful credentials test.

  3. Create a POS Receipt Profile, and record its code:

    DetailValue
    POS Receipt Profile<profile code>
    POS unit receiving the receipt profile<POS unit>

  4. Assign the POS Receipt Profile to the self-service POS unit in the POS Unit Card.

  5. Confirm the QR-code behavior that the profile defines.
    The Issue Digital Receipt After Sale, QR Code Timeout Interval Enabled, and QR Code Timeout Interval(sec.) fields determine whether the QR code is displayed after the sale, and how long it stays on the screen. On an unattended unit, setting a timeout interval makes sure the QR code closes on its own when a customer walks away.

  6. Confirm the email receipt requirements with the customer.
    Send E-Mail Receipt on Sale only works when a customer is attached to the sale, and that customer has an email address listed on their Customer Card. Sales without an attached customer receive the QR code only.

Step 2: Configure the self-service POS unit

Follow the full procedure described in Set up POS Self-Service Profile, and record the profile codes you use:

DetailValue
POS unit<POS unit>
POS TypeUnattended
POS View Profile<profile code>
POS End of Day Profile<profile code>
Master POS unit<master POS unit>
Slave POS units<slave POS unit(s)>
POS Named Actions Profile<profile code>
POS Security Profile<profile code>

Make sure that the following settings are in place:

  • POS Unit Card - the POS Type is set to Unattended. Without it, payments aren’t transferred automatically to the master POS unit.

  • POS View Profile - Show Prices Including VAT is activated, Initial Sales View is set to Sales View, and After End-of-Sale View is set to Login View.

  • POS End of Day Profile - the End of Day Type is set to Master & Slave, Master POS Unit No. points to the master unit, and both the master and the self-service unit use the same end-of-day profile.

  • POS Named Actions Profile - the self-service POS actions are assigned as follows:

    FieldAction code
    Login Action CodeSS-START-POS
    Text Enter Action CodeTEXT_ENTER
    Item Insert Action CodeSS-ITEM
    Payment Action CodeSS-PAYMENT
    Lock POS Action CodeSS-IDLE-TIMEOUT
    Idle Timeout Action CodeSS-IDLE-TIMEOUT

  • POS Security Profile - the Lock Timeout field is set to NEVER, because an unattended unit shouldn’t lock itself.

Step 3: Install and configure the device

  1. Record the device details:

    DetailValue
    Zebra device model and identifier<details>
    Kiosk mode configuration in Major Tom<configuration details>

  2. Install and configure Self-service Minor Tom on the device.
    Enter the POS-relevant information, review the configuration settings that are displayed, and click Validate.

  3. Install the HW Connector, and confirm that it starts and connects.
    The HW Connector is the bridge between the local hardware and the POS interface, so the scanner, printer, and payment terminal can’t be used without it.

  4. Switch Major Tom to kiosk mode.
    In the Major Tom configuration view, change the display mode to kiosk mode. A kiosk mode configuration banner is then displayed, from which you can reach the self-service configuration view.

  5. Confirm that the required hardware peripherals work:

    • Payment terminal - paired, online, and connected to the EFT interface used by the SS-PAYMENT action.
    • Scanner - scans an item barcode and inserts a sales line.
    • Printer - prints using the configured print template.
    • Network connectivity - stable, with the ports listed in the system requirements open.

Step 4: Set up the self-checkout URL

The self-checkout URL is what the device opens when it starts, so it determines which POS unit and environment the customer ends up in. Record and confirm the following:

DetailValue
Target URL<URL>
POS unit and environment associated with the URL<details>
Authentication and customer-access approach<details>
Expected landing screen and idle-timeout behavior<details>
  • The URL needs to resolve to the environment that holds the configured self-service POS unit. Pointing a device at the wrong environment is a common cause of a unit that opens, but can’t start a sale.
  • Because the unit is unattended, agree with the customer on how the device authenticates without a salesperson signing in, and make sure that no credential prompt can be reached by a customer.
  • The expected landing screen is the Login View defined in the POS View Profile. Customers start a sale from this view through the SS-START-POS action.
  • Idle-timeout behavior is defined in the timeout object of the sale and payment view JSON, which sets the number of idle seconds (after), the grace period (graceTime), the prompt displayed to the customer, and the SS-IDLE-TIMEOUT action that returns the unit to the Login View.

Verify the deployment

Run an end-to-end test sale on the device, and confirm each of the following:

#VerificationResult
1A customer can start a self-service sale on the Zebra device.
2Items can be scanned and paid for successfully.
3The sale posts correctly in Business Central.
4The completed sale returns to the Login View after the configured timeout.
5A digital receipt is issued successfully after the sale.
6QR-code and email receipt behavior matches the agreed POS Receipt Profile.
7The self-checkout URL opens the correct self-service flow.
8The POS unit, device, payment terminal, and HW Connector operate reliably throughout the test sale.

If any of these checks fail, work through the self-service profile troubleshooting checklist, which lists the setup steps in the order in which they need to be completed.

See also