Plugin Pulse Beta
← Pulse

WC-Checkout-Custom-Billing-Phone-Field

by Funke · eCommerce

Plugin will customize WooCommerce checkout phone field.

Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.

⚠ Stale⚠ Likely abandoned⚠ Few reviews

Health

D 45/100

Stale · Likely abandoned · Few reviews

Active installs

40+

≈40 estimated

Momentum

-31%

low volume, under 1,000 downloads a month

Biggest opportunity: Update recency scores 0/100. Last updated 3064 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.

How scoring works →
45 Health · D
Maintenance 3/100
Rating quality 76/100
Support 70/100

45 health vs 71 average across 9,845 eCommerce plugins

Install conversion

How it's measured →

1.7%

of downloads still active

At least 40 of 2.4K lifetime downloads are still running, in line with its category: the median eCommerce plugin keeps 1.4%, across 5,181 plugins.

Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other eCommerce plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.

High removal-risk signals

63/100

Maintenance and integrity signals that tend to precede a WordPress.org removal. Not an official status, a heads-up to act.

  • Long abandoned. No update in 8+ years — the top precursor to removal once a vulnerability is found.
  • Compatibility drift. Tested only up to WordPress 4.9.35, well behind 7.1.

Details

Version
1.0.2
Last updated
8.4y ago
Added
2018-06-14 · 8 yrs old
Requires WP
4.0
Tested up to
4.9.35
Requires PHP
—

Directory ranking optimization

How it's scored →

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

34 / 100

Under-optimized

Most to gain: Update recency

Update recency 0/100

Updated 3064 days ago, past the ~180 days where wp.org starts discounting

WP compatibility 7/100

Tested up to WordPress 4.9.35; the current branch is 7.1

Rating quality 52/100

5.0★ over 2 reviews, weighted for review count to 4.1★ and held back under 25 reviews

Listing tuning 84/100

3 of 5 tags set · short description in place

To rank higher: Last updated 3064 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.

Get the full rank-higher report →

Daily downloads

Since 5 Oct 2022 · 1,491 days · wp.org + Plugin Pulse archive

-31% low volume vs prior 30d
43 Nov 2026

30-day downloads

Rolling 30-day volume · peak 145 · peaks are release surges

724 Nov 2026

Directory rank

Ranked about #21,400 to #22,800, alongside the other plugins at 40+ installs. Plugins with the same install count swap places between wp.org requests, so this is where most of them sit. Checked monthly, last on 1 Nov 2026.

Update activity

Downloads in the last 30 days for every 1,000 active sites.

Not enough installs to measure. This needs at least 100 active sites; below that, a handful of downloads reads as tens of thousands.

What its installed base runs

via wordpress.org

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

v1.0 100%

Estimated active installs

The public count shows “40+”. Our estimate pins where the real number sits.

tracked estimate
40–50 ≈40

Crossed into this band today and a band this size takes about a year or more to cross, so the real count is still just over 40.

Install history since 29 Nov 2021

404 Nov 2026

AI assistants

How it's measured →

Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.

This plugin’s searches fall outside the topics measured so far. See the topics measured so far.

Readme readiness

2 of 8 pass · checked 1 Nov 2026

Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.

  • ✓ Says what it does "Plugin will customize WooCommerce checkout phone field."
  • ! Has a FAQ No FAQ section.
  • ! FAQ asks real questions No FAQ to judge.
  • ! Names who it is for Never says who the plugin is for or what they use it for.
  • ✓ Names what it works with Mentions WooCommerce.
  • ! Headings and lists 2 headings and 0 lists; assistants quote headed sections and bullet lists, not paragraphs.
  • ! Enough to quote 384 characters of description; under 1,000 there is little to quote.
  • ! Tags match the text Only 1 of 3 tags appear in the text ("WooCommerce checkout billing phone field", "WooCommerce mask billing phone" missing).

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

  1. 2026-11-04 30+ → 40+ up after 138 days in tier
  2. 2026-06-19 40+ → 30+ down after 230 days in tier
  3. 2025-11-01 50+ → 40+ down after 352 days in tier
  4. 2024-11-14 60+ → 50+ down after 307 days in tier
  5. 2024-01-12 70+ → 60+ down after 238 days in tier
  6. 2023-05-19 80+ → 70+ down after 209 days in tier
  7. 2022-10-22 90+ → 80+ down after 18 days in tier
  8. 2022-10-04 100+ → 90+ down

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Embed this report card

Drop a live Pulse card for WC-Checkout-Custom-Billing-Phone-Field into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/wc-checkout-custom-billing-phone-field" width="480" height="300" style="border:0" loading="lazy" title="WC-Checkout-Custom-Billing-Phone-Field — Plugin Pulse"></iframe>
Preview card ↗

WC-Checkout-Custom-Billing-Phone-Field: 40+ active installs, 5.0★ (2 reviews). Plugin Pulse (WP Mayor), as of 2026-11-04. https://plugins.wpmayor.com/plugin/wc-checkout-custom-billing-phone-field

Spotted a number that looks wrong? Report a data issue and we'll check it against the source.