2026-09-18 pdf labels barcodes label merge browser based graphical layout editor google sheets addin microsoft excel addon electronic shelf labels esl barcode3 labels label editor

Automate Customer-Specific Labels in Your Fulfillment Process

Every fulfillment operation eventually hits the same wall: customers want their own label layout, their own barcode, their own compliance text — and somebody has to make that happen for every order. That manual step is where order specific labeling for fulfillment usually breaks down.

With the Next Generation Label Printing System, the label design becomes a one-time job. The order-specific part becomes data. The printing becomes an automated pipeline.

The Manual Labeling Bottleneck in Fulfillment

In many warehouses, customer-specific labels are still produced through a semi-manual process:

An operator opens a label layout.
They replace the customer logo or address block.
They retype the order number, SKU, batch, or destination.
They check the barcode and print a test sheet.
They repeat this for the next order.

This causes several predictable problems:

Inconsistent branding: Labels look slightly different depending on who edited them.
Wrong data entry: A transposed PO number or incorrect batch code becomes a customer complaint.
High labor cost: Skilled staff spend time editing labels instead of packing or shipping.
Poor peak-season scaling: When order volume doubles, label editing becomes the bottleneck.

Order-specific labeling means that each shipment can require unique elements: customer logos, product details, barcodes, compliance information, or customer-mandated label dimensions. The only sustainable way to handle that variety is to stop editing labels per order and start automating the data flow into a fixed set of templates.

One-Time Setup: Designing Your Label Templates

LPSNG provides a web-based label studio where you design professional label templates once and reuse them across hundreds or thousands of orders.

A template can include:

Static elements such as your base layout, logo, and legal text.
Dynamic fields for customer-specific data such as ship-to address, PO number, customer article number, and batch.
1D and 2D barcode formats, including the formats your retail or logistics partners require.
Fields that are transformed just before printing using Python script blocks.

The Python Field Script API is useful when a customer has special formatting rules or conditional logic. For example, a customer-specific barcode may need to be built from several order fields, or a text field may need to change depending on the destination country. For a deeper look at this mechanism, see Using Python Scripts to Manipulate Label Fields in LPSNG.

Template data can come from your existing systems. If your data lives in spreadsheets, the Google Sheets Add-on lets you create label layouts and print directly from Sheets. The Excel Interface can be used in the same way for Excel files, including lookup tables that map customers to specific label designs. For the Google Sheets workflow, see How to Print Barcode Labels from Google Sheets with LPSNG.

The key principle is that templates stay modular. You do not create a new template for every customer. You create a small set of templates and feed them customer-specific data at print time.

The Automated Pipeline: From Order to Printed Label

The central automation interface in LPSNG is the Web Service API. It can:

Submit print jobs.
Render single labels as PDF or PNG.
Send labels directly to a printer.
Return job status and error information.

A typical automated fulfillment flow looks like this:

Your ERP, WMS, or order management system picks up a new order.
The system sends the order data to the LPSNG Web Service API.
LPSNG merges the order data with the referenced template.
Any attached Python field scripts transform or validate the field values.
LPSNG either renders a PDF/PNG or sends the label directly to the configured printer.
The job appears in the LPSNG job queue with a status.

The API call is just an HTTP request. Conceptually, the request shape looks like the following. The exact endpoint and field names depend on your LPSNG integration, but the automation principle is the same.

# Illustrative request shape — exact endpoint/fields depend on your LPSNG setup.
curl -X POST "https://lpsng.rsj.de/api/v1/print-jobs" \
  -H "Authorization: Bearer $LPSNG_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": "customer-123-shipping-label",
    "order": {
      "order_id": "SO-2026-0918-0042",
      "customer_id": "CUST-123",
      "ship_to": {
        "name": "Acme Distribution Center",
        "address": "Lagerstrasse 1, 10115 Berlin"
      },
      "items": [
        {"sku": "ACME-100", "quantity": 3, "batch": "L2409"}
      ]
    },
    "output": "pdf"
  }'

Your integration chooses between direct printing and digital output. Direct print is useful for high-volume shipping lines. PDF or PNG rendering is useful when you want to store, preview, or email the label before committing it to paper.

For environments where a full web service is not needed — for example, a local packing station or a test environment — LPSNG also offers the LPSNG Player, a standalone command-line print engine. It takes package and data input and produces PDF, PNG, JSON, print, or ESL output. For most automated fulfillment workflows, however, the managed cloud solution is the simpler path because it removes the need to operate and update a local print service.

Authentication for the API uses OAuth2. External systems register with a single URL, receive credentials, and then pass an access token with each request. This lets you connect an ERP, WMS, ESL base station, or custom middleware without embedding long-lived passwords in your job scripts.

Monitoring and Failure Handling in Automated Labeling

Automation only saves time if you can see what happened when something goes wrong.

LPSNG keeps a job queue in the web UI. Operators can monitor submitted jobs, see whether a label was rendered, and identify errors without opening the printer. This is the first place to check when an order does not arrive at the packing station.

The API also returns error information with job submissions. In a well-built integration, your system should:

Log the job ID returned by LPSNG.
Check the job status after submission.
Retry on transient network or rendering failures.
Alert an operator only when a job remains failed after a retry.

A useful pattern is to keep a simple job log at the integration level:

2026-09-18T08:12:04Z  job=JOB-8812  status=queued
2026-09-18T08:12:11Z  job=JOB-8812  status=rendering
2026-09-18T08:12:19Z  job=JOB-8812  status=printed

If your workflow requires approval or visual checking, render the label as PDF or PNG first. A preview step catches misconfigured templates before they reach a production printer. This is especially useful when onboarding a new customer or switching label stock.

For high-volume environments, the enterprise features for multi-user and multi-device support help keep the labeling process reliable across several packing lines or regional sites.

Best Practices for Customer-Specific Label Automation

Automation works best when you keep the label logic simple and push the complexity into data, scripts, and lookup tables.

Keep templates modular. Use dynamic fields for customer-specific elements instead of creating a new template for every customer. A customer logo can be a dynamic image, not a manually edited static layer.
Use the Python Field Script API for conditional logic. If a field must be formatted differently for a specific customer, attach a small script to that field. The script concept looks like this:

# Field script attached to a customer-specific barcode field.
# The LPSNG script context exposes the current field and the order data.
if data.get("customer_id") == "CUST-123":
    field.value = data["po_number"].upper().replace("-", "")
else:
    field.value = data.get("po_number", "")

This keeps customer rules close to the label field and prevents them from being duplicated in many downstream systems.

Use the Excel Interface for lookup tables. Map customer IDs to label designs, paper sizes, or special compliance text. The lookup file becomes a maintainable configuration source instead of hidden code.
Test with a small batch before full rollout. Start with one customer and a few orders. Check the barcode readability, label dimensions, and printer alignment. The LPSNG Player is a practical local testing tool when you do not want to affect the production queue.
Validate barcode formats and label dimensions early. LPSNG supports multiple 1D and 2D barcode formats, but the customer may require a specific symbology. Confirm that the generated barcode meets the customer or carrier specification before you automate the entire order stream.

FAQ: Automating Order-Specific Labeling with LPSNG

How do I integrate LPSNG with my existing order management system?

LPSNG provides a Web Service API that accepts print jobs with order-specific data. You can integrate your OMS or ERP by making HTTP requests to the API, using OAuth2 for authentication. The API can render labels as PDF or PNG or send them directly to printers, allowing seamless automation.

Can LPSNG handle different label designs for different customers automatically?

Yes. You can design multiple label templates in the LPSNG label studio and reference the appropriate template in each API call based on customer ID or other order data. Additionally, the Python Field Script API can dynamically modify field values, and the Excel Interface can serve as a lookup table to map customers to specific label configurations.

What if I need to run LPSNG on-premises or on a local device?

LPSNG offers an Embedded Edition that runs on a single-board computer such as a Raspberry Pi, suitable for on-premises or edge deployments. There is also the LPSNG Player, a standalone command-line engine that can process print jobs locally. For most users, the cloud solution provides the easiest managed experience.

How does LPSNG ensure secure access to the API?

LPSNG uses OAuth2 for authentication. External systems can register with a single URL to obtain credentials, and all API calls require a valid access token. This ensures that only authorized applications can submit print jobs or access label data.

Conclusion

Order specific labeling for fulfillment should not mean order-by-order design work. The practical alternative is to design a small set of reusable templates, connect your order system through the LPSNG Web Service API, and let dynamic data and field scripts produce the right label every time.

That approach removes the manual editing step, reduces data-entry errors, and gives your team a monitored, retryable print pipeline instead of a fragile human checklist. For fulfillment teams that want professional-looking customer labels without maintaining their own label generation infrastructure, LPSNG is the route from manual bottleneck to automated output.

Related posts