Use this page to look up error codes displayed in BatchMaker or to search by keywords (e.g. "reader not working", "tamper", "batch won't start"). Each section includes steps you can take before contacting support.
Important: BatchMaker saves all batch data locally on the unit. If an error occurs, your batch is never lost — it will continue to upload automatically once the issue is resolved.
Tag & Tamper Errors
Tamper Detected
Error Code: 5001
Keywords: tamper, broken tag, tamper loop, tag damaged, tamper error
BatchMaker detected that a tag is in a tamper state. This means the tag's tamper loop may be physically broken or the chip has been flagged as compromised. This is the tamper detection system working as intended — the tag should not be applied to product.
Steps to resolve:
Remove the tag from the line and set it aside for supervisor review. Do not apply it to product.
Physically inspect the tag for visible damage — look for a broken tamper loop or tail.
If multiple consecutive tags are failing, check the label applicator — it may be damaging tags during application.
If no applicator issue is found, check whether the affected tags are from the same batch — this may indicate a tag quality issue. Isolate the affected tags and notify your supervisor.
If no obvious cause can be found and the issue continues, contact ForgeStop support.
Unable to Read Tag Data
Error Code: 5002
Keywords: tamper URL, NDEF, tag not reading, tag read failed, line speed
BatchMaker was unable to read the full NDEF message from the tag. This is most commonly caused by the production line moving too fast for the reader to complete the read.
Steps to resolve:
Slow the production line down and re-present the failed tags to the reader.
Hand-scan a few of the failed tags individually to confirm the cause:
If they read successfully → the line speed was too fast. Adjust the pace and continue.
If they still fail consistently → the tags may be missing an NDEF message. Remove the affected tags and contact your tag supplier.
Tag Not Found / Unable to Select Tag
Error Code: 5003 / 5004
Keywords: UID not found, tag not detected, select failed, tag not reading, reader not picking up tag, no tag detected
BatchMaker could not detect or establish communication with the tag. This is usually a reader positioning or environmental issue.
Steps to resolve:
Check reader positioning — ensure the tag is placed directly on or close to the reader surface and held still during the scan.
Check for environmental interference — metal surfaces, other electronic equipment, or electromagnetic sources near the reader can disrupt scanning.
Check the reader hardware — inspect the USB cable and connections, ensure the reader is receiving power (check indicator lights).
In BatchMaker Settings, confirm the correct chip type is selected for your tags.
Unplug the reader, wait 15 seconds, reconnect, then relaunch BatchMaker.
Restart the tablet or PC.
If the issue continues, contact ForgeStop support.
Reader Errors
Reader Not Connected / Reader Error
Error Code: 2001 / 2002
Keywords: reader not working, reader disconnected, reader error, scanner not connecting, reader not detected, no reader found
BatchMaker cannot connect to or communicate with the NFC reader.
Steps to resolve:
Confirm you are using an approved ForgeStop-compatible reader model. If unsure, contact ForgeStop support for the approved hardware list.
Check the physical connection — ensure the USB or ethernet cable is firmly seated at both ends.
Check the reader indicator lights — confirm the reader is receiving power.
Unplug the reader, wait 15 seconds, reconnect, then relaunch BatchMaker.
Try a different USB or ethernet port on the unit if one is available.
If you have access to another reader, try swapping it in — always relaunch BatchMaker after connecting a different reader.
If the issue persists, ask your IT team to inspect the USB or ethernet port on the unit.
If still unresolved, contact ForgeStop support.
Data & Connectivity Errors
Data Loading Error
Error Codes: 1009, 1010, 1011, 1012, 1013, 1015
Keywords: batch won't start, brands not loading, products not loading, metafields not loading, companies not loading, data not loading, failed to load
BatchMaker was unable to load data from the ForgeStop platform. This is most commonly caused by a connectivity issue or an API credentials problem.
Important: Any batch data already scanned is saved locally on the unit — nothing is lost.
Steps to resolve:
Check the internet connection on the unit.
Open BatchMaker Settings and tap Apply Settings to re-push your credentials to the platform.
Retry the action.
Restart BatchMaker, then retry.
Restart the tablet or PC, then retry.
If the issue continues, contact ForgeStop support — this may be an API credentials or backend pipeline issue.
File Upload Error
Error Code: 3001
Keywords: file not uploading, upload failed, batch not uploading, outbox, sync error
BatchMaker failed to upload a completed batch file to the ForgeStop platform.
Important: The batch file is saved locally on the unit and BatchMaker will automatically retry the upload until it succeeds — your batch data is not lost.
Steps to resolve:
Check the internet connection on the unit — BatchMaker will resume uploading automatically once connectivity is restored.
If connectivity is confirmed and the upload is still not retrying after several minutes, contact ForgeStop support.
Application & Startup Errors
BatchMaker Won't Open
Error Code: 6001
Keywords: BatchMaker not opening, app won't launch, startup error, BatchMaker crashed, application error
BatchMaker failed to start.
Steps to resolve:
Confirm the unit is running Windows 11. BatchMaker requires Windows 11 to operate.
Restart the tablet or PC and try launching BatchMaker again.
Try running BatchMaker as Administrator — right-click the BatchMaker shortcut and select Run as administrator.
If BatchMaker still will not open, contact ForgeStop support. A reinstall may be required.
Wrong Administrator Password
Error Code: 4001
Keywords: wrong password, admin password, incorrect password, locked out, password error
The administrator password entered in BatchMaker is incorrect.
Steps to resolve:
Double-check the password and try again.
Contact your supervisor or system administrator for the correct credentials.
If credentials cannot be located, contact ForgeStop support.
System & Configuration Errors
Error Codes: 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1014
Keywords: settings error, configuration error, failed to save, file error, system error, label error, batch file error, CPU serial error, brand error
BatchMaker encountered an error reading or writing to a local file or system configuration. This is typically a machine-level issue related to folder permissions or system configuration — not something caused by the operator.
Important: Batch data is saved locally on the unit — nothing is lost. Batches will continue to queue and upload automatically once the issue is resolved.
Steps to resolve:
Restart BatchMaker and retry.
Restart the tablet or PC and retry.
Try running BatchMaker as Administrator — right-click the BatchMaker shortcut and select Run as administrator.
If the issue continues:
If your company owns and manages this unit, contact your IT department — this is likely a folder permissions or machine configuration issue.
If this is a ForgeStop-managed unit, contact ForgeStop support directly.
Note for Error Code 1006 (System ID Error): This error means BatchMaker was unable to read the hardware identifiers used to register this unit with the ForgeStop platform. Batches will be stored locally but may be rejected by the platform until resolved. Treat this as urgent and escalate immediately using the steps above.
Last Synced: 2026-03-14 · Sync Status: Current