<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Types on Manage.ID Documentation</title><link>/masterdata/data-types/</link><description>Recent content in Data Types on Manage.ID Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="/masterdata/data-types/index.xml" rel="self" type="application/rss+xml"/><item><title>Product</title><link>/masterdata/data-types/product/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/masterdata/data-types/product/</guid><description>&lt;h3 id="what-is-this-data"&gt;What is this data&lt;a class="td-heading-self-link" href="#what-is-this-data" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A product is identified by the combination of its &lt;strong&gt;product code&lt;/strong&gt; and &lt;strong&gt;product variant&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;h3 id="where-it-is-used"&gt;Where it is used&lt;a class="td-heading-self-link" href="#where-it-is-used" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;During production, the &lt;strong&gt;Select product&lt;/strong&gt; coding-scenario step matches a scanned or imported input value against this master data to identify the correct product and load its data — including any linked Various Data — into the scenario, so it can be used to fill in the label. See &lt;a href="/coding-scenarios/overview-steps-of-a-coding-scenario/production-data/"&gt;Production Data&lt;/a&gt; for the related coding scenario steps, and &lt;a href="/production_lines/preparing-production-on-a-production-line/"&gt;Preparing Production on a Production Line&lt;/a&gt; for how a product is assigned to a line.&lt;/p&gt;</description></item><item><title>Production Order</title><link>/masterdata/data-types/production-order/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/masterdata/data-types/production-order/</guid><description>&lt;h3 id="what-is-this-data"&gt;What is this data&lt;a class="td-heading-self-link" href="#what-is-this-data" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A production order represents a specific production run or batch of one product — it carries run-specific attributes such as batch number, quantity, and production/expiry dates, in addition to a link to the product being produced.&lt;/p&gt;&#10;&lt;h3 id="where-it-is-used"&gt;Where it is used&lt;a class="td-heading-self-link" href="#where-it-is-used" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;The &lt;strong&gt;Select production order&lt;/strong&gt; coding-scenario step identifies the order matching the current input and loads it, its linked product, and any linked Various Data into the scenario. See &lt;a href="/coding-scenarios/overview-steps-of-a-coding-scenario/production-data/"&gt;Production Data&lt;/a&gt; for the related coding scenario steps, and &lt;a href="/production_lines/preparing-production-on-a-production-line/"&gt;Preparing Production on a Production Line&lt;/a&gt; for how an order is assigned to a line.&lt;/p&gt;</description></item><item><title>Various Data</title><link>/masterdata/data-types/various-data/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/masterdata/data-types/various-data/</guid><description>&lt;h3 id="what-is-this-data"&gt;What is this data&lt;a class="td-heading-self-link" href="#what-is-this-data" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;Various Data is a generic key/value lookup table used to attach extra attributes to a product beyond its own fixed fields — for example translations, certificates, or additional reference data pulled from an external system. It has no relation of its own to Production Order, Logistic Unit, or any other table — only Product links to it.&lt;/p&gt;&#10;&lt;h3 id="where-it-is-used"&gt;Where it is used&lt;a class="td-heading-self-link" href="#where-it-is-used" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A link configured between a product column and Various Data means that whenever the &lt;strong&gt;Select product&lt;/strong&gt; coding-scenario step resolves a product, the matching Various Data row is automatically pulled in alongside it and made available for use on the label. A &lt;strong&gt;Select production order&lt;/strong&gt; step gets there too, but only transitively — via the order&amp;rsquo;s linked product, not a link of the order&amp;rsquo;s own (see &lt;a href="/masterdata/data-types/production-order/"&gt;Production Order&lt;/a&gt;). See &lt;a href="/coding-scenarios/overview-steps-of-a-coding-scenario/production-data/"&gt;Production Data&lt;/a&gt; for the related coding scenario steps.&lt;/p&gt;</description></item><item><title>Logistic Unit</title><link>/masterdata/data-types/logistic-unit/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/masterdata/data-types/logistic-unit/</guid><description>&lt;p&gt;&lt;em&gt;Available only when the Logistic Units feature is enabled.&lt;/em&gt;&lt;/p&gt;&#10;&lt;h3 id="what-is-this-data"&gt;What is this data&lt;a class="td-heading-self-link" href="#what-is-this-data" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A logistic unit represents a physical packaging unit — a pallet, carton, or case — tracked by a unique identifier. It can be linked to a product and/or production order, and carries a lifecycle status (for example packed, shipped, or blocked). The default pattern used when creating a logistic unit from scanned or printed ZPL data (&lt;code&gt;(?&amp;lt;=\(00\))\d{18}&lt;/code&gt;) extracts a GS1 SSCC — an 18-digit Serial Shipping Container Code following the GS1 application identifier &lt;code&gt;(00)&lt;/code&gt; — confirming that a logistic unit is the serialized, trackable packaging level in the labeling process.&lt;/p&gt;</description></item><item><title>Print Job</title><link>/masterdata/data-types/print-job/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/masterdata/data-types/print-job/</guid><description>&lt;h3 id="what-is-this-data"&gt;What is this data&lt;a class="td-heading-self-link" href="#what-is-this-data" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A print job is the unit of work sent to a printer.&lt;/p&gt;&#10;&lt;h3 id="where-it-is-used"&gt;Where it is used&lt;a class="td-heading-self-link" href="#where-it-is-used" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A print job is normally created by a coding scenario&amp;rsquo;s &lt;strong&gt;Send print job to printer&lt;/strong&gt;/&lt;strong&gt;Send print job to all&lt;/strong&gt; step, but an external system (an ERP or WMS, for example) can also create one directly by importing print job data or calling the print-job API. Both paths fire an event that a coding scenario can react to — the &lt;strong&gt;On print jobs import&lt;/strong&gt; and &lt;strong&gt;On print jobs API request&lt;/strong&gt; trigger steps let a scenario automatically start printing as soon as a print job arrives, with no operator scan required. See &lt;a href="/coding-scenarios/overview-steps-of-a-coding-scenario/send-print-jobs/"&gt;Send Print Job(s)&lt;/a&gt; and &lt;a href="/coding-scenarios/overview-steps-of-a-coding-scenario/event/"&gt;Event&lt;/a&gt; for the related coding scenario steps.&lt;/p&gt;</description></item><item><title>Custom Columns</title><link>/masterdata/data-types/custom-columns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/masterdata/data-types/custom-columns/</guid><description>&lt;h3 id="before-you-begin"&gt;Before you begin&lt;a class="td-heading-self-link" href="#before-you-begin" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;ul&gt;&#10;&lt;li&gt;You are assigned to a user group that has the &lt;strong&gt;Manage data columns&lt;/strong&gt; permission — this is required both to add a new column and to rename one.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="what-this-is"&gt;What this is&lt;a class="td-heading-self-link" href="#what-this-is" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;Beyond the fixed fields documented on each data type&amp;rsquo;s page, every master data table — Product, Production Order, Various Data, Logistic Unit, and Print Job — can be extended with custom columns to track whatever else your company needs. Each table has its own fixed capacity and per-value character limit; see that data type&amp;rsquo;s &lt;strong&gt;Custom / additional columns&lt;/strong&gt; section for the specifics.&lt;/p&gt;</description></item></channel></rss>