Who this is for
Product, logistics and manufacturing teams whose application database is PostgreSQL and whose labelling is still a manual copy-paste step.
How it works
Step by step
- 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.
Try it with your own data — signing up starts a 14-day Pro trial, no credit card. After that this feature needs Starter at $7.99/mo. Download now → | See pricing →
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.
Technical details
| Engine | PostgreSQL |
|---|---|
| Default port | 5432 |
| Query language | PostgreSQL |
| Row limit syntax | … LIMIT n |
| Driver | Your own ODBC/OLEDB/Oracle client driver |
| Platform | Windows desktop app |
| Credentials | Stay on your machine; the query runs from your network |
Requirements for a direct database connection
- Direct database connections need the LabelInn Windows desktop app — the connector that loads real database drivers is a Windows sidecar, so this path is not available on macOS today.
- You supply the PostgreSQL client driver; LabelInn does not redistribute database drivers.
- Point the connection at a read-only database user. LabelInn reads rows to fill labels — it should never need write access.
- While you are testing, keep the query small with `… LIMIT n` so a preview cannot pull an entire table.
What happens after you download?
Frequently asked 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.
What we verified
The capability is implemented in the LabelInn codebase and the referenced source file names the exact format, engine, port or endpoint described on this page.
lib/models/database_connection.dart — DatabaseKind.postgres('postgres', 'PostgreSQL', 5432)
Print your PostgreSQL data on the printer you already own
This feature runs on Starter — $7.99/mo, or $79.90/year (pay for 10 months, use 12). Signing up starts a 14-day Pro trial, so you can bind your own PostgreSQL data and print a real label before you pay anything.
Start your 14-day Pro trial → Download the app