If your label data already lives in a spreadsheet, the printing step should take minutes, not an afternoon of retyping. The workflow has three parts: create the label page, bring the spreadsheet in through the import, then print the batch. The software's own tutorial sets that order, and reversing it is where most of the rework comes from.
Why Excel is the right data source, and when it is not
For most small businesses the spreadsheet is the system of record long before any ERP exists. Part numbers, prices, batch codes, serial ranges, product descriptions — they are all in a file that somebody maintains by hand and everybody trusts. Using it as the label data source means the label and the catalogue cannot drift apart, because they are the same file.
It stops being the right answer in three situations. Past a few thousand rows edited by several people, a spreadsheet stops being reliable and starts being a version-control problem. When label content must be approved before it prints, the data has to come from a controlled system, not a shared file. And when labels need to print automatically at the moment of a warehouse transaction, no one is going to be sitting there opening an Excel file.
For everything in between — product labels, shelf labels, asset tags, shipping references — the spreadsheet is the correct and simplest source.
Two ways Excel connects to a label
The software's own documentation splits Excel use into two modes, and picking the wrong one is why people end up redrawing a label they already had.
New label — you have the spreadsheet but no design. The software reads the columns and lays out a label from the data automatically. This is the fast path from nothing: a sheet of part numbers and descriptions becomes a printable label without any layout work.
Import printing — you have a finished design and want to fill it with spreadsheet data at print time. You design once, print as usual, choose the Excel print option, and import the file. The layout stays; the fields take their values from the rows.
A rule of thumb: if the layout matters — a logo, a fixed barcode position, a compliance block — design first and use import printing. If only the data matters, let new-label mode lay it out.
Step by step: from spreadsheet to printed batch
The steps follow the software's own tutorial for Excel Import Printing, in the order it gives: set up the label page first, bring the Excel elements in second, print last.
Step 1 — Create the label and set its size
Start a New Label from the new-label wizard, then set the width and length in Label Page Settings. The tutorial puts this first because everything after it inherits the page: the import draws onto this canvas, and the print sends it at this size.
Match the numbers to the physical stock — 4×6 in for shipping labels, 100×150 mm for pallet and carton labels, 50×30 mm for shelf and product labels. On A4 sheets rather than a roll, the rows, columns and spacing fields in the same dialog are what lay several labels across one page.
Step 2 — Import the Excel label elements
With the page set, use the Excel import entry in the top-right corner of the editing screen. Microsoft Excel and WPS are both supported, in .xls and .xlsx. The import runs as a four-step wizard — Import Excel data, Select Columns, Select Style, Automatically Generate — and reads the column names, which then become the fields available on the canvas.
The dialog lists the conditions the sheet has to satisfy. They are worth reading once, because each of them fails the import without an error message:
- Every column needs a title, on the first row. It is the title that the variable name is matched against.
- Titles cannot be numbers.
2024,001or123as a header will not work. - No spaces or special characters. Characters such as
+ - ~ ! @ # $ % ^ & * _and the slash break the name matching. - Images in Excel cannot be imported. A column of pictures is not a data column.
- No formulas. The cell has to contain a value, not a function that produces one.
Check the column preview before going further: a misaligned import is cheap to fix here and expensive once the design is built around it.
Step 3 — Match the field names to the column names
This is the rule that decides whether an import works: the Excel column field name has to be the same as the variable name on the label. That match is what lets the software pick up the right content for each field — nothing else connects them.
So name the columns exactly what you want the label fields called. PartNo, not Part No.; one header row, not a merged one. Renaming a column after the label is built means re-binding every object that used it.
The object stays fixed on the canvas; only its content changes per row. Set the font size for the longest realistic value, not the shortest one: overflow on a thermal label does not wrap, it truncates.
Step 4 — Generate barcodes from a column
Click the one-dimensional barcode entry on the left of the editing page and the software drops a barcode object onto the canvas with the content 12345678. Bind that object to your code column, then choose the symbology: Code 128 is the general-purpose choice, retail products use EAN-13, and the other symbologies are generally for export cartons and specific specifications.
One behaviour is worth knowing before you start: if the content does not satisfy the rules of the selected symbology, the editing area shows blank rather than an error. A barcode that will not appear is usually a symbology mismatch, not a broken object.
The properties panel is where the rest lives: the mil value adjusts display density to match your printer's resolution, alignment can be set to the left, the colour can be changed, the text at the bottom can be hidden, and the machine-readable content can be separated from the human-readable text — a barcode that scans as ASDFGHJ next to a label that reads A001 is a deliberate setup, not a mistake.
Step 5 — Generate QR codes from a column
The same pattern, with the QR entry on the left of the editing page: an object appears with the content 12345678, and you bind it to a column. QR Code is the usual symbology; DataMatrix is generally used in other business areas such as medical logistics.
Three settings decide whether the code scans: the text at the bottom can be hidden, and once shown its font size and style are set separately — leave the text blank and the QR content is displayed automatically; the code set matters when a scanner only supports English (ANSI switches with the computer's language; UTF-8 and GBK suit a Chinese environment); and the error tolerance level decides how much damage the printed code survives.
Step 6 — Handle the date column
A date is the field most often rendered differently from what was intended, and the fix is a format decision rather than a software setting. For anything that leaves the building, pick an unambiguous form — 2026-04-03 or 03 APR 2026 — rather than 03/04/2026, which is read differently in different regions.
Step 7 — Print the batch
The tutorial's closing move: click print as usual, select Excel print, import the same Excel file you used for the import, and print. Preview the first, a middle and the last record before committing the run — the last record is where pagination and sequence problems surface.
Printing a mixed batch
When one sheet contains several products that need different label layouts — a large carton label for one SKU, a small shelf label for another — the practical approach is to sort the sheet by product, apply a filter, and print each group against its own template. Trying to make one template serve structurally different labels produces a compromise that fits neither.
If the requirement is one template with varying field content rather than varying layouts, no special handling is needed: the batch prints as one job and each row fills its own fields.
Six things that break a batch print
- Fields come in empty. The column name and the variable name do not match. That match is the only thing connecting them, and a space or a merged header is enough to break it.
- One blank label in the middle. A subtotal or blank row. Filter the sheet to non-empty rows.
- Barcodes print as numbers. The barcode object was bound as a text object, or the symbology does not accept the value's length. Check the digit count against the symbology specification.
- Text truncated on some labels. Font size was set for the shortest value. Reduce size or enable wrapping where supported, and check the longest row.
- Dates shifted by a day or a month. Text-typed dates or a locale mismatch between the data and the printing machine.
- Printer stops partway through. Usually a print queue or spooler limit rather than a software limit. Split the job into blocks of a few hundred if the spooler stalls.
Frequently asked questions
Can I print from a CSV file instead of an Excel file?
Usually yes, since a CSV is the same tabular structure without formatting. The one thing to watch is that CSV does not preserve column types, so codes and dates that were formatted in Excel arrive as plain text — which for barcode columns is often an advantage, and for date columns usually is not.
Why do my barcodes print as plain numbers?
Most often the value does not satisfy the rules of the selected symbology — the software simply leaves the editing area blank in that case, with no error message. Bind the column to a barcode object rather than a text object, and check the value against the rules of the symbology you chose.
Can every label in a batch carry a different QR code?
Yes, that is the normal behaviour of a bound field. Each row supplies its own value and therefore its own QR code. The pattern is the same as a barcode batch; only the symbology and the data capacity change.
What happens if a row has an empty cell?
The corresponding field prints blank on that label, and the rest of the row prints normally. A barcode bound to an empty value may print nothing at all, which is how a missing label is usually discovered — halfway through a run, when the gap is already on the roll.
How many rows can I print in one batch?
There is no fixed number, and the practical limit comes from three places: the printer's memory buffer, the software's job handling, and how long you are willing to watch. For runs above a thousand, split into blocks of a few hundred — a failed block is far cheaper to reprint than a failed thousand.
Can I use Excel formulas as label values?
Yes, as long as the formula resolves to a value before printing. Concatenating a prefix and a part number into one column is a common and reliable pattern. Volatile functions that recalculate on open are less reliable in a batch workflow; paste the result as values before the print run.
The spreadsheet is already the hard part of this job, and it is already done. Once the columns are clean, text-formatted and free of blank rows, the label software's contribution is a template and a binding — which is a ten-minute task that you will only ever do once per label design.
barcode and QR code labels · serial number labels · MasoLabel review
Need a hand with your own setup? Email labelprintingforalways@gmail.com or message us on WeChat at 18701979438. Questions about the free version are welcome too.