Woo Duplicate Customer Finder

woo-duplicate-customer-finder

Purpose

Scan WooCommerce customer records for duplicates: same billing email across multiple accounts, or identical shipping address across different email addresses. Exports a conflict report with customer IDs for manual review and CRM deduplication. Read-only.

Prerequisites

• WooCommerce store with REST API enabled
• Consumer Key with Read scope
• Minimum WooCommerce version: 3.5.0

Parameters

| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | store_url | string | yes | — | Base URL of the WooCommerce store | | consumer_key | string | yes | — | WooCommerce REST API consumer key (ck_...) | | consumer_secret | string | yes | — | WooCommerce REST API consumer secret (cs_...) | | dry_run | bool | no | false | No effect — read-only skill | | format | string | no | human | Output format: human or json | | match_on | string | no | email | Match on: email, address, or both |

Authentication

WooCommerce uses OAuth 1.0a for HTTP and Basic Auth over HTTPS.

For HTTPS stores (recommended):

Authorization: Basic base64(consumer_key:consumer_secret)

For HTTP stores (development only): Use OAuth 1.0a — include oauthconsumerkey, oauthnonce, oauthsignature, oauthsignaturemethod=HMAC-SHA1, oauthtimestamp, oauthversion=1.0

Never log or output consumerkey or consumersecret values.

See docs/AUTHENTICATION.md for full setup instructions.

Safety

Read-only skill — no mutations are executed. Safe to run at any time.

Workflow Steps

Step 1 — Fetch all customers

GET /wp-json/wc/v3/customers?per_page=100&page=1

Extract: id, email, billing.email, billing.address_1, billing.city, billing.postcode, billing.country

Step 2 — Build lookup maps

• Email map: normalized_email → [customer_ids]
• Address map: normalized_address_fingerprint → [customer_ids] (fingerprint = lowercased address_1 + postcode + country)

Step 3 — Find conflicts

Email duplicates: map entries with > 1 customer ID. Address duplicates: map entries with > 1 customer ID across different emails.

Step 4 — Export

API Endpoints Used

GET  /wp-json/wc/v3/customers   — all customer records

Pagination Strategy

WooCommerce REST API uses page/per_page pagination (not cursor-based).

Standard pattern:

page = 1
while True:
  response = GET /endpoint?per_page=100&page=page
  process(response)
  if len(response)                       ║
║  TIME:                     ║
║  MODE:  READ-ONLY                        ║
╚══════════════════════════════════════════╝

PER-OPERATION (emit after each API call batch):

[N/TOTAL]   →  records | params: =

COMPLETION (human format):

╔══════════════════════════════════════════╗
║  COMPLETE: woo-duplicate-customer-finder ║
║  RECORDS PROCESSED:                   ║
║  OUTPUT:                       ║
╚══════════════════════════════════════════╝

COMPLETION (json format):

{
  "skill": "woo-duplicate-customer-finder",
  "store": "",
  "completed_at": "",
  "records_processed": ,
  "output_file": "",
  "dry_run": false
}

Output Format

CSV filename: woo-duplicate-customer-finder_.csv Columns: match_type, match_value, customer_ids, emails, names, order_counts, total_spends

Error Handling

| Error | Cause | Resolution | |-------|-------|------------| | 401 Unauthorized | Invalid credentials | Verify consumerkey and consumersecret | | 403 Forbidden | Key lacks Read scope | Regenerate with Read scope | | 429 Too Many Requests | Rate limit | Wait 2 seconds and retry |

Best Practices

• Email matching catches the most common duplicates; address matching catches the same household with different emails.
• Do not delete duplicate accounts without reviewing order history on each — manually merge order counts first.
• Run after every large customer import to catch duplicates introduced by the import.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: navarroido
• Source: navarroido/Woocommerce-skill
• License: MIT

Install and usage instructions live in the source repository linked above.