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
  • When to Use BYO Serials
  • Validation
  • Mint Flow
  • Related Docs
Minting

Bring-Your-Own Serials

Was this page helpful?
Previous

Minting Security

Next
Built with

Bring-Your-Own (BYO) Serials lets brands mint passports against serial numbers that are generated outside tieback — for example, serials issued by a factory MES, an existing ERP system, or a partner’s pre-printed inventory.

When to Use BYO Serials

ScenarioUse BYO Serials?
Brand has no existing unit identification schemeNo — let tieback generate serials
Brand has an existing serial scheme they want to preserveYes
Pre-printed labels with externally generated serials need to be activatedYes
Compliance regime mandates a specific serial formatYes

Validation

Submitted serials are validated before mint:

  • Format — characters and length must match the configured pattern
  • Uniqueness — serials must be unique within the brand’s namespace
  • Capacity — submission size must be within the per-batch ceiling defined by the active plan

Validation runs synchronously for small submissions and asynchronously for large submissions, with row-level error reporting.

Mint Flow

1

Submit serials

Upload the serial list (CSV or API) bound to the target product or batch.

2

Validate

The validator returns accepted serials, rejected serials, and the reason for each rejection.

3

Mint

Accepted serials are minted as the unit identifier for the resulting passports.

4

Issue carriers

Carrier outputs (QR codes, NFC payloads) are produced against the BYO serials and made available through the export pipeline.

Related Docs

  • Minting Overview
  • Minting Lifecycle
  • Carrier Output Profiles
  • Exports & Print Jobs