NFC batch setup
Use Batch setup in the EnaFeedback mobile app to write many NFC tags in a row, and learn about counters, conflict prompts, the offline sync queue and the limits.
- Mobile app· admin
This article was verified with an older release. Screen names or steps may differ in the current version.
Batch setup is the mode in the EnaFeedback mobile app that lets the organization owner write many NFC tags one after another. You scan a poster's QR code, hold a tag near the phone and move on to the next poster. The app keeps each tag's trust code in a queue and sends them to the server in groups, so tags you have written are not lost even if the connection drops. Use it to tag dozens of locations in one walk, such as the floors of a hospital or the buildings of a campus.
To write, verify and lock a single tag, see NFC tags.
Required role, permission and version
- Owner role (the NFC settings permission belongs to the Owner only).
- A phone with NFC hardware and EnaFeedback Mobile 1.2.0 or later. The server needs at least EnaFeedback 2.1.103.
- The QR posters of the locations you will tag, either already on the wall or in your hand. Batch setup does not pick locations from a list; each location is found by its poster's QR code.
- Blank, writable NFC tags.
Start batch setup
Open NFC settings
Open NFC settings from the NFC settings row on the Manage tab, the shortcut on the Home tab or the NFC button in the middle of the bottom bar, then tap Batch setup.
Decide whether to lock
With Also lock tags on, each tag is closed against writing right after it reads back correctly. This cannot be undone. The option is off by default. If you are unsure, leave it off; you can lock tags one by one later with Lock.
Scan the next poster
The camera stays open: Scan the next poster QR. The app finds the place and shows the "Building · Floor · Unit · Place" line.
Hold the tag near the phone
Hold the tag near the phone. In one tap, the app writes the address and trust code, reads the tag back to check it and, if locking is on, locks it. On success, the phone vibrates and shows Written: <location>.
Move on
The camera restarts on its own. The same poster is ignored for 3 seconds so you do not scan it twice by accident. Continue with the next poster.
If a tag is written but cannot be locked, you see The tag was written and queued, but it could not be locked. The tag is valid; you can try locking it again later.
Locations that already have a tag
If the location you scanned already has a tag, you see This location already has a tag: writing a new one makes the old tag invalid.
- Write new tag continues.
- Cancel skips this poster.
- Turn on Don't ask again in this session to stop this prompt for the rest of the batch. This helps when you replace tags in bulk.
Counters and the sync list
Four counters for this run appear at the bottom of the screen:
| Counter | Meaning |
|---|---|
| Written | Tags written in this run |
| Synced | Tags the server has stored |
| Pending | Tags that have not reached the server yet |
| Failed | Tags that could not be saved or that need confirmation |
The list below shows items under Needs confirmation first, then Recent tags (the newest 40). Each row shows the place, the location code, Locked if the tag is locked, and one of these states: Pending, Synced, Needs confirmation, Failed or Skipped. You can skip a failed row with its X button.
When items are pending, Sync now starts sending right away.
Conflicts: Overwrite or Skip
While you write tags, another administrator may have changed the same location's tag. The item then moves to Needs confirmation: "Another administrator changed this location after the list was loaded."
- Overwrite: your tag becomes the valid one; the other tag no longer verifies.
- Skip: your tag's trust code is deleted and never sent to the server. That tag will not verify; you need to write it again.
Offline sync queue
Batch setup does not wait for the server after each tag. Every tag that reads back correctly goes into a queue:
- The queue is kept per organization in the device's secure storage (iOS Keychain, Android Keystore).
- Sending starts about 2 seconds after a write, or as soon as 20 items are waiting. Each group carries at most 100 items.
- Without a connection, the app retries automatically at growing intervals (at most once every 60 seconds); nothing is dropped. The screen shows No connection. Retrying automatically.
- If the server is busy, the app waits as long as the server asks: The server is busy. Retrying in N s.
- If your session has ended, the queue pauses: Sign in as an administrator to continue syncing.
- If you write a newer tag for the same location, the older unsent item leaves the queue.
If you try to close the screen while items are pending, you see Tags not synced yet. With Leave, sending continues while the app stays open, and remaining items are sent the next time NFC settings opens. Stay takes you back.
Let the queue empty
Queued items exist only on this phone, and tags that have not reached the server do not verify. When you finish a round, check that the Pending counter is zero.
Known limits
- Batch setup is only for the Owner role and phones with NFC hardware. On devices without NFC (for example an iPad) the option does not appear.
- The app does not list or order locations; you set the order by walking from poster to poster.
- The server applies a request limit per administrator. If you reach it, the queue waits and continues on its own.
- There is no summary screen for a run; the counters and the list show the results.
- After a batch, we recommend checking a few tags on site with Verify.
Related articles
Can't find what you need?
Our support team can help with anything from setup to reporting.
NFC tags
Write a location address and trust code to an NFC tag with the EnaFeedback mobile app, verify and lock the tag, and learn how field staff get a verified read.
Visitor screen
What does a visitor see after scanning a QR code? EnaFeedback visitor screen tiles, use without a location, language choice, announcement banner, request tracking and offline page.