Skip to main content

Integrating Next Plus with Label Printing Apps

Eli Gimelraikh avatar
Written by Eli Gimelraikh
Updated this week

Introduction

Next Plus can be integrated with a variety of label printing applications to automate and streamline barcode label generation within manufacturing and logistics processes.

This article presents a case study of integration with BarTender, a widely used barcode label design and printing software. While the specific technical examples provided here relate to BarTender, the same principles and integration flow can be applied to other label printing applications as well.

What is BarTender and Why Integrate with Next Plus?

Integrating Next Plus with label printing apps (such as BarTender) enables automatic generation and printing of barcode labels directly from production processes.

  • BarTender is a professional barcode label design and printing software used across manufacturing, logistics, healthcare, and retail.

  • Next Plus manages manufacturing workflows, production data, and reporting.

The integration allows data to flow seamlessly from Next Plus into the label printing applications. Typical data points include Part Numbers, Serial Numbers, Work Order Numbers, and other production-specific values.

In the label printing apps, this data can be:

  • Printed directly on the label (e.g., text fields like part numbers or work order references).

  • Encoded into barcodes or QR codes for scanning and traceability.

It is important to note that the barcode encoding and formatting are configured within the label printing application itself (e.g., BarTender), while Next Plus serves as the source of structured production data.

Requirements for Integration

Technical Components

  • Label printing software installed on a server with access to printers

  • Configuration Builder capabilities

  • A script or middleware to handle data transformation (e.g., JSON ➝ BTXML for BarTender).

  • Network connection availability between the Next Plus servers and the printing software.

  • Integration service configured in the label printing app to listen for data files or API calls.

Next Plus Configuration

Introduction

This guide walks you through creating webhooks, designing forms, and automating triggers for seamless printing operations

Bartender In-Depth integration Process

✅ Integration Checklist (Next Plus → BarTender)

Download the attachment and extract it, you'll get all the necessary items for the configuration

Prepare the following:

Next Plus

  • A Form with:

    • Printer field (string)

    • Label template field (string / path)

  • A Post-save Webhook Trigger configured on the Form.

BarTender Server

  • BarTender Integration Service installed and running.

  • webhook.btin deployed (Web Request Integration).

  • file watcher.btin deployed (File Trigger Integration).

  • extract.ps1 placed in C:\nextplus_print\extract.ps1.

  • Folder structure:

    • C:\nextplus_print\jobs (read/write for service account)

    • A path to the labels folder (UNC or local).

Configuration

  • Update field GUIDs in extract.ps1 to match your actual Form.

  • Set $btwPathPrefix to your label folder (UNC path recommended).

  • Ensure BarTender can access printers + label format files.

  • Test with a sample Form submission.

📝 In-Depth How Next Plus Prints Labels Through BarTender

Below is the simplified flow from a user filling out a form in Next Plus to a printed label on the shop floor.

1. User fills a Form in Next Plus

The operator opens a Form inside Next Plus and provides:

  • Target printer

  • Label template name/path

  • Stock serial or production data

  • Any additional fields required for the label

This Form acts as the data source for BarTender.

2. Next Plus sends a Webhook

When the Form is saved, the Post-save trigger sends a JSON payload to BarTender:

  • Selected printer

  • Label template

  • All other Form fields

BarTender’s Web Request Integration (configured via webhook.btin) receives this POST.

3. BarTender Integration stores the JSON and runs a script

webhook.btin:

  1. Saves the JSON request to C:\nextplus_print\data.json

  2. Calls the PowerShell script extract.ps1

extract.ps1 then:

  • Parses the JSON

  • Extracts required fields

  • Builds the full path to the .btw template

  • Generates a BTXML print file for BarTender

  • Drops the file into C:\nextplus_print\jobs

  • Creates a .done file next to it

This BTXML file contains:

  • The printer name

  • The label template path

  • Substring values (stockSerial, etc.)

4. BarTender detects the BTXML print job

The File Trigger Integration (file watcher.btin) continuously monitors:

C:\nextplus_print\jobs

When a .xml + .done pair appears, BarTender:

  1. Reads the BTXML

  2. Loads the .btw label file

  3. Sends the print job to the correct printer

5. Label is printed

BarTender executes the print in real time with the exact content coming from the Next Plus form data.

This ensures:

  • Fully automated flow

  • No manual handling

  • Consistent label formatting

  • Traceability from the production workflow to the printed output

⚙️ Configuration Details

Use this section for deeper setup steps when deploying.

1. Set up Webhook in Next Plus

  • Name: Printing app integration

  • URL: <BarTender Integration endpoint>
    Example:

    http://<bartender-host>/Integration/nextplus_webhook/Execute

  • Model: FormData

  • Events: Create

Notes:

  • webhook.btin writes this body to data.json.

  • The URL path must match the path inside the Integration Builder project.

2. Trigger the webhook from the Form

Inside the Form editor:

  • Add a Post-save Trigger

  • Select “printing app integration”

3. Form Requirements

Mandatory

  • Device Link: ON

  • Printer field: Windows printer name

  • Label field: Template filename/path in BarTender (e.g., ProductA/Label123)

  • .btw extension is optional – script will add it.

Important

extract.ps1 expects:

  • One field ID for the printer

  • One field ID for the label

These GUIDs must be updated to match your actual form.

4. How the BarTender webhook integration works

webhook.btin does:

  • Accept HTTP POST from Next Plus

  • Save JSON → C:\nextplus_print\data.json

  • Execute → C:\nextplus_print\extract.ps1

extract.ps1 does:

  • Read + parse JSON

  • Extract printer, label, stockSerial

  • Normalize label paths

  • Build full .btw path using $btwPathPrefix

  • Create BTXML file under:

    C:\nextplus_print\jobs\<guid>.xml

  • Create corresponding .done

  • Delete data.json

5. File watcher integration (printing)

file watcher.btin:

  • Watches C:\nextplus_print\jobs

  • Detects new BTXML files + .done

  • Sends them into BarTender Engine

  • Runs print job with correct printer + label

✔ Deployment Checklist (Detailed)

Place these files on the BarTender server:

  • [ ] C:\nextplus_print\webhook.btin

  • [ ] C:\nextplus_print\file watcher.btin

  • [ ] C:\nextplus_print\extract.ps1

Prepare required folders:

  • [ ] C:\nextplus_print\jobs

Integration Builder:

  • [ ] Load and deploy both integrations to **This Computer**

Script configuration:

  • [ ] Update printer/label field GUIDs

  • [ ] Set $btwPathPrefix to UNC or local path

  • [ ] Verify file permissions

Testing:

  • [ ] Submit a Form in Next Plus and confirm:

    • JSON arrives at server

    • BTXML file created

    • Label prints successfully

Attachment icon
Next Bartender Integration Files.zip
Did this answer your question?