WEIMI INSIGHTS / OEM PROCUREMENT • PROJECT COSTS
Compare engineering proposals by deliverables and decision points before treating an estimated production price as a complete project budget.
ENGINEERING
Pay for defined development work and evidence.
PROTOTYPE
Identify what the first physical build must prove.
PRODUCTION
Keep quantity and configuration assumptions visible.
Compare custom projects by scope and acceptance evidence, not by combining every charge into one unexplained machine price. No cost category is meaningful without its deliverables.
01 / BUYER NOTES
Ask the supplier to describe which parts of the proposal already exist and which need modification or new design. A different colour scheme is not the same project as a new dispensing mechanism. The engineering scope should reflect the actual technical work behind the requested customer experience.
Prepare a requirements list with priorities and unresolved assumptions. Mark what is essential for the pilot and what can wait. This helps the supplier estimate the work and prevents optional ideas from quietly becoming part of an undefined development commitment.
Request a written feasibility response before relying on a production quote. Some requirements may need sample trials or third-party integration review. Record those dependencies so the budget and schedule distinguish known work from questions that still need investigation.
02 / BUYER NOTES
NRE commonly refers to non-recurring engineering, but the label alone does not establish scope. Ask which design activities, documentation, software work and tests are included in the proposed charge. Identify any external testing, specialist services or tooling that will be quoted separately.
Agree the outputs of each stage. Useful deliverables might include an approved interface specification, a tested mechanism or a defined prototype build, depending on the project. Avoid measuring progress only by hours spent when the purchasing decision depends on whether a particular function works.
Clarify what happens if feasibility work reveals that the original approach is unsuitable. The agreement should explain the review point and available next steps. Have relevant commercial terms reviewed appropriately rather than assuming every development payment guarantees a production-ready machine.
03 / BUYER NOTES
Define the purpose of the prototype. It may be built to test one difficult mechanism or to demonstrate an integrated customer flow. Its materials, finish and service access may differ from a production design, so record what is included and what remains outside the acceptance scope.
Ask whether the quoted prototype price includes assembly, programming, test materials and the agreed trial work. Clarify transport and on-site assistance where relevant. A prototype delivered without the supporting test scope may leave the buyer with equipment but little evidence for the next investment decision.
Do not treat a working demonstration as automatic approval for commercial rollout. The final design may still require reliability work, documentation, compliance assessment or production preparation. Identify those stages and their expected outputs before moving from the first build to a batch order.
04 / BUYER NOTES
Ask which configuration and quantity support the estimated unit price. Prices for different batch sizes may depend on component sourcing, tooling and production methods. Keep the assumptions visible so a later change in screen, mechanism or payment hardware does not appear as an unexplained increase.
Clarify what the unit price excludes. Freight, installation, software services, local payment onboarding or optional accessories may sit outside it. Compare proposals on a consistent scope rather than ranking one all-inclusive offer against another estimate that covers only the cabinet and mechanism.
Review how design changes after prototype approval affect price and timing. A controlled change process should identify the requested modification, its implications and the approval needed. This keeps the production baseline useful and prevents an informal conversation from becoming an unexpected engineering charge.
05 / BUYER NOTES
Create a staged decision plan that matches the project’s uncertainties. Review the agreed evidence before authorising the next phase under the commercial arrangement. The aim is to learn whether the concept meets its requirements, not to keep progressing simply because a prototype already exists.
Keep documents, test results and configuration versions together. Clarify access to the deliverables and any ownership or use rights through appropriate agreement review. Do not infer rights to drawings, software or tooling solely from the name of a development fee.
Send WEIMI the requirements and intended pilot-to-production sequence. Ask for separate engineering, prototype and production scopes with clear assumptions. A structured proposal makes it easier to decide which work is necessary and which uncertainties remain before committing to a larger rollout.
Ask: What design work and evidence will be delivered?
Compare: Scope, exclusions and stage acceptance.
Ask: What functions and tests does this unit cover?
Compare: Configuration, trial support and remaining development.
Ask: Which quantity and approved design support the price?
Compare: Included components, services and change assumptions.
PRACTICAL ANSWERS
Not automatically. Ownership and permitted use depend on the agreement and deliverables. Review those terms explicitly with appropriate advice.
A prototype may involve one-off parts, assembly and testing that differ from repeat production. Ask for the actual scope rather than assuming the reason.
That misses development, validation and scope differences. Compare the full staged proposal and the evidence each stage will provide.
YOUR NEXT STEP
Share your essential functions, samples and planned quantities with WEIMI. Ask for distinct development, prototype and production scopes with documented decision points.
Explore equipment →Discuss your requirements →