GenFrontier homeScope a project
Menu
Reader questionHow do we generate SSCCs and print GS1-128 pallet labels that scan at our customers' docks?

SSCC pallet labels: numbering, GS1-128 layout and ASN matching

How to allocate SSCC numbers in software, print a GS1-128 pallet label that passes verification, and tie each SSCC label to the ASN your customer receives.

field-notes / traceability-standards / sscc-pallet-labels
A homing pigeon standing on a weathered wooden ledge with a small red ring around one leg.

An SSCC pallet label scans at a customer’s dock when four things are right. The number is an 18-digit Serial Shipping Container Code built from your own GS1 Company Prefix, with a correct check digit, and it is not reused within at least a year of shipment. The barcode is a true GS1-128 symbol, with the FNC1 character after the start character, Application Identifier (00) in the lowest barcode on the label, and print quality that meets GS1’s grade for logistic units. And the label sits in the right place on the pallet, carrying the same SSCC your advance ship notice (ASN) lists with the pallet’s contents.

This note takes each of those in turn, with the rule from the GS1 General Specifications (Release 26.0, January 2026) or the GS1 Logistic Label Guideline (Release 1.3, July 2019), and the design decision it creates for your WMS, ERP or label software. Customer specifications can add to GS1’s rules, and a section near the end shows how one published specification differs.

What an SSCC identifies

The SSCC identifies one logistic unit: a pallet, a roll cage, a parcel or any other unit “established for transport and/or storage that needs to be managed through the supply chain.” GS1’s General Specifications say the SSCC “is the only GS1 key that SHALL be used as the identifier of a logistic unit,” and that a GTIN with a serial number “SHALL NOT replace the SSCC” in that role.

Three properties follow, and each one matters in software:

  • It lasts for the life of the unit. An SSCC “remains the same for the life of the logistic unit to which it is assigned.” If the pallet survives unchanged from your dock to the customer’s store, so does the number.
  • It is assigned by whoever builds the unit. “The physical builder of the logistic unit or the brand owner of the logistic unit is responsible for the allocation of the SSCC.”
  • It is unique, not meaningful. The GS1 Company Prefix in the SSCC “makes the SSCC unique worldwide but does not identify the origin of the unit.” Do not parse an SSCC to find out who shipped a pallet; look it up.

The SSCC is not a product code. The GTIN on the case says what is in the box; the SSCC on the pallet says which pallet this is. For example, a pallet of 60 identical cases has 60 case barcodes carrying the same GTIN, and one SSCC.

The 18 digits of an SSCC, after Application Identifier (00) (00) E P P P P P P P S S S S S S S S S C AI 1 digits 2 to 8 digits 9 to 17 18 Extension digit 0 to 9 GS1 Company Prefix (length varies with your license) Serial reference your sequence Check digit from digits 1 to 17 A 7-digit prefix is shown. A longer prefix leaves fewer serial reference digits.
Structure as defined in the GS1 General Specifications, Release 26.0, section 3.3.1; prefix length shown for illustration. Source: GS1, checked November 2026.

Calculating the check digit

The 18th digit is a check digit calculated from the first 17 with GS1’s standard algorithm, the same one used for GTINs and GLNs. The General Specifications say the check digit’s verification “must be carried out in the application software” and “ensures that the number is correctly composed.” Your label software should calculate it, and your receiving software should check it on every scan.

The algorithm, from section 7.9.1 of the General Specifications, for an 18-digit field:

  1. Take the 17 digits before the check digit.
  2. Multiply them, from the left, alternately by 3 and by 1 (the first digit by 3, the second by 1, and so on to the 17th by 3).
  3. Add up the results.
  4. Subtract the sum from the nearest equal or higher multiple of ten. The result is the check digit.

GS1’s own worked example (Table 7-9) uses the 17 digits 37610425002123456. The weighted products add up to 101. The next multiple of ten is 110, so the check digit is 9, and the full number is 376104250021234569.

Position 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Digit 3 7 6 1 0 4 2 5 0 0 2 1 2 3 4 5 6
Weight 3 1 3 1 3 1 3 1 3 1 3 1 3 1 3 1 3
Product 9 7 18 1 0 4 6 5 0 0 6 1 6 3 12 5 18

Two implementation notes. Store the SSCC as an 18-character string, not a number, because a leading zero in the extension digit is significant. And test the check digit routine with GS1’s example before go-live; an off-by-one in the weighting produces numbers that look valid to people and fail at the scanners that check them.

Allocating SSCCs in software

SSCC allocation is a sequence problem: every logistic unit you build needs a number that has not been used recently by anyone sharing your prefix. The rule from section 4.3.1.1 of the General Specifications is short: “an individual SSCC number must not be reallocated within one year of the shipment date from the SSCC assignor to a trading partner. However, prevailing regulatory or industry organisation specific requirements may extend this period.”

The Logistic Label Guideline adds two practical rules. SSCC numbers “should be generated out of the logistic management system, e.g. the warehouse management system (WMS) or ERP,” and “SSCCs that have been created should be archived for traceability purposes.”

How many numbers your prefix gives you

The 18 digits are fixed, so a longer GS1 Company Prefix leaves fewer digits for the serial reference. The extension digit multiplies the capacity by ten. The table is arithmetic on the structure above; your prefix length is set by the license from your GS1 Member Organisation.

GS1 Company Prefix length Serial reference digits SSCCs available (with extension digit 0 to 9)
6 digits 10 100 billion
7 digits 9 10 billion
8 digits 8 1 billion
9 digits 7 100 million
10 digits 6 10 million

Even the smallest row in the table allows ten million pallets per prefix. The harder problem is collisions: two printers, two sites or two systems drawing from the same range.

One sequence, many printers

Pick one source of truth for the next number, and make every label printer, handheld and system request numbers from it. A database sequence or a single allocation service works; a counter stored in each label template does not. If a site must print while disconnected, give it a reserved block of numbers in advance and record the block as allocated to that site.

The extension digit is a convenient way to separate sources, because the Logistic Label Guideline leaves its use “at the discretion of the company allocating the SSCC.” For example, suppose a company with three warehouses and one co-packer assigns extension digits 1, 2, 3 and 4 to them. Each then runs its own serial sequence without any chance of overlap.

Reprints, voids and the one-year rule

Every SSCC needs a status, and the status decides whether the number may ever come back:

Status Meaning Can the number be used again?
Allocated Drawn from the sequence, not yet printed Only for the same pallet
Printed A label exists Reprint for the same pallet only
Applied and loaded Scanned at the trailer No
Shipped Included in a sent ASN Not within at least one year of the ship date
Voided Printed but never shipped Treat as consumed; do not reissue

Voided labels deserve a firm rule. A printed label can end up on a pallet, in a photo or in a scan log you cannot see. Treating every printed number as consumed costs nothing when the range holds millions of numbers, and it removes a whole class of duplicate-SSCC disputes.

A damaged label on an unchanged pallet gets a reprint of the same SSCC. A new number for the same pallet would break the link to the ASN you already sent.

What the allocation service should do

Whether the numbers come from the WMS, the ERP or a small service beside them, write its behavior down as requirements before anyone builds it. A workable specification covers eight points:

  1. One request, one or more numbers. A caller (printer station, handheld, system job) asks for a quantity of SSCCs for a named site and receives complete 18-digit strings, check digits included.
  2. Atomic allocation. Two callers asking at the same moment never receive the same number, even across sites.
  3. Same pallet, same number. A request to reprint for an existing pallet returns the SSCC already issued to it, never a new one.
  4. Reserved blocks for offline printing, recorded as issued to that site the moment they are reserved.
  5. A log of every number: who asked, when, for which pallet, and every status change after that.
  6. Range monitoring. An alert when a site’s extension digit or block passes a set share of its capacity, long before it runs out.
  7. No recycling. If you ever wrap a range, the service refuses any number shipped within the reuse window, and your window is at least the one year GS1 requires plus any longer customer or industry rule.
  8. Retention. SSCC records kept at least as long as the reuse window and your own traceability record retention, whichever is longer.

Whose prefix goes on the label

Use your own GS1 Company Prefix. The Logistic Label Guideline warns that when a shipper uses a cloud service to generate labels, “SSCCs are usually generated from the IT solution provider’s GS1 Company Prefix. This may lead to weaker traceability and is an incorrect use of the GS1 standards.” Check this with any label service or 3PL before the first shipment.

When a 3PL builds pallets for a brand owner, both parties qualify under GS1’s responsibility rule: the SSCC is allocated by “the physical builder of the logistic unit or the brand owner.” Decide which, in writing, before go-live. If the 3PL uses the brand owner’s prefix, the brand owner should hand it a dedicated extension digit or serial block and receive the allocation log back. If the 3PL uses its own prefix, the brand owner’s systems must accept SSCCs that do not start with its own prefix, and its ASN process must get those numbers from the 3PL.

Example (fictional). A snack distributor, Westbrook Provisions, prints pallet labels at two warehouses from label templates that each keep their own counter. Both templates start at serial 000000001. For three months nobody notices, because the two warehouses ship to different customers. Then a regional retailer DC receives pallets from both on the same day, and its WMS rejects the second pallet with a duplicate SSCC. The fix in the requirements: a single SSCC service in the WMS, extension digit 1 for the first warehouse and 2 for the second, a status for every number, and a rule that a voided label is never reissued. The acceptance test prints 500 labels at each site in parallel and checks for duplicates.

When to keep an existing SSCC and when to assign a new one

You keep an SSCC as long as the logistic unit is the same unit, and you assign a new one when you build a new unit. The GS1 guidance gives clear answers for the common warehouse cases:

Situation Keep or new? GS1 basis
Full pallet received and shipped on unchanged Keep The SSCC “remains the same for the life of the logistic unit” (General Specifications 4.3.1.1)
Carrier adds or replaces a transport label segment Keep “When adding or replacing a segment an SSCC already present must never be replaced or changed” (Logistic Label Guideline 2.3)
Label damaged, pallet unchanged Keep (reprint) Same unit, same number
Pallet broken down and rebuilt, or picked into a new pallet New Consolidators “will remove the old pallet labels and replace them with new pallet labels” (Guideline 9.1)
Co-packer or warehouse service provider builds new pallets New, and keep the old-to-new link “Retain a record of the relationship between the stock in the old consignment and stock in the new consignment” (Guideline 9.1)
Stacked pallets shipped as separate units One SSCC per pallet Guideline rule 8-7
Stacked pallets joined by wrap or straps and shipped as one Each pallet keeps its SSCC, plus an additional SSCC for the group Guideline rule 8-8
Pallet received with no SSCC The next party may allocate one Guideline 3.2

When units are nested, such as parcels on a pallet, the General Specifications say only the barcode of the higher logistic unit “SHOULD be readable.” Inner labels should be covered or otherwise kept from being scanned at the dock.

Building the GS1-128 barcode

GS1-128 is a subset of Code 128, and the difference is one character. The General Specifications define a “special double character start pattern”: a start character (A, B or C) “immediately followed by a Function 1 Symbol Character Code (FNC1).” They state the consequence plainly: “a Code 128 symbol, which does not begin with this start pattern, is never a GS1-128 barcode.”

That one character is behind an error that is easy to miss. A label template built with a generic Code 128 field can print 00376104250021234569 as plain Code 128. It looks right to the eye, and a scanner reads the digits. But a receiving system that expects GS1 data cannot tell that the first two digits are an Application Identifier, so it rejects the pallet or reads the wrong field.

Rules that decide whether the data parses

From the GS1-128 sections of the General Specifications (5.4 and the verification checks in 5.12):

  • FNC1 in the first position after the start character, flagging the symbol as GS1.
  • No parentheses in the encoded data. The brackets around AIs appear in the human readable line only.
  • Separators after variable-length fields. An element string whose AI is not in GS1’s table of predefined lengths must be followed by FNC1 (transmitted as the <GS> control character, ASCII 29) unless it is the last one in the symbol. In GS1’s Application Identifier reference, batch/lot in AI (10) and count in AI (37) are variable length and need the separator; the SSCC in AI (00) is fixed at 18 digits.
  • Fixed-length fields first is the recommended order, so that fewer separators are needed.
  • Limits: no more than 48 data characters in one symbol, and no longer than 165.10 mm (6.5 inches) including quiet zones.
  • Start C for numeric data. Start C should be used when the data, including the AI, begins with four or more numeric characters, which every SSCC string does.

On compact labels the Logistic Label Guideline adds a restriction: “Concatenation shall not be used with SSCC on cartons and outer cases and on A6 / 4x6 labels.” On a 4 by 6 inch label, the SSCC gets a barcode of its own.

How to tell GS1-128 from Code 128 at your own dock

Scanners that support symbology identifiers can be set to transmit one in front of the data. The General Specifications list ]C1 as the identifier for GS1-128 element strings. Scan a test label with that setting on: if the output does not start with ]C1, the symbol is not GS1-128, whatever the label software calls it. A barcode verifier makes the same check, and more, as part of grading.

Symptom at the receiving dock Likely cause How to check before shipping
SSCC field rejected as invalid, digits look right Printed as Code 128 without FNC1 Scan with symbology identifiers on; expect ]C1
Data contains “(” or “)” Parentheses encoded in the symbol Verifier data analysis; parentheses belong only in the text line
Lot number runs into the next field Missing FNC1 separator after AI (10) Read the raw scan output and look for the separator
Wrong barcode scanned as the pallet ID SSCC not in the lowest barcode, or an inner label exposed Visual check against the layout rules below
Check digit error Wrong weighting in the label software Test with GS1’s example 376104250021234569

Testing a new label template

Every new or changed template deserves the same short test before it prints a production label:

  1. Print three labels with known data, including a lot number long enough to need a separator.
  2. Scan each barcode with symbology identifiers on and save the raw output. Confirm the ]C1 prefix, the AIs, the separator after each variable-length field and the absence of parentheses.
  3. Recalculate the SSCC check digit independently and compare.
  4. Compare every human readable line and data title with the encoded data.
  5. Grade the barcodes with a verifier against the logistic unit specification below.
  6. Apply one label to a loaded pallet and check its height and distance from the edge.
  7. Send a test ASN containing the same SSCC to the customer, where they offer a test process, and keep their response with the template’s version history.

What goes on the label and where

The SSCC is “the single mandatory element for all GS1 Logistic Labels,” and only the bottom building block, the barcodes with their human readable lines, is mandatory. Everything else is added because a trading partner needs it.

The General Specifications describe three building blocks, top to bottom: free-format text and graphics; text with data titles that repeats what the barcodes carry; and the barcodes with their human readable interpretation. Information can also be grouped into up to three segments, usually carrier at the top, then customer, then supplier. The rule that matters most for scanning is in section 6.6.4.1.1: “In all cases, the GS1-128 barcode encoding the SSCC SHALL be placed in the lowest portion of the label.”

A pallet label in three segments, SSCC at the bottom CARRIER SEGMENT SHIP TO POST 64114 Carrier routing text, if agreed CUSTOMER SEGMENT FROM: Westbrook Provisions TO: Example Retail DC 12 ORDER NUMBER PO-778201 SUPPLIER SEGMENT CONTENT 10012345000017 COUNT 60 BATCH/LOT WB26-0412 BEST BEFORE (YYMMDD) 270115 (02)10012345000017(37)60(15)270115(10)WB26-0412 (00) 0 0012345 000004127 0 SSCC: lowest barcode
Fictional label for illustration; barcodes are drawn schematically and the numbers are placeholders, not valid identifiers. Layout rules: GS1 General Specifications 6.6.3 and 6.6.4; content rules: GS1 Logistic Label Guideline section 4, checked November 2026.

Content rules for a pallet of one product

For a homogeneous pallet that is not itself a trade item, the Logistic Label Guideline’s example uses AI (02) for the GTIN of the contained cases and AI (37) for their count, with optional batch or lot in AI (10) and one date: production (11), packaging (13), best before (15) or expiry (17). Several rules trip up label templates:

  • AI (01) and AI (02) “must never be used together on a logistic label,” and AI (37) is not allowed with AI (01).
  • “Only one batch number can be put on a logistic label.” If a pallet holds cases from different lots, the Guideline says those batch numbers “cannot be shown on the label”; they belong in the ASN.
  • A mixed pallet carries no trade item data on the label at all. The Guideline says electronic messaging “is strongly encouraged” to carry the contents for such pallets.
  • Each AI may appear only once on a label.
  • Dates in barcodes use the YYMMDD format defined for each date AI.

Sizes and text

The Guideline names two common sizes: A6 (105 by 148 mm) or 4 by 6 inches, “particularly suitable when only the SSCC, or the SSCC and limited additional data, is encoded,” and A5 (148 by 210 mm) or 6 by 8 inches for pallet labels with trade item data. Human readable text under each barcode must be at least 3 mm high. Data content in the text block should be at least 7 mm high, and data titles must be in English unless the trading partners agree another language.

The current General Specifications (Release 26.0) allow a GS1 DataMatrix or GS1 QR Code on a logistic label “in addition to the GS1-128 symbol,” containing all of the GS1-128 data. The GS1-128 remains the mandatory carrier for the SSCC except on units too small for an A6 label. What 2D barcodes change on consumer units is covered in our note on GS1 Sunrise 2027 and 2D barcodes.

A label that one handheld can read may still fail the grade your customer’s fixed scanners need. GS1 sets the numbers in Symbol Specification Table 5, “logistic units scanned in general distribution,” in section 5.12.3.5 of the General Specifications:

Parameter (GS1-128 on logistic units) Requirement
X-dimension (narrowest bar) 0.495 mm minimum and target, 0.940 mm maximum
Minimum bar height 31.75 mm (1.25 inches), not counting the text line
Quiet zones At least 10 times the X-dimension, left and right
Minimum print quality 1.5/10/660 under the ISO/IEC 15416 method
Maximum length 165.10 mm (6.5 inches) including quiet zones

The quality specification has three parts: 1.5 is the minimum overall symbol grade, 10 is the measuring aperture reference, and 660 is the light wavelength in nanometres. Only a verifier built to ISO/IEC 15416 measures the grade; a scanner either reads the symbol or does not. Verify during implementation, and then on a schedule, as rule 9-13 of the Guideline recommends.

Quiet zones are easy to lose on a busy label. The General Specifications (5.4.6.3) grade each quiet zone on each scan line: at least 10 times the module width earns grade 4 (A), anything narrower earns grade 0 (F). Text, a box border or the label edge printed too close to the bars can therefore fail a symbol whose bars are perfect. Leave the quiet zones in the template as protected areas that no other field may enter.

Printing choices that protect the grade, from the Guideline’s implementation section:

  • Black bars on a white background.
  • Label stock and ink that match, and no heat-sensitive material that darkens in sun or heat.
  • Printers checked, serviced and calibrated regularly.
  • An X-dimension at the higher end of the range where conditions are hard; the Guideline notes “freezing can degrade print quality,” which matters for frozen and chilled food.

Placement

For all pallets, the General Specifications (6.7.1.1) say “all GS1 barcodes SHALL be positioned in a space between 400 millimetres (16 inches) and 800 millimetres (32 inches) from the base of the pallet,” and at least 50 mm (2 inches) from any vertical edge, including quiet zones. Pallets under 400 mm tall get their barcodes as high as possible. Bars must run in “picket fence” orientation, perpendicular to the base.

The Guideline recommends labeling two sides of each pallet with identical labels, so one is always visible whichever way the pallet is stored. It notes that labels placed to the right of each side suit right-handed forklift drivers. And it warns against labels wrinkled on application or obscured by stretch film.

Linking the label to the ASN

The SSCC is only useful at the customer’s dock if the customer’s system already knows what it means. The Logistic Label Guideline describes the sequence for the shipper:

  1. Scan only pallets that are actually loaded (rule 9-17), so the ship notice matches the trailer.
  2. Send the despatch advice or ASN “upon staging / loading of the goods” (rule 9-18).
  3. List “for each logistic unit the SSCC and the contained trade items” (rule 9-19).
  4. Make sure lot numbers, dates and other variable data “match the information of the actual goods present on the logistic unit” (rule 9-20).

On the receiving side, the Guideline says the ASN “should be received and processed into the receivers’ system before the goods arrive,” and when the SSCC is scanned “it should match the information in the Despatch Advice / ASN,” so the received quantity posts automatically. That automatic posting is the reason customers ask for SSCCs. In X12 EDI the ship notice is the 856 Ship Notice/Manifest, and our note on EDI 856 ASN structure covers how the pallet level of the hierarchy carries the SSCC.

The same link supports traceability. Walmart’s published Food Traceability KDE Requirements lists “SSCC-18” alongside the lot number and traceability lot code source in the data it expects by ASN or EPCIS. For suppliers of foods on FDA’s Food Traceability List, the pallet’s SSCC becomes the key that ties a physical pallet to its lot records; our note on FSMA 204 traceability lot codes covers that side.

On your own receiving dock

The same rules apply in reverse when your suppliers ship SSCC-labeled pallets to you. The Guideline’s receiving rules translate into WMS behavior:

  • Load the supplier’s ASN before the truck arrives (rule 9-34), so the SSCC scan can post the receipt.
  • Validate the check digit on every scanned SSCC, and flag any SSCC that is not on an open ASN.
  • Where you store full pallets as received, use the supplier’s SSCC as the pallet identifier rather than printing a second license plate. The Guideline’s role table says distribution centers storing stock “will use the pallet label’s SSCC as the identifier.”
  • Keep labels on until put-away is complete (rule 9-35), and store goods “preserving the SSCC relationship” where possible (rule 9-37).
  • Put the consequence of an ASN-less delivery in the supply contract; rule 9-33 says rejection of delivery without a despatch advice “should be included in the contract.”

Where receipts are matched to purchase orders before the truck arrives, the SSCC scan closes the loop at the door.

The data your system must keep

To build the ASN from scans rather than from the order, the WMS needs a record for each SSCC: its contents (GTIN, quantity, lot, dates), the order and shipment it belongs to, its status, and who printed it and when. That record is also what lets you answer a customer’s shortage claim with evidence: which pallets were scanned onto which trailer, and what each one held.

Example (fictional). A frozen foods supplier, Lakeline Foods, generates its 856 from the sales order at order release, two hours before loading. On a busy day, one pallet is swapped for another of the same item from a different lot, and a second pallet is left behind. The customer’s DC receives an ASN listing 22 SSCCs; 21 arrive, and one of them is not on the ASN. The receipt drops to manual, and the supplier gets a compliance deduction. The requirement that follows: the ASN is built from loading scans, the loading screen refuses a pallet whose SSCC is not on the shipment, and the 856 is sent only after the door is closed. The acceptance test loads a trailer with one swapped and one missing pallet and expects the ASN to reflect exactly what was scanned.

Customer label specifications and how they differ from GS1

GS1 sets the floor. Customers can, and do, publish their own requirements on top, and your label software has to hold one template per requirement set. One published example shows how far a specification can move from the GS1 baseline.

Dot Foods’ consignment pallet label example, read in November 2026, asks for:

  • A 4 by 6 inch label with ship-from and ship-to blocks marked as required, and the SSCC in GS1-128 symbology at the bottom.
  • The word “Consignment” on the label.
  • An SSCC that “must tie to EDI 943 Transfer Order information.” The X12 transaction set list names the 943 the Warehouse Stock Transfer Shipment Advice, not the 856 Ship Notice/Manifest.
  • Two labels: one on the front (40-inch side) and one on the adjacent 48-inch right side, on top of the stretch wrap.
  • Placement “6 to 10 inches from the top and 6 inches from either vertical edge.”

That last rule is measured from the top of the pallet, while GS1 measures from the base. For example, on a hypothetical 60-inch-tall pallet, 6 to 10 inches from the top is 50 to 54 inches from the base, well above GS1’s 32-inch upper limit. Neither is wrong; the customer’s rule governs shipments to that customer. The point for your system is that placement belongs in the customer-specific work instruction, printed on the pick ticket or shown on the handheld, not assumed from the GS1 default.

A short matrix keeps the differences manageable:

What to record per customer Why it matters
Label size and required fields Drives the template
Barcode content (SSCC only, or SSCC plus content AIs) Drives the data you must have at print time
Placement rule and number of labels Drives the work instruction
Message that must carry the SSCC (856, 943 or another) Drives the EDI map
When the message must be sent Drives the shipping workflow
Where the specification lives and its revision date Lets you notice when it changes

What to do next

Check each of the four failure points against your current labels and systems before your customers do.

  • Confirm that every site prints SSCCs from your own GS1 Company Prefix, and from one allocation source.
  • Give every SSCC a status, archive every number issued, and never reissue a printed number.
  • Test your check digit routine with GS1’s example 376104250021234569.
  • Scan a label from each template with symbology identifiers on, and confirm the ]C1 prefix.
  • Have a sample of labels graded with an ISO/IEC 15416 verifier against 1.5/10/660, including labels from frozen or chilled areas.
  • Measure label height on a loaded pallet and check placement against GS1 and each customer’s specification.
  • Build the ASN from loading scans, not from the order.
  • Keep a customer label matrix, with the date you last checked each specification.

For the scan workflow and label templates as a piece of work, see our barcode, RFID and labeling service; for how labeling fits into distributor operations as a whole, see wholesale distribution. On the receiving side, the same SSCC and ASN link is what makes inbound purchase order visibility possible. If your labels or ship notices are being rejected and you want the rules written down as testable requirements, tell us what your customers are reporting.

Working on this problem?

If this field note describes a process you need to fix or build software around, tell us about it. We start with your process, your systems and your deadline.