Skip to content

The Pilot

Hyvä POS is in closed beta

Hyvä POS is currently in a closed beta (pilot phase) with a small group of merchants. It is not yet generally available: the App Store release follows the pilot, and features and configuration may still change - possibly in backwards-incompatible ways - before the general release. Want to take part? Sign up at hyva.io/pos.

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 moving fast.

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

Send these along and the Hyvä team provisions everything - there is nothing to buy during the pilot. The one thing you configure yourself is the API key connecting your store to the provisioned licenses (see Licenses below):

  • Your hyva.io account email - the account we provision the POS license into.
  • An Apple account email for the TestFlight invite. This can be a shared account (for example a team account used on several store iPads), 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 iPad itself uses.
  • The domain name of your Magento store - the Packagist access and the terminal licenses at hyva.io are created against it.
  • 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.

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 worth knowing:

  • TestFlight builds expire 90 days after release. As long as you update now and then this never surfaces; 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. Moving to a new iPad is signing into TestFlight and installing again - your store connection settings transfer with your usual device migration.

Getting the Module

The PRO module installs with Composer, exactly as described in installing the module - the only pilot difference is where the credentials come from: the Hyvä team sends you the Packagist key and project name directly, rather than you finding them on the Hyvä Hub after a purchase.

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.

Licenses

Terminal licenses are provisioned by the Hyvä team in your hyva.io account, against your store's domain name. Once we've confirmed they're in place, connect your store to them:

  1. Generate the API key and API token pair on your hyva.io account's POS licenses page - the token is shown only once, at generation.
  2. Enter both under Stores → Configuration → Hyvä POS → General → Hyvä POS License Connection (see buying and licensing for the full walkthrough).

From there, activating your device works as documented: the module fetches the provisioned licenses, you create locations and terminals in the Magento admin, and activate the iPad with the terminal's activation code.

Licenses work on a 30-day lease the app renews automatically in the background - a store outage never locks your register. If you add registers mid-pilot and run out of licenses, ask; that's a one-minute provisioning step on our side.

What to Expect During the Pilot

  • The product moves fast. 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.
  • Run it next to your existing register at first. The app is built for business continuity (offline mode, local receipts), but during a pilot the sensible path is proving it on real traffic while your current setup is still within reach.
  • Your feedback steers the roadmap. Reply to your pilot onboarding email with anything: bugs, missing features, hardware that misbehaves, 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 Settings that's worth checking and mentioning.
  • 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; nothing switches off by itself.