Key takeawaysEducational toys span many activity forms; identify what the user does before choosing a product category. ^[1] · OEM commonly describes manufacturing to another party’s requirements, but the actual scope varies. ^[2] · Private label concerns branding context and does not define design ownership or every customization. ^[3] · Procurement begins with a defined need, making a product-service matrix useful for comparing proposals. ^[4]

A supplier catalogue may list science kits, craft kits, party activities, and other educational products alongside services such as OEM, ODM, OBM, private label, customization, and packaging. Buyers can misread the list as a menu where selecting a product category automatically selects a complete service package. In practice, product and service are separate dimensions.

This article offers a practical way to map them. Start with the user experience, identify the product form, and then decide what support the brand needs to develop, adapt, manufacture, package, or present it. The goal is to ask specific questions before assuming that a broad label defines the work.

Map the product by user activity, not just its name

Write what the participant does. Does the user observe, assemble, create, compare, or play a group game? Educational toys include a wide range of activity forms, so the category name alone does not explain what a product offers. ^[1]

Identify the intended user and setting. A product for home use may have different instructions and packaging needs from a classroom or museum activity. Note adult support, group participation, setup, cleanup, and any household materials the user must provide.

Give each proposed product a short role statement. A science kit may introduce a specific observation; a craft kit may support a creative sequence; an activity kit may organize group play. These descriptions help buyers decide whether products are meaningfully distinct or merely use different themes.

Keep the learning or play claim proportionate to the task. A broad STEM label does not guarantee mastery or a specific outcome. Describe what the participant can do and what the product is intended to introduce.

Separate product category from service model

After defining the product, identify the starting point. The brand may have a finished specification, an early concept, an existing item to adapt, or only a market need. Each starting point may require different supplier input.

OEM is commonly associated with producing goods to another party’s requirements, although project usage can vary. ^[2] Ask whether the supplier is manufacturing against a complete specification, helping select components, adapting a design, or providing other development work.

Private label usually concerns selling under the buyer’s or retailer’s label. ^[3] It does not necessarily mean that the buyer designed the product, has exclusive rights, or may customize every component. Clarify branding, development, and manufacturing scope separately.

ODM, OBM, customization, and packaging may also be used differently by providers. Ask for plain-language definitions and a list of deliverables for the project. Do not assume an acronym or service heading resolves responsibilities, rights, or review needs.

Build a product-service matrix for the brief

A simple matrix can connect each product to the services under consideration. Rows may include product concept, activity, components, instructions, artwork, package, sample, and destination information. Columns can identify current state, desired support, buyer owner, supplier role, and open question.

Mark each decision as required, preferred, or undecided. A brand may require a specific activity but remain open to package format. Another may have finalized artwork but need help defining component options. This classification helps the supplier respond without guessing which points are negotiable.

Procurement involves identifying a need and obtaining goods or services to meet it. ^[4] A matrix makes the need more precise and allows the buyer to compare proposals against the same set of questions instead of relying on a broad product category or service label.

Add a column for evidence or deliverables. A sample, drawing, package proof, or component list each answers different questions. Specify which deliverable would help close an open decision and who reviews it.

Match product complexity to the requested support

A product with a clear activity and stable component list may need a different service discussion from a concept whose use sequence is still uncertain. Identify which decisions can be made internally and which would benefit from supplier input. The brand remains responsible for its product objectives even when it requests design support.

Consider dependencies. A change to a component can affect the user task, instructions, package dimensions, images, or safety review. A change to brand copy may affect package layout or translation. Ask the supplier which dependencies it sees and record them as questions before approving a change.

Avoid treating every service as necessary for every product. A package design may be complete while a product sample remains open; a product may be defined while market review is pending. The matrix should reflect what this project needs rather than repeat a generic service list.

If a product family is planned, identify which elements are shared and which are product-specific. Brand assets may be reused, while component descriptions and directions require separate versions. Keep shared and unique tasks clearly distinguished.

Check samples and package information against the map

Request samples to answer specific questions. A visual mock-up may help assess package hierarchy; a functional sample may show how the activity works; a component sample may address handling. State which elements are provisional and what the sample cannot establish.

Review each output against the matrix. Does the sample include the agreed components? Do directions match the task? Does the package describe the current version? Are supplier suggestions reflected as proposals or approved changes? This keeps product review connected to the scope discussion.

Separate usability, quality, safety, and educational-claim reviews. A prototype can reveal confusion but does not automatically prove compliance or a learning outcome. Assign specialist questions to appropriate reviewers and keep their conclusions linked to the exact product version.

Update the matrix when decisions change. If artwork or activity changes, note which files and approvals are affected. A product-service map is most useful as a working record, not a one-time intake form.

Use supplier information as a starting point, then confirm scope

A public catalogue can help buyers understand the supplier’s stated product categories and service areas. It should prompt focused questions: which product formats are relevant, which development inputs are available, and what does the buyer need to supply?

K&M publicly describes educational toy products and OEM/ODM services. Buyers can use that information to begin a project-specific conversation about product fit and supplier scope. ^[2] www.knmint.com The link is a starting point for public supplier information, not confirmation of a particular service package, design, price, schedule, capacity, certification, or guarantee.

Ask for a scope summary in plain language. It should state what will be developed or produced, what the buyer supplies, which samples or files will be delivered, who approves them, and what remains outside scope.

A useful product-service map helps a buyer reach that summary with fewer assumptions. It shows how the product’s real activity connects to the service requested and leaves unresolved questions visible until they are answered.

Frequently asked questions