Luck Next

Versions & permissions

Aligned with current Luck cloud and designer behavior (including designing barcodes and QR codes on labels and printing). The online license UI and your contract win if anything differs. More detail: Label printing software.

Cloud web features (online)

  • Excel smart template print, scan print, list print: Enterprise and LuckNext; sub-accounts need template print to use those flows.
  • Cloud save vs. local save: Standard is limited when choosing “save to local file”; sub-accounts saving locally need design create (and related) rights.
  • Counters, serials, LuckData connections: managed in console after sign-in; quotas and visibility vary by role. Luck counters = cloud serial rules; LuckData = enterprise data and audit – different menus and purposes.

Intranet, data, local services

  • Intranet offline design: requires intranet activation; not the full public account/quota stack – features as activated.
  • LuckData: on-prem data service – sources, query APIs, print history; cloud stores connection settings to it. Process vs. cloud parameters are different layers – document separately. Business dedup at scan vs. print history for traceability – evaluate separately.
  • LuckNext: HTTP API for print, preview, printer lists, etc. on workstation or servers – cloud or other deployment per delivery; separate install and license.
  • LuckCert: dev HTTPS helper – not a commercial CA.

SDK licensing

Embedding design and print in browser or business apps uses two JavaScript SDKs – entitlements vary by tier; contract and delivery docs are authoritative.

  • Enterprise: LuckDesign SDK (designer, templates, variables). If LuckNext SDK is not licensed, do not rely on LuckNext print SDK features.
  • LuckNext (product line): both LuckDesign SDK and LuckNext SDK for the full design-to-print workflow (printer lists, jobs, dialog print – as implemented).

Developer site and versions

Docs, demos, and scripts: dev.lucknext.com. SDK versions follow live site; use minified files from /sdk/ (e.g. sdk-luckdesign.min.js, sdk-lucknext.min.js) – never expose real keys or account IDs in public pages.

Demo entry points (URLs as online):

Tiers: Enterprise, LuckNext; roles: Ecosystem.

Feature checklist

Matches the bullets on Product overview for easy search.

Cloud: Excel smart template print, scan print, list print

Enterprise, LuckNext; sub-accounts need template-print and related rights.

Cloud: save templates, print history (partial)

Role- and license-dependent; history/audit often higher tiers. History ≠ scan dedup – different dimensions.

Cloud: save to local file (from browser/designer)

Standard policy restricted; sub-accounts need design create for local save.

Counters, LuckData connections

Console after login; quotas and visibility by account family. Cloud serials via Luck counters; LuckData connections for intranet data and history – not interchangeable.

Intranet offline design

Requires intranet activation; subset of public cloud.

LuckNext API, LuckData server

Separate deploy and license from the LuckDesign installer.

Related pages

Licensing inquiry Home