Overview
QuixWP Address Autocomplete adds address suggestions to the WooCommerce billing and shipping address fields. Selecting a suggestion can populate the street, city, state, postcode, and country while manual address entry remains available.
Provider requests pass through a WordPress REST endpoint. The provider API key stays on the server, but the partial address query still goes from the shopper's browser to your WordPress site and then to the selected provider.
- Classic shortcode checkout and WooCommerce block checkout.
- Native WooCommerce Core address-provider integration where available.
- 8 provider modes across 7 services.
- Google Places (New) and Google Places (Legacy) are separate modes with separate API-key fields.
- Shipping-country restrictions are derived from WooCommerce.
- Light and dark dropdown themes.
- A rolling 24-hour request limit to help protect provider quota.
Requirements
| Requirement | Minimum |
|---|---|
| PHP | 7.4 |
| WordPress | 6.0 |
| WooCommerce | 7.0 |
Tested up to: WordPress 7.1. This is the tested WordPress version, not a change to the minimum requirements above.
You also need an API key for one supported provider. Provider pricing, quotas, coverage, retention, and licensing can change; confirm the current provider terms before using the plugin commercially.
Installation
- In WordPress, go to Plugins → Add New Plugin → Upload Plugin.
- Select
quixwp-address-autocomplete.zip. - Choose Install Now, then Activate Plugin.
- Open WooCommerce → Settings → Address Autocomplete.
Quick start
- Open WooCommerce → Settings → Address Autocomplete.
- Turn on Enable Plugin.
- Choose one provider.
- Paste that provider's API key into its own API-key field.
- Review the green validation indicator, if shown.
- Choose Save changes at the end of the white settings panel.
- Test billing and shipping addresses at checkout.
WooCommerce Core integration
Where WooCommerce exposes its native address-autocomplete framework, QuixWP registers the selected, configured provider through woocommerce_address_providers. WooCommerce renders the suggestion interface for classic and block checkout, while QuixWP handles provider searches and address details through its server-side REST proxy.
Enable QuixWP, select a provider, enter its API key, and save as usual. With a usable provider configured, the plugin enables Core autocomplete and sets that QuixWP provider as preferred. Inactive QuixWP providers are not registered as fallback providers. On older supported WooCommerce versions without the framework, the plugin uses its compatibility interface.
WooPayments is not required. QuixWP adds alternative provider integrations, API-key handling, country restrictions, and request controls to Core's framework; it is not a separate address-verification service.
Test both checkout types you use, including suggestion selection and manual entry, after switching providers. The checkout screenshots below show the compatibility interface; the native WooCommerce dropdown can look different.
Settings reference
| Setting | Default | Purpose |
|---|---|---|
| Enable Plugin | Off | Master switch for checkout autocomplete. |
| Country Restriction | Derived | Read-only list based on the store's WooCommerce country configuration. |
| Minimum Characters | 3 | Characters entered before suggestions are requested. |
| Debounce Delay | 300 ms | Wait after typing stops before a request is sent. |
| Daily API Request Limit | 3,000 | Maximum combined suggestion and detail requests during a rolling 24-hour period. Valid range: 100 to 100,000. |
| Dropdown Theme | Light | Explicit light or dark suggestion-dropdown appearance. |
Provider setup
Only the selected provider is used at checkout. API keys entered for inactive providers remain saved but are not used. Google Places (New) and Google Places (Legacy) are intentionally separate so an existing store can keep a legacy key without mixing it with the current API.
| Provider mode | Setup guidance | Official links |
|---|---|---|
| Google Places (New) | Recommended for new Google Cloud projects. Enable Places API (New) for this key. | Docs · Pricing |
| Google Places (Legacy) | Compatibility mode for projects that already have Places API Legacy access. New projects cannot enable the legacy service. | Docs · Pricing |
| Mapbox Search | Uses Mapbox Search Box. Results are documented for temporary use; confirm your Mapbox agreement permits storing checkout address data. | Docs · Pricing |
| HERE Geocoding & Search | Create a project and REST API key in the HERE platform. | Docs · Pricing |
| TomTom | Create a key with Search API access. | Docs · Pricing |
| Loqate | The integration uses Loqate Address Capture, including container drill-down to retrieve a final address. | Address Capture docs · Pricing |
| LocationIQ | Create an access token and test coverage for every destination country. | Docs · Pricing |
| Geoapify | Create a project and API key, then review current quota and terms. | Docs · Pricing |
Provider comparison
The right provider depends on the store's shipping countries, local address formats, expected checkout volume, account requirements, and how each service returns structured address components.
For a practical selection framework, compare Google Places, Mapbox, HERE, TomTom, Loqate, LocationIQ, and Geoapify in the WooCommerce address autocomplete providers guide.
Country restrictions
The plugin reads the store's WooCommerce country configuration and shows the resulting restriction as a read-only setting. Change the relevant selling and shipping destinations under WooCommerce → Settings → General, then return to the Address Autocomplete tab.
Google Places (New) accepts up to 15 region codes. Google Places (Legacy) accepts up to 5 countries. Other providers have their own request rules. Keep the store's destination list focused and test the selected provider with each supported country.
Privacy and provider terms
The provider API key is not exposed to frontend JavaScript. However, address autocomplete necessarily processes a partial address query: browser → your WordPress site → selected provider. Selecting a suggestion also requests address details from the provider.
The plugin does not by itself guarantee compliance with GDPR or any other privacy law. The store owner is responsible for reviewing the provider's terms, data-processing agreement, retention practices, international transfers, and permitted use; selecting an appropriate provider; and updating the store privacy notice.
WordPress includes suggested disclosure text under the Privacy Policy Guide. Review and adapt it to the provider and legal basis used by your store.
Before going live
- Test the billing and shipping address fields used by your checkout.
- Search for representative addresses in every country your store serves.
- Confirm the street, city, state, postcode, and country are populated correctly.
- Test the suggestion dropdown using both a mouse and keyboard.
- Confirm customers can still enter an address manually if suggestions are unavailable.
- Review your provider dashboard, usage limits, billing, and account restrictions.
Troubleshooting
No suggestions appear
- Confirm the plugin is enabled and settings were saved.
- Confirm the selected provider has a key in its own field.
- Check the provider dashboard for account, billing, restriction, or quota errors.
- Verify the entered text meets the Minimum Characters setting.
- Check whether the rolling Daily API Request Limit has been reached.
- Clear page caches and test without JavaScript optimisation or combining.
A provider request fails
Customers can continue typing their address manually. Detailed provider diagnostics appear in a dismissible frontend notice only for logged-in administrators with the manage_options capability; shoppers are not shown those details. Verify the provider key, enabled APIs, account status, country coverage, and current provider terms before testing again.
Some fields are incomplete
Providers do not always return every component for landmarks, rural addresses, or partial records. Compare several real-world addresses and another provider before treating a missing field as a plugin defect.
Need help?
Open Address Autocomplete support and include your WordPress version, WooCommerce version, selected provider, checkout type, destination country, and a redacted screenshot. Never send an API key.