Answer first
A distributor should review a mixed-channel MOQ and pack-size brief as a quantity-and-data decision, not as one grand total. First, separate the intended demand by channel, destination market and proposed SKU. Next, show the sellable unit, inner pack, master case and any proposed pallet pattern for each SKU. Then distinguish the supplier’s indicative MOQ from the distributor’s purchase quantity, the channel’s order increment and the number of units each channel can practically receive.
The useful outcome is a short brief that exposes assumptions before anyone treats them as a commitment. It should show which quantities are preliminary, depend on a sample or final configuration, or need destination-market confirmation. It should also state whether a proposed case contains one SKU, a defined assortment or a promotional bundle.
Do not start with “What MOQ can we get?” Start with “What quantity can each channel receive, in what pack structure, for which proposed SKU and market?” A distributor can then ask Toywink for a channel-aware discussion without implying that a specification, price, availability, compliance position or delivery timing has been agreed. This approach also gives procurement a clear record of what requires confirmation.
Why a blended total can hide the actual decision
“Mixed channel” often means more than one route to market. Routes can have different order patterns, carton preferences and destination-market documentation needs. Combining every estimate into one number may help an internal forecast, but it is not enough to judge an order proposal.
An indicative MOQ is a supplier-side commercial starting point for a proposed configuration. A case pack is the number of units placed together in a defined outer case. A channel allocation is the quantity intended for a particular route to market. These can match, but they are not interchangeable. An order may meet an indicative MOQ while producing awkward residual units for a channel. Conversely, several channel estimates may look attractive in total but fail to meet the applicable quantity basis if they are spread across different proposed SKUs, artwork versions, languages or packaging formats.
Keep the quantity basis visible. Ask whether the discussion is based on one product version, one colour, one packaging version, one assortment, one purchase order or another agreed basis. Do not infer the answer from a catalogue image, a prior inquiry or a similar item. The answer can be SKU-, sample- and destination-market-specific.
Pack levels also need plain names. GS1 describes a trade-item hierarchy in which separate GTINs can represent a specific unit, pack, case or pallet. It also distinguishes the base, consumer, orderable and shipping roles, which may not be identical. [1] That is a helpful way to structure a brief even when a distributor is only at an exploratory stage: identify what is sold, what is ordered and what is shipped instead of using “pack” for all three.
Build the channel map before discussing quantity
Start with a one-page channel map. Give every proposed allocation a channel owner, destination market, timing window and confidence label. “Working estimate” is more honest than a number copied from a forecast. A row that cannot name its proposed SKU or market should remain separate rather than being added to a decision total.
Use three demand states: committed for an internally approved purchase scenario, qualified for stated interest subject to conditions, and exploratory for a directional figure. Do not merge them. A total containing all three is a planning range, not an order request. Record the owner for later quantity or case changes.
Translate demand into a pack-level working sheet
For each row, capture the proposed SKU or internal reference, destination market, channel, unit quantity, requested case quantity, full cases, residual units and any reason for a non-standard request. Do not populate product details or certifications from assumptions; mark them “confirm for proposed SKU/sample.”
| Review option | What the distributor records | When it can be useful | Main review question |
|---|---|---|---|
| One SKU, one standard case | Proposed sellable unit, units per case and full-case allocation | A channel can receive consistent cases | Does the proposed channel allocation divide into the confirmed case quantity? |
| One SKU, channel-specific handling request | Base case plus a requested split, label or handling step | A channel has a stated operational constraint | Is the request feasible for the proposed SKU, market and order quantity? |
| Defined assortment | Every included proposed SKU and its count per assortment | A channel is evaluating a fixed mix | Is the mix a separately identifiable, agreed configuration rather than an informal blend? |
| Separate orders by channel | A quantity and pack structure for each channel | Markets, labelling or commercial terms differ | Would combining them conceal a different packaging or destination requirement? |
The sheet is not a promise that an option is available. Keep each row’s market and channel identity until an authorised reviewer confirms that it can be consolidated.
A simple calculation can help without manufacturing false precision:
Proposed full cases = intended channel units ÷ confirmed units per case.
If the result is not a whole number, flag the remainder rather than quietly rounding it. The choices may be to adjust the allocation, obtain a confirmed alternative, separate the channel request, or retain the remainder as an unresolved decision. The correct path depends on the proposed SKU, sample, commercial terms, warehouse process and destination market. It should not be assumed from a generic “wholesale pack size.”
Need a structured starting point? Email Toywink with the proposed SKU, sample status, destination market and channel quantities for an MOQ and pack-size discussion.
Separate the four quantity questions
A sound brief answers four different questions in separate fields.
1. What is the supplier-side starting quantity?
Ask for the indicative MOQ, the unit of measure and the conditions that may affect it. The response could be tied to a proposed SKU, finish, packaging version, artwork, order timing or other commercial detail. Record the answer as “to be confirmed” until the relevant configuration has been discussed. Do not present an indicative MOQ as a standing Toywink policy or a fixed offer.
2. What is the distributor prepared to purchase?
This is the internal purchase scenario. It should be stated in units and, where relevant, in complete cases. Include the confidence state from the channel map. A cautious brief can show a base scenario and an upside scenario, but it should not use the upside to imply committed demand.
3. What can each channel receive?
A channel allocation can be smaller or larger than a case, depending on the confirmed commercial and operational approach. State the intended quantity, whether it is full-case only, and any known delivery-point or warehouse requirement. Avoid assuming that a retail account, marketplace or education-related channel has a universal rule. Its requirements may change by programme, destination and time.
4. What will travel together?
This is the physical pack decision. Identify the confirmed case count, whether cases are single-SKU or mixed, and whether any inner pack or pallet information is needed. GS1’s hierarchy guidance is useful here because it treats unit, pack, case and pallet as distinct trade-item levels and notes that the orderable unit may differ from the shipping unit. [1] The distributor does not need to create identifiers prematurely, but it should know which level is being discussed.
Test the commercial baseline before requesting an exception
A supplier conversation is easier when the distributor first presents a baseline: proposed SKU, sample status, market, channel allocation, intended total, preferred case structure and open questions. Record a different case quantity, label, assortment or allocation as a request, not an assumption.
This distinction protects both parties from vague language. “Carton of 24” might mean 24 individual sellable units, 24 inner packs, or a generic placeholder. “MOQ of 1,000” might be stated per proposed design or for a different configuration. The brief should ask for the exact measurement and not convert it silently.
Use an exception log with requested change, reason, affected channel, proposed SKU and decision owner. Add evidence where a channel instruction drives the request. A sample can clarify a question, but final pack information still needs confirmation for the proposed configuration.
Trade terms should remain separate from pack math. ICC explains that Incoterms® 2020 rules allocate responsibilities, costs and risk between buyer and seller under the selected rule. [2] In the brief, record the requested trade term and named place only as a commercial item to be confirmed. Do not use a trade term as a shortcut for who will split cases, label goods, arrange channel preparation or meet a particular programme’s rules.
Compare pack approaches without assuming a universal best answer
The table is a decision aid, not a pack recommendation. A smaller case may offer allocation flexibility while a larger case may simplify one warehouse flow. The right conclusion follows the confirmed SKU, channel evidence, commercial proposal and destination-market review.
| Approach to compare | Potential planning advantage | Potential issue to test | Evidence needed before it is treated as a plan |
|---|---|---|---|
| Standard master case | Clear full-case arithmetic for a proposed allocation | A channel estimate may leave a remainder | Confirmed units per case and channel allocation |
| Channel-specific case request | May align with a documented channel need | May create a configuration or handling exception | Written channel requirement and supplier confirmation for the proposed SKU |
| Predefined assortment | Lets the buyer assess a specific mix as one item | Individual SKU quantities may no longer align with demand | Exact assortment bill of materials, identifiers if applicable, and market review |
| Distributor-side allocation after receipt | Keeps the supplier request focused on a base pack | Distributor warehouse may need a controlled process | Warehouse capability, destination requirements and ownership of any rework |
Avoid treating the easiest arithmetic as the lowest-risk answer. A neat whole-case total can still be inappropriate if it relies on unconfirmed product data or a packaging assumption that does not suit the destination. Conversely, a remainder is not automatically a supplier problem. It is a prompt to decide whether the allocation, pack proposal or channel plan should change.
Put destination-market checks beside the affected row
Destination market belongs in the brief because packaging, labelling, import and product documentation questions may affect the proposal. The European Commission’s import guide advises businesses to assess product-specific import conditions, duties, safety and technical requirements, packaging and labelling rules, and customs documentation for the relevant EU context. [3] That does not establish what applies to any Toywink SKU or another destination.
For a U.S.-focused children’s product proposal, CPSC guidance says products within scope may require testing and a written Children’s Product Certificate, with exceptions or exemptions depending on the regulation. [4] Confirm current requirements for the product and import route. Retain the market, proposed product identity and document owner beside the channel quantity.
Do not add generic compliance language to every case row. Instead, create a destination-review flag: “not started,” “information requested,” “under review,” or “confirmed by responsible party.” The last status should identify the evidence and reviewer internally. It should never be inferred from a pack image, a previous market or a statement about a similar SKU.
Mixed-channel MOQ and pack-size brief checklist
Before sharing the brief, make sure it can be read by procurement, operations and channel teams without a separate explanation:
- Scope: Name each proposed SKU or internal reference, the relevant sample status and the destination market. Separate unlike configurations.
- Channel map: Show each channel’s quantity, confidence state, owner and timing window. Keep committed, qualified and exploratory quantities distinct.
- Pack hierarchy: State the sellable unit, inner pack if applicable, master case and any pallet information as “confirmed” or “to be confirmed.”
- Quantity basis: Record the indicative MOQ question and the basis on which an answer is requested. Do not label it fixed before confirmation.
- Arithmetic: Show intended units, confirmed units per case, full cases and remainders. Flag rounding choices for approval.
- Exceptions: List every requested non-standard handling, assortment, label or case change with its reason and decision owner.
- Market review: Put the market, regulatory or import-information owner, and document status next to the relevant row rather than in a generic appendix.
- Commercial terms: Record the requested Incoterms® rule and named place as subjects for agreement, separate from packaging assumptions.
- Version control: Date the brief, name the internal owner and retain a change log. A channel total should be traceable after a quantity or pack revision.
A checklist should reveal gaps. If master-case quantity is unknown, leave it unknown. If a channel has not supplied a written requirement, do not call it mandatory. Record any sample or destination-market dependency.
How to run the internal review meeting
Limit the meeting to decisions that change the request. Confirm that rows describe the same proposed SKU and package version, then review quantity basis, case arithmetic, exceptions and destination-market owners. The output should show: accepted internally, needs supplier clarification, or needs channel or market evidence. It is not a production instruction. If a forecast changes, revise the allocation and rerun the arithmetic; create a new review line where the change affects product, packaging, documents or destination.
FAQ: mixed-channel MOQ and pack-size planning
Is MOQ the same as a case pack?
No. An MOQ is a commercial quantity question that should be confirmed for the proposed SKU and configuration. A case pack is a physical quantity within a defined case. An order may satisfy an indicative MOQ but still leave allocations that do not fit full cases. Ask for both values and their stated basis rather than deriving one from the other.
Can we add quantities from retail, e-commerce and wholesale channels together?
They can be totalled internally only after the brief shows the same proposed SKU, version, market and pack assumption. Keep rows separate where a channel needs a different label, assortment, market treatment or handling step.
Should a sample determine the final case pack?
No. A sample can help ask targeted questions, but does not confirm final packing, documents, accessories, language, power arrangement or case quantity. Request confirmation for the proposed configuration and destination.
What should we send in an MOQ inquiry?
Send the proposed SKU or reference, sample status, destination market, channel breakdown, purchase scenario, requested pack information, exception request and open questions. Keep any trade term and named place separate from case-pack calculations.
Can a distributor split cases after import?
It may be an internal option, but it should not be assumed. Check the distributor’s warehouse capability, the relevant channel’s instructions, the destination-market implications and responsibility for any relabelling or repacking. Record it as a separate operating decision rather than presenting it as part of the supplier’s pack commitment.
When should the brief be locked?
Lock an internal working version when it has a named owner, a date, clear assumptions and a decision status for each meaningful row. It can still change. When a change affects a proposed SKU, pack level, destination market or quantity basis, issue a new version and state what changed. That is safer than overwriting a number and losing the reason behind it.
A clear brief does not force an early answer. It gives every party a common view of what has been proposed, what still needs confirmation and where a mixed-channel plan could create a pack or market dependency. For a cautious review of a proposed SKU, sample, destination market and channel allocation, email Toywink’s team.