Automated label printing from data and API

Outcomes for your team

Printing follows the process. You stay in control.

AxioLabel receives data, creates jobs, and moves them through a reliable print queue. IT can see the status, attempts, and outcome.

01Routes and triggers

Fewer manual starts

A route connects the source, template, and printer, then runs when the configured condition is met.

02Queue and recovery

Recovery from temporary failures

The background queue retains job state, controls attempts, and continues unfinished work after a restart.

03Dashboard and journal

Every job is traceable

The dashboard, queue, and journal show the current status, attempts, and outcome.

The next level

Studio creates the label. Automation turns it into a working process.

The designer and interactive printing remain available. Libraries, routes, background execution, and operational control are added on top.

Studio workflow

Template creation and configuration
Excel / CSV
Preview
Interactive printing

Managed printing process

Template and connection libraries
Print routes without programming
Queue with retries and recovery
Dashboard, journal, and system events

Automation is purchased as a separate product. The right to use the previously purchased Studio remains.

Use cases

One route provides a clear path from data to outcome

ERP, WMS, MES, and 1C are external system contexts. Connectivity is configured through a supported data source.

Integration

Integrator

Integrates printing into the existing information environment.

SourceSQL Server, MySQL, PostgreSQL or inbound REST API
LaunchExternal system request or schedule
RouteData mapping, template, and print rule
QueueAssigned printer queue
ResultExecution status and journal entry

Production

Production IT team

Organizes recurring label output for an operating area.

SourceProduction data from SQL Server or MySQL
LaunchLabel production schedule
RouteTemplate and rules for the target area
QueueQueue for the selected print line
ResultCurrent work and exceptions on the dashboard

On site

Local print area

Turns recurring file-based printing into a controlled process.

SourcePrepared Excel or CSV file
LaunchConfigured route start
RouteValidated layout and field mapping
QueueLocal printer queue
ResultConfirmed outcome in the journal

One print route

Build automated printing from clear steps

A route combines a ready template, data connection, launch rules, and printer queue — without a separate integration project.

01

Select a template

Create a layout in the designer or select a ready one from the shared template library.

One validated layout for the process

02

Connect the data

Configure Excel, CSV, SQL Server, MySQL, PostgreSQL, or an incoming request and verify the data in preview.

The connection is configured and verified in the interface

03

Build the route

Connect fields, template, launch method, and printer queue in one configuration.

The printing rule is clear and repeatable

04

Control the result

The dashboard shows the overall picture, the queue shows current work, and the journal shows completed printing.

Exceptions are visible before users report them

Reliable execution

A job does not disappear between data and printer

AxioLabel keeps the job before dispatch, controls attempts, recovers unfinished work after a restart, and records the outcome.

01
Job queueAccepts jobs, organizes work, and shows their status.
02
ExecutionSends the result to the assigned print queue and retries after a temporary error.
03
LogRecords the time, execution result, and error details.

The product at work

Exceptions are visible. Attempts and outcomes are retained.

Real screens from the accepted build show the path from a dashboard alert to a verifiable journal entry.

Automation dashboard with a safe sample connector start exception — ExceptionThe dashboard surfaces the alert
The attention card links a start error to a specific source and time.

Queue job card with attempts and state history — Queue and attemptsState history remains with the job
The card shows the assigned printer, attempts, and transitions from enqueueing to completion.

Outcome card with label previews, prepared data, and timeline — LogThe outcome remains verifiable after printing
The journal retains previews, prepared data, the timeline, and the execution outcome.

System journal with a completed queue recovery event — System eventRecovery leaves a verifiable trace
The system journal records completed queue recovery without exposing an internal stack trace.

Operational data and printing

Connect data sources and assign queues

Data sources

ExcelCSVSQL ServerMySQLPostgreSQLIncoming REST API

Excel and CSV are inherited from Studio. SQL Server, MySQL, PostgreSQL, and the incoming API are added in Automation.

Up to five print queues

The base license supports up to five operating-system print queues that can receive print output.

Printer Pack: five more queues →

Extended Printing

The separately purchased extension generates ZPL and TSPL commands for compatible printers.

Learn about the extension →

For integration teams and local IT

Put AxioLabel Automation to work in your process

Configure print routes with your own data, then choose the right offer and product delivery option.

Integration with ERP, WMS, MES, or 1C
Scheduled background printing
Observable queue, retries, and log

FAQ

Key facts

Automation is available for background printing. Purchase, download, and support terms are provided in the relevant website sections.

How is Automation different from Studio?

It includes Studio capabilities and adds SQL Server, MySQL, PostgreSQL, and an inbound REST API, routes, a background queue, a journal with saved output and reprinting, a dashboard, and system events.

It includes Studio capabilities and adds template and connection libraries, print routes, a background queue, a dashboard, a journal, and system events.

Can I continue printing interactively?

Yes. Interactive printing capabilities are inherited from Studio.

Which data sources does Automation support?

Excel, CSV, SQL Server, MySQL, PostgreSQL, and an inbound REST API. ERP, WMS, MES, and 1C connect through a supported data source or API; dedicated built-in connectors for them are not claimed.

Excel, CSV, SQL Server, MySQL, PostgreSQL и входящий REST API. ERP, WMS, MES и 1С подключаются через один из поддерживаемых источников или API; отдельные встроенные коннекторы для них не заявляются.

How many print queues are included in the base license?

Up to five. A separately purchased Printer Pack adds five more queues and can be purchased multiple times.

Where is Automation installed?

On a Windows x64 computer or server for all users of that computer. Background execution runs as a Windows service, while the management interface opens in a browser at the address and port selected during installation.

На компьютере или сервере Windows x64 для всего компьютера. Фоновое выполнение работает как служба Windows, а интерфейс управления открывается в браузере по адресу и порту, выбранным при установке.

How do I purchase and download Automation?

Choose the current offer in the product card: it will direct you to standard checkout or the sales team depending on the configured channel. The installer is published separately in Downloads.

The public date has not been announced. You can follow the news or apply for early access.

Which extensions are available for Automation?

Extended Printing generates ZPL and TSPL commands, additional workstations increase the number of concurrent users, and a Printer Pack adds five queues. Extensions are purchased separately.

Расширенная печать формирует команды ZPL и TSPL, дополнительные рабочие места увеличивают число одновременных пользователей, а Пакет принтеров добавляет пять очередей. Расширения приобретаются отдельно.

All product questions →