Sep 30, 2026Buying Guides
Mixed Noodle Pallets: Reconcile SSCC and ASN Before Dispatch
A shipment total can be correct while pallet contents are assigned to the wrong SSCC. Reconcile the physical load with the advance shipping notice before dispatch.
AI-generated editorial illustration of matching pallets to shipment records; not an actual shipment, logistics label or packing instruction.
If your receiving warehouse uses Serial Shipping Container Code (SSCC) pallet identification and an advance shipping notice, check the contents attached to each pallet identifier before dispatch. A correct total for the whole order can hide an incorrect allocation between pallets.
An SSCC identifies a logistics unit. The advance shipping notice, or ASN, communicates shipment information to the receiver. For the workflow discussed here, the critical connection is between that identifier and the actual goods on the corresponding pallet. It is not enough to know that all the ordered noodle cartons are somewhere in the container.
Confirm that this is the receiver's agreed process
First ask the warehouse whether it accepts the proposed mixed pallets and which shipment-data arrangement it requires. Do not impose a particular pallet or electronic-message design from another customer's manual.
The GS1 Logistic Label Guideline recommends linking each logistics unit's SSCC with its contained trade items in the despatch advice or ASN. It also recommends sending the notice during staging or loading so that it reflects the actual shipment, and processing it in the receiver's system before arrival.
Agree who records the final pallet contents, who creates the notice and who receives any corrections. This article does not establish that Noodle House or a particular warehouse already operates an EDI connection. Confirm the supported arrangement for the order.
The total can balance while the pallet records are wrong
The following is a hypothetical example using short working references, Pallet A and Pallet B. These are not valid SSCCs. Carton quantities are illustrative and do not represent a loading specification.
The order contains 12 cartons of egg noodles and 8 cartons of another dried wheat noodle SKU. The shipment total is 20 cartons.
Working pallet reference | Actual cartons on the pallet | Contents recorded in the notice |
|---|---|---|
Pallet A | 8 egg-noodle cartons + 2 dried-noodle cartons | 4 egg-noodle cartons + 6 dried-noodle cartons |
Pallet B | 4 egg-noodle cartons + 6 dried-noodle cartons | 8 egg-noodle cartons + 2 dried-noodle cartons |
Both columns total 12 egg-noodle cartons, 8 dried-noodle cartons and 20 cartons overall. A whole-order quantity check therefore passes. Each individual pallet record is still wrong.
The added check is to reconcile each physical pallet with the contents associated with its own real SSCC. Do not “correct” the case by changing the purchase-order quantities: in this example, the problem is the association between the load and its record.
Locate the mismatch before choosing the correction
Start from one affected pallet and its visible identifier. Compare the actual contents with the packing record and the notice intended for the receiver. Keep the unit of quantity explicit: carton counts should not silently become consumer-pack counts.
Then establish which element is wrong. Was the wrong existing label attached to the pallet? Was the pallet built differently from the plan? Or was the final packing record entered against the wrong identifier in the shipment data?
Ask the responsible packing and data owners to agree the correction. Do not invent a replacement SSCC simply to make a spreadsheet look consistent. If the pallet has been rebuilt, confirm the identification treatment with the responsible party under the applicable GS1 and receiver requirements.
Once corrected, check the physical identifier, contents record and latest notice together. Retain the superseded notice as history without leaving it in the receiver's active workflow.
Treat sending and acceptance as separate checkpoints
A sent file does not demonstrate that the warehouse has processed it against the expected delivery. Ask for the acknowledgement or other confirmation available in the agreed system, and identify who follows up if it is missing or reports a problem.
For a late change, confirm which correction process the warehouse expects and how it will distinguish the replacement information. Avoid sending several unlabeled attachments and assuming the last email wins. These are suggested coordination controls; the receiver's actual message rules and deadlines still govern the exchange.
A successful data reconciliation also does not prove that every carton is undamaged or that the goods are released for sale. Those checks remain part of the agreed receiving and quality process.
Keep this check separate from carton artwork
The carton-mark guide addresses the information printed for an order. The receiving checklist covers documenting what arrives. This pre-dispatch check closes a different gap: whether each pallet's shipment-data record describes the load attached to that identifier.
For a wholesale noodle order, send the proposed SKU mix and the receiving warehouse's instructions. Ask the parties to confirm who will prepare, transmit and reconcile pallet-level information before committing to that workflow.
Reference checked 30 September 2026: GS1 Logistic Label Guideline, Release 1.3, July 2019, sections 9.3.7 and 9.5.2. The numerical example and reconciliation sequence are practical illustrations, not a GS1 test protocol or an actual customer shipment.
