Merchandise Kit BOM and Variant Matrix: A Pre-Assembly Reconciliation Method

A merchandise kit bill of materials, or BOM, lists what belongs in each pack and how many units of each component it requires. A variant matrix identifies which approved product, artwork, insert, or pack version belongs to each kit type. Used together, they answer a practical question before assembly begins: do the confirmed usable components support the number and mix of complete kits the project requires?

This record belongs after the campaign direction and pack types have been approved. It does not select products, approve artwork, establish supplier scope, or assign gifts to individual recipients. Its job is narrower: turn an approved pack specification into quantities that the buyer, agency, and packing party can reconcile.

Begin with an approved pack specification

If the project still lacks an audience, quantity, budget basis, destination, or required date, begin with the agency merchandise brief. If the agency is still comparing product directions, use the client-ready merchandise shortlist.

Create the BOM only when each proposed pack type has a stable code and version. For example:

• STANDARD-V3
• PARTNER-V2
• SPEAKER-V1

The code should point to one defined set of contents. A label such as "VIP kit" is not enough if two teams use it for different products, inserts, or artwork.

The agency merchandise scope of work checklist should state who supplies the components, who approves the pack specification, and whether assembly, inspection, storage, or fulfillment is included. The BOM records the approved inputs and quantities. It does not create those responsibilities.

Give every component a precise identity

"Notebook" or "welcome card" may be clear in conversation but is too loose for an assembly instruction. Record the exact item or document reference available to the project, including the variant and version where those details matter.

A component row may need:

• Product or component reference.
• Color, size, finish, or other approved variant.
• Artwork or decoration version.
• Insert file and language version.
• Unit of measure.
• Units required in one pack.
• Pack types that use the component.
• Date or project stage for which the row applies.

This resembles the way established BOM systems separate the component item, quantity per assembly, unit of measure, sequence, revision, and effectivity. The Oracle JD Edwards bill-of-material documentation is one example of that structure. It is an ERP reference, not a requirement to use JD Edwards or to copy its fields into every merchandise project.

Shopify's developer documentation provides another useful distinction. Its bundle-app example represents components with exact variant references and aligned quantities, while distinguishing fixed bundles from mix-and-match offers. A campaign kit may be managed outside Shopify, but the underlying lesson still applies: the component reference and its quantity must stay paired. This article does not state that openXpromo or any particular store uses a bundle app.

Copy this blank BOM and variant matrix

Use one row for each exact component and variant combination. If the same notebook carries different artwork in two kits, those are separate rows. If the same undecorated notebook is shared without a configuration change, it may use one component reference with demand allocated across both pack types.

Calculate total units required as:

units per pack × complete kits required

First reconcile the usable pool for each exact component and variant:

"Confirmed physical quantity" should come from the project's accepted evidence, such as a receiving count or another agreed source. "Reserved or unusable" can include approved samples, damaged pieces, or units already committed elsewhere. Do not treat a catalog quantity, purchase quantity, shipping notice, or printed packing slip as a usable count unless the project owner has accepted it for that purpose.

Then allocate shared pools before calculating any pack capacity:

If a required value is unknown, write unknown. Do not enter zero merely to make the worksheet calculate, and do not call the kits available. When the pool and every allocation are known, unallocated is the confirmed usable pool minus the total allocated. A negative result means the allocation is invalid; it is not permission to borrow from another variant.

Calculate complete-kit capacity conservatively

For one fixed pack type, the theoretical complete-kit capacity is limited by the component that supports the fewest packs:

complete-kit capacity =
minimum of floor(allocated confirmed usable quantity ÷ units required per kit)

Shopify uses this same limiting-component logic when it calculates bundle availability from tracked component inventory. Its bundle eligibility and inventory guidance also describes exclusions for components whose inventory is not tracked or that can continue selling when out of stock, and it distinguishes bundle and component SKUs. That is evidence about Shopify's bundle behavior, not evidence about inventory held for a merchandise project.

For a buyer-side worksheet, use only confirmed usable quantities. If two pack types share a component, allocate that component across the approved demand before calculating capacity for each pack type. Otherwise, the same units may be counted twice.

Any unknown critical component makes final complete-kit capacity unknown. A partial calculation can still identify which facts need attention, but it cannot authorize assembly or promise a delivery quantity.

A synthetic two-pack example

The figures below are fictional and do not describe a customer, supplier, product, stock position, price, or delivery date. Assume the example requires 80 Standard kits and 20 Partner kits.

The notebook is shared, so its combined demand is 100 units. Suppose the accepted count shows these usable quantities:

The Standard kit has enough listed components for its required 80 units. The Partner kit is limited to 19 because the white bottle is one unit short. The arithmetic therefore supports 99 complete kits in this fictional mix, not 100.

The remaining components do not become an additional complete kit. The worksheet also cannot choose among replacing the bottle, reducing the Partner quantity, changing the kit specification, or obtaining another unit. Authorized project owners must choose a response and confirm its effects on cost, proof, assembly, and timing.

Control versions without mixing approvals

A variant matrix should reference approved artwork and insert versions, not determine whether a logo may be used. Keep brand authority and proof approval in their existing records. The sample and artwork approval checklist covers what a proof or physical sample can establish.

When a component, quantity, or file changes, issue a new pack version or record the applicable effectivity. Do not overwrite the old instruction after labels, picking, or assembly may have started. Record:

• The prior and revised pack versions.
• Rows affected by the change.
• Quantities already picked or assembled.
• The decision owner and timestamp.
• Whether the packing party has acknowledged the revision.
• Any units placed on hold pending a decision.

GS1 treats a predefined assortment as a fixed composition whose identity changes when the assortment changes. That principle supports clear version control. It does not mean an ordinary campaign kit must receive a GTIN.

Do not assume an overrun or shortage allowance

A percentage allowance should come from the actual order and applicable supplier terms. It should not be copied from an industry article or another supplier's policy.

A 2017 PPAI editorial discussion reported ranges of 5 to 10 percent, 5 to 12 percent, and exact-quantity approaches. It is not a current standard; the useful finding is that the published practices differ. Beacon's all-products policy lists requested purchase-order fields and its own 5 percent over-or-under rule. That is one supplier's policy, not an openXpromo term, a universal percentage, or evidence for any particular order.

Keep ordered quantity, received quantity, confirmed usable quantity, complete-kit requirement, and any accepted tolerance in separate fields. If a shortage remedy or ownership of extra units matters, resolve it in the project-specific written terms.

End with a release question

A completed matrix should lead to one recorded decision:

• Release the confirmed pack version for the quantity supported by current evidence.
• Hold one or more pack types while a component, count, or approval remains unresolved.
• Approve a revised quantity or pack version.
• Request a project-specific supplier response to a shortage or excess.
• Stop a route that no longer satisfies the brief.

The matrix itself does not authorize production, assembly, or shipment. Attach the decision to the exact BOM version and preserve the evidence used for the count.

Recipient assignment comes later. For individual shipments or multiple offices, use the multi-address corporate gifting guide to map approved kit codes to a controlled manifest and release wave. For event stock already received, the tech conference merchandise stock plan covers booth, meeting, and speaker allocations. Neither downstream record should silently change the approved pack contents.

To discuss a multi-component merchandise project, send openXpromo the project brief with the pack types, required quantities, component or product references, approved branding, broad destinations, budget basis, and required date. Product, decoration, packing, availability, costs, and timing remain subject to project-specific written confirmation.