The Pilot

You're in the pilot, or considering it. This page covers what's different while Hyvä POS is in closed beta: how you get the app, the module and the licenses, what we need from you to set that up, and what to expect from a product that is still changing.

Everything else in this documentation applies to the pilot as written: the register works the same whether the build came from TestFlight or, later, the App Store.

What We Need From You

We need two things to set the pilot up on our side; there is nothing to buy during the pilot. What you configure yourself is the connection from your store to your licenses (see Licenses below):

• The email address of your hyva.io account: the pilot is enabled on that account: it is where your Packagist key is issued, where you take your terminal licenses, and where the API connection for your store lives. If you don't have an account yet, create one at hyva.io first and send us the address you used.
• An Apple account email for the TestFlight invite. This can be a shared account (for example a team account used on several store devices), and it does not need to be the main Apple account on the device: you can sign into TestFlight with a different account than the one the device itself uses.
• For agencies and implementation partners: GitLab usernames or your GitLab group name for direct access to the module repository. Merchants normally don't need this: the Packagist key covers the install, and if a partner implements the POS for you, tell us who they are and we set up their access instead.

By taking part in the pilot you accept the Hyvä POS license terms; read them before you start.

Getting the App: TestFlight

During the pilot the app is distributed through Apple's TestFlight, not the App Store:

1. Install the TestFlight app from the App Store on the device that will run the register.
2. You'll receive an invite by email on the Apple account you gave us. Open it on the device (or enter the redeem code in TestFlight) and install Hyvä POS.
3. Updates arrive through TestFlight. Pilot builds ship frequently. Update when TestFlight prompts you, since fixes you've reported usually arrive in the next build.

Two TestFlight particulars:

• TestFlight builds expire 90 days after release. Updating now and then avoids this; a register that's been off for months may need a fresh install from the current invite.
• The invite is tied to the Apple account, not the device. To move to a new device, sign into TestFlight and install again; your store connection settings transfer with your usual device migration.

Licenses

During the pilot, terminal licenses are free and unlimited for as long as the pilot runs and you take part. You take them yourself from the Hyvä POS terminal product page, which your account can order from once it is in the pilot: one license per register you want to test on, registered against the domain of the store you are piloting. Take at least one before installing the module: the first license is what sends you the Your Hyvä POS access email with the Packagist key. In some cases the Hyvä team provisions the licenses into your account directly; your onboarding email says which applies to you.

Then connect your store to them:

1. On your hyva.io account, open POS Terminals (hyva.io/licenses/manage/shops) and generate the API key and API token pair for your store. The token is shown only once, at generation, but you can look the key up and reset the token on that page at any time.
2. Enter both under Stores → Configuration → Hyvä POS → General → Hyvä POS License Connection and save, then open Hyvä POS → Store Setup → Licenses and press Fetch Licenses: your licenses appear, and a scheduled job keeps them in sync from then on (see buying and licensing for the full walkthrough).

From there, activating your device works as documented: under Hyvä POS → Store Setup you create a location and a terminal, attach a license to the terminal, and activate the device with the terminal's activation code. Give the location its real address: the register takes its tax country from it.

Licenses work on a 30-day lease the app renews automatically in the background, so a temporary store outage does not lock your register. If you add registers mid-pilot, take another license; if the product page does not let you, ask.

After the pilot: what stays free

Pilot licenses cost nothing while the pilot runs. Afterwards, a Hyvä Commerce license includes two POS terminals, so two registers carry on as they are. Any terminals beyond what your license includes are charged at the regular rate after the pilot, unless you decommission them when it ends.

Getting the Module

The PRO module installs with Composer, as described in installing the module. Your first terminal license (see Licenses above) triggers an email titled Your Hyvä POS access with the Private Packagist key and URL for your store and the two composer config lines that set them up. Run those two lines in your Magento project as they are, then composer require hyva-themes/magento2-hyva-pos and the usual setup:upgrade, setup:di:compile and cache:flush. That email contains credentials: forward it to your developer if they do the install, and to no one else. If Composer cannot find the package, the two config lines did not land in the project you are installing into; run them again from that project's root.

Implementation partners who prefer working against the source can get GitLab repository access on request: include the GitLab usernames or group name in your onboarding reply. Merchant accounts normally don't get repository access: the Packagist key covers the install, and when a partner implements the POS for you, we set access up for their developers.

What to Expect During the Pilot

• The product changes frequently. Features and configuration may still change, occasionally in backwards-incompatible ways. Module updates (composer update hyva-themes/magento2-hyva-pos) and app updates are best taken together; release notes flag when a build needs a matching module version.
• Start on a test or staging copy of your store. It is beta software: install the module there first, put a few sales through the register, and only then install it on the live store. Staging and live can use the same API key and token. If the staging environment sits behind HTTP basic authentication, the app cannot get through it; exempt Magento's REST API (everything under /rest/) from the basic auth, or allow the IP address your devices connect from (see the FAQ).
• Then run it next to your existing register at first. The app is built for business continuity (offline mode, local receipts), but during a pilot you can prove it on real traffic while your current setup is still in place.
• Your feedback informs the roadmap. Reply to your pilot onboarding email with anything: bugs, missing features, hardware that does not work, wording that reads wrong. For bug reports, a screenshot plus what you expected to happen is usually enough; the register also keeps an error log under Reports → Errors you can check and include.
• Hardware: the hardware pages list what's been physically tested. If you're buying new gear for the pilot, pick from the tested list, and if you already own something that isn't on it, tell us; expanding tested coverage is part of what the pilot is for.

After the Pilot

The general release lands on the App Store, and licenses move to regular buying and licensing through hyva.io. We'll contact every pilot participant about the transition well before anything changes. Pilot stores keep working; no register is deactivated automatically.