The people who own the label can change the label.
Labels are where production meets compliance, and a wrong pallet label is a rejected delivery. LabelBee is a label designer in the browser: lay the label out by dragging, bind its fields to the live order and pallet data, check it with real values, and let rules decide which printer it goes to.
In daily production across multi-site manufacturing groupsThe problem it removes
A label change should not need a release.
In most plants the label lives in a printer file that one person understands. A new customer requirement, a changed expiry rule or one more barcode turns into a ticket, a wait, and a hand-edited file nobody can preview. Meanwhile the values printed on it are typed in by hand, and a typo on a pallet label comes back as a rejected delivery weeks later.
Lay it out, do not code it
The label is a canvas. Text, barcodes, shapes and images are placed by dragging, sized in millimetres or inches, and checked at the resolution the printer actually prints at. The person who owns the label content can change the label.
The values come from the order, not from a keyboard
Fields on the label are bound to real production data: batch number, customer, expiry date, net amount, quantities, SSCC and GTIN. Nobody retypes them, so nobody mistypes them.
See it before the printer does
Fill the placeholders with sample values and look at the finished label on screen. A test run prints nothing and wastes no stock, and it catches the overlapping field or the missing digit while that is still cheap.
The right label reaches the right printer
Rules decide which design goes to which printer in which situation. A line does not print a label meant for another line, and moving production to a different machine does not mean re-pointing anything by hand.
Every label keeps its history
Designs are versioned and grouped into categories, with printed samples kept beside them. You can see what the label looked like on the day it was printed, which is the question you get asked when a delivery is queried.
Other systems can ask for a print
An order system, an ERP or an automation can request a label over an interface, hand over the values it holds, and the job goes into a queue you can watch. Printing does not depend on someone standing at a screen.
A look inside
One screen where the label, the data and the values meet.
What it does
From the empty canvas to the printed pallet.
Designer
A label you build by hand, in a browser
Text, barcode, shape and image elements on a canvas, sized in millimetres or inches, at the print resolution you choose. Zoom in on a single field, undo a change you did not mean, bring an existing design in or take one to another site.
- Text, barcodes, shapes and images
- Millimetres or inches, at real print resolution
- Undo, redo, import and export
Data
Fields that fill themselves
Each placeholder is bound to a value the plant already holds: the production order, the pallet, or a system outside the line. Rules fill fields without a person touching them, and a formula covers the values that have to be worked out rather than read.
- Order, pallet and external sources
- Rules that complete the label automatically
- Derived values from a formula you write once
Proof
Real values before real stock
Put sample values into the placeholders and preview the finished label. A test run puts the whole thing together without sending anything to a printer, so a bad layout costs a minute instead of a roll of labels and an hour of the line.
- Sample values per placeholder
- Full preview before anything prints
- Versions, categories and kept samples
Printers
Every printer on the site, in one list
Printers are registered once with their address, their resolution and their label size, and each one is given the driver it needs. Adding another printer of a model you already run is a configuration change, not a release.
- Registered once, visible per site
- Drivers assigned, not built in
- Network label printers speaking ZPL
Routing
The right label, the right printer, the right job
Routes carry the rule: this design, this situation, this printer. The line prints what it should print without an operator choosing from a list at three in the morning. Every request lands in a queue with a history behind it.
- Design and printer routes per site
- A visible queue and a full print history
- Other systems can request a label over an interface
Documentation
It ships with a real manual, in six languages
Not a wiki page and not a slide deck: a fifty-seven page user manual that walks through every screen, in English, German, Spanish, French, Polish and Romanian. It is generated from the application's own documentation, so it does not drift away from what people see. The interface is in the same six languages.
- English, German, Spanish, French, Polish, Romanian
- Fifty-seven pages, every screen covered
- Written from the application, so it stays current
How it runs
On the site, next to the printers.
On-premise, in the plant
It installs on the appliance or the server that already sits in the plant, on the same network as the label printers. Nothing has to leave the site for a label to be designed, previewed or printed.
- No dependency on an outside link
- Prints on the plant network
- Your own certificates
Private Kubernetes
Sites that already operate their own cluster host it there instead, using your ingress, your storage and your sign-on.
- Bring your own identity provider
- Bring your own storage
- Fits the platform you already run
On its own, or beside the line
It runs as part of a production installation, where the order and pallet values are already at hand, or on its own against the systems you point it at. Same product, and the same install shape at every site.
- Standalone or alongside line control
- One install per site, one design library
- Rolled out plant by plant
Works with the rest of the range
The order and pallet values a label needs are the ones the line and the order system already hold, so the label is filled from the same account of what was produced instead of a second copy of it. An automation can watch the print queue and raise the right person the moment a printer stops.
How to start
Start with the label that causes the most trouble.
Pick the one label that gets reworked most often. We rebuild it in the designer with you, bind it to real orders, and print it. If it holds up, the rest of the label library follows one design at a time.