Default or External ID

In modern event management, badges serve as more than just a name tag – they're a tool for seamless entry, efficient tracking, and enhanced attendee engagement. One of the essential features of Badge Builder is the ability to incorporate both QR codes and barcodes on badges, offering versatile options for data handling and integration.

QR Codes and Barcodes:

Badge Builder allows event organizers to embed QR codes and barcodes on each badge, transforming them into multi-functional assets. Both QR and barcode data can be generated in two ways:

1. Default: This option generates codes automatically within the ExpoPlatform system. It's quick, easy, and requires no additional data imports, making it ideal for straightforward setups

2. External: For events with specific data requirements or outside registration vendors, organizers can load custom QR and barcode data. By uploading data through participant imports or API integrations organisers have the flexibility to control precisely what information each code contains

When uploading external data for barcodes, it's essential to ensure the information is provided in the correct format to ensure compatibility with Badge Builder. Please review the supported formats below.

The platform supports the following barcode formats:

• ITF (Interleaved 2 of 5): A numeric-only format often used for inventory and warehouse management.

• Code 128: A versatile and high-density barcode that supports both letters and numbers, making it ideal for encoding alphanumeric data.

• Code 39: Known for its simplicity and robustness, this format also supports alphanumeric data and is widely used in various industries.

• EAN-13: Primarily used in retail, this barcode format encodes 13-digit numbers and is compatible with global standards.

By adhering to these format options, organisers ensure that externally loaded data aligns with the badge's layout and functionality, allowing smooth and accurate scanning during the event.

🆕 [NEW SECTION] FAQ: Common questions about external QR data

Added April 2026. Source: Elena Potapov (Product/Eng). Gap identified by Julia Oliveira (TAM).

Q1. Do exhibitors have badges?
No. Badges (digital and printed) only exist for participants and team members (TM). Exhibitors do not have badges, which is why the External QR field is not in the exhibitor import template — only in the participant import template.

Q2. What format should the External QR value be?
It must be a QR string (text value), not a URL. The field name in some exports may be misleading.

Q3. Where do I get the QR string from?
Typically from the client's badge provider (third-party vendor printing the physical badges). The TAM should ask the client to request this from their provider.

Q4. Where do I activate external badges once the data is uploaded?
Activate it on both Digital Badge and Printed Badge configuration, for the relevant categories that should use external QR codes. If only one is activated, the badge will be inconsistent across channels.

Q5. Full process for using external QR codes:

1. Get the QR strings from the client's badge provider.

2. Upload them via participant import (or via API).

3. In Badge Builder → Digital Badge: switch QR source to "External" for the relevant categories.

4. In Badge Builder → Printed Badge: do the same.

5. Verify on a test profile that the badge displays the external QR string.