Turn fragmented industrial label printing into a single configured, fully traceable workflow. LDP brings BTW templates, data sources, print jobs, print logs, and branding together in one platform.
Support for databases, files, APIs, manual entry, and composite data sources in one place.
A guided execution flow that helps operators preview, select, assign, and print.
Every printed label can be traced, reviewed, and reprinted from its original snapshot.
Branding, language switching, and deployment options adapt to different customer environments.
LDP is a label data platform built for industrial labeling workflows. It centralizes BTW templates, data sources, print jobs, printer assignment, print logs, and audit records so teams can run labeling operations with far more consistency and control.
It is common to see one BTW file per machine, copied repeatedly until nobody is sure which version is current. LDP introduces a central template library with integrity checks and reference validation.
SAP, Excel, databases, APIs, and manual entry often live in separate workflows. LDP unifies them under one data source layer and supports composite sources for merged print-ready tables.
When something goes wrong, teams often cannot answer who printed, when it was printed, how many labels were output, or which parameters were used. LDP records each batch and each label for faster investigation.
When BarTender sits inside the plant and business systems live elsewhere, deployment becomes difficult. LDP supports REST, bridge agent, and MOCK modes while also offering branding and language controls for customer delivery.
Managing scattered .btw files is the first problem LDP solves. Once uploaded, the platform automatically identifies named data source fields, label dimensions, and file metadata to standardize template assets from the start.
Databases, files, APIs, and manual entry can all be managed in one place. When a single label needs business data from several systems, LDP can combine multiple sources horizontally into one print-ready dataset.
A print job template is a complete printing configuration. It defines which labels are used, which data sources and printers are assigned, and how fields, quantities, validation rules, and notifications should behave.
LDP turns complex print operations into a guided process. Operators can choose a template, confirm data, assign printers, check the estimated output, and start printing with much less room for error.
LDP does more than record a finished status. It preserves variable values, template paths, timestamps, and print snapshots for each label so organizations can rebuild and audit each batch with confidence.
LDP can proactively send critical print information to stakeholders. Even when teams are away from the system, they can still see when a task starts, when it ends, what failed, and what the batch actually contained.
LDP is not only an internal tool. It can also be delivered under your own company brand to customers, subsidiaries, or plants. Company name, logo, favicon, theme color, support email, and footer information can all be managed centrally, with built-in language switching.
Ideal for demos, validation, and proof-of-concept projects when no real BarTender environment is available.
Best when the LDP service and BarTender are on the same machine or network segment and can connect directly through REST APIs.
Designed for public LDP deployments with private BarTender instances inside the plant, using an active bridge agent instead of exposing internal services.
Support multiple on-site BarTender nodes routed by agent_code. Each printer can be bound to one agent without complicated network planning.
Deploy on Linux, develop on Windows, connect to MySQL or MariaDB, and run from modern browsers while integrating with BarTender Automation Edition and above.
No backend compilation and no frontend build pipeline for everyday maintenance tasks.
A lean dependency set keeps deployment simpler and avoids heavy native module requirements.
Use MySQL in production and MariaDB in development without changing the operating model.
Track logins, configuration changes, template uploads, print batches, and reprint activity.
Use JWT, role permissions, and encrypted sensitive fields to reduce operational risk.
Archive each print dataset and template reference so reprints can be reproduced from the original run.
Manage multiple production lines, multiple template types, and multiple printers while pulling live data from MES systems and keeping managers informed through notifications.
Use one job template for shipping labels, inner carton labels, and pallet labels, with composite data sources and row-level selection for flexible execution.
Run one centralized LDP deployment while each plant executes printing locally through bridge agents, balancing control, security, and on-site responsiveness.