Address Autocomplete Problems Caused by Custom Fields Plugin

You have installed the ApiCheck WooCommerce plugin, but address autocomplete is not working. Street name and city are not being filled in automatically. Chances are a Custom Fields plugin is the culprit.

The Problem

WooCommerce uses standard field names for address fields: billing_address_1, billing_city, billing_postcode, and so on. ApiCheck hooks into those standard names.

Custom fields plugins such as Checkout Field Editor, WooCommerce Custom Fields, or Flexible Checkout Fields can modify those field names. Sometimes fields are renamed, sometimes they are replaced by new fields with different IDs.

If the field IDs do not match what ApiCheck expects, the fields will not be completed.

Three Causes

1. Modified Field Names

The custom fields plugin has replaced the standard WooCommerce field names with its own names. ApiCheck looks for billing_address_1, but that field is now called checkout_street_address.

2. Persistent Database Changes

Some plugins store their settings in the database. Even after deactivating the plugin, the modified field names remain active until you manually reset them.

3. Conflicting JavaScript

Both plugins try to monitor and fill the same form field. This leads to race conditions where one plugin overwrites the completion of the other.

Solutions

Step 1: Inspect the Field Names

Open your browser DevTools (F12), go to the Elements tab, and look at the input fields of your checkout form. Check whether the id and name attributes match the WooCommerce standard.

Step 2: Reset via WooCommerce

Go to WooCommerce → Status → Tools → Checkout fields and click Reset. This restores the default WooCommerce field names.

Step 3: Clear Cache

Clear the plugin cache and the browser cache. Reload the checkout page and test again.

Step 4: Use Compatible Plugins

Not all custom fields plugins cause conflicts. Checkout Field Editor (by ThemeHigh) and Flexible Checkout Fields (by WP Desk) are known to be compatible with ApiCheck.

Preventive Measures

• Always test changes on a staging environment first
• Make a backup before installing or modifying plugins
• Document which field IDs you use so you can quickly roll back if problems arise

Conclusion

Conflicts between custom fields plugins and ApiCheck can almost always be traced back to modified field names. Check the IDs in your DevTools and reset to the WooCommerce standard if needed. Still stuck? Contact us at [email protected].