maintain-inventory-for-a-product-bundle

Maintain inventory for a product bundle

Tags: Bundle, Inventory, Products, SKU, Sync

Use this task to automatically sync inventory for a simple product bundle – no theme modifications required. When configured with unique SKUs for the bundle and its components, and with quantities needed from each component for each bundle unit, this task keeps the bundle inventory set to the greatest possible value, given the quantities of its components. It also appropriately subtracts from component inventory whenever the bundle is ordered, and appropriately raises component inventory when a bundle order is refunded and restocked.

• View in the task library: tasks.mechanic.dev/maintain-inventory-for-a-product-bundle
• Task JSON, for direct import: task.json
• Preview task code: script.liquid

Default options

{
  "bundle_product_sku__required": "BUNDLE",
  "component_product_skus_and_quantities_per_bundle__keyval_number_required": {
    "BUNDLE-A": 1,
    "BUNDLE-B": 2,
    "BUNDLE-C": 3
  },
  "inventory_buffer_quantity__number": "1"
}

Learn about task options in Mechanic

Subscriptions

shopify/orders/create
shopify/refunds/create
shopify/inventory_levels/update
mechanic/user/trigger

Learn about event subscriptions in Mechanic

Documentation

Use this task to automatically sync inventory for a simple product bundle – no theme modifications required. When configured with unique SKUs for the bundle and its components, and with quantities needed from each component for each bundle unit, this task keeps the bundle inventory set to the greatest possible value, given the quantities of its components. It also appropriately subtracts from component inventory whenever the bundle is ordered, and appropriately raises component inventory when a bundle order is refunded and restocked.

Usage:

• Run this task manually to sync the bundle's inventory with that of the component product that has the least inventory in stock.
• This task will run automatically whenever the bundle product is ordered, and whenever the bundle product is refunded in such a way that it is restocked.

Requirements:

• This task only considers inventory from the default location configured in the shop.
• Configure this task with a unique SKU for the bundle product. The bundle product SKU must not be re-used by any other products.
• This task can sync inventory across multiple product variants sharing the same component SKU. But, if a single SKU is used for multiple variants in the same store, all such variants must start with and maintain equal inventory levels.
• Use the right-hand side of the "Component product SKUs and quantities per bundle" option to control how many units of each component SKU is required for each single bundle unit. If your bundle requires one wrench and two sprockets, for example, make sure to add "1" and "2" on the right-hand side, each number associated with the right SKU.

Notes:

• Whenever this task runs, any inventory updates to the bundle product will be overwritten. For the purposes of this task, the bundle's inventory is exclusively derived from the inventory of its components. (This also means that this task does not support "nested" bundles, in which a bundle component product is itself a bundle managed by another copy of this task.)
• Feel free to manually adjust inventory for component products, keeping in mind that components with shared SKUs must be kept equal to each other. The bundle product's inventory will be synced appropriately.
• Use the "Inventory buffer quantity" option to artificially keep the bundle product's inventory lower than the actual available quantity.

• Fulfillment order moves (i.e. between locations) containing the bundle product SKU will be ignored by this task.

Installing this task

Find this task in the library at tasks.mechanic.dev, and use the "Try this task" button. Or, import this task's JSON export – see Importing and exporting tasks to learn how imports work.

Contributions

Found a bug? Got an improvement to add? Start here: ../../CONTRIBUTING.md.

Task requests

Submit your task requests for consideration by the Mechanic community, and they may be chosen for development and inclusion in the task library!