PostgreSQL is where a lot of modern operational data ends up. Rather than exporting it for every label run, LabelInn queries it directly and prints one label per returned row.
Product, logistics and manufacturing teams whose application database is PostgreSQL and whose labelling is still a manual copy-paste step.
How it works
Install the LabelInn Windows app and your PostgreSQL client driver on the machine that will run the job.
Add the PostgreSQL connection: host, port 5432, database and a database user that can read the tables you need.
Write the PostgreSQL query that returns exactly the rows you want to label, one row per label.
Map each result column onto a label field — text, barcode, QR or RFID — then preview a few rows.
Print the result set, or save the query so the next run is one click.
Write ordinary PostgreSQL. Append LIMIT n while you are testing so a preview never pulls the whole table.
What you can do
Result columns bind to any label field, so barcode and QR content comes straight out of PostgreSQL.
Re-run the saved query whenever you need the current rows — no export, no copy-paste, no stale file.
Mix database columns with static text, counters, dates and serial numbers on one label.
Printed rows are recorded in the print history, so a reprint or an audit can find the exact job later.
Queries can be parameterised, so an operator supplies a work order or batch number instead of editing SQL.
Questions
Does label data leave my network when I print from PostgreSQL?
The query runs from the machine you installed LabelInn on, against your own PostgreSQL server. Credentials stay local. What leaves the machine is what you choose to sync — the label design and the print record.
Which PostgreSQL do I write?
Ordinary PostgreSQL. LabelInn does not rewrite your SQL; it runs the statement you saved and maps the result columns onto label fields. Use `… LIMIT n` while testing.
Can I print to a Zebra or TSC printer from PostgreSQL without a driver?
For models LabelInn drives natively over ZPL, TSPL or TPCL, yes — the command stream is generated and sent directly. That is independent of the database driver, which is only used to read your rows.
Try it with your own PostgreSQL data
Start on the free plan, print a real label, and only pay when you want LabelInn to run the job for you.