> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Carrier Output Profiles

> Vendor-compatible export presets that format CSV manifest headers, delimiters, and filenames for label printing, NFC encoding, and RFID software.

**tie*back***

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 **tie*back*** Support) may apply. If neither is set, **tie*back*** uses its **System Default** format.

## Supported Export Formats

Profiles apply to manifest-style exports only:

| Format                 | Description                                         |
| ---------------------- | --------------------------------------------------- |
| QR Print Manifest      | Resolver URL manifest for label printing software   |
| NFC Encoding Manifest  | Resolver URL manifest for NFC encoding pipelines    |
| RFID Encoding Manifest | Resolver URL manifest for RFID URL-in-tag pipelines |

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

## Day-One Profiles

**tie*back***

ships with profiles for common vendor ecosystems:

| Profile                 | Column Convention               | Use Case                                  |
| ----------------------- | ------------------------------- | ----------------------------------------- |
| Generic VDP (LF)        | `DATA`, `Serial`, `GTIN`        | Standard variable data printing (Unix)    |
| Generic VDP (CRLF)      | `DATA`, `Serial`, `GTIN`        | Standard variable data printing (Windows) |
| BarTender (BarcodeData) | `BarcodeData`, `Serial`, `GTIN` | Seagull BarTender                         |
| BarTender (DATA)        | `DATA`, `Serial`, `GTIN`        | Seagull BarTender (alternate)             |
| NiceLabel (QR)          | `QR`, `Serial`, `GTIN`          | Loftware NiceLabel                        |
| NiceLabel (DATA)        | `DATA`, `Serial`, `GTIN`        | Loftware NiceLabel (alternate)            |
| Zebra (DATA)            | `DATA`, `Serial`, `GTIN`        | Zebra ZDesigner                           |
| Zebra (BarcodeData)     | `BarcodeData`, `Serial`, `GTIN` | Zebra ZDesigner (alternate)               |
| NFC (ndef\_uri)         | `ndef_uri`, `Serial`, `GTIN`    | NFC NDEF URI record                       |
| NFC (uri)               | `uri`, `Serial`, `GTIN`         | NFC URI record                            |
| RFID (uri LF)           | `uri`, `Serial`, `GTIN`         | RFID URL-in-tag (Unix)                    |
| RFID (uri CRLF)         | `uri`, `Serial`, `GTIN`         | RFID 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 **tie*back*** profile.
4. Export and import directly, with 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 **tie*back*** 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.

## Related Docs

* [Minting Overview](/minting/overview)
* [Exports](/minting/exports-print-jobs)
* [GS1 Digital Link Contract](/product-module/gs-1-digital-link-contract)
* [Resolver & GS1 Digital Link](/product-module/resolver-gs-1-digital-link)