Neither a factory nor a sourcing company automatically owns every product decision. Define who recommends, who performs, and who approves design changes, samples, substitutions, and quality issues. The buyer should retain a clear approval path even when another party coordinates communication.
Key takeaways
- Product design connects form, function, and user needs; the buyer should identify who controls design choices. [1]
- Supply-chain coordination moves information among parties, making change communication an explicit responsibility. [2]
- Quality control depends on defined expectations and documented review, not a partner’s general label. [3]
- OEM describes a production relationship but does not assign every development or approval task. [4]
A sourcing company may coordinate conversations and a factory may make the toy, but neither role alone explains who decides whether a design change is acceptable. If the buyer does not assign decision rights, a suggestion can become an assumed requirement, or a sample can be treated as approved even though only one feature was reviewed.
This guide focuses on decision ownership: who proposes, implements, reviews, and approves product changes. It helps buyers compare direct factory and sourcing-company models while keeping responsibility for the custom product clear.
Separate recommendation, execution, and approval
For every major task, distinguish who may recommend an option, who performs the work, and who gives final approval. A factory may recommend a component alternative; a sourcing company may relay the option; the buyer may decide whether the product brief changes.
Product design connects a product’s form with its function and intended user. [1] The buyer should state which aspects are fixed, which can be adjusted, and who has authority to approve each category of change.
OEM commonly refers to manufacturing according to another party’s requirements, but that label does not automatically allocate design or approval rights. [4] Ask each partner to describe its role in the project and document any design support separately.
If the product includes educational content or brand claims, name the reviewer responsible for those decisions. Manufacturing and sourcing coordination do not automatically provide authority to approve customer-facing claims.
Define who controls the product specification
Maintain a buyer-approved master specification with a version and date. It should identify activity, components, package, instructions, target markets, and known open points. Supplier files should reference this master rather than relying on email history.
Ask the factory what level of specification it needs to manufacture or prepare a sample. Ask the sourcing company how it will distribute revisions and confirm which suppliers have received them.
Do not let each party maintain a different unofficial version. If the sourcing company consolidates product data, define whether it edits files or only passes them along, and who checks the result.
When the specification is incomplete, label assumptions clearly. A preliminary proposal should not be mistaken for a finalized product instruction. The buyer should identify the next decision that will stabilize the relevant feature.
Set sample review and approval boundaries
Each sample should have a purpose: testing the activity, confirming dimensions, reviewing a component, or checking package layout. State what the sample represents and what remains provisional.
Ask who receives the sample, who records observations, and who resolves conflicting feedback. A sourcing company can coordinate the review process, but the buyer should know who has authority to approve the product.
Quality control checks defined characteristics against expectations. [3] Determine which features are reviewed and how a deviation is documented. A general visual approval should not be interpreted as acceptance of every technical, safety, or commercial question.
If a sample is approved conditionally, write the conditions. For example, the buyer may accept the activity while requiring a package correction or further review. Keep each decision attached to the sample version.
Manage changes across the factory and intermediary
Use a change request that records the current requirement, proposed revision, reason, affected files, recommendation, approval owner, and outcome. This clarifies whether a message from an intermediary is a suggestion or an approved buyer instruction.
Supply chains involve information flows among suppliers and buyers. [2] Define who notifies affected parties when a change is approved, and how each party confirms receipt of the current version.
A component substitution may alter activity, instructions, package dimensions, or prior review. Ask the party proposing the change to explain likely effects, then assign appropriate reviewers. Do not assume a sourcing company can approve technical equivalence on the buyer’s behalf.
Keep rejected options in the change log as rejected. This prevents a later production conversation from reviving an alternative that the buyer explicitly declined.
Decide how quality issues are escalated
Agree how a reported deviation will be described and who investigates it. A factory may identify a production issue; a sourcing company may help relay information; the buyer should know who determines disposition and what evidence is needed.
Define which criteria are checked and where results are recorded. Avoid using vague categories alone. A product-specific record might identify completeness, fit, instruction correspondence, or package details, depending on the design.
Separate quality concerns from safety and regulatory questions. If an issue may affect safety or compliance, involve an appropriate specialist and do not assume the factory’s or intermediary’s initial description resolves it.
Assign a single buyer contact to consolidate internal feedback. This helps prevent different departments from giving conflicting instructions to the factory or sourcing company.
Choose the model that matches your governance capacity
A direct factory relationship may suit a buyer that can manage technical communication and documentation. A sourcing company may add coordination, but the buyer should understand how information reaches the manufacturing team and who remains accountable for each deliverable.
Compare the models against decision rights, not general claims of convenience. Ask how each would handle a sample comment, component change, package correction, or disagreement about a requirement.
K&M publicly describes STEM toy manufacturing and OEM/ODM services. Buyers can use that information to ask how product decisions and approvals would be handled in a custom program. [4] K&M STEM toy factory The link is a starting point for public supplier information, not confirmation of a particular decision process, capacity, price, timing, or guarantee.
Before starting, agree a responsibility matrix covering proposal, execution, review, approval, and notification for each major product task. A clear matrix reduces ambiguity without suggesting that one partner type is always better.
Sources
Frequently asked questions
Can a sourcing company approve product changes for the buyer?
Only if the buyer has explicitly delegated that authority. Define who recommends, implements, and approves each change.
Does sample approval mean every feature is accepted?
Not automatically. Document the sample version, review purpose, scope, and any conditions.
Who should own the master specification?
The buyer should assign a clear owner who controls approved versions and communicates changes.
Does an OEM relationship include design decisions?
Not by definition. Confirm whether design support is included and who retains final approval.