When Should Setup, Programming, or NRE Be Requoted on a 3D Printing Reorder?
Published
When Should Setup, Programming, or NRE Be Requoted on a 3D Printing Reorder?
Setup, programming, or non-recurring engineering should not be charged again merely because a buyer places another order. Requote it only when the controlled production basis has changed, prior setup cannot be reused, agreed records or assets are unavailable, qualification must be repeated, or the new release adds real one-time work. The quote should identify the trigger, deliverable, reuse basis, and approval needed.
Choose the right order path
Farm intake fits multi-SKU, recurring, inspection-sensitive, staged, packaged, scanning, reverse-engineering, or otherwise complex work. Instant quote fits clean files and straightforward requirements.
Start with a reuse test, not the previous invoice
Compare the reorder against the last approved production baseline. Check the part and drawing revision, source file, material and color, orientation or process route, approved machine or lane when relevant, inspection plan, packaging, labeling, destinations, supplied components, and release conditions. If those inputs and the supplier's controlled records remain usable, the reorder may need only recurring production work.
| Situation | Likely treatment | Buyer evidence to request |
|---|---|---|
| Controlled inputs and production basis are unchanged | Reuse prior setup where it remains available and fit | Baseline identifier, reuse confirmation, recurring price scope |
| Minor administrative change with no production effect | Document the update without inventing technical NRE | Reason no setup or validation changed |
| Revision, material, route, inspection, packaging, or component changed | Quote only the incremental one-time work needed | Change-to-task mapping, deliverable, approver, completion evidence |
| Records, fixtures, programs, or qualification cannot be reused | Recreate or requalify under an approved scope | Retention or ownership basis, gap, replacement plan |
| Supplier initiates a process transfer | Allocate cost and approval according to the agreement | Change notice, validation plan, responsibility, acceptance gate |
Separate four cost buckets
- Recurring production: work repeated for each release, such as printing, routine processing, ordinary inspection, packaging, and shipment.
- Reusable one-time work: controlled setup, programming, planning, fixtures, or records that remain applicable.
- Incremental change work: engineering or qualification tied to a buyer or supplier change.
- Recovery work: recreating missing, expired, damaged, or nontransferable assets and records.
Require a trigger-to-deliverable crosswalk
For each proposed one-time charge, ask what changed, why the previous baseline cannot be reused, what work will be performed, what tangible record or outcome it creates, who approves it, whether it applies to one SKU or a family, and what future reuse rights follow. Avoid vague lines such as “setup” when the quote cannot explain the work boundary.
Fit, non-fit, and production risks
This framework fits repeat parts, multi-SKU catalogs, revision-controlled production, supplier transfers, inspection-sensitive releases, and programs with paid setup or engineering. A simple clean-file reorder may not need a formal NRE review. Instant quote is appropriate when requirements are straightforward; managed intake is safer when changes, records, qualification, ownership, or staged releases need coordination.
- A quote repeats old NRE without showing new work.
- A revision change is released before setup and acceptance scope are approved.
- Amortized NRE assumes demand that never becomes firm.
- Paid fixtures, programs, or records have undefined ownership and retention.
- A supplier process transfer creates requalification work with no responsibility rule.
The repeat production runs page owns recurring supply. Use the quote cost-drivers guide to normalize recurring economics and the production RFQ guide to document repeat-order scope.
Make the request quote-ready
- Last approved SKU and revision baseline, current files, and requested quantity or release pattern.
- Every changed input, effective date, affected inventory, and whether old and new revisions may coexist.
- Existing setup, programs, fixtures, inspection plans, packaging data, approvals, ownership, retention, and transfer rights.
- Requested one-time deliverables, acceptance evidence, approvers, reuse term, and treatment on future reorders.
- Separate recurring unit, one-time, amortized, optional, and contingency lines.
Frequently asked questions
Is every reorder supposed to include NRE again?
No. An unchanged reorder may reuse controlled files, approved setup, programming, and prior qualification. The supplier should identify any new one-time task and the change that made it necessary.
What changes can justify new setup or programming work?
A new revision, material, orientation, process route, machine class, inspection plan, packaging configuration, supplied component, destination requirement, or lapsed controlled record can create new work. The exact trigger should be stated.
Should NRE be rolled into the unit price?
Either structure can work, but buyers need visibility. Separating one-time work from recurring unit economics makes quote comparison and later reorders easier; amortization needs a defined quantity and treatment if demand changes.
Who owns reusable setup records or programming?
Ownership and reuse rights depend on the written agreement. Define whether paid deliverables are buyer-owned, supplier-controlled, transferable, modifiable, retained for a stated period, or usable only within the original production process.
Choose the right order path
Farm intake fits multi-SKU, recurring, inspection-sensitive, staged, packaged, scanning, reverse-engineering, or otherwise complex work. Instant quote fits clean files and straightforward requirements.
Make the final decision explicit
Document the baseline, decision rule, approvers, evidence, exceptions, and next-review trigger before releasing work. Use managed farm intake for complex programs and instant quote for clean files with straightforward requirements.