A bundle and its components are both being counted as stock to pick

The parent and its parts are one obligation, not two

A bundle is a selling unit assembled from other sellable units. Shopify's bundle documentation captures the structure: the bundle carries its own SKU, distinct from the SKUs of its components; whether a bundle is available depends on the availability of its components and the quantities of each it requires; and order and fulfillment representations can include the component line items. That last point is the trap. A system that shows the parent line and the component lines may be displaying one obligation in two views — or it may be instructing two picks, depending on how the feed was built.

The documentation does not say which representation your warehouse received, and it does not say that both parent and components should be independently picked. That question is answered by your bundle definition and your integration's actual output, not by the presence of both kinds of rows on a screen.

Define the physical requirement of one bundle unit first

Before touching the order, write down the bundle definition: which components belong to the bundle and how many units of each one bundle unit requires. Multiply by the number of bundle units ordered. The result is the physical pick requirement, expressed in component units, and it is the only quantity the warehouse should consume for that line.

Keep the units straight at every handoff. If components are themselves sold in different pack sizes than the bundle uses, apply the documented conversion rather than counting labels. If the bundle includes an item the warehouse does not stock as a loose component — a pre-assembled kit, for example — record that as a different fulfillment path instead of forcing it into the component arithmetic.

Trace what the warehouse feed actually transmitted

Compare three records for one genuine bundle order: the order representation in the store, the fulfillment representation if the platform has one, and the pick list or payload the warehouse received. Establish whether the integration sends the parent line and lets the warehouse explode it into components, sends pre-exploded component lines, or sends both. Each design is workable; each fails differently. A warehouse that explodes a parent it was also sent as components will double-pick. A warehouse that expects components but receives only a parent SKU it does not stock will stall or guess.

Do not generalize from one integration. A bundle app, a native platform bundle, and a custom feed can all represent the same order differently, and the behavior of yours is established by inspecting its output on real orders — or its documentation — not by analogy. If the feed's behavior cannot be determined from available records, that is an open question for the integration owner, not a reason to pick both rows and reconcile later.

Count each unit of stock exactly once

After the pick requirement is fixed, inspect how inventory moved. Determine whether the platform deducted stock at the parent level, at the component level, or both, using the actual inventory history for the affected SKUs. Shopify's bundle availability depending on component availability implies components are the stock being consumed; if your records show the parent SKU also holding and losing a quantity, find out what that parent quantity physically represents before adjusting anything.

Reconcile by matching units, not lines, but do not treat dual decrements as automatically erroneous. If both a parent quantity and component quantities moved, establish what each quantity represents before correcting anything: whether the parent quantity is virtual or derived from components, reflects pre-assembled kits, or is a separately stocked item; whether assembly occurred; and whether the order actually dispatched. Only after those checks should the inventory owner decide whether a reversal or adjustment is warranted, with the evidence attached. If deductions are missing, check fulfillment and dispatch records and the integration's posting behavior before concluding that stock was or was not consumed; a missing deduction alone does not prove shipment, and shipment alone does not prove which level should have been deducted. Never net discrepancies against each other and call the totals close enough.

Assign the repair to the right owner

Three different repairs belong to different owners here. The pick list for open orders is an operations correction: reissue it in component units and recall the duplicated instruction before the warehouse doubles a shipment. The stock correction is the inventory owner's decision, made against the documented deduction history and only after each moved quantity is understood. The feed behavior is the integration owner's repair, made only after its actual output is known.

Record the outcome as: representation explained and single count confirmed, duplicate count found and corrected at a named level, or unresolved with an owner. If the feed or bundle configuration is the concern you want scoped help with, a Prism consultation can discuss the storefront and integration setup you describe; confirm scope, responsibilities, fees, and terms before work, and keep order exports and customer details out of the inquiry.

Parent-to-component obligation table

Complete one table per genuine bundle order before picking or adjusting stock. The physical requirement row governs the pick; every other row explains how systems represented or consumed it. Write unknown where a record is absent rather than assuming the integration's behavior.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.