Change the constraint, not just the number
What does the upgrade actually add?
Compare two exact saved setup plans, inspect their source scope, and separate new purchase costs from an existing owned list.
Source type, optical output, input power, working area, workflow and measured process evidence are distinct. A shared brand/connector/software name does not establish a reusable component or transferable license.
Keep a no-purchase outcome.
Keeping the existing machine is an option when its documented scope answers the task. It does not erase operating, service or material costs. If the process evidence is unresolved, refine the task, request an appropriately scoped sample or explore another process before buying.
Reuse is offered only for an explicitly owned exact component/revision with documented target interfaces and known whole quantities. A bundled package price is never reduced because you already own one included item. License-transfer rights remain separate from software compatibility.
Create the exact setup lists · Saved projects · Compare machine facts without saving projects · Alternative process questions · Original project paths
Reuse needs its own evidence
Two exact plans: Existing and target configurations, packages, source dates and currencies remain distinct.
Conditional reuse: Ownership, exact component/revision, documented target interfaces and whole quantities must all be established; software-transfer rights are separate.
No-purchase path: Keeping the current plan remains an option. Unknown resale credit or setup cost is not zero and does not establish payback.
Original anonymous decision diagram. It does not declare any current component reusable, reduce a bundle price or recommend a purchase. Your actual comparison and explicit export remain the controls above.