How the refuser scan works

The refuser scan looks at orders from the last 60 days that are now cancelled, keeps the ones paid by Cash on Delivery, and counts the customers behind them. When you click Tag N customers, the app adds the tag cod-refused to those customers. From then on, the rule "Hide COD for customers tagged cod-refused" hides COD for them at checkout. The scan is part of the Pro plan; on the Free plan the section shows a "Pro feature" badge.

How do you run it?

1. Open Khaleeji COD and go to the Find customers who refused COD section.
2. Click Scan orders. The page shows "Scanning…" while it reads your orders.
3. Read the result, for example "3 cancelled COD orders found. 3 customers to tag."
4. Click Tag 3 customers (the number matches your result). When it finishes, you see "Tagged 3 customers cod-refused."

If the scan finds nobody new to tag, the tag button doesn't appear.

Which orders does it look at?

• Orders created in the last 60 days. By default, Shopify lets apps read orders from the last 60 days only. Older orders need an extra permission, and Khaleeji COD doesn't ask for it.
• Cancelled orders only. Every other order is skipped.
• Orders paid by Cash on Delivery. The scan keeps an order when its payment method name includes "Cash on Delivery" or «الدفع عند الاستلام», or is exactly "COD". Orders paid by card, wallet or buy now, pay later are ignored.
• Up to 1,000 cancelled orders per scan, newest first. If your store has more than that in 60 days, the scan checks the newest 1,000.

Why is the customer count lower than the order count?

The result counts orders and customers separately. The customer number can be lower because:

• one customer can have several cancelled COD orders, and is only tagged once
• customers who already have the cod-refused tag are skipped, and the result adds a line such as "2 orders are from customers who are already tagged."
• an order with no customer attached can't be tagged

Does it tag anyone without asking?

No. Scanning only reads your orders. Nothing is tagged until you click Tag N customers. The app then adds the cod-refused tag and nothing else. It doesn't remove or change other tags.

The result shows numbers, not names, and the button tags every customer it counted. If you want to check each customer first, look at your cancelled COD orders in Shopify admin before you tag. If you tag someone by mistake, open that customer in Shopify admin and remove the tag.

Is every cancelled COD order a refusal?

Not always. The scan can't tell why an order was cancelled. Some are refusals at the door, but you may also have cancelled some orders yourself, for example because an item was out of stock or the customer asked before it shipped. If you click the button, those customers are tagged too.

If that matters for your store, review your cancelled COD orders first (how to find cancelled COD orders), tag, then remove the tag from anyone who shouldn't have it. How to spot repeat refusers covers what counts as a pattern and how to be fair to a customer who refused once.

"Shopify hasn't approved this app to read customer data yet"

The scan reads the customer on each cancelled order. Shopify treats customer information on orders as protected customer data, and an app needs Shopify's approval before it can read it. Until Khaleeji COD has that approval, the scan stops and shows: "Shopify hasn't approved this app to read customer data yet. The scan works once that access is granted."

This approval is between the app's developer and Shopify. There's nothing to change in your store. A few more things to know:

• From each order, the scan reads only the payment method, whether the order has a fulfillment, and the customer's ID and tags. It doesn't read names, emails, phone numbers or addresses.
• The message only affects the scan. Your saved checkout rules stay as they are.
• While you wait, you can tag customers by hand in Shopify admin. See how to block COD for specific customers with tags.

What else should you know?

• Results aren't saved. Run the scan again whenever you want a fresh count.
• If tagging stops part way, you see "Tagging stopped:" followed by the reason. Customers tagged before the problem keep their tag. Run the scan again: they're now skipped, and the rest are counted.
• The money-lost report works from the cancelled COD orders this scan finds, but it only counts the ones that had shipped. Run a scan before you read it. Tagging still covers every cancelled COD order, shipped or not.