Create
Build a packing label.
Ask for a part number, lot and barcode. Start from a template, let the agent shape the document, then inspect the rendered result.
AI-first platform · native MCP · your agents
Label design and print automation.
AI-native by design.
Print fully automatically from business data, or let operators print manually through guided forms. Create labels and workflows with AI copilots, and connect your own agents through native MCP.
Design the label. See the whole workspace.
Manual printing. Guided by a form.
Fully automated printing. Triggered by your data.
See the services behind your operation.
Actual product interface · synthetic Northline Parts data. Select any image to inspect it.
AI-native at the core
Built for AI.
Ready for your agents.
Give an agent the tools to build labels, construct automations and investigate printing problems. OpenLabelEngine makes the documents, previews and controls available through native MCP.
Structured documents
Labels, automations and forms have defined schemas and stable IDs. Agents can work on specific objects, nodes and fields.
Native MCP tools
Discover permitted Center operations, read document schemas and request real rendered previews through your agent's MCP client.
Visible changes. Human decisions.
Keep versions, validation and role checks in the workflow. By default, agent-authored labels and forms need human approval; new automation deployments do too.
Automate
Turn an order into a workflow.
Have an agent assemble supported nodes, map order fields and add checks. Review the graph and try sample data before deployment.
Observe
Put your agent on watch.
Configure an external agent to poll operating status or receive supported webhook events, investigate failures and propose fixes for review. You provide the agent, schedule and notification rules.
Start with what you need
One label today.
A connected operation tomorrow.
Print fully automatically from connected data, or let an operator print manually through a form. Use either mode—or both—in the same installation. The same path runs from one printer in one location to many printers across locations.
- 01One printer, one locationDesign, check the preview and print from the Center. A local Runner is optional.
- 02Automate the routineA saved workflow prints from your data. A check that fails can follow a review branch.
- 03Many locations, many printersKeep the chosen version in the Center. Each site runs it beside its own printers, from one printer to thousands.
01 / A small team, a first label
Your browser. Your label. Your printer.
Build the label in the Designer. The operator enters or scans values in a form, checks the preview and starts printing in Print Center. The Center can print directly to a reachable, supported network printer. A Runner is optional.
Explore printing in the CenterStart with the Center. Add local services when your workflow needs them.
02 / More orders, fewer repeated steps
Give the routine work a workflow.
A configured trigger starts printing automatically, without an operator submitting each job. Read business data, map it to a label and check required fields and valid quantities. In this example, a positive quantity continues to print; an invalid quantity follows a review branch. The Automation is the saved workflow; you choose where it runs.
Follow an order-processing scenarioExample checks: required fields and a positive quantity. Review is a configured branch.
03 / More sites, one coordinated operation
Keep the choice central.
Put execution close to the work.
What begins as one printer in one location can become many sites. Choose a document version in the Center, with review where configured, and assign it to each site service group. Each Automation Service (Runner) stays beside the printers at that location—one printer or thousands—and reports state back. The two sites below show the pattern, not a live fleet count.
Explore the multi-site workflowAssignments and reported state are different. A sent job is not a confirmed print.
01 / 03Design the label in the Center.
24 seconds · one story, three chapters · no loop
The three names, explained
- Center
- The shared application for design, operator printing, documents and operations.
- Automation
- A saved workflow of configured steps. It runs in the execution location you select.
- Automation Service (Runner)
- The local executable for assigned work near printers and data. Optional for direct printing from the Center.
Label Designer
One design.
Every product and batch.
Build the label around your data. Place text and barcodes, inspect object settings, and check the rendered result before the design reaches a station.
Explore the Label Designer →
Visual print automation
See the whole process.
Make each decision explicit.
Once configured, a trigger starts the workflow: read incoming records, prepare label values, apply checks and send accepted work to the printer automatically. No operator needs to fill out a form or click Print for each job. Route exceptions for review.
Follow the order-to-label scenario →From a useful design to daily work
Give every team
the part they need.
Design & data
Reusable labels, variable values and rendered previews.
Build the label →Manual printing with forms
An operator enters or scans values, checks the preview and starts the print.
Guide the operator →Fully automated printing
Business data or a configured trigger starts the workflow and sends accepted records to printing.
Connect the workflow →Local execution
Service groups, deployed versions and local print queues.
Run near your printers →Operations & review
Rendered comparisons, distribution state and print history.
Follow the result →Migration & integration
Import diagnostics, versioned documents and API access.
Bring existing work forward →Across the operation
Choose what each site runs.
Keep shared designs and workflows in the Center. Assign a specific version to a service group, then inspect the group’s reported application state.
In the Northline example, Vienna packing and Brno dispatch use separate service groups. A saved edit becomes operational through an explicit deployment.
Explore the two-site scenario
Start from your operation
A concrete path to explore.
Integration team
Orders arrive from your business system
Follow source data, mapping, branches and print requests.
ERP data to labels → Warehouse teamAn operator needs the right label now
Explore station inputs, label preview and batch work.
Warehouse printing → Operations teamSeveral sites share a label process
See how documents, groups and local services fit together.
Multi-site labeling → Migration teamExisting labels need a considered move
Start with an import, inspect diagnostics and review the result.
Plan a migration →After the print request
Keep a record
you can work with.
Open a job’s record to inspect its context and rendered output. Use the reported state to decide what needs attention and whether a reprint is appropriate.
A sent job and a confirmed result are different states. The record keeps that distinction visible for the print path you use.
Explore print traceability
Your first workflow
Bring one label.
Follow it all the way through.
Choose a representative label, its input data and a print path. The quickstart and compatibility guide help you turn a first look into a useful evaluation.