Skip to content

Operations

With Checkout Commander, you build operations. An operation mutates an existing checkout element in the category and operation type you configure — it doesn’t create a new shipping rate or payment method, it simply changes what is already there.

Every operation has these visible parts:

  • Operation Name: identifies the operation in the app; customers do not see it.
  1. Enabled status determines whether the operation is active. A disabled operation is saved but does not affect checkout.
  2. Action is the operation logic that performs controls its mutation. What the action does, and how you configure it, varies by operation type — see that type’s own documentation for the details.
  3. Conditions are optional questions about the checkout. All conditions must pass for the operation to apply. See Conditions.

Operation categories group operations by checkout topic. Checkout Commander currently has usable operations for:

  • Shipping Rates, which are the options customers choose for delivery.
  • Payment Methods, which are the ways customers can pay.

The categories are independent. A Shipping operation does not change payment methods, and a Payment operation does not change shipping rates.

An Enabled operation can change checkout after its saved configuration has been published to Shopify. A Disabled operation is not published to Shopify, and does not affect checkout or count toward the active-operation allowance. See App Health for how publishing works.

Your plan provides one shared allowance for enabled operations. Only operations set to Enabled count toward it; disabled operations do not. You can save an operation as disabled when no active capacity is available, then enable it after disabling another operation or changing your plan. See Plans for the allowances.

Operations execute in a set order, and an earlier change can affect what a later operation sees. See Order of operations for how that order works and how to change it.