Hide Cash on Delivery (COD) at Shopify Checkout

Yes. High-value COD orders carry the most risk — a refused parcel at the door ties up expensive stock, wastes a shipping cost you already paid, and often means a long, awkward chase to recover either the goods or the money. You can hide COD above a chosen cart total — hide it over $300, for instance — so a large order must be paid up front while a small, everyday order keeps the convenience of paying on delivery. That split matters because COD's genuine value to a store is real: it converts buyers who wouldn't otherwise trust an unfamiliar checkout with their card details, and removing it entirely for every order would lose those conversions along with the risk. Restricting it only above the value where a refusal actually hurts keeps the upside for small orders while cutting off the exposure on the orders that would sting the most if they came back unpaid.

Partly. On eligible plans Shopify offers payment customizations that can hide a payment method based on a handful of built-in conditions — cart contents, shipping destination, cart total — and for a single simple case, that's a genuine, correct native capability. It's real but limited in practice: the condition set is basic, some capabilities are gated to specific Shopify plans without warning, and there's no way to preview what a rule would actually do or keep a record of what it would have affected before you switch it on. A rules app fills those specific gaps rather than replacing the native capability outright — it can express a richer combination of conditions as one readable rule, tells you up front while you're writing it if your plan would block a particular capability, and lets you preview and monitor the outcome against real orders before it ever changes a live checkout.

Yes — for example, hide COD when the cart contains a made-to-order item that's expensive to remake if the order is refused, or hide it for customers who don't carry a trusted tag you've applied after their first successful order. Both are the same underlying shape: a condition beyond the basic cart-total check most native tools offer, targeting the specific situations where COD's risk actually concentrates on your particular store rather than applying one blanket rule to every checkout. Ruleproof expresses these as plain rules you write and read back as a sentence — 'hide Cash on Delivery when the cart contains [product] or the customer lacks the trusted tag' — and previews them on a test shopper before they ever go live, so you can confirm the rule targets exactly the situations you intended and nothing broader.

No. The rule compiles into a genuine Shopify Function that runs on Shopify's own infrastructure, in the same request as everything else already happening at checkout, typically in a few milliseconds. Nothing is added to your theme, no third-party script runs in the buyer's browser, and no call goes out to an external server mid-checkout to make the decision — all of which are the usual sources of a slow or janky checkout when merchants bolt on third-party logic the wrong way. Because the check runs exactly where Shopify itself expects checkout logic to run, it performs the same way Shopify's own native payment customizations do, rather than behaving like an app that has to round-trip somewhere else before checkout can proceed. A buyer whose cart triggers the rule simply sees COD absent as part of the same page load, with no extra wait or visible step.