A carton label can scan cleanly and still identify the wrong carton. The printed number may be valid, yet another packing line has already used it. A reprint may create a new number for the same unit. A spreadsheet may remove its first zero before the advance shipping notice is sent.
GS1 SSCC allocation controls address those failures. They link each physical logistics unit to one controlled identifier. That link must survive printing, packing and dispatch. Barcode design is only one part of the task.
This guide explains the number and checks a worked example. It then builds a practical allocation record. It also covers multiple packing sites, label reprints and nested cartons and pallets. The examples use invented operational data. The sample digit pattern is for arithmetic only. It is not an assigned prefix. Do not use it on live shipping labels.
Separate the unit, its identifier and its barcode
The Serial Shipping Container Code, or SSCC, identifies one logistics unit. That unit may be a carton, parcel or pallet formed for transport or storage. Its contents may include one garment variant or a mix. GS1 Australia's SSCC guidance explains the unit's role and its connection to shipment information.
The identifier is the number. A barcode is a way to carry that number so equipment can read it. A label is the printed surface. It may carry the barcode, readable text and other shipping details.
Keep those three concepts clear in system discussions. Replacing a damaged piece of label stock does not necessarily create a new physical unit. Printing two labels for two sides of one pallet does not create two pallets.
The SSCC also differs from an item code or GTIN. Two cartons can contain the same trade item. Each carton still needs its own logistics-unit identity. The item describes what is packed. The SSCC identifies the particular unit carrying it.
Use the number as a lookup key. Maintain the garment quantities, sizes, colours and order links in the associated record. Do not expect a scanner to discover those facts from the SSCC's digits alone.
Confirm who may allocate the number
Begin with the company that controls the GS1 Company Prefix. Verify the prefix from its actual licence record. Do not copy a prefix from a customer label or assume that any familiar company number is suitable.
GS1 Sweden's creation guide explains the need for a company prefix and a controlled sequence. It also makes clear that the company must track the sequence numbers it uses. An online check-digit tool does not maintain that allocation history for the factory.
A brand may use several factories or logistics providers. Agree who may issue numbers before printing starts. Establish who owns the range, who can issue numbers and who retains the history. Give the service provider a clear instruction. Access to a logo or order file is not an allocation agreement.
Record the exact prefix length. It determines how much space remains for the serial reference. Do not hard-code a seven-digit prefix because a demonstration used seven digits.
Keep a named owner for prefix changes, site additions and system migration. Give the printing team an approved setup. Staff should not choose a prefix at the start of each shift.
Understand the 18-digit structure
An SSCC has four parts. These are the extension digit, GS1 Company Prefix, serial reference and final check digit. Together they contain exactly 18 numeric digits. GS1 US explains this structure and shows how prefix length affects number capacity.
The extension digit is one digit. The prefix has the length assigned to it. The serial reference fills the remaining space before the check digit. The extension digit and serial reference together provide room to issue distinct numbers.
The Application Identifier for an SSCC is 00. It tells a GS1 data parser what follows. It is separate from the 18-digit identifier. An element string can contain AI 00 followed by one SSCC. It then has twenty numeric data characters: two plus eighteen.
This distinction matters when a supplier asks for a “twenty-digit SSCC.” Clarify whether the requested field includes the AI. Do not add two digits to the underlying identifier. Establish the input field before calculating its check digit.
Store a clearly named SSCC field containing eighteen digits. If another interface needs AI plus SSCC, build that field by an explicit mapping. Keep the two formats from being mixed in the same column.
Work through a check digit from first principles
For this arithmetic example, use extension 0. Add the fictitious seven-digit prefix 1234567 and serial reference 000000321. Joining these fields gives seventeen digits before the check digit:
Body = 0 + 1234567 + 000000321 = 01234567000000321.
Here, the plus signs mean joining text fields. They do not mean numeric addition. The leading zero is part of the identifier and must remain in place.
The algorithm in GS1 General Specifications, section 7.9.1 uses alternating weights of three and one. Start at the rightmost digit of the seventeen-digit body with weight three. Move left, changing the weight each time.
The body has seventeen digits. Its first, third and other odd positions from the left thus also have weight three. The even positions have weight one. The sums for this example are easy to check in two groups.
Positions from the left | Digits in those positions | Sum of digits | Weight | Weighted result |
1, 3, 5, 7, 9, 11, 13, 15, 17 | 0, 2, 4, 6, 0, 0, 0, 3, 1 | 16 | 3 | 48 |
2, 4, 6, 8, 10, 12, 14, 16 | 1, 3, 5, 7, 0, 0, 0, 2 | 18 | 1 | 18 |
Total | 66 |
The next multiple of ten at or above 66 is 70. The check digit is 70 minus 66, which is four. Append that digit to the body.
Complete example = 012345670000003214.
A compact rule is to choose the digit that makes the weighted total a multiple of ten. If the total already ends in zero, the check digit is zero. It is not ten, because the final field has only one digit.
GS1 Ireland's calculator asks for seventeen digits when completing an SSCC. Use the SSCC section and the correct input length when making an independent check. Do not include AI 00 in the number submitted for that calculation.
Know what a valid check digit cannot prove
The example passes the arithmetic test because 66 plus four equals 70. That proves only that this digit string satisfies the calculation. It does not prove that the prefix is licensed to the user or that the number has never been allocated.
It also does not prove that the label is on the right carton. Copying one valid number onto a second carton leaves both labels with the same valid check digit. The problem lies in identity assignment.
The calculation cannot detect every possible data change. Take two digits that carry the same weight. Swapping them leaves their weighted sum unchanged. A checksum is only one check. Also compare the full value with its source record.
A useful release check asks three separate questions. Does the number have the right structure? Was this number allocated to this unit? Does the applied label contain that exact number?
Calculate capacity without inventing a new prefix
Let p be the number of digits in the licensed company prefix. Two of the eighteen positions hold the extension and check digits. The other sixteen hold the prefix and serial reference. The serial reference therefore has 16 minus p digits.
With the example's seven-digit prefix, the serial reference has nine digits. With a nine-digit prefix, it has seven. This is a length calculation; it does not grant permission to use a prefix.
Assume all ten extension digits are available. Then the theoretical number of combinations is ten times the serial-reference combinations. The seven-digit-prefix case gives ten times one billion, or ten billion. The nine-digit case gives ten times ten million, or one hundred million.
Those results agree with GS1 US's capacity examples. A local implementation may reserve ranges or use only one extension digit. Its available pool may therefore be smaller than the theoretical total.
Do not solve an approaching range limit by extending the SSCC beyond eighteen digits. Check the remaining capacity and approved issue method. Resolve any needed prefix arrangements before the range runs out.
Prevent collisions across packing lines and sites
Suppose two packing lines each keep a local spreadsheet. Both read 000000321 as the last serial used. Both use the same extension and prefix. Each then issues 000000322 for a different carton. The result is a collision even though both calculations are correct.
One practical design uses a shared allocator. It reserves a number before returning it to a packing station. The reservation and the next available value must update as one protected operation. Two requests should not receive the same assignment.
Another design assigns non-overlapping ranges to sites. In that case, record each site's bounds and prevent local issue beyond them. The central owner must know which ranges have been issued, reserved or retired.
These are implementation choices, not a claim that GS1 requires one software architecture. The required outcome is controlled uniqueness. Test it with simultaneous requests, interrupted printing and delayed retries.
A station may reserve a number and then lose its connection. It should recover that assignment. Blindly requesting another number can create an unexplained unused record. Reusing the old number for a different carton can create a more serious duplicate.
Keep an allocation register separate from the print queue
The allocation register states which number belongs to which physical unit. The print queue records attempts to produce labels. One allocation may have several print attempts, including a controlled replacement.
Record the full SSCC, unit type and site. Add the packing record, allocation time and current status. Add the shipment reference when it becomes known. Record who requested a reprint and why.
A print job marked successful does not prove that its label was applied. Staff may remove a jammed sheet, mix two label stacks or discard a damaged label. Record the step that links the printed identifier to the actual unit.
Keep reserved but unused numbers visible. Do not quietly recycle them during a shift to make the sequence look continuous. A gap can have a clear reason. A duplicate identity is harder to repair after goods leave the site.
Protect the register during migrations. Carry forward used values, reserved ranges and relevant shipment dates. Starting a new system's counter at one can repeat numbers issued by the old system.
Count physical identities rather than printed labels
Consider an original packing example with thirty cartons, grouped ten per pallet. The process assigns an SSCC to each carton and to each of the three pallet units. That requires thirty-three distinct identifiers.
Assume the local label design prints one label per carton and two labels per pallet. It produces thirty carton labels plus six pallet labels, or thirty-six labels. The two labels on a given pallet must carry the same pallet SSCC.
Object or output | Count | Distinct SSCCs in this example |
Cartons | 30 | 30 |
Pallet units | 3 | 3 |
Printed labels | 36 | 33 |
The two-label choice is an example, not a universal instruction for every unit. Apply the actual placement and partner requirements. The point is that label quantity and identity quantity serve different purposes.
Suppose two carton labels are damaged before dispatch. Two replacement prints raise the number of labels to thirty-eight. The original thirty-three physical identities remain. Reprinting should not automatically issue two new SSCCs.
Reconcile allocation, printing and physical packing by their own counts. Thirty-eight print events can be correct for thirty-three active units. The five extra copies must have an explained purpose.

Handle reprints and rebuilt units differently
A damaged label may be on an unchanged unit. In that case, preserve the identity in a controlled replacement. Check the SSCC against the unit's record before applying the replacement. Remove or obscure an obsolete or unreadable duplicate where it could cause confusion.
The GS1 Logistic Label Guideline says that adding or replacing a label segment must preserve an SSCC already present. A carrier's new routing segment should not silently create a new identity for an unchanged pallet.
A different case arises when a unit is broken down and its goods are repacked into new units. GS1 US's SSCC introduction calls for a new SSCC for the new logistics unit. Preserve links from the old unit to the new ones.
Write both cases into the procedure. “Print again” and “create new unit” should not be one ambiguous command. Staff need to know which task they are doing. Are they replacing a label? Or are they changing the physical grouping that it identifies?
Keep the reason and time of any new assignment. Later staff can then explain the change. They can see why the old SSCC no longer identifies the dispatched unit.
Control carton and pallet relationships
In the thirty-carton example, each carton record points to one of the three pallet SSCCs. Keep those relationships with the packing event. A pallet scan can then retrieve the known children.
GS1 General Specifications describe nested logistics units and the links between parent and child identifiers. They also address unintended reads. A scanner meant to read a pallet should not accidentally read one of its cartons. The operating procedure should make the intended level clear.
Test what happens when a carton moves to a different pallet before dispatch. Remove the old relationship and record the new one through the supported process. A physical move without a record change leaves the old pallet's contents wrong.
Do not add carton and pallet quantities together when they describe the same goods. The parent relationship organizes the units; it does not create extra shirts. Likewise, one pallet scan is not proof that staff checked each child's contents.
Encode AI 00 and the barcode correctly
For the arithmetic example, the readable representation may show (00) followed by 012345670000003214. The parentheses identify the AI to a person. GS1's bracket guidance states that those brackets are not encoded as barcode data.
Do not create an ordinary Code 128 image of the printed text and assume that it is GS1-128. GS1's format guidance explains the FNC1 character that follows the start character. It allows reading systems to recognize the GS1 structure.
The barcode also has its own symbol check character. That is distinct from the SSCC's final numeric check digit. Use software that supports the required GS1 encoding. Adding visible punctuation cannot imitate that structure.
Current GS1 General Specifications identify GS1-128 as the normal required carrier for this logistics application. They also allow specified 2D alternatives or additions under stated conditions. Confirm the actual application rule and partner scanning support before changing the carrier.
Give the raw identifier its own field in the label template. Keep it separate from the text shown to a person. This helps stop parentheses, spaces or duplicated AIs from entering the wrong interface field.
Check the generator's input contract
Barcode software does not always expect the same input. One tool may accept the body and calculate the last digit. Another may expect the full identifier. A field named “SSCC” does not resolve that difference.
For example, DevExpress's SSCC generator documentation describes a seventeen-digit input. It pads shorter values. It also removes the last digit when given an eighteen-digit input. Those are product behaviors, not general GS1 rules.
Record the software version, expected input and resulting decoded value. Validate the body length before calling a generator that can pad values. Otherwise, a missing digit may go unnoticed. The result can look like a complete barcode.
Keep test examples with leading zeros. Include a deliberate wrong check digit and a wrong-length value. Confirm which errors the application rejects and which it changes automatically.
Do not validate only the text printed below the symbol. Decode the symbol and compare it with the approved value. A template could print the right text while encoding a different field.
Verify the printed label under real conditions
A successful scan at one desk does not establish full barcode quality. GS1 New Zealand explains that a symbol may scan despite data or technical faults. Different scanners can respond differently to those faults.
Review the actual production label, printer settings and packaging surface. Check that bars, spaces and readable text remain clear. Keep the required clear areas around the symbol free of borders, tape and other printing.
Qualify the design and print process through formal verification. Use the specification that applies to the label. Keep the report with the approved template and settings. A screenshot of the design cannot establish the quality of a physical print.
Also test the operational route. Scan an applied label and retrieve its unit record. Compare the displayed contents with the packing record. This checks whether the good symbol points to the correct information.
Check changes to stock, ribbon, printer or layout. Does the accepted evidence still apply? A visually similar label can behave differently after a production change.
Set a defensible retention and reuse rule
GS1 Australia's guidance states that an SSCC remains with its logistics unit for that unit's life. The rule uses the shipment date from the assignor to a trading partner. Do not reassign the SSCC within one year of that date. Industry or regulatory requirements may extend that period.
Notice the starting event: shipment, not the day someone printed a test label. A local policy should preserve the date needed to apply the rule. Additional partner or traceability needs may call for a longer retention period.
Do not treat the first anniversary as an instruction to recycle a number. Check the applicable conditions, remaining unit life and record needs. A continuing sequence can be simpler when enough capacity exists.
Retain retired identities in searchable history. Deleting them to shorten a list can remove needed evidence. That history may explain an old shipment or a later return.
Troubleshoot by finding the failed layer
When a label fails, find the problem layer. Check number allocation, encoded data, print quality and record lookup. These failures can look similar at the dock but need different fixes.
A duplicate SSCC needs an allocation investigation. Reprinting both cartons more clearly will not remove the collision. A wrong carton link needs a controlled identity correction. This applies even when the number itself is valid.
A scan that returns no record may reflect a missing or late data link. A label that cannot be decoded may reflect its symbol or print conditions. Capture the actual scanner result first. Then decide whether to change the barcode or receiving data.
For leading-zero loss, inspect each handoff as text. Compare the source identifier, export field, imported value and decoded symbol. Locate the first point where the value changes.
Use ApparelDiary's ERP factory checklist for the wider system pilot. Follow the SSCC through every handoff in this test. Confirm that it still refers to the same unit.
Two packed cartons may have the same SSCC. Stop both from leaving while the team resolves the error. Identify each carton from its packing evidence. Decide which assignment is valid. Correct the other through the approved route. Update the affected shipment data before release. Keep the old values in the incident record so a later scan can be explained. Check any notice already sent to the receiver. It must not still describe two cartons as one identity after the label fix.
Release labels with a usable evidence trail
Before first live use, approve the prefix configuration and allocation method. Verify an example independently. Test concurrent issue, failed printing, reprint and repacking. Include a migration or counter-reset test if that risk exists.
Then qualify the printed output and its data path. Trace an applied label back to its allocation. Then find the linked packing record and shipment message. Record the template and software versions used.
Use ApparelDiary's export packing-list guide to control declared contents and export documents. The SSCC process supplies the stable unit identity that those records can reference.
Keep care-label approval separate too. Care-label validation concerns the garment's supported care instruction. A logistics barcode's acceptance cannot approve that instruction or the garment's quality.
Frequently asked questions
Is an SSCC eighteen or twenty digits?
The identifier has eighteen digits. AI 00 adds two data characters when it precedes the SSCC in a GS1 element string. State which field an interface expects.
Can two labels carry the same SSCC?
Yes. Both must identify the same physical logistics unit under the approved placement scheme. They must not be used to give different units one shared identity.
Does a correct check digit prove uniqueness?
No. It verifies a mathematical relationship among digits. Allocation history and unit assignment are separate controls.
Does a new carrier label require a new SSCC?
Replacing routing information on an unchanged unit should preserve its SSCC. Rebuilding goods into new logistics units is a different event. Follow the applicable process for those new units.
Keep identity stable from packing to receipt
A reliable SSCC process joins a valid number to a real unit. It then preserves that relationship. The check digit supports data validation. The allocator prevents duplicate issue. The print process creates a readable carrier, and the packing record gives the identifier meaning.
Test each link with evidence from an actual unit. The number, physical grouping and associated record should agree. Downstream teams can then use the identifier with a clear view of what it refers to.
Carton labels must match the packing record, so see the export packing list reconciliation and carton blank consumption.
References
GS1 Australia — Serial Shipping Container Code.
GS1 US — Serialized Shipping Container Codes.
GS1 — General Specifications, release 26.0.
GS1 Ireland — Check Digit Calculator.
GS1 — Logistic Label Guideline, release 1.3.
GS1 US — An Introduction to the Serial Shipping Container Code.
GS1 GO — Are brackets present in the GS1-128 barcode?
GS1 GO — What is the format of GS1-128?
DevExpress — Serial Shipping Container Code generator.
GS1 New Zealand — Why can a barcode scan yet fail verification?




Discussion0
Loading the discussion…