Server-side API proxy
Geocoding requests go through your WordPress REST endpoint, so provider API keys are not exposed in page source or browser network requests.
Help customers complete billing and shipping address fields faster, reduce avoidable typos, and keep geocoding API keys protected with a server-side WordPress proxy.
Address Autocomplete is designed for one practical workflow: better address entry inside WooCommerce checkout.
Geocoding requests go through your WordPress REST endpoint, so provider API keys are not exposed in page source or browser network requests.
Choose Google Places (New), Google Places (Legacy), Mapbox, HERE, TomTom, Loqate, LocationIQ, or Geoapify through one plugin interface.
When a suggestion is selected, address details can populate street, city, state, postcode, and country fields.
Registers the selected provider with WooCommerce's native autocomplete framework for classic and block checkout where available, with a compatibility interface for older supported versions.
The plugin can read WooCommerce shipping countries and restrict suggestions to destinations your store actually serves.
Choose an explicit light or dark suggestion dropdown. WooCommerce renders the native interface where available; older supported versions use the plugin's compatibility styling.
Keyboard navigation, ARIA attributes, screen-reader support, Escape handling, and outside-click closing are built in.
Compatibility with WooCommerce High Performance Order Storage is declared to avoid unnecessary status warnings.
A lightweight provider adapter connects to WooCommerce's native checkout interface where available. Provider API requests stay server-side, without bundled geocoding SDKs.
Connect the provider that best fits your store, region, and expected checkout volume. The checkout integration stays the same, and the active provider can be changed from the plugin settings.
Useful for merchants with existing Mapbox, HERE, TomTom, LocationIQ, or Geoapify accounts, and agencies standardising those services across client stores. QuixWP adds provider choice and request controls to Core's framework without requiring WooPayments.
The plugin avoids the common mistake of exposing provider API keys directly in frontend JavaScript.
Provider requests are proxied through WordPress instead of exposing keys to the browser.
If a provider fails, checkout remains usable and customers can still type their address manually.
Configuration lives under WooCommerce settings and follows normal WordPress admin patterns.
PHP filters and JavaScript events are available for custom checkouts and integrations.
All provider options and core checkout features are included. Geocoding provider costs are billed separately by the provider you choose.
Planned Woo Marketplace release with updates and support.
Start with the provider whose coverage, terms, and current pricing fit your store. Test address quality in every country you sell to before launch.
Yes. The plugin sends geocoding calls through your WordPress server, so keys are not exposed in frontend JavaScript.
Yes. The plugin is designed for both classic checkout and WooCommerce block checkout.
The address field remains usable as a normal text input, so checkout is not blocked.