Centralized templates
Create, import, and organize in the browser the templates used by production teams.
API-first label operations
From your business system to the printer, without manual steps
Centralize templates, send data through the API, and print on the devices already running at the plant through a local agent.
OAuth 2.0 client credentialsREST APILocal Print AgentBarcode, QR, and Data Matrix
A print pipeline, not another file to manage
Separate layout from operational data and connect printing to the system that already manages orders, batches, and production.
Dynamic data and codes
Bind business-system fields to text, images, barcodes, QR codes, and Data Matrix.
Focused print API
Authenticate a service account and enqueue a job with one HTTPS request to POST /v2/jobs.
Print on the local network
The agent receives the job, generates the PDF, and uses the operating-system print queue.
Operational control
Monitor agents, printers, and jobs from the workspace without touching production PCs.
Integration credentials
Use separate service accounts for systems and environments, with secrets that can be rotated or revoked.
The workflow stays simple
Business Central, SAP, a MES, a WMS, or a custom service all use the same contract.
1
Prepare the template
Define dimensions, artwork, and dynamic field names in the Labels workspace.
2
Create a credential
Generate a dedicated service account and keep its secret in the calling system.
3
Send the job
The business system obtains an OAuth token and sends the template, printer, copies, and variable data.
4
Print locally
The agent on the plant network processes the job and passes it to the printer.
Connect the ERP with a standard API call
Labels does not require a proprietary connector. The source system builds the payload, obtains a token, and sends the job.
Microsoft Dynamics 365 Business Central
A small AL extension can read an order, batch, or item and call Labels through HttpClient.
SAP
An SAP Integration Suite flow or an ABAP HTTP/REST client can send the same payload.
MES, WMS, and custom applications
Any system that can use OAuth 2.0 and HTTPS can enqueue a print job.
Business Central and SAP are API integration examples, not preinstalled connectors.
Minimal examplePOST /v2/jobs
{
"idT": "template-id",
"printerId": "printer-id",
"format": "100 x 50 mm",
"numberCopies": 2,
"data": [{
"item": "A-1042",
"lot": "LOT-260903"
}]
}Built for the engineer's coding agent
Public OpenAPI, agent-readable guides, a non-destructive validation endpoint, a local sandbox, and executable examples let an AI agent discover the contract, implement it, and verify the result before the first real print.
Frequently Asked Questions
How do I access Chemilla Labels?
Access is managed by your workspace administrator. If you already have an account, sign in to open the workspace.
Do we need a dedicated connector for our ERP?
No. The supported integration uses OAuth 2.0 client credentials and a REST API. The required work is mapping business-system data to the print payload.
How does the Print Agent work?
The Print Agent is a lightweight application that runs on your local network. It receives assigned jobs and sends them to printers reachable from the plant.
Are Business Central and SAP ready-made connectors?
Not yet. They can integrate with Labels using their HTTP and OAuth capabilities; configuration, mapping, and error handling must be implemented in the project.
Start with one real workflow
Show us a template, its source data, and the printer. We will explain how to connect them without building a parallel platform.