PCBA Packaging, ESD and Transit Protection: The PO Requirements Buyers Forget

Your purchase order probably runs to several pages. Stackup, impedance targets, surface finish, solder paste alloy, test coverage, inspection criteria, first-article release. All of it written down, all of it arguable against a document if something goes wrong.

Then the boards pass final inspection, and the paperwork stops.

Nothing in the PO says what the assemblies are sealed in. Nothing says whether moisture-sensitive parts get a desiccant and an indicator card. Nothing says how many boards share a bag, whether two production lots can share a carton, or what has to be printed on the outside of that carton. Nothing says what you are entitled to photograph and claim if the pallet arrives crushed.

This is the single widest gap in PCBA contract manufacturing documents, and it only becomes visible after the shipment lands. By then the question is no longer technical. It is a question about who owes whom, and the answer depends entirely on what was written before the boards shipped. If the PO is silent, the default answer is that the supplier packed it "per standard practice" — their standard, defined after the fact, and usually adequate, right up until the one shipment where it is not.

Why the gap exists

Three things combine to create it.

Packaging is assumed to be the supplier's trade. Buyers specify what they consider engineering content and treat packing as logistics overhead. But packing a populated assembly is engineering content: it involves electrostatic discharge paths, moisture ingress into plastic-bodied components, resonance and abrasion during road transit, and lot traceability. None of that is a shipping clerk's decision.

The failure mode is delayed and ambiguous. A board damaged by electrostatic discharge in transit does not arrive visibly broken. It arrives, passes a quick visual check, gets installed, and fails in the field weeks later. By then the causal chain back to a bag that was not actually dissipative is unprovable. Latent damage with a long fuse never generates the feedback that would have prompted someone to write the requirement.

Incoterms get mistaken for a packaging specification. Agreeing on delivery terms allocates freight cost and the point at which risk transfers. It says nothing about whether the goods were adequately prepared for the journey. A supplier can meet their delivery obligation perfectly and still have packed the boards in a way that guaranteed damage. Those are separate questions governed by separate clauses, and only one of them is usually in your document.

The receiving-dock problem, stated precisely

When a damaged or degraded shipment arrives, you need three things to make a claim stick: a criterion that says what acceptable condition means, evidence captured before the goods were disturbed, and a responsible party identified by the contract rather than by argument.

A typical PO gives you none of the three. The criterion does not exist because packaging was never specified. The evidence does not exist because nobody told the receiving team to photograph a sealed carton before opening it. The responsible party is undetermined because the freight forwarder points at the packer, the packer points at the carrier, and your own receiving process cannot distinguish between them.

Everything below is aimed at installing those three things in advance.

The six requirement classes

Treat these as six separate clauses, not one "packaging shall be adequate" sentence. Each one has a different failure mode, a different owner, and a different form of evidence.

1. Electrostatic protection: level and materials

State the protection class you require and require the supplier to name the actual materials used.

What to put in the PO:

• Whether assemblies must be enclosed in a shielding barrier (a Faraday-type enclosure that attenuates external fields) or whether dissipative/antistatic material is sufficient. These are not interchangeable terms and buyers routinely accept the cheaper one while believing they bought the other.
• Whether the shielding bag must be the primary enclosure directly containing the assembly, or whether an inner dissipative liner plus outer shielding bag is acceptable.
• A requirement that all cushioning, trays, dividers and tape in contact with the assembly be ESD-safe, not just the outer bag. A shielding bag stuffed with ordinary bubble wrap is a common and self-defeating configuration.
• A requirement that the supplier declare the material type and the standard it is qualified against in the shipping documents, so your incoming inspection can verify what it is rather than assume.
• Whether bags must be sealed, and by what method.

Why it matters: the bag is the only part of the protection scheme your receiving team can actually inspect. If you did not specify what it has to be, you cannot reject it for being the wrong thing.

2. Moisture-sensitive devices: drying, barrier and labelling

Populated assemblies containing moisture-sensitive plastic packages can absorb enough ambient moisture to be damaged by later rework reflow. If you will rework, repair, or reflow anything after receipt, this class is not optional.

What to put in the PO:

• A requirement that the supplier identify which devices on the BOM are moisture-sensitive and state their sensitivity level, derived from the component manufacturer's own data rather than invented.
• Whether assemblies must ship in a moisture barrier bag with desiccant and a humidity indicator card.
• A requirement that the bag carry a label stating the sensitivity level, the bag seal date, and the permitted exposure window after opening.
• The agreed handling rule after the seal is broken: what exposure duration is permitted, and what the recovery bake requirement is if that window is exceeded. Set these values jointly with the supplier against the component manufacturers' published data — do not accept an unexplained number, and do not invent one yourself.
• Who bears the cost of recovery baking if the bag arrives already breached or the indicator card has tripped.

Why it matters: this is the clearest example of a defect you cannot see. An assembly that absorbed moisture looks identical to one that did not, until something delaminates during a rework cycle months later.

3. Mechanical restraint and stacking

What to put in the PO:

• A requirement that assemblies be individually separated so that no board's components can contact another board. Face-to-face stacking of populated assemblies with only a thin interleaf is a frequent source of bent leads, cracked passives, and scraped connectors.
• Restraint requirements for tall, heavy, or cantilevered components — large electrolytics, inductors, shielded modules, heatsinks, connectors overhanging a board edge. These act as levers on their own joints under transit vibration.
• Whether trays or custom fixtures are required rather than loose bagging, and who owns and pays for them if so. Note that this overlaps with tooling and NRE ownership, which is worth settling in the same conversation.
• Void-fill requirements so contents cannot shift inside the carton, and a rule that cushioning must not be in direct compressive contact with component bodies.
• Maximum stack height or weight on the carton, and a requirement that this limit be printed on the carton rather than merely agreed in email.
• Whether palletisation, strapping, edge protection or stretch wrap is required for the shipment size in question.

Why it matters: this is the one class where the damage is visible on arrival. That makes it the easiest to claim on — provided a criterion existed.

4. Quantity per container and lot-mixing rules

This is the class buyers forget most completely, and the one that does the most downstream damage to traceability.

What to put in the PO:

• A fixed quantity per bag and per carton, or an explicit statement that quantities may vary with a count declared on each label.
• Whether a single bag or carton may contain more than one production lot or date code. If mixing is permitted, require that every lot present be listed on the label.
• Whether partial cartons are acceptable and how they must be marked.
• A rule for rework and repaired units: must they be segregated and identified, or may they be mixed into normal stock?
• Whether units from different alternate-part approvals may share a container. If you approved a second-source part for part of the build, mixing approved variants into one unmarked carton destroys your ability to isolate a population later.

Why it matters: your entire upstream traceability chain — material lot records, alternate part approvals, first-article release — terminates at the packaging label. If the label does not carry lot identity forward, a field problem cannot be bounded to a population, and you end up treating every unit you ever received as suspect.

5. External marking and traceability data

What to put in the PO:

• The required fields on every carton and bag label: your part number and revision, the supplier's reference, PO number, lot or batch identifier, quantity, and date.
• The format: human-readable plus machine-readable, and which barcode or 2D symbology your receiving system can actually scan. Specify this, or you will receive a symbology you cannot read.
• Required handling and condition markings: ESD-sensitive symbol, moisture-sensitive labelling, orientation, stacking limit, and any fragility marking.
• A requirement that the packing list reconcile to the carton labels — same lot identifiers, same quantities, same revision — so a discrepancy is detectable at the dock rather than at the assembly line.
• Whether a certificate of conformity or lot traceability record must accompany the shipment or be transmitted in advance.

Why it matters: a label is the cheapest control in the whole chain and the one that determines whether every other record stays connected to physical goods.

6. Receiving inspection and evidence preservation

The first five classes define what the supplier owes. This one defines what you must do to be able to enforce them.

What to put in the PO and in your own receiving procedure:

• A defined inspection-on-arrival step that happens before cartons are opened: photograph the pallet as delivered, the carton exterior, any crush or puncture, any tilt or impact indicator, and the labels.
• A rule that suspect shipments are not opened or dispersed until documented, and not mixed into inventory.
• A requirement to check and record humidity indicator card status and bag seal integrity at opening for moisture-sensitive shipments.
• The notification window for reporting packaging-attributable damage, and the required form of that notice.
• The disposition path: who decides between accept, bake and accept, sort, return, or scrap; who pays for sorting; and how replacement units are expedited.
• A requirement that the supplier retain packaging records — materials used, seal dates, label images or data — for an agreed period, so a late-emerging problem can still be investigated.

Why it matters: an unenforced right is indistinguishable from no right. Most packaging claims fail not because the contract was silent but because the goods were unpacked, mixed, and installed before anyone documented their condition.

Where packaging requirements belong in the document set

Buyers often try to put all of this in the PO body and find it does not fit. A cleaner split:

• Quality agreement or supply agreement — the durable rules: ESD protection class, moisture-sensitive handling policy, lot-mixing policy, label field list, record retention, notification windows, disposition and cost responsibility. These do not change per order.
• Packaging specification, referenced by the PO — the physical detail: bag type, tray or fixture drawing, quantity per container, carton size and stacking limit, label artwork and symbology. Maintain this as a revision-controlled document so a change is visible rather than silent.
• The PO itself — quantity, the specification revision it invokes, destination, delivery terms, and anything order-specific such as a split shipment or a special pallet requirement.

The point of the split is that the PO should reference a revision, not restate the content. If packaging rules live only in scattered email, there is no revision to point at when a shipment deviates.

Settle this during the RFQ, not after the first shipment

Every item above has a cost. Shielding bags cost more than antistatic ones. Moisture barrier bags with desiccant and indicator cards cost more again. Custom trays carry a tooling charge. Individual bagging costs labour per unit. Smaller cartons with a lower stacking limit cost more to ship.

If you introduce these requirements after the quote is accepted, you are asking for a price change, and you will either pay it or get a negotiation. If you put them in the RFQ, they are priced into the comparison and every supplier is quoting the same scope. That is also the only way the quotes are genuinely comparable — a supplier who assumed bulk bagging will underbid one who assumed individual shielding bags and trays, and nothing on the quote sheet will reveal why.

Two practical RFQ additions:

1. Attach the packaging specification as part of the RFQ package, alongside the Gerber, BOM, CPL and assembly drawing.
2. Ask each supplier to quote packaging as a visible line item or declare it included, and to state any deviation from your specification in writing. A supplier who intends to deviate will usually say so when asked directly and almost never volunteer it otherwise.

Buyer self-check

Run this against your current PCBA documents before the next order:

• [ ] Does any document state the required ESD protection class, and does it distinguish shielding from dissipative material?
• [ ] Are inner cushioning, trays and tape covered by the ESD requirement, or only the outer bag?
• [ ] Has the supplier identified which BOM devices are moisture-sensitive and declared their sensitivity levels?
• [ ] Is moisture barrier packaging with desiccant and an indicator card required where applicable, and is the post-opening exposure and recovery rule written down and jointly agreed?
• [ ] Are assemblies required to be separated so components cannot contact an adjacent board?
• [ ] Are tall, heavy or overhanging components specifically restrained, and is trays-versus-bagging decided along with who owns the tooling?
• [ ] Is a stacking or weight limit specified, and is it printed on the carton?
• [ ] Is quantity per bag and per carton fixed, or at least declared on the label?
• [ ] Is lot mixing within a container permitted, prohibited, or simply unaddressed?
• [ ] Are rework units and alternate-part variants required to be segregated and marked?
• [ ] Is the label field list specified, including a machine-readable format your system can scan?
• [ ] Must the packing list reconcile to carton labels on lot identifier, quantity and revision?
• [ ] Does your receiving procedure require photographs of sealed cartons before opening?
• [ ] Is there a notification window and a defined disposition and cost-responsibility path?
• [ ] Must the supplier retain packaging records, and for how long?
• [ ] Was packaging scope included in the RFQ so that competing quotes covered the same work?

Any unchecked box is a position you will have to argue from scratch on the day a shipment arrives wrong.

What to ask a supplier before you commit

• Which standards do you work to for electrostatic protection and moisture-sensitive handling, and can you name the bag and cushioning materials you intend to use for our assemblies?
• Who in your organisation owns the packaging decision, and is it documented per part number or decided per shipment?
• What is your default quantity per bag and per carton for an assembly like ours, and do you mix lots?
• What goes on your standard carton label today, and in what barcode format?
• Can you work to our packaging specification as attached, and where would you need to deviate?
• If a shipment is damaged in transit, what evidence do you require from us, and what is your process and timeline for replacement?
• How long do you retain packaging and lot records?

None of these require the supplier to make a capability claim they cannot support. They ask what the current practice is and whether it can be bound to a document. A supplier who can answer all seven in writing is one whose packaging will probably have been fine anyway — but now you have the clause.

FAQ

Do I really need to specify packaging if the supplier has never shipped me a damaged board?

A clean history tells you the supplier's default practice has been adequate for your product and your lanes so far. It does not tell you the practice is documented, that it will survive a change of packer, shift, subcontractor or freight route, or that latent electrostatic and moisture damage has not been occurring undetected. Writing it down costs one document revision and converts a habit into an obligation.

Is an antistatic bag the same as a shielding bag?

No, and the distinction is the most common quiet substitution in PCBA shipments. A dissipative or antistatic bag limits charge generation and allows charge to bleed away, but does not meaningfully attenuate an external electrostatic field reaching the contents. A shielding bag provides a conductive enclosure that does. If your assemblies need field attenuation, you must say "shielding" and require the material type to be declared, because both products are pink or silver plastic to a receiving clerk.

Our boards get installed immediately and never reworked. Can I skip the moisture requirements?

Largely yes, and this is a legitimate way to avoid paying for protection you do not need. The moisture-sensitivity concern is specifically about absorbed moisture causing damage during a later high-temperature excursion. If nothing you do after receipt reflows the assembly, that exposure is not in your process. Confirm it honestly though: field repair, depanelling with a thermal step, conformal coating cure, and selective soldering of later-fitted parts all count, and so does long-term warehouse storage before a future rework.

Why does quantity per carton matter if the total quantity is correct?

Because the carton is the unit your traceability and your inventory both operate on. An undeclared variable quantity means every receipt needs a full manual count to reconcile, and an unmarked mixed-lot carton means that when a field failure traces to one material lot, you cannot tell which received stock contains it. The total being right solves the commercial question and leaves the quality question open.

Should the packaging specification sit in the PO or somewhere else?

Keep the durable policy in a quality or supply agreement, keep the physical detail in a revision-controlled packaging specification, and have the PO reference the specification by revision. Restating detail in each PO guarantees drift between orders and gives you nothing to point at when a shipment deviates.

The shipment arrived crushed. What do I actually need to make a claim?

Three things, and you need them before the goods are disturbed: a written criterion defining acceptable delivered condition, photographic evidence of the pallet and sealed cartons as delivered including labels and any impact indicators, and a contractual route that identifies who is responsible and within what notification window. Opening and dispersing the cartons first destroys the second item, which in practice is how most otherwise valid claims are lost.

Does agreeing delivery terms cover packaging?

No. Delivery terms allocate freight cost and define where risk of loss transfers. They are silent on whether the goods were adequately prepared for transit. A supplier can satisfy their delivery obligation and still have packed the assemblies in a way that made damage likely. Treat packaging adequacy as a separate clause with its own criterion.

How do I introduce these requirements to an existing supplier mid-programme?

Send the packaging specification as a change request, ask for a price impact and a lead-time impact if any, and agree an effective date tied to a specific PO or lot rather than "going forward". Expect some cost where you are genuinely adding protection, and expect none where you are documenting what they already do. Handling it as a visible, priced change is what keeps it from being quietly ignored.

Related links

• PCB Assembly and Contract Manufacturing
• PCBA First Article Inspection Report and Release Terms
• PCBA Test and Inspection Requirement Definition in the RFQ
• Turnkey PCBA BOM Risk and Alternate Part Approval
• PCB Assembly Contract Manufacturing: Supplier Scope
• PCBA Quote Comparison and Scope Boundaries
• Request a Quote
• Contact