Address autocomplete for WooCommerce checkout

Choose address autocomplete for WooCommerce by region and checkout method, then check incomplete addresses, manual entry and saved delivery fields.

Address autocomplete for WooCommerce fills checkout fields from a customer’s selected suggestion. Choose a method that supports your checkout and delivery countries, then verify the address saved on the order. A suggestion can still miss a unit or point to a place your carrier cannot serve.

Keep manual entry available. The customer must be able to correct a suggested address and complete checkout when the lookup service cannot find their destination.

Choose the supported address method

Start by separating address assistance from delivery approval. Autocomplete suggests matches while someone types. Format validation checks rules such as required fields or a postcode’s structure. Delivery-service validation checks the destination against the service that will carry the parcel. Passing one check does not establish the others.

WooCommerce’s address-autocomplete framework supports providers for both classic shortcode checkout and Checkout Blocks. That framework does not establish compatibility for every older extension. Record your WooCommerce version, checkout type and exact extension before changing settings.

For a documented Google-based option, Google Address Autocomplete supports both checkout types and permits manual entry. Its country restriction controls where assistance appears. Countries outside that selection use standard checkout fields. Choose only countries you sell and ship to, and keep your shipping-zone rules separate.

Google’s separate Address Validation API coverage includes Australia and New Zealand. That does not mean a Google Places autocomplete extension calls the validation service. Buy a validation integration only when its documentation identifies that service and its supported regions. A carrier’s acceptance of a parcel remains a separate check.

Configure the Google Address Autocomplete extension on an isolated copy of your store with outbound fulfilment disabled:

  1. Confirm the extension’s installed release supports the checkout shown on your checkout page. Include any custom checkout or address-field extension in this check.
  2. Create a Google Cloud project with billing enabled. Enable Places API, Maps JavaScript API and Geocoding API, then restrict the API credential to your store’s domain.
  3. Open WooCommerce > Settings > Address Autocomplete. Enter the credential, enable billing and shipping assistance, select the intended countries and save.
  4. Start with default field mapping and separate address lines. Select a suggestion and inspect the filled fields before adding a map or custom mapping.

If suggestions fail, inspect the extension’s settings notice for an unavailable service. Check billing and domain restrictions before changing checkout fields. Keep credentials out of screenshots and support messages.

Preserve the customer’s delivery fields

Test the customer’s complete delivery details, including anything the suggestion leaves out. A correct street match can still produce an unusable parcel label if the apartment number disappears.

Use the following fictional inputs as field-mapping exercises. They are invented examples, not verified postal destinations. For a real suggestion test, use provider-approved test data without sending a customer’s address.

Address cases to work through

CaseFictional inputExpected saved-order check
House18 Example Street, Exampleton, WA 6999Street number and name stay together. Locality, state, postcode and country occupy their own fields.
UnitUnit 7, 18 Example StreetUnit 7 survives in address line 2 or the deliberately configured equivalent.
BusinessExample Retail, Loading bay B, 18 Example StreetCompany and receiving instructions survive in their intended fields. A place name does not replace the street.
Postcode mismatchExampleton with a different postcodeThe customer can correct the locality or postcode. A plausible format does not prove the pair is right.
Unsupported destinationAn invented rural delivery description with no matchManual entry stays available. The order retains what the customer entered.

For each case, write down the intended shipping fields before touching autocomplete. Select a suitable suggestion where one exists, then add missing details manually. Submit the isolated order and compare its saved shipping address with your expected fields. Inspect billing separately, even when the customer initially uses the same address for both.

Now select a second suggestion after adding a unit. Watch whether the old unit remains attached to the new street or disappears without warning. Either result needs a clear correction path before the customer places the order.

If a suggestion is incomplete or rejected, leave the customer’s typed details available for editing. Do not force a customer to select an unrelated match just to continue. A postcode lookup that reveals fields only after a search also needs a usable failure path.

Verify checkout and the fulfilment record

An address method is ready when customers can correct their details and the fulfilment system receives the intended shipping address. A completed-looking checkout form is only the first checkpoint.

  1. Use the keyboard to enter an address, move through suggestions and choose a result. Confirm focus remains visible and the customer can reach every field without a mouse.
  2. Dismiss suggestions and finish by hand. Repeat on a phone and with a screen reader, checking field labels and any error announcement.
  3. Change country after selecting a result. Confirm the form does not keep an old state or postcode that belongs to the previous country.
  4. Simulate an unavailable lookup service on the isolated store. Confirm manual checkout still works and entered details remain intact.
  5. Place an order with different billing and shipping addresses. Reload the order in administration and compare both records with the intended values.
  6. Inspect a test packing slip, label preview or disconnected fulfilment export. Confirm it uses shipping details and preserves the unit, company and any supported delivery instructions.

Inspect the lookup request with fictional data to establish what the selected service receives. Record whether typed address fragments leave the browser, which provider receives them and whether a server relays the request. Compare that behaviour with the provider’s terms and your store’s privacy information. Save only redacted evidence.

If checkout is correct but the label loses a unit, compare the saved order with the export mapping before changing autocomplete. If the wrong address appears in both, inspect field mapping and the customer’s final correction. The WooCommerce checkout guide helps verify the surrounding order flow after the address checks pass.

Keep the tested checkout type, extension release and fulfilment mapping with your store’s operating notes. Repeat the affected cases after a checkout, address-service or fulfilment update.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup