POP82 / Bulk production
Bulk Production with Multiple SKUs & Variants
A large order with many variants needs a clear answer to two questions: what is shared, and what changes? Use a variant matrix to connect each deliverable to its drawing, artwork, quantity and receiving identity.
Buena Park, California · POP82
Inside POP82
The details take shape
A view from the POP82 production film. Define the material, dimensions and finish in your project brief.
Plan the project details
- Variant matrix and shared components
- Released quantity per version
- Labels that match receiving records
Distinguish a part, a variant and a kit
A part identifier describes a component. A variant identifies a particular approved configuration, such as a display with a specific graphic. A kit identifies the set delivered to a recipient. Reusing one code for all three can hide a mismatch when only the artwork changes.
Choose identifiers that your purchasing and receiving teams can use consistently. A short internal code is useful when the accompanying record describes it unambiguously. Keep earlier revisions traceable rather than silently replacing a file under the same name.
Use a matrix that exposes shared work
| Item to resolve | What the buyer should supply |
|---|---|
| Variant identifier | The sellable or receivable configuration name. |
| Shared structure | The drawing revision used by more than one variant. |
| Changing elements | Graphic, size, finish, language or component differences. |
| Released quantity | Confirmed quantity for this version, separate from forecast. |
| Allocation | Which destinations or kit identifiers receive the version. |
Check the totals in two directions
Sum the variant quantities to obtain the order’s finished-unit count. Separately, total each component across all variants to establish how many pieces are needed. A shared base may have one combined fabrication quantity even when the finished displays carry several graphic versions.
For illustration, 80 displays with artwork A and 40 with artwork B can use 120 identical bases if the approved structures are the same. The graphic totals remain 80 and 40. If the second graphic needs a different panel size, the base or interface also needs review before treating it as shared.
Freeze each release and record exceptions
Label the issued matrix with a revision and release date, and retain the previous version. When one SKU changes, mark the affected rows and compare the change with work already approved or underway. Confirm the revised scope before assuming the rest of the batch is unaffected.
At receiving, use the same variant names on the packing list. If identical-looking parts are meant for different configurations, identify them through their packaging or agreed markings. The identifier must remain useful after a larger carton is opened.
Before the next step
Questions about your project
Clear answers for planning, approvals and your production brief.
Should every graphic version have a separate bulk order line?
Give each deliverable graphic version a quantity-bearing record, even when its physical structure is shared. This lets the team total common parts while preserving the exact artwork allocation.
How should a late change to one SKU be documented?
Identify the changed row, new file revision and affected quantity. Review its impact on shared parts, packed units and delivery allocations before issuing the revised release.
How can spreadsheet sorting avoid pairing artwork with the wrong SKU?
Keep the SKU, revision, artwork reference and quantity in the same complete row, and sort the entire table rather than a single column. Use stable identifiers that do not depend on row position. Check a few known pairings and reconcile totals after sorting, then issue a dated release copy that the production team can reference.
How should discontinued SKUs appear in a repeat-order schedule?
Keep the earlier release as a reference and clearly identify which SKUs are excluded from the new order. Avoid ambiguous blank quantity cells or carrying old quantities into an active schedule. The new release should distinguish lines to make from historical or discontinued lines, with totals calculated only from the explicitly ordered quantities.
What is the first planning step for Multiple SKUs & variants?
A part identifier describes a component. A variant identifies a particular approved configuration, such as a display with a specific graphic. A kit identifies the set delivered to a recipient. Reusing one code for all three can hide a mismatch when only the artwork changes. Choose identifiers that your purchasing and receiving teams can use consistently. A short internal code is useful when the accompanying record describes it unambiguously. Keep earlier revisions traceable rather than silently replacing a file under the same name.
What information helps start a discussion about Multiple SKUs & variants?
Begin with the intended result and the current project status. Identify variant matrix and shared components, attach the relevant drawing or reference, and separate confirmed requirements from choices still being evaluated.
How can Multiple SKUs & variants help with bulk project planning?
Apply the guidance to each configuration rather than only the total quantity. Record released quantity per version for the relevant version, then list sample quantities, production units and destination allocations separately.
What approvals help put Multiple SKUs & variants into practice?
Connect the actual specification, artwork and acceptance reference to one revision. Resolve variant matrix and shared components with the responsible reviewer; a planning guide does not replace approval of the specific job.
What files support a review of Multiple SKUs & variants?
Supply the current drawing, artwork or reference documents and explain what each one establishes. Include labels that match receiving records in the handoff, label incomplete information and avoid sending conflicting revisions without an explanation.
What should I know about “check the totals in two directions” for multiple skus & variants?
Sum the variant quantities to obtain the order’s finished-unit count. Separately, total each component across all variants to establish how many pieces are needed. A shared base may have one combined fabrication quantity even when the finished displays carry several graphic versions. For illustration, 80 displays with artwork A and 40 with artwork B can use 120 identical bases if the approved structures are the same. The graphic totals remain 80 and 40. If the second graphic needs a different panel size, the base or interface also needs review before treating it as shared.
What should I know about “freeze each release and record exceptions” for multiple skus & variants?
Label the issued matrix with a revision and release date, and retain the previous version. When one SKU changes, mark the affected rows and compare the change with work already approved or underway. Confirm the revised scope before assuming the rest of the batch is unaffected. At receiving, use the same variant names on the packing list. If identical-looking parts are meant for different configurations, identify them through their packaging or agreed markings. The identifier must remain useful after a larger carton is opened.
What needs to be defined for variant identifier in multiple skus & variants?
The sellable or receivable configuration name. For multiple skus & variants, attach the approved variant identifier requirement to the relevant drawing or sample revision. List version differences and their quantities. Flag unresolved choices and changes before release; compare quotations using the same written specification.
What needs to be defined for changing elements in multiple skus & variants?
Graphic, size, finish, language or component differences. For multiple skus & variants, attach the approved changing elements requirement to the relevant drawing or sample revision. List version differences and their quantities. Flag unresolved choices and changes before release; compare quotations using the same written specification.
What needs to be defined for released quantity in multiple skus & variants?
Confirmed quantity for this version, separate from forecast. For multiple skus & variants, attach the approved released quantity requirement to the relevant drawing or sample revision. List version differences and their quantities. Flag unresolved choices and changes before release; compare quotations using the same written specification.
What needs to be defined for allocation in multiple skus & variants?
Which destinations or kit identifiers receive the version. For multiple skus & variants, attach the approved allocation requirement to the relevant drawing or sample revision. List version differences and their quantities. Flag unresolved choices and changes before release; compare quotations using the same written specification.
Explore related services and guides
Your next project
Let’s make the brief real.
Share dimensions, quantity, artwork and your target date with our Buena Park team.
