Direct answer: VA/VE (value analysis/value engineering) is not "cut 5% every year" and it is not "switch to cheaper material". It is a systematic reduction of total cost through design, material, process, standardisation, packaging/logistics, yield and supply-chain collaboration without sacrificing function, quality, regulatory compliance or delivery; cost breakdown/target costing, validation, customer approval and commercial sharing turn it into a closed loop. A manufacturer's VA/VE/cost-reduction page should state the method, cost baseline, validation boundary, customer approval, annual productivity/sharing mechanism and evidence—not just "continuous cost reduction/competitive price". Otherwise, when a customer asks "where did the cost come from, what was validated, who is responsible for quality", the answer becomes an ad-hoc explanation.
This guide is for equipment, automotive parts, electrical/electronic, appliance, medical device, new-energy, hardware/injection-molding and export manufacturers in Changzhou and nearby areas. It explains how to write and accept a VA/VE cost-reduction page. Information is current to 2026-11-05. It is a review of public rules and project practice, not procurement, cost-accounting, quality, PPAP, legal or compliance audit advice; the specific cost reduction, quotation, contract, validation and customer approval depend on the company's procedures, customer requirements, drawings/standards, contract and applicable law.
VA/VE means "same or better function, lower cost", not the slogan "lower price without lower quality"; it needs a cost breakdown/baseline, not a guess. Any cost reduction affecting customer assembly/regulatory status/critical characteristics/appearance must be validated and approved—never switch first, report later. Annual productivity/target cost/gain-sharing are contractual: define the base, validity and raw-material/currency adjustments.
How does the VA/VE page relate to price, quotation, second-source, NPI/PPAP, quality and PCN pages?
The price page answers "whether/how to show prices"; the quotation page answers "quote fields/validity"; the second-source/alternative-material page answers "how to add a source/change material"; the NPI/PPAP page answers "new-product introduction"; the PCN/EOL page answers "change notification"; the quality page answers "PPM/8D". The VA/VE page answers "how an existing product reduces cost without sacrificing function/quality/regulatory compliance, how it is proven, and how savings are shared". Price is the result; VA/VE is the method; a second source is a source; VA/VE is value optimisation—they cannot replace each other.
Common breakpoints: treating VA/VE as procurement price pressure; treating cheaper material as VE; no cost baseline; counting material only, not yield/logistics/warranty; no validation; customer unaware; all savings kept by one side; annual productivity without a base/validity; no raw-material adjustment. A page that states method, cost, validation, approval and commercial mechanics gives procurement, R&D, finance and sales one playbook.
| Page/topic | Answers | Covers | Cannot replace |
|---|---|---|---|
| VA/VE/cost reduction | Function/cost optimisation | Method/validation/sharing | Quote/second source |
| Price page | List/range price | External price | Cost/method |
| Quotation | Quote fields/validity | Trade terms | VA/VE validation |
| Second source/alternative | Add source/change material | Source/validation | Value optimisation |
| NPI/PPAP | New-product introduction | Planning/validation | Production cost-down |
| PCN/EOL | Change/discontinuation | Change management | Cost-down proposal |
| Quality/8D | Defect/corrective | Quality | Cost structure |
This page map is editorial; contract changes/quality liability reference the Civil Code of the PRC and the Product Quality Law of the PRC.
What is the difference between VA/VE and a direct price cut?
A direct price cut is a price concession and may not improve cost; VA/VE changes function/design/material/process/supply chain to create a structural reduction in total cost while maintaining or improving function, quality, regulatory compliance and delivery. VA focuses on existing-product function/cost analysis (value = function/cost); VE focuses on value optimisation during design/development. Sources include design simplification/part reduction, material substitution/lightweighting, process/yield, standardisation/common parts, packaging/logistics, supply chain/second source, energy/loss and after-sales/returns. Not every reduction is sustainable, and not every customer accepts the same solution.
Acceptance checks: type of reduction; function/cost baseline; structural or not; customer impact; sustainability; one-off vs recurring; investment/payback. Common gaps: price talk only; no function analysis; treating a one-off negotiation as VA/VE; unsustainable reduction; no investment/payback; customer rejection.
| Type | Characteristics | Evidence | Common gap |
|---|---|---|---|
| Direct price cut | Price concession | Quote/contract | No cost improvement |
| VA | Existing function/cost | Function analysis | Price only |
| VE | Design/development optimisation | Design review | Too late |
| Material/design | Part reduction/substitution/lightweight | BOM/testing | Unvalidated |
| Process/yield | Cycle/loss/automation | Pilot/data | Unstable |
| Packaging/logistics | Volume/protection/freight | Testing/quote | Omitted |
| Supply chain | Second source/negotiation/localisation | RFQ/audit | Unvalidated |
The classification is editorial; the specific VA/VE method follows company/customer/industry practice.
How should cost breakdown/target costing be accepted?
Cost reduction needs a baseline: material/purchased parts, labour/manufacturing, equipment/tooling amortisation, quality/scrap, packaging/logistics, tariff/currency, management/sales/profit. Target cost can be derived from the customer target price or a should-cost estimate; distinguish fixed/variable, direct/indirect and one-off/recurring. Cost data must map to BOM/process/volume/plant/currency/tax; a "5% reduction" without a baseline is not enough. Open-book arrangements need scope/confidentiality/audit rules.
Acceptance checks: cost structure; BOM/process; fixed/variable; volume/plant; currency/tax; target cost/should-cost; baseline version; open-book scope; confidentiality. Common gaps: total price only; missing cost items; unclear volume assumptions; currency/tax omitted; outdated baseline; open-book without boundaries.
| Cost item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Material/purchased | BOM/price/loss | BOM/quote | Loss omitted |
| Labour/manufacturing | Hours/rate/cycle | Process/rate | Guesswork |
| Equipment/tooling | Depreciation/amortisation | Asset/volume | Omitted |
| Quality/scrap | PPM/rework/scrap | Quality data | Not counted |
| Packaging/logistics | Volume/protection/freight | Quote | Omitted |
| Tariff/currency | Trade terms/currency | Quote/contract | Ignored |
| Management/profit | Allocation/target | Finance | Opaque |
The cost breakdown is editorial; specific accounts/basis follow company finance, quotation and customer requirements.
Where do cost-down ideas come from, and how are they prioritised?
Common sources: design simplification/part reduction/modularisation; material substitution/lightweighting/recycled content; process improvement/automation/cycle time; yield/rework/scrap; standardisation/common parts/SKU reduction; packaging/transport/warehousing; second source/localisation/negotiation; energy/water; after-sales/returns/warranty; software/configuration. Prioritise by saving, investment/payback, quality/regulatory risk, customer impact, lead time and reversibility. Start with low-risk, fast-payback, customer-acceptable projects, then pursue structural design changes.
Acceptance checks: idea list; saving; investment/payback; risk; customer impact; lead time; priority; owner. Common gaps: material only; yield/logistics ignored; no saving estimate; risk not assessed; customer impact ignored; too many projects without priority.
| Source | Typical action | Evidence | Common gap |
|---|---|---|---|
| Design | Part reduction/simplification/modularisation | Review | No cost impact |
| Material | Substitution/lightweight/recycled | Testing | Unvalidated |
| Process | Automation/cycle time | Pilot | High investment |
| Yield | Rework/scrap | Data | Unstable |
| Standardisation | Common parts/SKU reduction | BOM | Customer differences |
| Packaging/logistics | Volume/protection/freight | Testing/quote | Omitted |
| Supply chain | Second source/localisation | RFQ/audit | Unvalidated |
| After-sales | Returns/warranty | Data | Ignored |
Sources/prioritisation are editorial; specific projects follow products, customers and investment-return assessment.
How should a cost-down proposal be validated, and what must not be sacrificed?
Do not sacrifice: function/performance, safety, regulatory/substances, reliability/life, customer assembly/interfaces, appearance/colour, manufacturability/yield, delivery/capacity or after-sales/warranty. Validate at least: dimensions/material/performance/reliability; regulations (RoHS/REACH/FCM/CE etc.); trial assembly/pilot; customer critical characteristics; packaging/transport; software/firmware where applicable. Any reduction affecting customer assembly/regulatory status/critical characteristics must follow the change process and be approved—never "switch first, report later".
Acceptance checks: validation matrix; test reports; regulatory/substances; trial assembly/pilot; customer critical characteristics; packaging/transport; software regression; customer approval. Common gaps: dimensions only; material downgrade; reliability not tested; regulatory not tested; customer unaware; pilot skipped; packaging damage.
| Dimension | What to prove | Evidence | Common gap |
|---|---|---|---|
| Function/performance | No reduction/improvement | Testing | Not tested |
| Safety | No increased risk | Assessment | Ignored |
| Regulatory/substances | RoHS/REACH/FCM etc. | Report | Not tested |
| Reliability/life | Life/failure rate | Testing | Not done |
| Assembly/interface | Customer/tooling | Trial | No trial |
| Appearance | Colour/texture | Limit sample | Colour difference |
| Pilot/yield | Stable/cycle | Pilot | Skipped |
| Customer approval | Written/PPAP | Record | Switch first |
Validation dimensions are editorial; specific projects follow drawings, standards, customer requirements and regulations.
How should customer approval and change be accepted?
First check whether the contract/quality agreement requires customer approval of design/material/process/source changes; customer-critical parts, regulated parts, automotive/medical products usually require written approval. The change package includes: change description/reason, cost impact, function/quality/regulatory impact, validation report, samples/PPAP, switching plan, inventory/old stock, traceability and effective date. Do not ship before approval; after approval, update BOM/ERP/AVL/drawings/control plan/inspection standards, and notify after-sales/spares/labels/instructions where applicable. Articles 543/544 of the Civil Code allow negotiated changes and presume no change where unclear; Articles 615/617 address liability for non-conforming quality.
Acceptance checks: contract clauses; customer approval; change package; impact analysis; validation; switching; old stock; system updates; downstream documents. Common gaps: no contract clause; verbal approval; switch first; missing impact analysis; mixed old stock; BOM not updated; customer unaware.
| Step | What to do | Evidence | Common gap |
|---|---|---|---|
| Contract | Change/approval clause | Contract/quality agreement | Missing |
| Change package | Reason/cost/impact | Documents | Incomplete |
| Customer approval | Written/PPAP | Record | Verbal |
| Switching | Lot/date/inventory | Plan | Switch first |
| Old stock | Isolate/use up/scrap | Record | Mixed |
| System | BOM/ERP/AVL | Screenshot | Not updated |
| Downstream | Labels/instructions/spares | Version | Missed |
Change/approval follows the contract, quality agreement, customer requirements and applicable law; this is not legal advice.
How should annual productivity, target cost and gain-sharing be described?
Annual productivity/continuous cost-down is a common commercial term, not a legal mandate; define the base (list price/prior-year price/cost), percentage, period, scope, exceptions (raw material/currency/regulation/customer change), payment/invoicing and retroactivity. Target cost is a financial target for development/production, not a requirement that a supplier lose money. Gain-sharing should define the calculation basis, ownership, duration, investment offset and quality/delivery conditions. Raw-material/currency movements need an adjustment mechanism; it cannot be "down only".
Acceptance checks: annual productivity clause; base/percentage/period; exceptions; adjustment mechanism; target cost; sharing ratio/duration; investment offset; quality/delivery conditions. Common gaps: no base; raw-material increases not adjusted; verbal gain-sharing; investment not offset; reduction despite poor quality; customer/supplier loss.
| Mechanism | What to state | Evidence | Common gap |
|---|---|---|---|
| Annual productivity | Base/percentage/period | Contract | No base |
| Target cost | Target/basis/owner | Quote/finance | Guesswork |
| Gain-sharing | Ratio/duration/calculation | Agreement | Verbal |
| Investment offset | Tooling/equipment/validation | List | Not offset |
| Material/currency | Adjustment trigger | Clause | Down only |
| Quality/delivery | Conditions | KPI | Not linked |
Annual productivity/sharing is editorial; specific terms follow the contract, quotation, finance and customer negotiation.
How should project governance and KPIs be accepted?
VA/VE needs a cross-functional team (procurement/R&D/process/quality/finance/sales), a project list, targets, owners, timing, investment/payback, risk, customer approval and benefit calculation. KPIs may include annualised savings, gross margin, yield, PPM, delivery, customer acceptance, payback and one-off vs recurring. Benefits must be confirmed by finance, not "theoretical savings"; failed projects should be reviewed so mistakes are not repeated.
Acceptance checks: organisation/duties; project list; targets/timing; investment/payback; risk; customer approval; benefit calculation; review. Common gaps: procurement alone; too many projects; inflated benefits; no finance confirmation; no failure review; customer rejection.
| Element | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Organisation | Cross-functional/duties | Appointment | Procurement alone |
| Projects | List/targets/timing | Register | Too many |
| Investment/payback | Amount/period | Calculation | Not counted |
| Risk | Quality/regulatory/customer | Assessment | Ignored |
| Benefits | Annualised/finance-confirmed | Finance | Inflated |
| Review | Failures/lessons | Record | No review |
Governance/KPIs are editorial; specific organisation/metrics follow company size and customer requirements.
How should supplier cost pressure and business ethics be described?
Cost reduction cannot rely on late payment, forced levies, corner-cutting, false invoicing or shifting unreasonable risk; suppliers need a reasonable profit/cash flow, otherwise quality/delivery/compliance risk rises. Avoid: pressing unit price without helping reduce cost; annual reduction ignoring material increases; passing all customer reductions down; threatening a second source without orders; making suppliers bear customer design defects; squeezing environmental/labour/safety costs. Sustainable reduction means joint improvement, transparent cost and fair sharing.
Acceptance checks: supplier cost breakdown; reasonable profit; payment; risk allocation; environment/labour; second-source strategy; communication. Common gaps: price pressure only; late payment; all risk shifted; environment/safety squeezed; second source as a threat; supplier loss.
| Risk | Sign | Evidence | Common gap |
|---|---|---|---|
| Price pressure only | No improvement | Cost table | No support |
| Late payment | Longer terms | Payment record | Cash flow |
| Risk shifting | Supplier bears customer defect | Contract | Unfair |
| Environment/labour | Cost squeezed | Audit | Compliance risk |
| Second-source threat | RFQ without order | RFQ | Relationship damage |
| Quality | Cost-down, quality-down | PPM | Customer complaint |
Business ethics is editorial; specific payment/contract/compliance follows company policy and law.
How should the website VA/VE page be written?
A public page should include: VA/VE method, applicable products/stages, cost breakdown/target cost, cost-down sources, validation boundary, customer approval/change, annual productivity/sharing, project governance/KPIs, cases (redacted/authorised), contact/version. Write verifiably: state "we have a method/cost baseline/validation/customer approval", not "annual X% reduction/lowest price/cost-down without quality loss".
Separate "public information" from "customer/contract documents": cost breakdown, BOM, drawings, validation reports and customer prices are provided per permission/contract; the public page gives method, process, capability and contacts, and does not publish customer/supplier sensitive information. If supplying components or carrying out contract manufacturing, state that the company supports the machine builder/brand owner with VA/VE and change approval and does not declare the whole product cost reduction. Multilingual pages should match sales countries.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Method | VA/VE/target cost | Process | "Lowest price" |
| Scope | Products/stages | List | "All products" |
| Cost | Breakdown/baseline | Template | "10% reduction" |
| Sources | Design/material/process/logistics | Cases | "Cheaper material" |
| Validation | Function/quality/regulatory | Reports | "No quality loss" slogan |
| Customer approval | Change/PPAP | Record | Switch first |
| Commercial | Annual/sharing/adjustment | Contract | "Must reduce every year" |
| Contact/version | Data request/date | Form | No entry |
This page structure is editorial; external claims must be truthful and verifiable, per company procedures, customer requirements and the contract.
What must not be written?
High-risk claims: "X% reduction every year" (only if the contract/cost allows); "lowest price in the industry" (hard to verify/possible unfair competition); "cost down without quality down" (needs validation/boundary); "VA/VE = cheaper material" (possible downgrade); "the customer does not need to know" (change approval); "all savings belong to us/the customer" (contract); "every product can be reduced" (unrealistic); "cost reduction does not affect delivery" (capacity must be validated); "ISO certification guarantees cost reduction" (system ≠ project benefit). These are inaccurate or misstate responsibility.
Safer wording: "VA/VE method, cost baseline, cost-down sources, validation/customer approval, annual/sharing mechanism and evidence, subject to company procedures/customer requirements/contract". External promotion must also comply with advertising/fair-competition law; customer/supplier information needs authorisation/redaction.
| Page wording | Problem | Suggested wording | Basis |
|---|---|---|---|
| "X% every year" | Contract/cost constraints | Per contract/project | Commercial |
| "Lowest price" | Hard to verify | Value/total cost | Advertising law |
| "No quality loss" | Needs validation | Validation/boundary | Quality |
| "Cheaper material" | Possible downgrade | Equivalence/approval | VA/VE |
| "Customer need not know" | Change approval | Notify/approve | Contract/Civil Code |
| "All savings ours" | Contract/fairness | Sharing mechanism | Commercial |
| "System = cost-down" | System ≠ benefit | Project/finance | ISO |
These red lines are editorial; whether a claim is false advertising/breach is determined by regulators and the contract, and this is not legal advice.
Go-live acceptance checklist
Ten checks: VA/VE method, cost baseline/breakdown, cost-down sources/priority, validation boundary, customer approval/change, annual/sharing, project governance/KPIs, supplier ethics, cases/redaction, page wording/version. Each needs an owner, evidence and review date. The pass condition is not "the page says cost reduction", but that a customer can see where the cost comes from, how it is validated, who approves and how savings are shared.
Before go-live, run one real product/cost-down project through: method → cost → sources → validation → customer approval → commercial → governance → page wording. Any step that fails is a gap in the page or the process.
| Check | Pass condition | Evidence | If it fails |
|---|---|---|---|
| Method | VA/VE/target cost | Process | Add |
| Cost | Baseline/breakdown | Template | Calculate |
| Sources | Design/material/process | List | Add projects |
| Validation | Function/quality/regulatory | Reports | Validate |
| Customer approval | Written/change | Record | Approve |
| Commercial | Annual/sharing/adjustment | Contract | Add clauses |
| Governance | Team/projects/benefits | Register | Build |
| Ethics | Reasonable profit/payment | Policy | Correct |
| Cases | Redacted/authorised | Authorisation | Remove |
| Wording | No "must/lowest" | Page test | Remove |
This checklist is editorial; specific compliance/quality requirements follow company procedures, customer requirements and the contract.
Who should read this, who should not, and what decisions does it support?
It suits procurement, R&D, process, quality, finance, sales and website teams at equipment, automotive parts, electrical/electronic, appliance, medical device, new-energy, hardware/injection-molding and export manufacturers in Changzhou and nearby areas; also companies asked for annual cost-down/target cost or seeking higher margin. It does not suit products with no cost-reduction space, customers who do not accept changes, or those wanting one page to replace cost accounting/validation/contract/legal advice.
Read it if a customer requires annual cost-down/target cost; margin is falling; you are building or revising a VA/VE page; or you need to separate price, quotation, second source, NPI/PPAP, PCN and VA/VE. Skip it if you treat VA/VE as price pressure, switch to cheaper material without validation, keep the customer uninformed, or keep all savings. It supports self-review of method, cost, sources, validation, approval, commercial, governance and page wording.
FAQ
What is the difference between VA/VE and a direct price cut?
A direct price cut is a price concession and may not improve cost; VA/VE changes design/material/process/standardisation/logistics/supply chain to create a structural function/cost improvement while maintaining or improving function, quality, regulatory compliance and delivery. It needs a cost baseline, validation and customer approval—not a guessed price cut.
How should annual productivity/target cost be set?
Annual productivity is a common commercial term, not a legal mandate; define the base (list price/prior-year price/cost), percentage, period, exceptions (raw material/currency/regulation/customer change) and adjustment mechanism. Target cost is derived from the customer target price or should-cost, with BOM/process/volume/currency/tax assumptions—not guesswork.
What must not be sacrificed?
Function/performance, safety, regulatory/substances, reliability/life, customer assembly/interfaces, appearance, manufacturability/yield, delivery/capacity and after-sales/warranty. Any reduction affecting customer assembly/regulatory status/critical characteristics must follow the change process and be approved.
How should a cost-down proposal be validated/approved?
Validate at least dimensions/material/performance/reliability, regulations (RoHS/REACH/FCM/CE etc.), trial assembly/pilot, customer critical characteristics, packaging/transport and software/firmware; submit a change package (reason/cost/impact/validation/switching/old stock/effective date) and obtain written customer approval/PPAP before switching; update BOM/ERP/AVL/drawings/control plan.
How should savings be shared and quoted?
Follow the contract/quotation: annual productivity, target cost, gain-sharing (ratio/duration/calculation/investment offset/quality-delivery conditions), raw-material/currency adjustment. Quotes should state validity, MOQ, currency, trade terms and adjustment; do not reduce without an increase mechanism, and do not pass all customer reductions to suppliers.
How should the website/customer statement be written?
State the VA/VE method, applicable products/stages, cost breakdown/target cost, cost-down sources, validation boundary, customer approval/change, annual/sharing, governance/KPIs, redacted cases and contact/version; do not write "X% every year/lowest price/no quality loss" without evidence. Customer/cost documents are provided on a need-to-know basis.
One-sentence takeaway
A Changzhou manufacturer's VA/VE page is not about the word "price cut". It should turn the method, cost baseline/breakdown, cost-down sources, validation boundary, customer approval, annual/sharing, project governance and supplier ethics into a verifiable checklist—so a customer can see where the cost comes from, how it is validated, who approves and how savings are shared.
Method and limitations
This is a review of public rules and project practice, not an audit or legal opinion on any company's procurement, cost, quality, PPAP, contract or compliance. No undisclosed customer/supplier cost data were used. Method, cost, validation, approval, commercial and acceptance items are editorial suggestions, not cost-accounting/quality/legal conclusions. The specific cost reduction, quotation, contract, validation and customer approval depend on company procedures, customer requirements, drawings/standards, contract and applicable law.
Sources and scope
Information is current to 2026-11-05. The following are public official/primary pages; their clauses, versions and scope control.
- Civil Code of the People's Republic of China: National People's Congress. Article 509 (full performance), Articles 543/544 (contract modification), Articles 577/584 (breach/damages), Articles 615/617 (non-conforming quality).
- Product Quality Law of the People's Republic of China (2018 amendment): Beijing Municipal Market Regulation Administration. Article 26 (producer quality responsibility), Article 27 (marking), Articles 40/41 (repair/replacement/return/compensation).
- Standardization Law of the People's Republic of China (2017 revision): MOFCOM policy database. Article 27 (enterprise-standard self-declaration and supervision).
- ISO 9001:2015 Quality management systems — Requirements: ISO. Quality management system, process approach and continual improvement.
- ISO 56002:2019 Innovation management system — Guidance: ISO. Systematic innovation/improvement methods that can support VA/VE governance.