Customers

Someone who shops online is the same customer at the counter, with the same account, order history and group pricing. The register reads customer records live from Magento's customer API and keeps a local copy for offline lookups; it writes back only when the cashier creates or edits an account.

Find and Attach

Search by name or email from the checkout screen or the Customers tab. Results come live from Magento, with the locally cached customer list filling in when the connection is slow or gone.

Attaching a customer to the sale does two things immediately:

• The sale lands in the customer's Magento order history, visible online and at the counter.
• Their customer-group pricing applies: tier prices and group-specific prices re-resolve on every cart line the moment the customer is attached.

Groups themselves are plain Magento customer groups. A wholesale customer gets wholesale prices at the register with nothing POS-specific to set up.

Guest and Walk-in Sales

By default a sale does not require a customer account. A Guest Checkout button clears the attached customer, and a sale without one books to your walk-in customer: a set of default name, email, phone and address values stamped on the order so every POS order is a complete Magento order.

• On the free tier, the walk-in values live per device under Settings → Walk-in Customer. Empty fields fall back to placeholder values on the order; fill in real ones if your jurisdiction requires a complete address on receipts.
• On PRO, the walk-in defaults come from Magento, under Stores → Configuration → Hyvä POS → Terminal Defaults → Walk-in Customer Defaults or a per-location override, and empty fields inherit the resolved store address.

Magento's walk-in values apply on the register as they arrive. With Lock Walk-in Customer Defaults on, the fields show a lock and a Magento badge and cannot be edited on the device. Unlocked, the device may edit them, and a local edit holds until Magento's value next changes.

Allow Guest Checkout decides whether a sale may be paid with no customer attached. On the free tier it is a device setting under Settings → Store → Checkout. On PRO, for a terminal bound to a location, it comes from Stores → Configuration → Hyvä POS → Terminal Defaults → Customers → Allow Guest Checkout, overridable per location. With it off, a sale needs a registered customer before it can be paid, and checkout answers "Guest checkout is not allowed." The walk-in details do not count as a customer. Refunds, exchanges and layaway payments are not affected, and the cart can still be held.

On PRO, a customer can later claim the receipt into their account by scanning the receipt QR code while logged in.

Create at the Register

An account can be created during the sale:

• Required: first name, last name, email.
• Optional: company, VAT number, and a first address (street, city, postcode, country, phone) one disclosure tap away, worth capturing for VAT-relevant B2B sales and shipped orders.
• Create Account in Magento checkbox: checked, the details become a real account; unchecked, they only ride along on this sale.

The account is a normal Magento customer, created through the standard customer API on the free tier, and immediately usable online with a password-reset email. New accounts start in your store's default customer group.

Validation

On the free tier the register checks the basics before submitting: required fields present, email in a valid format. Magento remains the authority and its errors surface inline.

On PRO, creation runs through a server-side validator pool: once live while the cashier types, and again authoritatively at save. Validators return graded outcomes:

• Errors block the save (a duplicate email, a missing required field).
• Warnings inform but let the save through.
• Suggestions offer a corrected value the cashier accepts with one tap: a normalized VAT number, a fixed postcode format.

First-party validators cover required fields, email uniqueness, EU VAT-number format and per-country postcode patterns. Agencies add their own for address-verification services or house rules; see customer validators.

Edit at the Register

From the customer's detail panel the cashier can correct the name and email, and manage the address book in full: add, edit and delete addresses, set the default billing and shipping flags, with postcode formats checked per country. Changes save straight to the Magento customer record.

The customer group can be changed too, but only by staff with the manage-groups permission. Everything beyond that (custom attributes, account status) belongs in the Magento admin, and the edit screen says so.

Customer Details

The detail panel shows the profile, addresses and full Magento order history. On PRO it also shows the customer's webshop wishlist, plus store credit, gift card and reward point balances where a credit provider is installed.

Also on PRO: a newsletter toggle that subscribes or unsubscribes the customer from the register, with the same validation the webshop applies, and the Customer Insights tile: spend, purchase frequency, and what they bought last time, computed live when tapped.

Where OTP Applies

The cashier never needs a customer's password: at the register, staff act on the customer's behalf. The one place a customer signs themselves in is self-checkout (PRO): the shopper enters their email on the kiosk, Magento emails a one-time code, and entering it attaches their account to the kiosk cart, with their group pricing and order history. No password is typed on a shared screen. Codes expire, and repeated wrong attempts are rate-limited server-side.

Where It's Configured