HDI PCB Tooling and NRE Charges: Who Owns What You Paid For on the Reorder

The first HDI order goes fine. You pay the unit price, you pay a tooling or NRE line that sits beside it, you get boards, they work. Three months later you place the same part number again and the quotation comes back with a tooling line on it a second time. Sometimes it is reduced. Sometimes it is not. Nobody in the thread can point to a document that says which it should be.

That conversation is not a pricing dispute. It is the consequence of a contract that charged you for deliverables it never named.

The reorder invoice is where an unnamed charge gets re-argued

A tooling or NRE line on a first HDI quotation is almost always a single number with a single word next to it. "Tooling." "NRE." "Engineering charge." One line, one figure, no breakdown.

That single line is in fact paying for a bundle. The bundle usually includes drill programs and routing programs generated from your data, an electrical test fixture or test program, a panelisation and array layout decision, the engineering records that confirm how the microvia structure and impedance requirements will be built, and the first-article setup work that proves the process window on your specific build. These are separate artefacts. They have separate lifespans. They respond differently to a revision change, and they behave differently when you move the job somewhere else.

When they are invoiced as one word, none of that structure is visible. And an invisible structure cannot be waived selectively, because there is nothing to point at. The reorder conversation therefore starts from zero every time, and whoever has more leverage that month wins it.

What "tooling" and "NRE" actually bundle on an HDI job

Before you can negotiate a waiver you need the itemised list. Ask the supplier to break the charge into named deliverables, and ask what event makes each one stop being valid.

Drill and route programs. Machine data derived from your drill and outline files. On an HDI build this is not one program: via spans that start and end on different layers are drilled in separate operations, and the program set reflects that. These are generated once per fabrication revision and typically survive an unchanged reorder.

Panelisation and array layout. The decision about how your part is arranged on the production panel, including spacing, tooling strips and fiducials. This is derived from your part outline plus the supplier's panel format. It survives a reorder of the same part, but it does not necessarily survive a quantity change large enough to justify a different array, and it does not transfer to a supplier whose panel format differs.

Electrical test fixture or test program. For a fixtured test this is physical hardware built to your netlist; for flying probe it is a program. Hardware has a storage location and a physical lifespan; a program has a revision. Both are tied to the netlist, which means both are invalidated by a netlist change even when the change looks cosmetic to you.

Microvia and impedance build confirmation. The engineering records in which the supplier declares how stacked or staggered microvia spans will be formed, which layers are sequentially laminated, and how an impedance requirement will be met within the stackup. This is the output of engineering review time, not of a machine. It is the item most often paid for and least often named.

First-article setup and process window proof. The work of running your build once and confirming the result against the acceptance criteria. This is consumed on the first order and does not exist as a transferable artefact, which is exactly why it is the hardest part of the charge to argue about later.

Stencil or assembly programming, if the order is turnkey. Separate from fabrication tooling, with its own ownership question. Keep it on a separate line so that a fabrication-only reorder does not inherit an assembly charge.

Paying for a deliverable is not the same as owning it

This is the distinction that most RFQs never make, and it is the one that decides the outcome.

There are at least three positions a supplier can hold on any item in the list above, and all three are commercially normal:

• You own it. You paid for it, it is yours, and you can require it to be released to you or to a nominated third party. This is the position buyers assume by default and the one least often written down.
• The supplier owns it, and your payment bought the right to have it used on your orders. The artefact stays with the supplier. You get continuity as long as you keep ordering there. You cannot take it with you.
• The supplier owns it and your payment was amortised into the first order's price. There is nothing to transfer because the charge recovered a cost rather than purchasing an asset.

None of these is unreasonable. What is unreasonable is leaving it unstated, because then the question only gets answered at the moment you want to leave — by the party you want to leave.

Note also that ownership of a supplier-generated program is not the same as ownership of your design data. Your Gerber, ODB++, netlist and drawings are yours throughout. A drill program derived from them is a different artefact, and a supplier may reasonably treat their derivation work and machine-specific formatting as their own. Ask which of the two you are buying.

Three scenarios, three different waiver logics

"Can the tooling be waived?" is not one question. It is three, and they have different answers. Ask the supplier to fill in a matrix like this at RFQ stage, before the first order, while the answer is still cheap to obtain.

Two things are worth reading off that table rather than from a supplier's sales language.

First, "revised build" is not a single state either. A change confined to silkscreen does not touch the same deliverables as a change to a microvia span. The matrix is only useful if the contract ties re-charge to *which deliverable the change invalidates*, not to the existence of a revision. Otherwise any revision, however trivial, reopens the whole charge.

Second, transfer is mostly a documentation question, not an asset question. Very little of an HDI tooling package is physically portable. What you can realistically take with you is the record layer: the frozen revision, the declared microvia spans, the stackup as built, the impedance construction that was accepted, the exceptions the first supplier raised, and the inspection results. That package is what keeps a second supplier from re-deriving your build from scratch. Secure the right to receive it, in a usable format, as part of the first order.

Validity and storage: the clause that quietly expires

A waiver on an identical reorder is usually conditional on the deliverable still existing. Fixtures occupy space. Programs sit on a machine or in an archive. Suppliers retire both.

So the waiver clause needs a validity statement, and the validity statement needs three parts: how long the artefact is retained, what notice you get before it is retired, and what happens to the charge if you reorder after retirement. Without the notice obligation, the first two are not useful to you — you find out the fixture is gone at the moment you are trying to place an urgent repeat.

Ask for retention to be expressed as a period from the last shipment rather than from the first order. A part you reorder annually should not fall out of validity because the clock started on the day of the original PO.

What to ask at RFQ stage, not at reorder stage

Every item below costs you one line in an email before the first order. After the first order, each of them costs a negotiation.

• Break the tooling/NRE charge into named deliverables, with a figure against each.
• State for each deliverable whether the buyer owns it, has use rights to it, or is paying an amortised cost.
• State which deliverables are waived on an identical reorder, and what makes a reorder "identical" — same fabrication revision, same netlist, same array, same order profile.
• State what triggers a partial re-charge on a revised build, mapped to the deliverable the change invalidates rather than to the revision itself.
• State the retention period for fixtures and programs, measured from last shipment, and the notice obligation before retirement.
• State what records will be released to the buyer on request, in what format, and whether release is conditional on anything.
• Keep fabrication tooling and assembly programming on separate lines.

Clause language you can put in the PO

Adapt rather than copy; the point is that each clause names a deliverable and an event, so there is something to point at later.

> Itemisation. Supplier shall itemise all non-recurring charges by deliverable: drill and route programs, panelisation/array layout, electrical test fixture or test program, microvia and impedance build confirmation records, first-article setup, and assembly programming where applicable. A single aggregated "tooling" line is not accepted.

> Ownership. For each itemised deliverable, Supplier shall state in writing whether (a) ownership passes to Buyer on payment, (b) Buyer holds use rights for Buyer's orders only, or (c) the charge represents amortised cost with no transferable asset. Absent a statement, (b) applies.

> Reorder waiver. Non-recurring charges shall not be re-applied on a reorder of the same part at the same fabrication revision, same netlist and same array format, provided the relevant deliverables remain within the retention period in clause [x].

> Revision re-charge. Where a revision invalidates a specific deliverable, re-charge shall be limited to that deliverable. Supplier shall identify the invalidated deliverables in writing before the revised order is confirmed.

> Retention and notice. Supplier shall retain test fixtures and machine programs for [period] from the date of last shipment, and shall give Buyer [notice period] written notice before retiring or disposing of any retained item.

> Record release. On Buyer's written request, Supplier shall release to Buyer or Buyer's nominee the frozen fabrication revision index, declared microvia span table, as-built stackup, accepted impedance construction, declared exceptions and inspection records for shipped lots, in a readable electronic format.

Buyer self-check before the first HDI order

• [ ] Is the tooling/NRE charge itemised by deliverable, or is it one word?
• [ ] For each item, do you know whether you own it, rent it, or are amortising it?
• [ ] Is "identical reorder" defined by revision, netlist and array — not by part number alone?
• [ ] Is revision re-charge tied to the invalidated deliverable rather than to any revision?
• [ ] Is there a retention period measured from last shipment?
• [ ] Is there a notice obligation before a fixture or program is retired?
• [ ] Do you have a written right to receive the record package you would need at a second supplier?
• [ ] Is assembly programming separated from fabrication tooling?

Related reading

• HDI PCB quote package checklist — what to submit so that the baseline these deliverables attach to is frozen in the first place.
• HDI PCB cost drivers and quote optimisation — the recurring unit-price side, separate from the one-off charges discussed here.
• HDI PCB prototype and low-volume quote expectations — why small quantities make the NRE share visible.
• HDI build class specification and decision ownership — who decides the structure that the build confirmation records describe.
• HDI panel utilisation and array format — why the array decision is both a cost item and a transfer obstacle.
• Repeat order change control terms — the change-control side of keeping a reorder genuinely identical.
• HDI PCB capability overview and submit an RFQ — to declare the build and request an itemised charge breakdown.

---

FAQ

Is a tooling charge on a reorder always wrong?

No. It is wrong only when the deliverables it covers are still valid and still being used. If the fixture was retired, the array changed, or the netlist moved, a charge is legitimate. The problem is not the charge, it is not being able to tell which case you are in.

We paid the NRE. Doesn't that mean the tooling is ours?

Not automatically. Payment can purchase an asset, or purchase use rights, or recover an amortised cost. All three are normal commercial positions. Which one applies is whatever the contract says, and if the contract says nothing you are usually in the use-rights case by default.

Can we take the tooling to a second supplier?

Most of it, no. Drill programs and panelisation are machine- and panel-format-specific; a new supplier will re-derive them. What does transfer usefully is the record package: frozen revision, microvia span declarations, as-built stackup, accepted impedance construction, declared exceptions and inspection records. Secure the right to that package rather than arguing over programs.

A revision changed only the silkscreen. Why is there a new tooling charge?

There shouldn't be one covering deliverables the change cannot invalidate. This is why the re-charge clause should map to deliverables rather than to the existence of a revision. Ask which specific items were invalidated and why.

Should we ask for the NRE to be amortised into the unit price instead?

It is an option, and it changes what you are buying. Amortisation removes the separate line but also removes the asset: there is nothing to own and nothing to waive later. It also ties your unit price to an assumed volume. If you choose it, make sure the assumed volume is stated, because a shortfall usually triggers a price revision.

How long should a test fixture be retained?

That is a commercial term rather than a technical one, so state it as a period from last shipment and have the supplier confirm it in writing, together with a notice obligation before disposal. A retention period measured from the first order can expire on a part you order regularly.

Does this apply to prototype orders too?

It matters more on prototypes, because prototype volumes rarely absorb the charge and because prototypes are the orders most likely to be revised. Itemisation at prototype stage is also what lets you see what the production transfer will actually cost.