Browse apps

Guides

How to Stop Fake Cash on Delivery (COD) Orders on Shopify

TL;DR

To stop fake Cash on Delivery (COD) orders and reduce Return to Origin (RTO) losses on Shopify, enforce server-side Cart and Checkout Validation rules before order creation. In LabX Fraud Filter, you can block placeholder phone numbers, disposable email domains, unserviceable ZIP codes, unsupported countries, and repeat-RTO customer tags at checkout while filtering bots on the storefront.

Offering Cash on Delivery (COD) on Shopify removes payment friction in markets where shoppers prefer paying the courier in cash or on doorstep terminals. However, because a COD checkout requires zero upfront payment authorization, it is also the easiest target for fake COD orders on Shopify, competitor inventory lockup attacks, and costly Return to Origin (RTO) parcels where the courier arrives at a fake address or the buyer simply refuses delivery.

Unlike credit card fraud—which leaves a trail of card verification failures—a bogus COD order looks like a normal manual-payment purchase until your warehouse packs the box, pays outbound shipping, and absorbs the return freight fee weeks later. Waiting until after the order is created to inspect every phone number and postal code by hand does not scale when prank orders or automated scripts flood your checkout.

In this guide, we break down how to block COD (Cash on Delivery) fraud on Shopify before an order is ever created using server-side Cart and Checkout Validation Functions, how to configure phone, email, postal code, country, name, and customer tag rules in LabX Fraud Filter, and how to combine checkout validation with native Shopify controls. For a full look at protecting both your storefront and checkout, see our Shopify fraud prevention guide.

Why are fake Cash on Delivery (COD) orders and RTO so costly on Shopify?

When a credit card fraudster places an order, the primary risk is a future chargeback and non-refundable gateway fees. When someone submits a fake Cash on Delivery order, the damage hits your fulfillment operations and cash flow directly:

  1. Outbound and Return to Origin (RTO) courier fees: When a parcel is dispatched to a fake street address, an unreachable phone number, or a serial impulse buyer who refuses the package at the door, the carrier charges you both outbound shipping and RTO return freight.
  2. Inventory lockup during peak campaigns: Competitors or bad actors can submit dozens of high-quantity COD orders using throwaway emails (@mailinator.com, @yopmail.com) and placeholder phone numbers (0000000000). Shopify deducts those units from your available stock immediately, leaving real paying customers staring at an out-of-stock button during your flash sale.
  3. Wasted warehouse labor and packaging: Pick-and-pack teams spend time printing labels, boxing items, and calling invalid mobile numbers to confirm orders that were never real.
  4. No credit card signals in default Fraud Analysis: Because COD is processed as a manual payment method without card authorization, standard card checks like CVV and AVS do not run. If your defense starts after checkout completes, the fake order is already sitting in your fulfillment queue.

To reduce COD RTO (Return to Origin) on Shopify, you have to stop bad buyer data at the checkout form before Shopify creates the order record.

How do you restrict COD by order value, phone, country, and buyer identity?

Merchants searching for ways to restrict COD by order value, phone, and country are actually solving two separate technical problems in Shopify’s checkout architecture: controlling when the COD payment option appears versus blocking invalid or abusive buyer details from completing checkout.

Understanding which tool handles each responsibility prevents gaps in your checkout defense:

Control LayerWhat It ChecksWhere It RunsCan a Buyer Bypass It?Best Used For
Native Shopify Shipping & Payment ControlsCart order value, weight, shipping zone, or payment method customizationOn Shopify’s servers during shipping/payment selectionNoLimiting COD availability to specific shipping rate price ranges, weights, or domestic zones
Storefront Blocking (Fraud Guard app embed)Visitor IP, CIDR range, country, region, ISP/ASN, device, Tor exit nodes, datacenter hosting trafficIn the visitor’s browser on storefront pagesYes—by disabling JavaScript or calling the Cart API directlyStorefront traffic and bot blocking before bots or outside-region visitors browse your catalog
Checkout Protection (Cart & Checkout Validation Function)Buyer Email, Phone, Name, Country, Zip, and Customer tagServer-side on Shopify’s checkout infrastructureNo—enforced on every cart and checkout progressionBlocking fake phone strings, disposable emails, unserviceable COD postal codes, unsupported countries, and repeat RTO accounts

It is important to state clearly what each layer does and does not do:

  • Order value thresholds vs. identity validation: LabX Fraud Filter does not filter by cart subtotal or hide a single payment gateway while leaving others open. If you want to hide the COD option on orders over a specific dollar amount, configure price-based conditions on your COD-eligible shipping rates in Shopify Admin (or use a payment customization rule).
  • Hard server-side blocks on fake buyer data: Once a shopper is in checkout, LabX Fraud Filter’s Checkout Protection runs as a Shopify Checkout Validation Function on Shopify’s own servers. When a buyer enters a blacklisted phone pattern, a throwaway email domain, a high-RTO postal code, or logs into an account tagged for past COD refusals, the function blocks the checkout submission entirely before an order can be placed.
  • Browser vs. server enforcement: Storefront scripts are helpful for stopping automated scrapers and casual visitors from unsupported countries, but because Shopify serves storefront pages from its CDN, any browser rule can be bypassed by turning off JavaScript. Only server-side Checkout Validation Functions cannot be bypassed.

Which Checkout Protection rules stop fake COD orders before creation?

In LabX Fraud Filter, Checkout Protection evaluates the exact fields a buyer types into checkout—or the tags on their Shopify customer profile—against your compiled ruleset on Shopify’s backend. You can combine six server-side conditions to filter out fake COD orders:

ConditionMatch Types AvailableHow Normalization WorksHow It Stops COD Fraud & RTO
PhoneExact match, ContainsStrips all non-digits (+, -, spaces, parentheses) so only digits (0–9) are comparedRejects specific repeat-RTO mobile numbers (Exact match) or dummy digit sequences like 0000000, 1111111, 1234567, and invalid prefixes (Contains)
EmailExact match, ContainsTrims spaces and folds all characters to lowercaseBlocks known repeat offenders (Exact match) and disposable email domains (@mailinator.com, @tempmail.com, @yopmail.com) via Contains
ZipExact match, ContainsTrims spaces and folds to lowercaseStops orders to unserviceable postal codes (Exact match) or regional postal prefixes where your courier does not support cash collection (Contains)
CountryMulti-select target countriesUppercases two-letter ISO country codes (countryCode)Prevents checkout submission when the delivery address is in a country you do not ship to
NameFirst Name, Last Name, or Full Name (Exact match / Contains)Trims whitespace and folds to lowercaseCatches obvious test orders (test, asdf, fake) or repeat abuse aliases entered in the shipping name fields
Customer tagBuyer has any of these tags, Buyer has none of these tagsChecks customer.hasTags on Shopify’s servers (up to 100 tags)Blocks logged-in repeat RTO buyers tagged e.g. cod-rto (any mode), or restricts checkout to verified accounts (none mode, which also blocks untagged guests)

Because buyers fill out Shopify Checkout step by step, the validation function only evaluates a field after the shopper has entered a value—so a Zip or Phone rule will never flash a premature error while those inputs are still blank.

How do you block fake phone numbers and unserviceable postal codes step by step?

Two of the strongest predictors of a fake COD order are a nonsensical phone number (which prevents the courier from calling at delivery) and a postal code outside your courier’s reliable COD service area. Here is how to set up both rules in the Checkout Protection rule builder:

Step 1: Block dummy phone patterns and blacklisted COD numbers

  1. Open LabX Fraud Filter in your Shopify Admin, click Checkout Protection, and click Add rule.
  2. Make sure Rule status at the top is set to Enable.
  3. In Step 1 (If), select Condition = Phone.
  4. Choose your Match type:
    • Select Exact match to block specific phone numbers that have refused previous COD deliveries. Because the app strips all formatting symbols automatically, entering 15550109999 will block +1 (555) 010-9999, 1-555-010-9999, and 15550109999 alike.
    • Select Contains (in a separate rule) to catch placeholder digit strings that prank buyers type to get past required phone fields—for example, 0000000, 1111111, 9999999, 1234567, or 9876543.
  5. Enter up to 100 values per rule (one per line or comma-separated).
  6. In Step 2 (Then), write a clear Error message (up to 255 characters) or click one of the built-in phone presets:
    • “This phone number is not eligible to complete this order.”
    • “We could not verify this phone number. Please contact support.”
    • Or write a COD-specific prompt, for example: “Please enter a valid, reachable mobile number so our courier can confirm your delivery.”
  7. Set Position to Next to the field that triggered the rule (inline, which attaches the error directly to $.cart.buyerIdentity.phone) and click Save.

Step 2: Restrict unserviceable ZIP codes and unsupported countries

If certain remote postal codes or cross-border destinations generate unsustainable RTO rates:

  1. Click Add rule in Checkout Protection and set Condition to Zip.
  2. Choose Exact match for individual postal codes or Contains to match regional postal prefixes.
  3. Enter the restricted postal codes in Values.
  4. In Then, select a recommended preset—such as “{shop_name} does not deliver to this zip or postal code.” or “We are unable to ship to the provided zip code.”—and choose Next to the field that triggered the rule ($.cart.deliveryGroups[0].deliveryAddress.zip).
  5. For country-level enforcement, add a Country rule, pick your restricted destinations in Target countries, and pair it with storefront country rules as explained in our guide to blocking countries on Shopify.

How do you stop repeat RTO offenders with email and customer tag rules?

Many RTO losses come from the same small group of repeat buyers who order multiple options on COD and refuse the parcels they change their mind about, or who use throwaway emails to place fake orders.

  1. Block disposable email domains at checkout: Create an Email rule with Match type set to Contains and click the Quick add untrusted email domains chips (+ @mailinator.com, + @tempmail.com, + @guerrillamail.com, + @10minutemail.com, + @dispostable.com, + @yopmail.com, + @trashmail.com, + @getairmail.com). Note that the storefront disposable-email toggle in Settings only covers newsletter signup forms—only a Checkout Protection Email rule blocks disposable emails during checkout. For more domain patterns, see our guide on blocking customer emails and domains on Shopify.
  2. Block repeat RTO customer tags: Whenever a COD parcel comes back as Return to Origin due to buyer refusal, add a customer tag in Shopify Admin such as cod-rto or rto-blocked. Then create a Checkout Protection rule with Condition = Customer tag and Match type = Buyer has any of these tags, and enter cod-rto.
    • LabX Fraud Filter only requests the optional read_customers permission when you save a customer tag rule.
    • Because customer tags do not have an input field on the checkout page, tag errors automatically display at the Top of checkout ($.cart)—for example: “Your account is not eligible to complete this order.”
  3. Add their phone and email to Exact match rules: Because a tagged customer might log out and attempt a guest checkout, also add their phone number to your Phone (Exact match) rule and their email to your Email (Exact match) rule.

How do storefront rules and fail-open safeguards protect real buyers?

If an automated bot or competitor is flooding your store with fake COD checkouts from cloud servers, you should also filter that traffic before it reaches your cart:

  • Enable Tor and datacenter blocking on the storefront: In Settings > Mitigator, turn on Block Tor traffic and Block datacenter traffic. Datacenter blocking stops automated traffic coming from hosting providers where bots run (note that it is not consumer VPN blocking, so real shoppers on residential networks are unaffected).
  • Built-in fail-open architecture: You never have to worry that a rule error will freeze your checkout. LabX Fraud Filter registers its Checkout Validation Function with blockOnFailure: false, falls back to an empty ruleset if a configuration metafield is unreadable, and checks that your compiled rules stay within Shopify’s 64,000-byte metafield ceiling (up to 100 checkout rules per store) before publishing.

Frequently asked questions

Why does Shopify Fraud Analysis not catch most fake Cash on Delivery (COD) orders?

Shopify built-in Fraud Analysis relies heavily on credit card checks such as AVS (Address Verification System) and CVV matching, and it runs only after an order is placed. Because Cash on Delivery is a manual payment method with no card authorization at checkout, fake COD orders bypass card checks and immediately tie up inventory unless you validate buyer details before checkout completes.

How does phone number matching work when blocking fake COD orders at checkout?

In LabX Fraud Filter, Checkout Protection strips all non-digit formatting characters—such as plus signs, hyphens, parentheses, and spaces—before comparing phone numbers on Shopify servers. You can use Exact match to block specific repeat-abuse numbers or Contains to reject fake sequences (for example, 0000000 or 1234567) and unsupported area prefixes.

Can a buyer bypass COD checkout blocks by disabling JavaScript?

No. While storefront traffic rules run in the visitor browser and can be bypassed by disabling JavaScript, Checkout Protection runs on Shopify servers as a Cart and Checkout Validation Function. Every cart and checkout submission is evaluated server-side before an order can be created.

How do I block repeat Return to Origin (RTO) customers from placing new orders?

Tag the customer account in Shopify Admin (for example, cod-rto or cod-blocked) and create a Checkout Protection rule in LabX Fraud Filter with Condition set to Customer tag and Match type set to Buyer has any of these tags, alongside rules for their phone number and email address.

Sources

  1. Shopify Dev Docs — About Cart and Checkout Validation Functions
  2. Shopify Help Center — Manual Payment Methods and Cash on Delivery
  3. Shopify Help Center — Managing Customer Tags

Part of our guide: Shopify fraud prevention →

Put your first blocking rule live in minutes

Install LabX Fraud Filter free on Shopify, turn on the Fraud Guard embed and add your rules.

Install free on Shopify

Free plan available