For software errors inside BatchMaker, see Common Software Errors & Troubleshooting
Reader Placement Issues
Incorrect reader placement is the most common cause of missed scans on the production line.
Symptoms: Products are passing the reader but some tags are not being scanned, or scan rates drop at higher production speeds.
Steps to resolve:
Measure the distance between the reader face and the INFOTAP label on your product. It must be within 1.5 inches (3.5 cm).
Confirm the reader is aligned squarely with the label — angled placement reduces read reliability.
Use Test Mode in BatchMaker to scan test products and confirm reliable detection before running a live batch.
If products are moving too quickly past the reader, try reducing line speed or repositioning the reader to extend the contact window.
Interference from Metallic Surfaces or Equipment
NFC readers are sensitive to nearby metal, which can absorb or reflect NFC signals and reduce scan reliability.
Symptoms: Scans work in isolation but fail when products are on the line, or read distance appears shorter than expected.
Steps to resolve:
Check whether the reader is mounted against or near a metallic surface (conveyor frame, metal shelving, equipment housing).
If possible, add a non-metallic spacer or mount between the reader and any metal surface.
Keep other electronic equipment (motors, compressors, radios) at a distance from the reader where possible.
Re-test using Test Mode after any adjustment.
Tag Orientation Issues
NFC tags have a preferred orientation for optimal read performance. If labels are applied inconsistently to products, scan reliability may vary.
Symptoms: Some products scan well while others are missed, with no clear pattern related to line speed or reader position.
Steps to resolve:
Check that INFOTAP labels are applied consistently to the same position and orientation on every product.
Confirm the label face (the side with the antenna) is facing toward the reader, not away from it.
If label application is automated, check the applicator alignment. If manual, review placement procedure with operators.
Tamper Loop Alerts at End of Batch
Symptom: After stopping a batch, the confirmation screen shows one or more broken tamper loops.
This is expected behavior when Tamper Detection is enabled. BatchMaker detected products whose tamper-loop tags were already broken before leaving the production line.
Next steps:
Note the count of broken tamper loops shown on the confirmation screen.
Identify and set aside any products flagged during the run for review before shipment.
If tamper loop breaks appear unexpectedly at high volume, review product handling on the line — tags may be getting damaged during processing or packaging.
Note: Tamper Detection is only relevant for brands using tags with a physical tamper loop. If you do not use tamper-loop tags, this setting should be off.
Last Synced: 2026-03-12 · Sync Status: Draft