Operations overview
Every rule in Checkout Commander is an operation: a small “when these conditions are true, do this” statement. You can have many operations, on the same checkout surface or across both.
The rule shape
Section titled “The rule shape”Every operation has three parts:
- Conditions — a list of
ifstatements. All conditions must be true for the operation to fire. See Conditions. - Match — which shipping rates or payment methods the operation is about. (For example, a hide operation that targets a specific rate name.)
- Action — what to do: hide, rename, or sort. The shape of the action depends on the operation type.
A simple shipping hide operation reads as English:
When the cart weight is over 5 kg and the customer’s country is CA, hide the shipping rate titled “Standard”.
Three operation types
Section titled “Three operation types”- Hide — remove a rate or method from the list. Shipping has four modes; payment has two. See Hide shipping rates and Hide payment methods.
- Rename — change the display name. Supports per-locale translations on Developer and Pro plans. See Rename shipping rates and Rename payment methods.
- Sort — change the order of rates or methods. Shipping supports field-based and custom (bucket) sorts; payment only supports custom sorts. See Sort shipping rates and Sort payment methods.
Two surfaces
Section titled “Two surfaces”You build operations for one of two surfaces:
- Shipping — affects the list of delivery options the customer picks from at checkout.
- Payment — affects the list of payment methods the customer picks from at checkout.
The surfaces are independent. A hide operation on a shipping rate doesn’t affect payment methods, and vice versa.
Per-surface parity
Section titled “Per-surface parity”The two surfaces are intentionally similar but not always identical:
- Hide: shipping has four modes (Hide, Show, Lowest, Highest); payment has two (Hide, Show). Payment also has the concept of placements — a hide can target one or more placements (e.g. accelerated checkout only).
- Rename: shape is the same. Multi-locale translations are gated to the same plans.
- Sort: shipping supports field-based and custom sorts; payment only supports custom.
If a feature exists on one surface and not the other, the per-surface guide calls that out.
Enable and disable
Section titled “Enable and disable”Every operation has an enable/disable toggle in its form. Disabled operations stay in the database and keep their position in the list, but don’t run. Use this to temporarily turn off a rule without deleting it.