Help Center
English
Contents

Checkout protection: block shoppers and hold risky orders

Block shoppers by email, phone, address or IP, and let order rules require online payment, hold or refuse risky orders.

Checkout protection keeps out the orders you don't want, while everyone else checks out as usual. Open Settings › Checkout protection. The Block list tab stops or limits particular shoppers; the Rules tab decides what happens to new orders in each market.

Block list

Add an entry for an email address, a phone number, an address or an IP address. Entries match the way people actually type them: emails in any letter case (for Gmail, also without dots or a +tag), phone numbers in international format, addresses by postcode and first line with spaces and punctuation ignored, and IP addresses one at a time or as a range (CIDR, such as 203.0.113.0/24).

Each entry has an effect. Refuse stops checkout and shows your store's message. Prepaid only hides cash on delivery and other pay-later methods; the shopper can still pay online. Add a note for your staff (shoppers never see it) and, if you like, an end date after which the entry stops applying. The list is checked when the shopper enters their contact details and address, and again when they place the order. It holds up to 10,000 entries.

Each entry also chooses where it applies, under Applies to: checkout, blog comments, reviews, the contact form, newsletter sign-ups, back-in-stock requests, sign-in and saved addresses (customer accounts), order tracking and the Returns and Delivery portals, and review votes. Email and IP address entries can apply anywhere and apply everywhere by default; phone numbers can apply to checkout, the contact form, back-in-stock requests and accounts; addresses apply to checkout only. Outside checkout a blocked shopper gets the usual answer and nothing is sent or saved: a comment, review or contact message is kept as spam and they're told it's waiting for approval or was sent, and sign-ups, back-in-stock requests, sign-in codes, order lookups and votes look accepted but do nothing. Saving an address and checking a gift card balance are refused. The effect (refuse or prepaid only) matters only at checkout.

Marking a blog comment, product review or contact message as spam adds its email and IP address to the list for blog comments, reviews and the contact form for 90 days, marked as learned from that submission. Moving it back to approved or pending removes them. Editing such an entry makes it your own, and it stays until you change it.

To block someone you've already dealt with, use Block this customer on their customer page or on one of their orders.

To add or remove many entries at once, use bulk add or bulk remove. The change runs in the background and shows its progress, and Stop ends it early (entries it already changed stay; cancelling a CSV import stops it too); rows that couldn't be added are listed with the reason. You can also import and export the list as a CSV file (type Checkout block list), with the columns kind, value, effect, note, expires_at and country_code.

Order rules

Order rules belong to a market, up to 50 per market. Each rule has up to 5 conditions, and all of them must match. Rules run in priority order, and the first one that matches decides: Allow lets the order through and stops checking, Require prepaid takes away cash on delivery and other pay-later methods, Hold creates the order but keeps it from fulfilment until you review it, and Refuse stops the order.

Conditions can use:

  • Order total, in your store's base currency.

  • Payment method: cash on delivery or prepaid.

  • Customer's orders and Customer's returned shipments: the shopper's placed, uncancelled orders and returned-to-sender orders in your store, found by their email or phone.

  • Orders in the last hour and Orders in the last day, by phone, email or IP address: orders already placed.

  • Postcode: is, starts with, or is in a list.

  • Guest checkout: whether the shopper isn't signed in.

  • Item quantity.

  • Customer group: is a member or isn't a member.

  • Product tag, category, vendor or brand (equals) and product title (contains).

Every count is your store's own; nothing is counted across stores. If a count can't be read at checkout, a condition on it doesn't match. If you delete a tag, category, vendor or brand that a rule uses, that condition matches nothing, so deleting it never makes a rule catch more orders. Your cash on delivery rules stay as they are and are checked separately.

Held orders

A held order is created and its stock is committed as usual, but it isn't released for fulfilment. The order page shows a Held for review banner with a one-line reason built from the rule, for example "Held: COD, order total over ₹5,000.00, first order". Choose Approve to release it to fulfilment, or Cancel to cancel it and refund any payment already captured.

Use the Held for review filter on the orders list to see every order waiting for you. An order nobody reviews is cancelled automatically after the number of days set in Checkout protection: 3 by default, anything from 1 to 30.

What shoppers see

Shoppers never see why. A refused shopper sees only your storefront message "We can't accept this order. Contact the store if you think this is a mistake.", and a shopper who must pay online sees "Pay online to place this order." You can reword both like any other storefront message: see Customize storefront messages. Checkout protection doesn't fingerprint devices or give shoppers a risk score.

Privacy

Apps can manage the block list, order rules and held orders through the Store API. The orders/held and orders/released webhooks tell them when an order is held and when it's approved.

Was this page helpful?