LPSNG Pricing: Which Edition Fits Your Needs?

Before you compare LPSNG pricing, compare your operation. A label printing system is not an impulse purchase: the edition that saves a three-person workshop money may be wrong for a multi-region fulfillment center, and the enterprise-ready setup may be overkill for a single packing station.

LPSNG does not publish a public price list. Instead, pricing is tied to the edition and the size of your use case: Cloud, Embedded, Enterprise, or White Label. This article walks through how to choose the right edition based on scale, integrations, deployment preferences, and total cost of ownership — so your first conversation with RSJ Software GmbH starts from a clear specification, not a blank sheet.

Understanding Your Label Printing Needs

The buying decision starts with five practical questions.

1. How large is your labeling operation?

LPSNG serves a wide range of scenarios, from a single shipping workstation to multi-user, multi-region corporate environments.

• Single user: A fixed workstation or an office printer often needs the core design and print workflow, not a complex user model.
• Small team: Several users may need shared label layouts, a common job queue, and consistent output without local file copies.
• Enterprise: Multiple regions, devices, and user roles require centralized management and controlled access.

2. Which integrations do you actually need?

Integration costs affect the real price of a labeling system. LPSNG provides several integration paths, and the right edition depends on which ones you use:

• Web Service API for submitting print jobs, rendering single PDF/PNG labels, and direct printing.
• OAuth2 for connecting external applications such as ESL base stations.
• Google Sheets Add-on for creating layouts and printing from Sheets.
• Excel Interface for using Excel files as data or lookup tables.
• ESL Interface for updating electronic shelf labels via JSON.
• Python field scripts for modifying field values before printing.

If your team lives in spreadsheets, the Google Sheets or Excel integration may lower your effective cost much more than a bare web service integration would.

3. Where should the system run?

Deployment preference is a major pricing fork:

• Cloud-hosted: No local server or single-board computer to maintain.
• On-premise / embedded: Complete LPSNG on a single-board computer such as a Raspberry Pi, useful for local control or offline environments.
• Hybrid: Starting in the cloud, then moving selected workflows to embedded or enterprise deployments as volume grows.

4. How complex are your labels?

The base system supports barcode formats, label design, and PDF generation. But some workflows need more:

• Complex barcodes such as 1D and 2D formats.
• Python field scripts for calculated text, price formatting, or dynamic content.
• 3D packing plans imported from Excel and visualized in the Excel Add-In.

A pack station that prints only EAN labels has different requirements from one that produces case labels, pallet labels, and customer-specific packing documents.

5. What is your total cost of ownership?

Budget is not just the invoice price. Consider:

• Time spent maintaining a local server or Raspberry Pi.
• Time saved by automated, API-driven label generation.
• Cost of errors when labels are designed independently on each workstation.
• Cost of custom development if you had to build the web service interface yourself.
• Hardware, hosting, and update management.

LPSNG positions the edition choice around these TCO factors, not around a simple per-label fee.

LPSNG Editions at a Glance

LPSNG offers four deployment and licensing models. All editions share the core functionality: web UI, label studio, job queue, PDF generation, and the web service interface. The differences are in hosting, management, and multi-user control.

Cloud Solution

The Cloud Solution is the hosted multi-user edition. RSJ Software GmbH runs the infrastructure, and you use the web UI and API.

Typical fit:

• Distributed teams that need shared access without a shared office network.
• Companies that want automatic updates and minimal IT overhead.
• Operations that prefer an operating expense over hardware ownership.
• Teams that want to start quickly without installing anything locally.

Because the cloud edition removes local infrastructure, the upfront cost is usually lower than embedded or enterprise self-hosted options, while the recurring cost tracks your usage.

Embedded Edition

The Embedded Edition is a complete LPSNG installation on a single-board computer such as a Raspberry Pi.

Typical fit:

• Offline or low-latency environments where cloud access is unreliable.
• Data sovereignty requirements that demand local storage and processing.
• Fixed workstations on packaging lines or warehouse stations.
• Teams that prefer a one-time hardware and license cost over long-term subscription fees.

The embedded edition gives you local control. The trade-off is that you manage the device, backups, and updates yourself.

Enterprise Features

The Enterprise Features add multi-user, multi-region, and multi-device support for corporate environments.

Typical fit:

• Organizations with multiple warehouses or production sites.
• IT departments that need user roles, permissions, and centralized management.
• Compliance teams that need consistent, auditable label templates across regions.
• High-volume environments with many printers, MDE units, or label workstations.

Enterprise is not a separate product as much as an operational layer over the core LPSNG system. Pricing for this tier is designed around multi-region coordination and delegated administration.

White Label Solution

The White Label Solution tailors the LPSNG user experience for printer manufacturers, paper manufacturers, and system integrators.

Typical fit:

• OEMs that want to embed label design and printing into their own product ecosystem.
• Integrators that need to deliver a custom-branded labeling workflow to their customers.
• Paper or printer vendors that want a pre-integrated software companion for their hardware.

White label pricing depends heavily on the scope of customization, branding, and distribution model.

Cost-Benefit Analysis and ROI

LPSNG pricing is not a public menu, but the cost-benefit logic is consistent across editions.

Upfront vs recurring costs

• Cloud Solution: Lower upfront cost, recurring subscription tied to the number of users, regions, or usage.
• Embedded Edition: Higher one-time hardware and license cost, lower recurring cost, but you own ongoing maintenance.
• Enterprise Features: Often a negotiated contract based on multi-site deployment, user count, and support level.
• White Label Solution: Project-based pricing that reflects integration work, branding, and partner support.

For a small operation, the cloud subscription may look cheaper initially. For a high-volume factory floor with many printers and no stable internet, an embedded deployment can quickly pay for itself by avoiding cloud dependency and per-month fees.

Time savings from automation

The web service API removes manual label creation from your workflow. Instead of opening a layout, editing a field, and clicking print for every order, an upstream system submits the job programmatically.

A minimal web service integration might look like this:

#!/usr/bin/env bash
set -euo pipefail

# Fetch an OAuth2 bearer token from the LPSNG web service.
ACCESS_TOKEN=$(curl -sS -X POST "$LPSNG_BASE_URL/oauth/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=$LPSNG_CLIENT_ID" \
  -d "client_secret=$LPSNG_CLIENT_SECRET" \
  | jq -r '.access_token')

# Submit a print job for a single label.
curl -sS -X POST "$LPSNG_BASE_URL/ws/jobs" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "layout": "shipping-label-a6",
    "format": "pdf",
    "data": {
      "sku": "LP-1024",
      "price": "19.90",
      "ean": "4001234567890"
    }
  }'

The exact endpoint paths and payloads are documented in the Web Service Interface and OAuth2 guides. The important point is the workflow: the API, not manual desktop clicks, becomes the primary path for label generation.

For a warehouse printing 500 labels per day, even 30 seconds saved per label adds up quickly. At a loaded labor cost of €40 per hour, that is roughly €4,200 per year in direct time savings — and it does not include the reduction in misprints, rework, or label stock waste.

Error reduction and centralized design

Centralized label design and version control reduce the cost of mistakes. When every workstation prints from the same layout, you avoid:

• Different formatting between shifts.
• Outdated compliance or barcode settings on one machine.
• Re-printing because one user edited a local template incorrectly.
• Inconsistent customer-specific labeling across regions.

The Order Specific Labeling and Packaging Lines use cases show how this plays out in fulfillment and traceability scenarios.

Integration costs

LPSNG already provides the interfaces you would otherwise have to develop:

• OAuth2 authentication handles secure access to the web service.
• Python field scripts add calculation logic without writing a standalone application.
• The ESL interface updates shelf labels from the same system.
• The Excel and Google Sheets integrations let business users maintain data without developer time.

Using these supported paths is the managed way to work with LPSNG. You do not hand-roll printer command streams or invent a new protocol. The web service and field script APIs are the published, supported surface.

Cloud vs. Self-Hosted: Choosing Your Deployment

The deployment decision is a trade-off between operational simplicity and local control.

Start in the cloud, move later

Many teams start with the Cloud Solution because it requires no hardware and no network configuration. Once volume grows or local requirements emerge, they evaluate the Embedded Edition or Enterprise Features for specific sites.

The core functionality is consistent across editions. A layout designed in the cloud can be migrated to an embedded installation in principle, because the job queue, label studio, PDF generation, and web service interface are present everywhere. The exact migration steps should be confirmed with RSJ support, especially if you use edition-specific features such as multi-region management or white label branding.

Enterprise is a control layer, not just more users

Enterprise Features matter when you need more than labels. Multi-region support means a packaging line in Germany and a fulfillment center in Poland can run from the same controlled template set. Multi-device support means handheld MDE units, label printers, and ESL displays are orchestrated from one system.

For OEM and integrator scenarios, the White Label Solution changes the question from “which edition do we rent?” to “how do we embed labeling into our product?” That is a project, not a subscription.

FAQ

What is the price of LPSNG?

LPSNG pricing is not publicly listed on the website. Contact RSJ Software GmbH for a quote tailored to your edition (Cloud, Embedded, Enterprise, or White Label) and usage volume.

Is there a free trial or free tier?

The product information does not mention a free trial or free tier. You may need to contact sales to inquire about evaluation options.

Can I switch from cloud to embedded later?

Yes, LPSNG offers multiple deployment editions. The core functionality is consistent across editions, so migrating from Cloud to Embedded or Enterprise is possible, though specific migration steps should be confirmed with RSJ support.

Does LPSNG offer volume discounts for enterprise?

Enterprise Features are designed for multi-user, multi-region, and multi-device environments. Volume discounts are likely available but not specified in the public documentation; contact RSJ for enterprise pricing.

Conclusion

The right LPSNG edition is not the one with the lowest sticker price. It is the one that matches the way you print labels today and how you expect to print them in two years.

If you need a hosted, multi-user system with no local infrastructure, the Cloud Solution is the natural starting point. If you need local control, offline operation, or a one-time hardware cost, the Embedded Edition is the better fit. If you are running multiple sites or need delegated administration, Enterprise Features justify their place in the budget. If you are an OEM or integrator, the White Label Solution turns LPSNG into a product component rather than a subscription.

Start by listing your integrations, volume, and deployment constraints. Then contact RSJ Software GmbH with that specification, and ask for a quote that covers the edition, usage, and migration path. The Next Generation Label Printing System is designed around that conversation: one platform, multiple deployment models, and a consistent API across them.