An inventory label maker is useful only when the printed identifier has a clear job. A label on a product type, a uniquely tracked asset, and a shelf location may all carry a barcode, but they identify different things. GS1's identification guidance distinguishes trade items, locations, and individual company assets for that reason. Start with the record the label should represent, then work outward to the label, printer, software, and scanner.

Key takeaways

  • Decide whether the label identifies a product type, one asset, or a location before designing its code.
  • In a batch job, repeated copies and unique serial values are different instructions; software may handle them through different data fields.
  • Test barcode size and placement where staff will actually scan the label.

Start with Polono for an overview of our printing range, then define the inventory records and scanning workflow before comparing individual devices.

Start with the record: what is being identified?

Three common labeling tasks need different identifiers. A stock or product label identifies a type of item. An asset label identifies one particular object that may be checked out, moved, serviced, or retired. A location label identifies a shelf, bin, drawer, or other place. GS1 assigns separate identification roles to trade items, individual assets, and locations. A small internal system can use its own codes, but the distinction between these jobs is still useful.

Consider a warehouse with twenty identical desk lamps in bin B-12. The stock record may identify the lamp type, while B-12 identifies the place where units are stored. If each lamp is tracked separately for service, each unit also needs an individual asset identifier. Printing the bin code on the lamps would confuse the object with its location; printing one shared product code on individually tracked assets would not distinguish one unit from another. These are illustrative workflow choices, not prescribed identifier formats.

The first question for a prospective printer is therefore not how many barcode styles it advertises. Ask which record the label will retrieve, whether that record represents a type or an individual instance, and whether the identifier must remain stable when the item moves. Write down the answer before assigning label dimensions or buying supplies.

Build the label data before choosing a printer

An effective label begins with a small, controlled set of fields. A typical internal worksheet might contain an identifier, short description, object type, location, and a status field. The printed label need not display every field in the database. Its main job is to give a person or scanner a reliable route to the right record. Decide whether a scan should open a product master record, a single asset record, or a location record, and test that lookup in the actual application. A printed code alone does not update stock quantities.

Separate fixed data from variable data. Fixed artwork can repeat on every label; an item number, bin code, batch value, or asset serial may change by row. GS1's printing guidance makes this static-versus-dynamic distinction before the print process is selected. That question matters even when the team uses a private internal code rather than a GS1 retail barcode.

Define ownership of the identifier, too. Decide where new IDs are generated, how duplicates are prevented, and whether reprinting preserves the original ID. Those are process decisions to verify in the source system and label software. Do not assume that the printer itself manages the inventory database.

Plan batch printing: copies are not serial numbers

Batch jobs often mix two different needs. Ten identical shelf labels may need ten copies of one code. Ten individually tracked assets need ten distinct codes, even if their descriptions are identical. BarTender's documentation illustrates the distinction: a connected database field can control identical copies per record separately from the quantity of serialized numbers. That is an example of what label software can do, not a promise that every label maker or software edition supports it.

Write a sample print table before evaluating a system. One row could contain location = B-12, copies = 3 for three identical bin markers. A different row could contain a starting asset ID and serial count = 3 for three distinct asset labels. Ask the software vendor how these fields map into its print job, how it handles a skipped or failed print, and how an operator can reprint one label without accidentally issuing a new ID.

CSV import can reduce repetitive typing when the software supports it. BarTender's documented CSV integration maps fields from a trigger file to named label data sources and notes that its interface differs by version. Treat that as a feature to confirm in the exact software plan, along with field mapping, permitted characters, print quantities, and access to the inventory source. A spreadsheet export that prints nicely but cannot be reconciled with the live records may create a second, inconsistent source of truth.

Match the barcode to the actual scan task

A barcode that looks sharp on a screen may be hard to read after it is printed and placed on a real object. GS1 advises choosing barcode type, size, placement, and print quality for the primary scanning environment. A label scanned close up at a desk can face different constraints from one scanned on a high shelf or curved container. Define the scanner or phone, expected distance, lighting, surface, and placement before shrinking the symbol to fit a narrow label.

Leave the symbol's required clear margin intact. GS1 calls these margins quiet zones and treats them, along with contrast and placement, as parts of barcode artwork that affect decoding. The exact dimensions depend on the chosen symbol and applicable specification. Do not apply a retail 2D rule to every private inventory code. Keep decorative borders, text, and cut edges out of the area required by the actual symbology.

Test two things separately: whether a scanner decodes the symbol, and whether the decoded value resolves to the intended record. One successful scan proves little about a whole batch. For programs that require formal symbol quality, GS1 describes ISO-based verification as a graded assessment that goes beyond a scanner's simple read. A small internal pilot can still reveal wrong values, misplaced labels, or unreliable scanning, but it should not be described as formal verification.

Evaluate printer and label stock as a working system

The selection of Polono labels and supplies depends on the surface and handling it will encounter. GS1's printing playbook examines print process, substrate, product handling, and operational testing as separate considerations. For an inventory project, make a short requirement sheet: label dimensions; the material and shape of the object; whether it will be rubbed, cleaned, chilled, or exposed to light; how long it must remain readable; and where it will be scanned. Then ask for evidence or samples for the exact printer, stock, and application conditions.

Print capacity also has to match the data. GS1 distinguishes static information from changing information when selecting a printing process. When identifiers vary by record, confirm that the proposed hardware and software can print from the chosen data source at the needed volume and resolution. Compare the complete workflow, including data import, preview, operator corrections, and reprints, rather than treating print speed as the only throughput measure.

Media width, feed format, print method, adhesive and application surface are compatibility questions for the exact setup. No single printer category guarantees that every label will stay attached or readable in every environment. A supplier's material claim is most useful when it names the construction, surface, exposure, and service conditions that were actually evaluated.

Run a small record-to-scan pilot

Start with representative records, including a short ID, a long ID, a duplicate-prone description, a location change, and a deliberate reprint. Prepare a small batch on the proposed label stock. Apply the labels to the actual surfaces and let operators scan them using their normal device and distance. Record which source row produced each label and which application record each scan opens.

Compare output quantities with the job instructions. If one row requests multiple identical copies and another requests a serial sequence, check both results separately. BarTender's database-printing documentation shows why the distinction matters and even notes that some printer drivers may mishandle variable copy counts in a single job. The exact driver and software combination therefore belongs in the pilot.

Repeat the scan after normal handling in the intended setting. Check for missed scans, wrong record lookups, and unclear human-readable text. GS1's barcode guidance connects scanning environment and print quality with barcode design.

Check whether the stock remains readable and attached after representative handling. GS1's printing checklist includes substrate and operational testing.

If a formal barcode grade is required for the application, arrange the applicable verification separately.

Document failures by cause before scaling: data mapping, wrong ID, print quality, label placement, stock behavior, or scanner settings. A pilot cannot prove lifetime durability, but it can reveal that the proposed combination does not work in the immediate workflow.

If inventory labeling is part of a broader operation, our label maker guide for small businesses connects printer selection with everyday workspace and supply considerations.

Inventory label maker selection checklist

Use these questions to compare candidate systems against the same job:

  • What does each label identify: an item type, a particular asset, or a location? Where is the authoritative record?
  • Can the exact software version accept the required source fields, map them to the template, and support the needed batch process? The documented CSV workflow is one example, not a default capability.
  • Can the intended scanner read the printed code at the planned distance and placement?
  • Does the proposed stock fit the printer and the real surface and handling conditions?

Also ask who will create new identifiers, correct records, authorize reprints, and review mismatches. Keep the answer in the workflow document so a later equipment change does not silently change the meaning of a printed code. The most useful choice is the setup that passes these tests with the team's real data and operating conditions.