RFID Encoding & Variable Data Guide | American Price Mark Supplies

RFID Encoding & Variable Data

Understand EPC encoding, serialization, and what data you need to provide for custom RFID labels.

#️⃣ EPC Standards 📊 Variable Printing 🗄️ Data Integration
Get a Free Quote →
RFID label encoding and programming - EPC chip and antenna inlay for serialized data

Types of RFID Encoding

#️⃣

EPC (Electronic Product Code)

The standard data format for RFID. Contains a unique identifier that links to your database.

  • 96-bit or 128-bit standard formats
  • SGTIN for retail products
  • SSCC for logistics/pallets
  • GIAI for assets
🗄️

Serialized Data

Unique serial numbers encoded into each tag for individual item tracking.

  • Sequential numbering
  • Random unique IDs
  • Custom serial formats
  • Ties to your database records
📝

User Memory

Additional data stored directly on the RFID chip beyond the EPC.

  • Product details
  • Manufacturing date
  • Batch/lot numbers
  • Custom data fields

What Data Do You Need to Provide?

The data you provide depends on your application. Here's what we typically need:

For Retail (SGTIN)

  • Company Prefix (GS1)
  • Item Reference Number
  • Serial number range or format
  • Retailer-specific requirements

For Logistics (SSCC)

  • Company Prefix (GS1)
  • Serial reference format
  • Extension digit (if required)
  • Trading partner requirements

For Assets (GIAI)

  • Company Prefix (GS1)
  • Asset reference format
  • Serial number scheme
  • Integration requirements

For Custom Encoding

  • Data format specification
  • Field definitions
  • Serial number scheme
  • Sample data file

How the Encoding Process Works

1

You Provide Requirements

Tell us your application (retail, warehouse, asset tracking) and any specific requirements (retailer mandates, system integration needs).

2

We Define the Encoding Spec

We'll recommend the right EPC format and data structure. For custom encoding, we'll document the exact specification.

3

You Provide Data (if variable)

For serialized or variable encoding, provide your data file (Excel/CSV) or the rules for generating serial numbers.

4

We Encode & Verify

Each tag is encoded and verified for correct data and read performance. We can provide encoding reports for your records.

5

Labels Ship Ready to Use

Labels arrive encoded and ready to apply. No additional programming needed on your end.

Common EPC Formats Explained

Format Full Name Used For
SGTIN-96 Serialized Global Trade Item Number Retail products, item-level tagging
SSCC-96 Serial Shipping Container Code Pallets, cases, logistics units
GIAI-96 Global Individual Asset Identifier Fixed assets, equipment tracking
GRAI-96 Global Returnable Asset Identifier Reusable containers, pallets, totes
GDTI-96 Global Document Type Identifier Documents, files, records

Variable Printing Options

In addition to encoding unique data on each RFID chip, we can print matching variable data on the label face:

🔢

Serial Numbers

Human-readable serial numbers that match the encoded EPC for visual verification.

📊

Barcodes

1D or 2D barcodes (Code 128, QR, Data Matrix) for backup scanning with barcode readers.

📝

Custom Text

Product names, descriptions, dates, lot numbers, or any other variable text fields.

🎨

Color Coding

Different colors or graphics based on product category, department, or other criteria.

Frequently Asked Questions

What is EPC encoding?

EPC (Electronic Product Code) is the standard data format stored on RFID tags. It's a unique identifier—like a license plate for your product—that links to detailed information in your database. The EPC itself doesn't contain product details; it's a pointer to your records.

Do I need a GS1 Company Prefix?

For retail applications (especially if selling to major retailers), yes. A GS1 Company Prefix is required to create valid SGTIN codes. For internal asset tracking or closed-loop applications, you can use proprietary encoding schemes without GS1.

Can you encode variable data (different data on each tag)?

Yes. We encode unique data on each tag—serial numbers, EPCs, or custom data. You provide the data (spreadsheet, database export) or the format/rules, and we encode each tag accordingly.

What file format should I provide for encoding data?

Excel (.xlsx) or CSV files work best. Include one row per tag with columns for each data field. We'll work with you to map your data to the correct encoding format.

Can you print matching data on the label?

Yes. We can print human-readable text, barcodes, and serial numbers that match the encoded RFID data. This allows backup scanning with barcode readers and visual verification.

Data File Requirements

When providing data for variable encoding, please follow these guidelines:

✓ Do:

  • Use Excel (.xlsx) or CSV format
  • Include column headers
  • One row per tag/label
  • Include all required fields
  • Use consistent formatting
  • Verify data before sending

✗ Don't:

  • Use PDF or Word documents
  • Include merged cells
  • Leave blank rows in the middle
  • Mix data formats in one column
  • Include special characters
  • Send incomplete data

Tip: Not sure how to format your data? Send us a sample and we'll create a template for you to fill in.

Need Help with Encoding?

Tell us about your application. We'll help you define the right encoding specification and send a quote within 24 hours.

Request a Free Quote →

Or call: 800-537-5310