How should I number my ID tags?

Best Practice for Numbering Tags

Stageforce supports both numeric tag numbers and tag numbers with an alpha prefix. Either format will work, but we recommend using a prefix when starting a new tag program or ordering a new series of tags.

Why use a prefix?

A prefix creates a distinct numbering range. This can help prevent duplicate tag numbers as your inventory grows or when you order tags in multiple batches.

For tags ordered from Atlas RFID, use a single uppercase hexadecimal letter:

A, B, C, D, E, or F

Example tag ranges:

- A00000001 through A00001000
- B00000001 through B00001000

Do not use letters outside A–F for Atlas RFID tags, even though Stageforce may accept other letters.

Keep the prefix consistent

The tag number created in Stageforce must match the number printed and encoded on the physical tag, including the prefix.

For example:

- If the physical tag is encoded as A00001234, create it in Stageforce as A00001234.
- If the physical tag is encoded as 00001234, leave the Alpha Prefix field blank.

Adding a prefix in Stageforce when the physical tag does not contain that prefix creates a different tag number. Stageforce will not recognize it as a match when scanned.

Choosing a prefix

Use the prefix to identify a permanent tag series or numbering range. Avoid assigning prefixes based on information that may change, such as:

- Warehouse
- Current location
- Employee
- Product category

A tag may move or be reassigned, but its number should remain the same.

What about existing tags?

Numeric-only tags remain fully supported. If your current tags scan correctly and have unique numbers, there is no need to renumber or replace them.

Our recommendation is:

- New tag orders: Use a single A–F prefix consistently in Atlas RFID and Stageforce.
- Existing numeric tags: Keep the current numbering format.
- Every tag: Make sure the number in Stageforce matches the physical tag exactly.