Smart COD for WooCommerce

Shipping Class

You can define an informational message to display before the payment methods, when the COD method is not available for a customer.

You can define different messages per restrict reason.

Extra Fees You can configure a standard extra fee and a separate fee for local pickup.

You can use a fixed price or a percentage of the customer’s cart amount.

You also have a nice rounding option.

You can enable tax for this fee.

Settings Backup Export your Free settings as a JSON file and restore them on the same store from WooCommerce > Smart COD: Settings backup. Review the current and saved values before confirming. No Smart COD AI account is required.

Backups include COD availability, fees, restriction selections and messages. Sharing consent, credentials and order/customer data are excluded and remain unchanged during restoration. Files from another store are not accepted because product, shipping and category identifiers are store-specific. A preview expires after ten minutes; changing settings after preview requires a new preview.

Developer-Friendly The plugin integrates seamlessly with WooCommerce and uses a clean, object-oriented codebase. It also provides the following filters for easy customization:

wc_smart_cod_fee: Alter the extra fee.

wc_smart_cod_available: Alter the current COD restriction.

wc_smart_cod_fee_title: Change the COD fee title.

Since the plugin extends the existing WooCommerce Cash on Delivery Gateway, there’s no need to enable or disable gateways manually.

External services COD Protection and order-history sharing are optional and off by default in this Free plugin. Enabling the sharing setting in Cash on Delivery settings registers the installation with api.woosmartcod.com and permits the collection described below. Collection includes future physical COD creation snapshots and subsequent outcomes in signed background batches, without requiring tracking or a 24-hour wait. The existing filtered cancellation relay still sends eligible historical and future cancellation evidence and a capped prior-completed tracked COD count for the same shopper at that shop. An existing enabled sharing setting applies to this collection after updating, without another activation step or expansion notice; disabled settings remain disabled. Registration includes a generated installation identifier, shop domain, operating country and public signing key. Events include pseudonymized customer/location identifiers, a non-reversible order reference, timestamps, totals/currency, shipping method, item count, guest/registered status and courier/tracking where available. The service validates signed submissions, deduplicates events and applies an additional secret-keyed transformation to identity tokens. Data supports same-store COD protection and, subject to server-side eligibility review, cross-store machine-learning training; collection does not activate live ML scoring. No individual shop could perform that cross-shop processing locally.

When COD Protection is enabled and checkout contains an email address or telephone number, the plugin sends locally generated SHA-256 identity tokens, the installation identifier and operating country to the COD Protection endpoint. Raw email and telephone values are not sent. The service checks only eligible events belonging to that same installation and returns only an allow/disable decision with a decision reference and policy metadata, not customer-history counts. The service records aggregate decision statistics and pseudonymized supporting evidence for denials, rather than storing every raw checkout lookup request. A timeout, invalid response or unavailable service leaves Cash on Delivery available. Turning the option off stops future collection, transmission and checkout lookups. The plugin does not call courier APIs.

Service information: cancelled COD service privacy details, Terms and Conditions and Privacy Policy.

COD Protection, successful history and order lifecycle Classic shortcode checkout remains supported. Cart and Checkout Blocks are also supported on WooCommerce 9.9 or newer through the native Store API and Blocks extension APIs. The same COD rules, fees and optional order-lifecycle collection apply to both checkouts. Third-party gateways and checkout fields require their own Blocks support.

Changes in this release: collection expands from filtered cancellation evidence to prospective physical COD creation and outcome events. The successful-history allowance adds context so earlier cancellations are not considered in isolation. This prepares representative data for cross-store machine-learning training; receiving data does not automatically activate ML scoring at checkout.

New lifecycle events do NOT require tracking or a 24-hour wait. A new physical COD order created and cancelled within minutes is still recorded whenever the sharing setting is enabled. Other payment methods, virtual-only orders and deposit-child orders are excluded. Existing historical cancellations retain their filtered relay: this release does not import all past creations or completed orders.

Collection and COD restriction are different. Not every collected cancellation is a qualifying negative match. The existing shipment/fulfilment checks remain: tracking, a prior physical-order completed status or a shipped/fulfilled transition. The lower-confidence untracked fallback applies only without a recognized tracking integration, after at least 24 hours between creation and cancellation, with a fulfilment-stage source status when supplied. Tracking AND 24 hours are not universal joint requirements. A cancellation by itself is not proof of refusal or non-delivery.

Optional and off by default in this Free plugin. Protection checks only this installation. When the existing sharing setting is enabled, the plugin sends future physical COD creation snapshots and later status/outcome changes (including completed, cancelled, refunded and reopened orders) to api.woosmartcod.com in signed background batches. Creation snapshots include pseudonymized email/telephone and postcode identifiers, order reference, timing, totals/currency, shipping method, item count and guest/registered status. Courier names and tracking codes are included where available. Raw customer email, telephone and names are not sent. Data is used for COD protection and, subject to server-side eligibility review, cross-store machine-learning training.

There is one sharing setting. After updating, stores that already enabled sharing also collect future physical COD creation snapshots and subsequent outcomes, without a separate activation or upgrade notice. Stores with sharing disabled remain disabled. Switching sharing off stops future capture, transmission and checkout checks. Historical cancellations keep their existing compatibility relay. Old orders first observed after the update or activation are marked as late observations, not invented checkout snapshots.

The configurable successful-history allowance uses only directly matching email or telephone in this store and affects only the history-based restriction. Default minimum rate: 100%, preserving the existing history restriction unless the merchant chooses a lower rate (50% to 100%). Nine known successful orders and one qualifying dispatched-then-cancelled order meet 90%. Pending orders do not count. WooCommerce completed status is merchant-reported, not automatically courier-confirmed. New completion rows and cumulative historical snapshots are not summed: the service uses a conservative maximum to avoid counting the same deliveries twice. Exact individually imported historical success coverage may therefore be incomplete.

Checkout calls contain hashed identifiers, not raw identity values. The service records aggregate operational counts and pseudonymized evidence for actual denials. This is distinct from storing every raw lookup request. Transport/service errors fail open. More details: https://woosmartcod.com/cancelled-cod-data-sharing/