Offline permanent activation handbook

Customer: keep the same local business

1. Create/open your local business. The automatic trial is seven days plus three days grace. Expiry preserves records and access to activation.
2. Desktop: open the launcher's License & local package section and choose Show activation request. Android: open the local business → License → Copy activation request. Permanent native activation requires Android 1.3.0-preview or a compatible later build.
3. Send that request to support using any available phone, email or private agreed channel. It contains installation proof and local business identity, not passwords or sales.
4. Confirm the package, platform, installed version, price and payment recipient with support, then pay through the agreed channel. Desktop Retail/Water has the advertised ₱499 one-time offer; other arrangements require their own agreed price.
5. Receive the signed product key or .gnjlicense file. Transfer it to the original device by USB, file transfer or copy/paste.
6. Paste/import the key, choose Verify & preview, check the package/version, then Apply local package. Desktop closes Owner/POS windows during activation. Your existing business, receipts, stock and passwords remain.

No reinstall, new local business, trial reset or cloud login is required. The short local trial reference is not a paid activation key.

Super Admin: issue without creating a cloud tenant

1. Open Offline licenses. Do not create a cloud tenant solely to activate an offline business.
2. Paste/import the customer request. Select a supported package, the exact purchased app version and the agreed amount. Verify the installation and review the preview.
3. Record the business name and customer contact. Verify actual receipt of payment and the customer's ownership of the supplied request. Record the method, payment reference and verification note.
4. Generate the permanent key, copy/download it and send it privately. Payment fields are manual verification evidence; the system does not automatically charge or verify a provider.
5. Use the Local-generated purchases list to recover/download an already issued key. It remains Not cloud-registered until separately registered; duplicate issuance is blocked.

Terms, recovery and cloud access

• Permanent use covers the purchased build and installed licensed features. Updates/support may have separate terms; their expiry does not stop the purchased version.
• Keys are bound to the installation and local business. A key for another device/business or version is rejected. Copying the key does not license another installation.
• Apply to the same installed business even if its trial has expired. Never clear app storage or reinstall to address an activation problem.
• Device loss, reinstall/rebinding, package upgrades and moving to another purchased version need separate support review. This page does not implement automatic replacement or transfer.
• The key does not grant a Cloud subscription or upload local sales. Desktop's later metadata registration remains separately verified and operational reporting needs an active matching Cloud subscription. Android cloud registration/reporting is separate work.
• A disconnected device cannot learn immediate server revocation. Keep signing private keys on the administrator server only.

Administrator deployment requirements

Apply migration 068 to an existing database using a verified backup/rehearsal; never apply the fresh baseline to existing data. Configure PACKAGE_OFFLINE_ISSUER_KEY_FILE and PACKAGE_OFFLINE_ISSUER_KEY_ID, or the existing desktop issuer variables. The signing key must be a protected server-only RSA private key. The matching public key must be installed in the customer desktop/APK. Configuration readiness is shown in Offline licenses; cloud deployment is separate from local build verification.

Local item pictures

Desktop 0.4.1: open Business Owner → Products & stock → Add product. Save the item, open Edit, and use Choose local picture. JPEG, PNG and WebP up to 2 MB are supported. Authorized catalog editors can replace/remove the picture. The picture appears in the catalog and POS, is included in the local database backup, and requires no Google authorization.

Android 1.4.0-preview: unlock Business Owner → Catalog, create the product, then choose Item picture → Camera or Choose photo. The camera may lock Owner when the app goes into the background; unlock Owner and choose Save picture locally. The selected photo is retained while you unlock. Native pictures are resized and saved locally, with a limit of 1,000 pictures per business. Encrypted owner backups include the pictures within the existing 20 MB backup limit; keep the backup password separately.

Cloud reporting retains the item details and uses a placeholder. It does not upload item picture bytes or a device file URL. Older backups without pictures remain readable; restoring conflicting newer pictures stops the merge rather than overwriting them. Cancelled or unavailable camera actions leave the saved item unchanged.

Previously purchased version-bound keys remain bound to their purchased version. Confirm update/license terms before changing versions; do not clear local data to update.