Help Center

What a template controls

A label template controls the design inside one label cell. It does not control the paper size, rows, columns, margins, or pitch of the sheet. Those physical details come from the selected sheet definition so a template can be reused without accidentally changing where the label lands on the paper.

Use templates to decide which fields appear, where they appear, and how they look. Text elements can show company, item, type, warehouse, or system values depending on the print workflow. Barcode and QR elements encode scannable values. Image elements can show a company logo, type image, or template-specific artwork. Shape elements are useful for backgrounds, accents, or visual separation when they do not make the code harder to scan.

The entity compatibility on a template matters. A specific asset label can use item fields because it prints known serialized items. A type label can use type fields because it is not tied to one physical asset. A generic Asset ID label should be able to print before the item exists. If a template appears in the wrong picker, check its intended use and supported entity settings before making it the default.

Choosing fonts for labels

Label fonts should be chosen for readability first. A label may look good on a large editor canvas but still be difficult to read at half an inch tall, under warehouse lighting, or after a printer softens the edges. Use bold, simple fonts for Asset IDs and Type IDs. Save decorative or brand-heavy fonts for supporting text where a missed character will not break scanning or intake.

Pluck includes a curated set of readable built-in fonts so teams can make labels feel less generic without depending on uploads. Mono fonts are helpful for serials, Asset IDs, and codes because every character has predictable width. Condensed fonts can fit more text, but they can become hard to read when the label is small. Display fonts should be tested on paper before they become a default template.

Uploading company fonts

Custom font uploads are controlled by subscription entitlement and managed from Company settings. When the company is allowed to upload fonts, the Terminology tab accepts company font files and makes them available to label templates. Supported formats include WOFF2, WOFF, TTF, and OTF. Upload multiple files when a family has separate regular, bold, italic, or display styles so templates can use the right face.

Uploaded fonts should be treated like any other brand asset. Use names that users can recognize, avoid duplicate near-identical files, and test the result in print preview. If a custom font fails to load, the preview should warn and fall back rather than opening the browser print dialog before the label is ready. If a font is only needed for a logo, consider using the logo image instead; text fonts are best when the content changes from label to label.

Images, logos, and render readiness

Images make labels feel branded, but they also add print-readiness risk. A logo or type image needs to load before the browser print dialog opens. Use the preview to confirm that the image is visible, scaled correctly, and not covering the barcode or QR code. If the print dialog opens too early, close it and use the preview Print button after the label page finishes rendering.

Keep image opacity, contrast, and placement practical. A low-opacity background can look polished, but it should never interfere with a scannable code or operational text. For small labels, the most important visual hierarchy is usually code, identifier, short item/type description, and then branding. Pretty comes after readable and scannable.