Address Autocomplete questions.

Start with Geoapify — it’s free for up to 3,000 requests/day, requires no credit card, and takes about 2 minutes to set up. Once you’re happy with how the plugin works, you can switch to any other provider from the settings page without touching code.

For a live production store: Google Places gives the best global accuracy; Mapbox is the best value at scale; Loqate is the best choice if address deliverability is critical (e.g. luxury goods, medical supplies).

Almost — you need to enter an API key for your chosen provider, select that provider in the settings, check “Enable Plugin”, and save. The plugin won’t load any scripts until it’s explicitly enabled, so activation itself has no impact on your store.

No. The plugin loads a small (~6 KB) JavaScript file that only activates when a customer starts typing in the address field. It has no impact on initial page load time, no blocking scripts, and no external SDK loaded into the browser.

Yes. All geocoding API calls are proxied through your WordPress server via a REST endpoint. The customer’s browser only ever talks to your own domain — the API key never appears in the page source, network tab, or JavaScript bundle.

Yes, any time. All 7 providers are included. Switching takes one click in the settings page — enter the new API key, select the provider, save. No code changes, no data migration, no downtime.

The most common cause is a URL restriction on your Mapbox token. URL restrictions are designed for client-side browser tokens and don’t work for server-side PHP requests (which don’t send an Origin header). Create a new token with no URL restrictions and try again. If it still fails, the error message will appear in the browser’s Network tab response for the /suggest request.

HERE’s autocomplete API requires at least one of: a country filter (in=countryCode:) or a proximity location (at=lat,lng). This means HERE requires WooCommerce shipping countries to be configured. Go to WooCommerce → Settings → Shipping → Shipping options and set at least one destination country, then try again.

Yes, slightly. Loqate returns a hierarchy of results — it first suggests localities (suburbs, streets) as “containers”, then drills down to individual addresses when you select one. The plugin handles this automatically: selecting any suggestion in the dropdown triggers a background lookup that resolves it to a final address. From the customer’s perspective it behaves identically to any other provider.

Google gives $200 of monthly API credit free, which covers roughly 67,000 Places API requests — enough for most small to medium stores. However, you do need to add a credit card to your Google Cloud project to unlock the free credit. If you’d prefer a completely card-free option, Geoapify (3,000/day) or LocationIQ (5,000/day) are the best alternatives.

Yes. The plugin supports both the classic shortcode checkout ([woocommerce_checkout]) and the Gutenberg block-based checkout. Block checkout compatibility is declared to WooCommerce via the FeaturesUtil API, so you won’t see any compatibility warnings in WooCommerce status.

This is intentional. When you select a suggestion, the plugin immediately shows the full label so you can see your selection — then fetches the structured address details from the provider API in the background. Once the details arrive, address_1 is updated to just the street portion (e.g. “City Circuit” instead of “Apple Store, City Circuit, Malvern East VIC 3145, Australia”), while the city, state, postcode, and country fill their respective fields. This typically happens within 200–500ms.

The checkout remains fully functional. If the autocomplete API fails for any reason, the address field reverts to a normal text input — customers can always type their address manually. The error is logged to the browser console (QuixWP AC: detail fetch failed) but no visible error is shown to the customer.

Go to WooCommerce → Settings → Shipping → Shipping options and confirm your shipping destination is set to “Limit to specific countries” with Australia selected. If it’s set to “Ship to all countries”, the plugin will not apply a restriction. The plugin reads this setting dynamically — no plugin settings need to change.

This can happen with landmark or POI addresses (parks, businesses) where the provider returns the postcode in the formatted label string but not as a standalone structured field. The plugin automatically tries to extract the postcode from the label as a fallback. If extraction still fails, try selecting a more specific address suggestion (e.g. a street address rather than a park or business name).

WooCommerce reloads the state dropdown after a country change. The plugin waits 350ms after setting the country before setting the state, to allow WooCommerce time to reload the state options. If your theme or other plugins delay this reload significantly, the state may not set. You can listen to the qwp_ac_autofilled JavaScript event to handle the state yourself:

document.body.addEventListener( 'qwp_ac_autofilled', function( e ) {
    console.log( 'Autofilled address:', e.detail.address );
} );

Go to WooCommerce → Settings → Address Autocomplete and change the Dropdown Theme setting. Choose Light for stores with a white or light checkout background, or Dark for dark-themed stores. The dropdown theme is set explicitly — it does not follow the visitor’s OS dark mode preference.

Yes. All colours are CSS custom properties. Add overrides in your theme’s stylesheet:

.quixwp-ac-theme-light {
    --qwp-ac-active-bg:    #f0fff4;    /* Selected item background */
    --qwp-ac-active-color: #1a7f3c;    /* Selected item text */
    --qwp-ac-mark-bg:      #c6f6d5;    /* Query match highlight */
}

No child theme required — any custom CSS location works.

The dropdown uses z-index: 9999 by default. If something else on your checkout has a higher z-index, override it:

.quixwp-ac-dropdown {
    --qwp-ac-z: 99999;
}

Generally yes, provided the plugin uses standard WooCommerce field IDs. If your checkout plugin uses custom field IDs, use the filter hooks to point to the correct selectors:

add_filter( 'qwp_ac_field_address_1', function( $selector ) {
    return '#custom_billing_address';
} );

Yes. Full HPOS compatibility is declared via WooCommerce’s FeaturesUtil::declare_compatibility() API. No warnings will appear in WooCommerce → Status → Features.

Yes. The plugin activates per-site on a multisite network. Each site has its own settings and API keys stored independently in wp_options.

All geocoding requests are made server-to-server — the customer’s IP address and keystrokes never reach the geocoding provider directly. For the strictest GDPR compliance, use Geoapify or LocationIQ, which are EU-hosted with full GDPR data processing agreements available.

Yes. Implement the AutocompleteProviderInterface, extend AbstractProvider, and register via the qwp_ac_register_providers action hook. Your provider will automatically appear in the admin settings UI including its own API key field. See the documentation for a full example.

All settings are stored in a single wp_options row under the key quixwp_ac_settings. Deleting the plugin via WP Admin removes this key along with any other plugin data.

Yes. The uninstall.php routine removes all plugin options and transients when you click “Delete” in WP Admin → Plugins. Deactivating does not delete any data.

Visit quixwp.com/support or email hello@quixwp.com. Include your WordPress version, WooCommerce version, active provider, and a screenshot of the browser console if you’re reporting a technical issue.