← 部落格← Blog

導入實務Implementation

產線序號化：從噴印到裝箱的實務考量Serialization on the production line: from printing to packing

序號化（serialization）是讓每一件產品在產線上被賦予並標示一個獨一無二的代碼。它是追溯能力的起點：沒有可靠的單品識別，後續的召回、流向查詢與防偽都會打折扣。這篇文章從實務角度，談噴印標示、掃描驗證，以及單品到外箱、棧板的階層彙整，並介紹 GS1 標準裡的關鍵概念。Serialization means assigning and marking a unique code on each unit as it moves down the line. It is the foundation of traceability: without reliable unit-level identity, recall, track-and-trace and anti-counterfeiting all become weaker. This article looks at the practical side — marking, scan-to-confirm verification, and aggregating units into cases and pallets — and introduces the key concepts from the GS1 standard.

為什麼要在產線上做序號化Why serialize at the line

批號（lot/batch）告訴你「這一批」是什麼時候、用哪些原料做的；序號則進一步告訴你「這一件」是哪一件。當你需要精準縮小召回範圍、回答通路或主管機關「這件貨從哪來、去了哪」的提問，或是讓消費者掃碼確認真偽時，單品層級的識別就是關鍵。對食品、保健與部分受規範的品類而言，能對應到 TFDA 等主管機關的追溯追蹤要求，更是基本門檻。A lot or batch number tells you when a group of products was made and from which materials. A serial number goes one step further and identifies the individual item. When you need to narrow a recall precisely, answer a channel partner's or regulator's question about where a specific item came from and where it went, or let a consumer scan to verify authenticity, unit-level identity is what makes it possible. For food, health products and certain regulated categories, being able to meet the track-and-trace expectations of authorities such as the TFDA is a baseline requirement.

序號化做得扎實，後面的數位追溯才有意義。反過來說，如果產線標示不穩、掃描讀不到、彙整對不起來，再好的後端系統也只是把錯誤資料整理得很整齊而已。Solid serialization is what makes downstream digital traceability meaningful. The reverse is also true: if marking is unreliable, scans fail to read, or aggregation does not line up, even the best back-end system simply organises bad data neatly.

標示與噴印：選擇與權衡Marking and printing: options and trade-offs

把代碼放到產品上有幾種常見做法，各有適用情境。最常見的是直接在包裝或標籤上印製人眼可讀文字加上條碼或 QR Code；也可以採用直接在產品或外殼上做標記（雷射或噴印），或是貼上預先印好的標籤。選擇時通常要權衡材質與表面、產線速度、單位成本，以及最重要的——可讀性與耐久性。There are a few common ways to put a code onto a product, each suited to different situations. The most common is printing human-readable text plus a barcode or QR code on the packaging or label. You can also mark the product or housing directly (for example by laser or inkjet), or apply a pre-printed label. The choice usually balances substrate and surface, line speed, unit cost, and most importantly readability and durability.

無論用哪種設備，幾個原則放諸四海皆準：對比要足夠、留白（quiet zone）要留夠、條碼尺寸要符合掃描距離與設備能力。GS1 對符號的最低品質等級與尺寸有明確規範，產線送出去之前最好用驗證式掃描器確認等級，而不是等到通路退貨才發現讀不到。Whatever equipment you use, a few principles hold everywhere: enough contrast, an adequate quiet zone around the symbol, and a symbol size that suits the intended scan distance and scanner capability. GS1 specifies minimum quality grades and sizes for symbols, so it is worth confirming the grade with a verifying scanner before product leaves the line — rather than discovering an unreadable code when a channel partner sends it back.

代碼放哪、怎麼確認讀得到Code placement and scan-to-confirm

位置選擇看似小事，卻常常決定成敗。代碼要放在不會被折邊、封膜、收縮膜或下游貼標蓋住的地方，也要避開高反光或弧度太大的表面。一致的位置還有一個好處：下游的掃描站與通路的讀取流程都能標準化，不用每個品項各自摸索。Placement looks like a small detail but often decides success. Put the code where it will not be covered by a fold, seal, shrink film or a downstream label, and avoid highly reflective or sharply curved surfaces. Consistent placement has another benefit: downstream scan points and your channel partners' read processes can be standardised instead of being figured out item by item.

標示之後，最好緊接著做「掃描確認」——也就是在產線上即時讀回剛印上的代碼，確認它確實可讀、內容正確、而且尚未被使用過。這一步能把瑕疵品在離開產線前就攔下來，避免重複序號或漏號流到市場。把標示與驗讀放在同一個工序裡，是序號化最值得投資的環節之一。Right after marking, it pays to add a scan-to-confirm step — reading the code back on the line in real time to verify that it is genuinely readable, correct, and not already used. This catches defective marks before they leave the line and prevents duplicate or missing serials from reaching the market. Pairing marking with read-back in the same operation is one of the highest-value investments in serialization.

• 可讀性：等級是否達標、是否有破損或墨點。Readability: does it meet the required grade, free of voids or smears.
• 正確性：印上的代碼是否就是系統指派的那一個。Correctness: is the printed code exactly the one the system assigned.
• 唯一性：這個序號是否從未在別處出現過。Uniqueness: has this serial never appeared anywhere else.

從單品到外箱、棧板：階層彙整與 SSCCFrom unit to case to pallet: aggregation and SSCC

單品序號只是第一層。實務上商品會裝成外箱、外箱再疊成棧板，因此需要把「哪些單品在哪個外箱、哪些外箱在哪個棧板」的關係記錄下來——這就是彙整（aggregation）。有了彙整關係，出貨時只要掃一個棧板或外箱代碼，就能推知裡面所有單品，不必逐件拆掃；發生問題要回溯時，也能順著層級一路展開。The unit serial is only the first level. In practice items are packed into cases, and cases are stacked onto pallets, so you need to record which units are in which case and which cases are on which pallet — this is aggregation. With those relationships captured, shipping can scan a single pallet or case code and infer everything inside, instead of scanning every unit; and when something goes wrong, you can unwind the hierarchy level by level.

在 GS1 標準裡，物流單位（外箱、棧板這類運送與儲存單位）是用 SSCC（Serial Shipping Container Code，序號化貨運容器代碼）來識別的。SSCC 是一個全球唯一的代碼，用來指認一個特定的物流單位；它通常承載在 GS1-128 條碼上，搭配對應的應用識別碼（Application Identifier）使用。單品端則多以 GTIN 搭配批號、有效日期與序號等資訊來描述。把這些標準化的識別串起來，彙整關係才有共通語言，跨公司、跨系統交換時不會各說各話。In the GS1 standard, logistics units — shipping and storage units such as cases and pallets — are identified with an SSCC (Serial Shipping Container Code). An SSCC is a globally unique code that names a specific logistics unit; it is typically carried on a GS1-128 barcode together with the relevant Application Identifiers. At the unit level, items are usually described with a GTIN plus information such as batch, expiry and serial. Tying these standardised identifiers together gives aggregation a shared language, so that exchanges across companies and systems do not talk past each other.

產線速度與不良品處理：要先想清楚的事Line speed and reject handling: plan for these first

序號化必須跟得上產線節奏。導入前先量好實際的每分鐘產量，確認標示、驗讀與資料記錄都能在節拍時間內完成，不會成為瓶頸。也要想清楚異常情境：讀不到的代碼怎麼補印或剔除？序號要怎麼作廢、會不會被回收再用？掃描站故障時產線要停還是進入降級模式？這些規則最好在設計階段就定好，而不是現場臨時決定。Serialization has to keep up with the line. Before rollout, measure your real throughput per minute and confirm that marking, read-back and data logging all fit within the cycle time without becoming a bottleneck. Think through the exceptions too: how do you reprint or reject an unreadable code? How is a serial voided, and can it ever be reused? If a scan point fails, does the line stop or run in a degraded mode? These rules are best decided at the design stage rather than improvised on the floor.

不良品與重工尤其要小心。被剔除的單品、拆箱重裝的外箱，其序號與彙整關係都必須同步更新，否則系統裡的數量會和現場對不上。建立清楚的作廢與重新彙整流程，並讓現場人員容易操作，是維持資料可信度的關鍵。一個好的追溯平台，應該讓這些例外處理變簡單、留下完整紀錄，而不是逼現場用紙筆另記一份。Rejects and rework deserve special care. When a unit is removed or a case is opened and repacked, its serial and aggregation relationships must be updated in step, or the quantities in the system will no longer match the floor. Clear void-and-re-aggregate procedures, easy for operators to follow, are what keep the data trustworthy. A good traceability platform should make these exceptions simple and fully logged — not force the floor to keep a separate record on paper.

選擇平台時，與其問「它內部怎麼運作」，不如看它是否貼合上述實務：能否與你既有的噴印標示設備和 ERP 對接、是否原生支援 GTIN、SSCC 與 GS1 應用識別碼、能否清楚呈現單品到棧板的彙整、以及例外處理是否好用。把這些對齊好，序號化才會是助力而不是負擔。When choosing a platform, rather than asking how it works inside, look at whether it fits the practices above: can it connect to your existing marking equipment and ERP, does it natively support GTIN, SSCC and GS1 Application Identifiers, can it clearly show aggregation from unit to pallet, and is exception handling easy to use. Get those aligned, and serialization becomes an asset rather than a burden.