Code 128 vs EAN-13 for Product and Inventory Labels
Choose a barcode format for internal stock or retail products and verify the print using the actual scanner.

Quick answer
Choose the symbol after establishing what the receiving scanner or trading partner expects. Code 128 can encode internal identifiers with letters and numbers. EAN-13 is commonly used for retail identifiers and follows a specific numeric structure.
Verify the label and the system that consumes it
Suppose a warehouse puts an internal item identifier such as BIN-A17 on an aisle label. A receiving application that supports Code 128 can handle letters and digits for this use. The retail product shipped to a store has a separate identifier obtained through the appropriate organization and follows that partner’s rules. Keep those workflows independent in the inventory records. Print proof labels and scan them with the actual receiver. If the decoded string is correct, check that the app looks up the intended record and does not normalize values in a way that loses leading zeros. The text printed below a symbol helps a worker cross-check the result if a reader fails.
Use the FixHubLab Barcode Generator for supported Code 128 output. Use the Barcode Scanner to test an image or as a convenience check alongside the real hardware workflow. For retail onboarding, obtain the right barcode specification, identifier and print guidance from the trading partner or local GS1 organization. A check digit helps validate the number’s structure and cannot establish assignment to a real product. Avoid taking a sample number from a reference site and putting it on a commercial label. Verify width, required quiet zones, print setup and label placement on the physical packaging. A reader’s beep is the start of verification. Owners also need to see the expected string and correct product or location in the receiving application.
Identify where it will scan
A company needs warehouse labels and also wants to ship to retail stores. Before putting time or money into this step, agree on a concrete criterion. Treat whatever is essential to complete the job as a mandatory requirement. Keep convenience, speed and ease of handoff in a separate part of your notes. This helps you avoid promoting something that looks easier in a trial but cannot complete a critical part of the task.
Start here. Ask the receiving platform which symbologies and identifiers it supports. Keep internal location codes separate from externally assigned product identification.
An internal label is accepted by one scanner and mistakenly treated as a retail identifier. Think through how a customer or colleague would discover this error. A clear, visible failure is easier to resolve than a result that looks successful and leaves a problem for the next person. If it would be hard to notice, add one direct inspection that examines the outcome itself. Record evidence for the result instead of relying entirely on a successful status label.
Confirm the result. Scan a valid sample in the actual application and inspect the stored value. Work through this step before expanding the change. One realistic example is enough to reveal a category of failures that an ideal example misses. A trial is also a useful time to learn what to do when the result is ambiguous, especially if different people would have to resolve disagreement.
Check partner rules for specific channel and region requirements before producing labels. Capture the decision and the reason in a short note so it can be revisited if the workload, policy or software changes.
Use legitimate assigned identifiers
Example situation. A product will appear in externally managed commerce channels.
Follow the trading partner’s and GS1 organization’s requirements for product identifiers where applicable. Use the organization’s appropriately assigned values. Give the test enough room to show the original problem. Use the same entry point that someone with the issue would use. If several variables change between attempts, note which ones cannot be held constant and avoid assigning a cause yet. You can make a smaller experiment after getting that first picture.
A random checksum-valid number is assumed to identify a real product globally. It helps to document the specific contrast as soon as you see it. Save an innocuous screenshot, a small sample or a short time record if appropriate, with identifying details removed when they are unnecessary. The next person will need a result that can be interpreted without guessing what happened immediately before you captured it.
Inspect the outcome. Confirm product ownership and onboarding in the receiving process before printing a production run. If you need to hand this to support or a maintainer, include the expected outcome, the first unexpected observation and the last known working state.
Keep an approved list mapping each real identifier to its matching product and pack level. Write down whether the follow-up confirms your original explanation or exposes another factor. Confirmed evidence supports a specific change. If the behavior still varies without a known reason, retain the last working settings and focus the next test on that variation.
Protect leading zeros and data type
An inventory CSV includes numeric-looking part numbers. Decide what should stay intact while you try the change. For a small trial this might be the original input, a visible result another person already depends on, or access from a second supported device. Keep an appropriate copy or note of the earlier state. Tests that are easy to reverse make it possible to learn even when the first idea is wrong.
Store identifiers as text when their exact characters matter. Confirm the expected encoding before feeding data into a generator.
Watch for this: A spreadsheet silently changes a code’s length during export. Consider the exact point where you would stop and revert. If the issue appears, reproduce it without repeating a consequential action unnecessarily. A disposable example or read-only observation can give you the needed evidence. In a shared environment, tell others handling the test what state you expect to see before the next step.
Compare electronically decoded values with the source field, including leading zeros. Verify the ordinary case that should have remained intact as well as the intended improvement. If one passes and the other fails, keep both observations and examine the relationship between them.
Keep a sample with similar-looking identifiers to catch normalization collisions. Use the result to write a one-sentence acceptance condition. Make it specific enough that another person would know which setup to use and when to stop.
Verify validation and check digits
A tool accepts a barcode entry but the scanner rejects it.
Identify what the format encoder expects, including check-digit behavior. Use the correct format for the data rather than forcing a shape. Start with conditions you can readily repeat. Ask if your normal day includes a meaningful variation, such as a busy period, a second account or input from a different source. Select the variation based on your real use instead of trying every theoretical case.
An operator appends its own check digit where the generator already calculates one. Record whether you found a recurring failure, a one-time event or an unresolved observation. The three have different implications. A repeating mismatch is easier to verify and to pass along for repair. A one-time interruption can still matter, but document the context and look for a separate observation before committing to an explanation.
Decode the printed result and compare it with the original approved identifier. A simple check for the result usually beats a complicated proxy. If a reading looks surprising, return to the user-visible outcome and trace it back to the earliest relevant event you can observe. Comparing that observation to the expected rule may show exactly what additional information to collect.
Check the published spec and the receiving application’s expectations separately. Use a representative size or repetition count when it affects the result. If a small test and a normal-sized workload behave differently, include both in the handoff so the earlier test can be understood in context.
Plan height, width and quiet zones
Use this case to review the plan. Recognition drops when labels are printed on small stock.
Choose a printable size appropriate for the symbol and intended scanner. Preserve clear margins and avoid distorting the barcode. Write down who owns the setting, file, service or decision before considering the trial finished. In a personal setup that may simply mean keeping the needed information somewhere you can find it later. In a shared setup it may determine whether the next person is able to continue during an interruption. Give that person enough context to determine if the result still applies.
Failure that matters: The graphic is stretched horizontally or squeezed across a curved surface.
Print on the actual material and scan under working conditions. A successful check has a concrete observable result. Confirm it from the normal user path, then put the test input and the observation in your notes. If cleanup is needed, remove test artifacts carefully and retain the benign evidence needed to repeat the test later.
Test how label orientation and package curvature affect scanner access. Check any agreement about when to rerun the trial. An annual review can miss changes that happen at a specific release or after access is revoked. Conversely, some checks make sense on a fixed calendar because no individual event will remind you to try them. Choose the trigger that fits the use case and record a known starting point.
Keep formatting and output consistent
Try it when you need to: A batch of hundreds of labels comes from an inventory export.
Use clearly named files, verify count, and spot-check data, label placement and human-readable text. Keep the production source stable.
Establish the expected result before starting. A useful way to make this concrete is to describe the one thing you plan to observe and the condition under which it should hold. Save a baseline using the same input or conditions you will use after the change. If another person helps, have them record the expected result independently. That can surface a difference in interpretation before you spend time debugging an apparent failure.
An easy mistake to miss: Correct barcodes are attached to the wrong boxes because names or row order changed.
Compare first, last and selected random scan results against the batch manifest. Preserve the comparison in a form you can come back to: write down the input, what you expected and what you actually saw. In a decision with several options, keep one record per option rather than changing the definition of success for each trial.
Review late changes after regenerating only the affected entries. Think about whether this follow-up calls for revising the original rule or handling a separate case. If it is separate, keep the original test available and check that both cases still succeed. This is also useful when you need to explain why something that looked fine in a demonstration behaves differently in ordinary use.
Check printer and scanner together
A new printer or driver changes output appearance. This is a good place to watch where the result starts to differ from what you expect. Note the entry conditions and any settings or data that you have assumed. Take an initial reading, then do the work with those same conditions recorded. Avoid resetting everything at the first sign of trouble. A change that accidentally hides the symptom gives you less information about what caused it.
Compare resolution, print scaling, darkness and physical labels. Scan with the intended reader and also verify the receiving app logs the right data.
Inspect this failure: A successful beep is treated as proof that the entire workflow stored the intended product. Make the first follow-up test small enough to repeat without changing unrelated parts of the setup. Start at the first boundary you can observe, then check the next one only if the initial result was right. Write down the observations in order. A later symptom can look like the root problem if you check the later step first and do not have an earlier reading.
Inspect the decoded string and the record it updates, using safe test data. When the check is successful, repeat the ordinary action from its normal starting point. This catches results that only worked because the original test left a session, a temporary setting or a sample file in place. If somebody else follows the directions later, their starting conditions might be different.
Check OCR or human-readable text separately if operators use it for manual entry.
Maintain the label standard
Multiple staff generate labels across locations.
Begin with a simple case where you can tell if things went wrong even before looking at any reports. Keep a copy of the starting inputs and confirm the result that ought to follow from them. Ask what the user will see and what the underlying system ought to do. Those are worth checking separately when a screen, message or summary can still look correct even though a change did not reach the place you intended.
Record approved symbol types, data sources, label dimensions and verification steps. Document who maintains trading-partner mappings.
An unapproved spreadsheet becomes the only reference for what each printed code means. Include this possibility when you define a failure. Try a known good case beside the suspected one. If both fail in the same way, examine what they share. If only the particular case fails, save the difference that makes it a useful test.
How to verify: Ask a second team member to regenerate and verify a sample from the standard.
Revisit when scanners, printers or inventory software change. On the next pass, use a second representative input or condition to make sure the first result still applies. A narrow test can be decisive if it measures the thing you need. A wider sample is useful when your real work includes several distinct patterns and one result cannot stand for all of them.
A short verification checklist
| What to check | How to tell |
|---|---|
| Identify where it will scan | Scan a valid sample in the actual application and inspect the stored value. |
| Use legitimate assigned identifiers | Confirm product ownership and onboarding in the receiving process before printing a production run. |
| Protect leading zeros and data type | Compare electronically decoded values with the source field, including leading zeros. |
| Verify validation and check digits | Decode the printed result and compare it with the original approved identifier. |
## Keep symbol choice in your label documentation
Write down supported data type, encoding format, human-readable text, output file and printer profile. Add the trade partner’s approved guidance where a label is used in external commerce. A warehouse locator can have letters and digits. A retail EAN-13 identifier has a defined numeric structure and assignment context. Test decoded values in the receiving application and check the real record that appears. Retain a print proof and check on actual label material. For an artwork or packaging redesign, confirm barcode area and contrast as part of final proof approval.
A temporary label created for test scans should be stored apart from production artwork, so the approved pack identity remains easy to distinguish.
If ordering or return workflows scan several package levels, label each level only according to the partner’s assigned product mapping. Ask the receiving operator to verify which physical package and inventory record are associated with each test scan.
Related reading
Reference documentation explains the relevant standards or workflow. Try the related FixHubLab resource for a practical next step. Use the FixHubLab blog to find the rest of the guide series.
