For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Getting Started
    • Introduction
    • Getting Started
    • Tia — Operations Assistant
    • Architecture
    • Security Architecture
  • Onboarding & Plans
    • Onboarding Overview
    • Plans & Subscriptions
    • Tia Credits
  • Tenancy & Governance
    • Roles & Members
    • Audit Log
    • Notifications
    • Economic Operators
  • Authoring Studios
    • Content Studio
    • Theme Studio
    • Advanced Studio (Track B)
  • Product Module
    • Products
    • Custom Fields
    • Global Search
    • Identifiers
    • Product Import
    • Bulk Editing
    • Bulk Updates
    • Resolver & GS1 Digital Link
    • GS1 Digital Link Contract
  • Localisations
    • Overview
    • Market Packs
    • Multilingual Content
  • Domains & Custom Hostnames
    • Domain Architecture
    • Resolver Domain Flow
    • Custom Hostname Setup
    • DNS Setup Guide
    • Resolver & Passport Rendering
    • Custom Hostname Lifecycle
    • Troubleshooting
  • Passports
    • Overview
    • Passport Operations
    • Lifecycle States
    • Controlled Update & Break-Glass
    • Content & Templates
    • Themes & Presentation
    • Consumer Experience
    • Publication Lifecycle
    • Brand Setup & Readiness
    • Drafts
  • Passport Intelligence
    • Passport Intelligence
    • Intelligence Overview
    • Scan Visibility
    • Trust Signals
    • Engagement Insights
    • Investigation Timelines
    • Data & Privacy
    • Roadmap
  • Minting
    • Overview
    • Lifecycle
    • Architecture
    • Limits & Performance
    • Token Preview
    • Exports & Print Jobs
    • Carrier Output Profiles
    • Bring-Your-Own Serials
    • Security
    • FAQ
  • API Reference
    • API Credentials Guide
    • API: Credentials
    • API: Products
    • API: Identifiers
    • API: Import
    • API: Batches
    • API: Attachments
    • API: Bulk Updates
    • API: Minting
    • API: Resolver
    • API: Search
On this page
  • Overview
  • Default Profiles
  • Supported Export Formats
  • Day-One Profiles
  • Profile Lifecycle
  • Vendor Compatibility Guide
  • How to Request a New Profile
Minting

Carrier Output Profiles

Was this page helpful?
Previous

Bring-Your-Own Serials

Next
Built with

tieback

supports Carrier Output Profiles — vendor-compatible export formatting presets that ensure your CSV manifests are ready for direct import into label printing, NFC encoding, and RFID programming software.

Overview

When exporting token data (QR Print Manifest, NFC Encoding Manifest, or RFID Encoding Manifest), you can select an Output Profile to automatically format column headers, delimiters, and filenames to match your downstream software’s requirements.

Profiles are strictly scoped by ecosystem:

  • Print/VDP profiles (BarTender, NiceLabel, Zebra, Generic VDP) are only available for QR Print Manifest exports.
  • NFC profiles are only available for NFC Encoding Manifest exports.
  • RFID profiles are only available for RFID Encoding Manifest exports.

Default Profiles

Brands can configure default output profiles for each ecosystem in Settings → Minting. When exporting, the default profile is applied automatically unless you explicitly choose a different profile at export time.

If no brand default is set, a global system default (managed by tieback Support) may apply. If neither is set, tieback uses its System Default format.

Supported Export Formats

Profiles apply to manifest-style exports only:

FormatDescription
QR Print ManifestResolver URL manifest for label printing software
NFC Encoding ManifestResolver URL manifest for NFC encoding pipelines
RFID Encoding ManifestResolver URL manifest for RFID URL-in-tag pipelines

The Full Manifest (12-column audit export) always uses the System Default format.

Day-One Profiles

tieback

ships with profiles for common vendor ecosystems:

ProfileColumn ConventionUse Case
Generic VDP (LF)DATA, Serial, GTINStandard variable data printing (Unix)
Generic VDP (CRLF)DATA, Serial, GTINStandard variable data printing (Windows)
BarTender (BarcodeData)BarcodeData, Serial, GTINSeagull BarTender
BarTender (DATA)DATA, Serial, GTINSeagull BarTender (alternate)
NiceLabel (QR)QR, Serial, GTINLoftware NiceLabel
NiceLabel (DATA)DATA, Serial, GTINLoftware NiceLabel (alternate)
Zebra (DATA)DATA, Serial, GTINZebra ZDesigner
Zebra (BarcodeData)BarcodeData, Serial, GTINZebra ZDesigner (alternate)
NFC (ndef_uri)ndef_uri, Serial, GTINNFC NDEF URI record
NFC (uri)uri, Serial, GTINNFC URI record
RFID (uri LF)uri, Serial, GTINRFID URL-in-tag (Unix)
RFID (uri CRLF)uri, Serial, GTINRFID URL-in-tag (Windows)

Profile Lifecycle

Each profile follows a governed lifecycle:

  1. Draft — Editable schema definition. Not available for exports.
  2. Published — Active and selectable. Only one published version per profile at a time.
  3. Deprecated — No longer selectable for new exports. Historical exports remain downloadable.

Publishing a new version automatically supersedes the previous published version.

Vendor Compatibility Guide

To determine which profile to use:

  1. Open your label/encoding software and check its CSV import documentation.
  2. Identify the expected column header for the barcode/URL data field (e.g., BarcodeData, DATA, QR, uri).
  3. Select the matching tieback profile.
  4. Export and import directly — no manual column renaming required.

How to Request a New Profile

If your software requires a column layout not covered by the day-one profiles, contact tieback Support with:

  • Software name and version
  • Expected CSV column headers
  • Delimiter preference (comma, semicolon, or tab)
  • Line ending preference (LF or CRLF)

Our team will create and publish a custom profile for your workflow.