Connecting Your Store

The guided setup walks you from an empty app to a register that is ready to sell. It starts with the store URL and authentication, then covers the settings a counter needs: store view, payments, tax, printer and receipts.

The Guided Setup

On the first screen, choose Connect Store. You can connect as many stores as you want, and add more later from settings. Try Demo Mode on the same screen explores the app against a sample catalog without connecting anything.

The wizard then walks these steps:

1. Store URL: your Magento web address, for example https://www.example.com. When a store with the same URL is already connected in the app, the step says "This store is already connected as ." and offers Continue That Store's Setup Instead. The notice does not block: continuing with Next adds a second connection to the same store.
2. Authentication: pick a method (below) and enter its credentials.
3. Permission Check: the app authenticates and checks every resource it needs. Anything missing is listed with a hint on how to fix it, and setup continues either way.
4. Store Settings: the store view to sell from, plus categories and inventory source. Magento's default store view is preselected, and each view shows the base currency of its website, which is the currency the register will use. Products, categories and customers come straight from Magento; there is no import step.
5. Payment Methods: which methods this register offers.
6. Tax & Pricing: these should match your Magento tax configuration.
7. Printer Setup: a receipt printer over Bluetooth or WiFi, or AirPrint.
8. Receipt Settings: header, footer, logo and branding. The last button reads Start Selling.

Three further steps appear only when they apply. Two of them sit between the permission check and the store settings:

• hyva.io Connection, when the PRO module is installed but the store is not linked to hyva.io yet. The app checks the connection, confirms it, and moves on by itself.
• Terminal Activation, when the PRO module is present and this device is not a terminal yet. Activating here means the settings steps arrive already filled in from the terminal's location; see activating your device.

The third, Fiscal Compliance, follows the store settings in countries that require signed receipts (Germany, Austria, France, Italy). Fiscal signing is not available in the app yet, so the step says "Fiscal signing is not available yet" and links to what that means for the store's country; see fiscal compliance.

Every settings step carries Skip for Now, so you can get to the register first and configure later from settings. Terminal activation is skippable unless your store requires terminal registration. The permission check offers Continue Anyway when something failed.

Pausing and Discarding

Closing the wizard asks what to do with the work so far:

• Save for Later keeps your progress. The first screen then offers Resume Setup, which returns to the step you left and signs back in with the saved credentials.
• Discard Setup deletes the store connection and any settings entered so far. This cannot be undone.

Authentication Methods

Integration Token

The recommended method for production. Create an integration in Magento (how), copy the access token, and paste it into the app. The token does not expire; you revoke it from the Magento admin when a device should no longer have access.

Requires the standalone Bearer token setting described in Magento configuration.

OAuth 1.0a

The strictest option: the app signs every request with the consumer key and secret, so a captured request cannot be replayed or tampered with. Enter all four credentials from the integration (consumer key, consumer secret, access token, access token secret). No extra Magento settings needed.

Admin Login

Enter the username and password of a Magento admin account and the app requests a token for you. Tokens expire (four hours by default); with stay signed in enabled (the default), the app stores the credentials in the device keychain and renews the token automatically, so you only notice if the password changes. Without it, the session expires after a few hours and the register stops until someone signs in again.

If the account has two-factor authentication with Google Authenticator, the app asks for the six-digit code after the password. Other 2FA providers cannot be answered from the app; use an integration token for those accounts.

Admin tokens are tied to the account: signing in on a second device with the same admin account may invalidate the first device's session. Give each device its own admin account, or use an integration token.

Use this to evaluate quickly. For production, prefer an integration token: it survives password rotations, does not depend on 2FA settings, and can be revoked independently.

Multiple Stores

Add as many Magento stores as you like from Settings → Connection. Each store has its own authentication, catalog, and settings, and you switch between them from the store picker in the header. One store can run PRO while another runs free.

Store Views and Currency

The register prices in the base currency of the website its store view belongs to, read when the device first connects. A store with several websites can carry several currencies; the register follows the store view it sells from. To change it, pick another store view in the store picker, or open Settings → Store Configuration, which names the store view and website the currency comes from and offers to adopt a new value when Magento reports one.