Some products are inherently higher risk for Cash on Delivery returns. Fragile items that might arrive damaged. High-value electronics where the financial exposure on an RTO is significant. Customised or personalised products that can’t be restocked if returned. For these, blocking COD at the product or category level is the right approach.

Why Product-Level COD Rules?

Your store might be perfectly happy offering COD on most products — it drives conversion and serves customers in cash-heavy markets. But a blanket “COD allowed” policy that applies equally to a ₹200 accessory and a ₹15,000 laptop makes no sense from a risk perspective.

Smart COD Control lets you apply COD rules at the product and category level, so you can offer COD strategically rather than as an all-or-nothing proposition.

Setting Category-Level Rules

Go to WooCommerce → Smart COD → Product Rules → Categories. Select any product category and choose whether COD is:

Setting Product-Level Rules

For individual products, the rule appears on the product edit screen under a new Smart COD tab. Override the category rule for specific products where needed — for example, allow COD on most electronics but block it for one particularly high-value item.

Mixed Cart Handling

When a cart contains products from multiple categories with different COD rules, Smart COD Control applies the most restrictive rule. If any product in the cart has COD blocked, COD is blocked for the entire order.

Practical Examples

For help configuring product-level rules, visit the ThePluginForge support page.

Download Smart COD Control free →

Smart COD Control is a comprehensive toolkit for managing Cash on Delivery in WooCommerce. This guide walks you through every major setting from first install to a fully configured COD management system.

Installation

Install Smart COD Control from the WordPress plugin directory or upload the plugin ZIP. Activate it, then navigate to WooCommerce → Smart COD in your admin menu.

1. General Settings

The General tab controls the top-level COD behaviour:

2. OTP Verification

Configure SMS gateway, OTP length, expiry, resend limits, and the message template. Test with a real phone number before enabling.

3. Location Rules

Set country, state, and pincode allowlists or blocklists. Start permissive and tighten based on your RTO data.

4. Fee Settings

Set a fixed, percentage, or combined COD fee. Configure the label text and any exemption rules (by customer history, order value, or product category).

5. Trust Rules

Define what constitutes a “trusted” customer. Trusted customers can receive lighter restrictions — skipping OTP, lower fees, higher COD value caps.

6. Product and Category Rules

Block COD for specific products or entire categories. High-value electronics, fragile goods, custom/personalised items — configure which products can and can’t be purchased via COD.

7. Analytics and Reporting

The analytics tab shows your COD vs prepaid order split, blocked order counts, and RTO trends over time. Use this data to tune your rules.

Recommended Starting Configuration

If you’re not sure where to start:

  1. Enable OTP verification for all new customers
  2. Set a maximum COD order value of 2× your average order value
  3. Add a modest COD handling fee (₹25–₹50 or 2–3%)
  4. Review your RTO data after 30 days and add pincode blocks for problem areas

Full documentation and a setup walkthrough video are available at the ThePluginForge support page.

Download Smart COD Control free →

A first-time customer with no order history placing a large COD order is a fundamentally different risk profile from a customer who has placed and received 10 prepaid orders over the past year. Treating both customers identically — either blocking COD for everyone or allowing it for everyone — is leaving money on the table or accepting unnecessary risk.

Customer trust scoring in Smart COD Control lets you differentiate.

What Is Customer Trust Scoring?

Trust scoring assigns a risk level to each customer based on their order history with your store. Customers with a track record of successfully received orders are “trusted” and get more permissive COD access. New customers or those with a history of returns or cancellations are flagged as higher risk and face additional restrictions.

Configuring Trust Rules

In WooCommerce → Smart COD → Trust Rules, you define what “trusted” means for your store. Examples:

You can require all conditions or any combination.

What Happens to Untrusted Customers?

You control this. Options include:

This approach minimises friction for your best customers while maintaining protection where it’s needed.

Guest Checkout and Trust Scoring

Guest checkouts don’t have an account history. You can configure how guest COD orders are treated — some stores block COD for guests entirely and require account creation, others allow it with mandatory OTP verification.

Building Trust Over Time

Trust scoring creates a virtuous cycle: new customers who want COD complete OTP verification and receive their first order. After N successful orders, they’re trusted and get smoother COD access. This rewards genuine customers progressively without permanent blanket restrictions.

Documentation for trust scoring configuration is available at the ThePluginForge support page.

Download Smart COD Control free →

Every Cash on Delivery order carries a cost that prepaid orders don’t: the risk of a return shipment, the cost of the carrier’s COD collection fee (where applicable), and the operational overhead of handling a cash payment. A COD handling fee makes that cost visible to the customer — and nudges them toward prepaid alternatives.

The Psychology of COD Fees

When a customer sees “Cash on Delivery + ₹40 handling fee” next to “Pay Online — Free,” the comparison is clear. A small fee doesn’t need to cover your actual COD cost — it just needs to make the prepaid option look more attractive. Many stores report a 15–25% shift toward prepaid payment after adding a modest COD fee.

Setting Up the Fee in Smart COD Control

Go to WooCommerce → Smart COD → Fee Settings. You can configure the fee as:

The fee label shown to the customer is fully customisable. “COD Handling Fee”, “Cash Payment Surcharge”, or a more neutral “Service Fee” — whatever fits your store’s tone.

Fee Exemptions

Smart COD Control lets you configure fee exemptions. You might waive the COD fee for:

Minimum and Maximum Order Value for COD

Alongside the fee, you can set a minimum and maximum order value for COD eligibility. Small orders (under ₹500) might not warrant the overhead. Very large orders (over ₹10,000) carry enough RTO risk that you’d prefer to require prepayment or additional verification.

Tax Treatment of the Fee

The COD fee can be configured as taxable or tax-exempt. In most jurisdictions, a payment processing surcharge is not subject to GST/VAT — check your local tax rules and configure accordingly.

Testing the Fee

Before going live, place a test order using COD and verify the fee appears correctly on the order review, order confirmation email, and the WooCommerce order record.

Full setup documentation is available at the ThePluginForge support page.

Download Smart COD Control free →

If you’ve been running a WooCommerce store with Cash on Delivery for any length of time, you’ll have noticed patterns. Certain cities, certain postcodes, certain pin codes — they produce a disproportionate share of your Returns to Origin. Geographic blocking lets you take action on that data.

Why Block COD by Location?

Not all locations are equal for COD reliability. Factors that increase RTO rates in specific areas include:

Smart COD Control lets you block COD for any combination of countries, states, and specific pincodes/postcodes.

Setting Up Geographic Restrictions

Navigate to WooCommerce → Smart COD → Location Rules. You have several levels of control:

Country-Level Blocking

Block COD entirely for specific countries. Useful if you ship internationally and COD fraud is disproportionately high from certain countries.

State/Region-Level Blocking

Block COD for entire states or regions within a country. Less blunt than country-level blocking but still broad.

Pincode/Postcode Blocking

The most targeted option. Paste in a list of pincodes (comma-separated or one per line) and COD is blocked for orders destined for those locations. The customer sees COD listed but greyed out with a message like “Cash on Delivery is not available for your location.”

Building Your Blocklist

Start with your return data. Export your WooCommerce orders, filter for COD returns, and extract the postcodes. Sort by RTO rate. Any postcode with an RTO rate above your acceptable threshold (typically 20–30%) is a candidate for blocking.

Revisit and update your blocklist quarterly — RTO patterns shift as your customer base, carrier partnerships, and product mix evolve.

Allowlist Mode

Instead of blocking specific locations, you can switch Smart COD Control to allowlist mode — COD is disabled everywhere by default, and only explicitly allowed for specific pincodes. This is useful for stores that want to offer COD as a targeted feature for verified-delivery areas only.

Combining with Other Rules

Geographic rules stack with other Smart COD Control rules. You might allow COD in a problematic postcode only for customers with an order history — blocking new customers while allowing verified repeat buyers.

Need help building your location rule strategy? Visit the ThePluginForge support page.

Download Smart COD Control free →

OTP (One-Time Password) verification for Cash on Delivery is the most effective single technique for reducing fake WooCommerce orders. It adds five seconds of friction for legitimate customers and stops fraudulent orders cold. Here’s exactly how to set it up with Smart COD Control.

How OTP Verification Works

When a customer selects Cash on Delivery at checkout and clicks Place Order, Smart COD Control intercepts the order placement and sends a one-time password to the phone number the customer entered. The customer must enter the correct OTP on a verification screen before the order is confirmed. If the phone number is fake, no OTP arrives and the order never completes.

Step 1: Connect an SMS Gateway

Smart COD Control integrates with popular SMS gateways to deliver OTP messages. Supported gateways include Twilio, MSG91, Textlocal, and others. In the plugin settings (WooCommerce → Smart COD → OTP Settings), select your gateway and enter your API credentials.

If you’re not sure which gateway to use:

Step 2: Configure OTP Settings

Once your gateway is connected, configure the OTP behaviour:

Step 3: Customise the OTP Message

The SMS message template is fully customisable. The default is something like: “Your ThePluginForge store verification code is {otp}. Valid for 10 minutes.” You can change this to match your store brand and include your store name.

Step 4: Test Before Going Live

Use a real phone number you own to test the full OTP flow before enabling it for customers. Place a test COD order, verify you receive the OTP, enter it correctly, and confirm the order completes. Also test the “wrong OTP” and “expired OTP” error states.

What Customers See

After clicking Place Order, the customer is shown a clean verification screen asking them to enter the OTP sent to their phone number. The screen displays the last few digits of the number for confirmation, a resend option (after the cooldown), and a countdown timer showing when the OTP expires.

Exempting Repeat Customers

You can configure Smart COD Control to skip OTP verification for customers with a positive order history — for example, customers who have previously placed and received at least one paid order. This reduces friction for loyal customers while maintaining protection for new and high-risk orders.

Full documentation and gateway setup guides are available at the ThePluginForge support page.

Download Smart COD Control free →