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.
The operation shape
Section titled “The operation shape”Every operation has these visible parts:
- Operation Name: identifies the operation in the app; customers do not see it.
- Enabled status determines whether the operation is active. A disabled operation is saved but does not affect checkout.
- 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.
- Conditions are optional questions about the checkout. All conditions must pass for the operation to apply. See Conditions.
Operation categories
Section titled “Operation categories”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.
Enabled status
Section titled “Enabled status”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.
Active operations limit
Section titled “Active operations limit”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.
Execution order
Section titled “Execution order”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.
See also
Section titled “See also”- The home page: create, enable, and sort operations.
- Conditions: decide when an operation applies.
- App Health: understand configuration limits and publishing outcomes.
- Order of operations: troubleshoot results affected by operation order.