Stores comparing Google Places vs Mapbox vs Loqate for WooCommerce autocomplete are usually asking the same question: which API should fill the shipping address as the customer types? All three can show a suggestion dropdown on address line 1, fetch a structured result, and populate street, city, state, postcode, and country. They are not the same product, and the right pick is usually the network you already pay for, plus the apartment behaviour you need.
Google Places is a Maps Platform search API. Mapbox Address Autofill is Search Box suggest and retrieve. Loqate Address Capture is GBG structured postal search. Address Guard Pro treats them as interchangeable autocomplete providers, so you can choose any one, then pair it with a separate validation vendor.
This article compares Google Places vs Mapbox vs Loqate WooCommerce autocomplete in practical terms: what each fills, how nested units differ, how billing works, and when to pick one over the others. For the checkout flow itself, see the WooCommerce address autocomplete guide. Dedicated setup lives in Mapbox address autocomplete for WooCommerce. Autocomplete is not the verify step. That split is covered in WooCommerce address validation vs autocomplete.
The short answer
Choose Google Places when you already have a Google Maps Platform project, want Places suggestions and Address Validation on one API key, or want customers to search the way they search in Maps.
Choose Mapbox Address Autofill when you already have a Mapbox token, want search-quality street suggestions without putting Google Places on checkout, or plan to validate with a different vendor.
Choose Loqate Address Capture when you already have a Loqate or GBG account, ship a lot of flats and office suites, or need nested building-then-unit results that land the apartment on address line 2.
None of them replaces WooCommerce shipping zones, tax, or carrier rates. Those still run on country, state, and postcode. Autocomplete answers a different question: can the customer enter a complete, consistent address without typing six fields by hand?
What all three providers do at WooCommerce checkout
WooCommerce only checks that required fields are filled in. A missing house number, a postcode from another country, or a street name with a typo will still pass. Google Places, Mapbox, and Loqate Capture all close that gap on address line 1.
Address Guard Pro attaches suggestions after a few characters (commonly three). The customer picks a match. The plugin then fills:
- Address line 1 (street and house number)
- Address line 2 when the provider returns a unit, apartment, or building name
- City
- State or region
- Postcode
- Country
The customer can still type freely. Autocomplete does not replace the form, and it does not force a selection. That is why it feels light at checkout: the correct, consistent address becomes the easy path.
If they ignore the dropdown and type a fake street, checkout still works. That is why most stores that print shipping labels also run a validation provider at place-order. Autocomplete stops the typo. Validation checks the result before payment.
That shared checkout behaviour is why Google Places vs Mapbox vs Loqate is a provider decision, not a plugin decision. The customer-facing flow is the same. The data network, nested-unit behaviour, and billing account are what change.
Google Places vs Mapbox vs Loqate: side by side
| Google Places | Mapbox Address Autofill | Loqate Address Capture | |
|---|---|---|---|
| Company | Google Maps Platform | Mapbox | Loqate (GBG) |
| Autocomplete product | Places API (New) | Search Box (suggest and retrieve) | Address Capture |
| Validation pair | Google Address Validation | None in Address Guard Pro. Pair with Google, Loqate, or Smarty. | Loqate Address Verify |
| What it searches | Place data: streets, addresses, and place-like names | Streets and addresses, not businesses or landmarks | Structured postal search against Loqate records |
| Nested units | A selected place. Unit data depends on the result. | Feature retrieve. Unit data depends on the result. | Can drill from building to apartment, then fill sub-building |
| Address line 2 | Filled when place details include a unit | Filled when the feature includes a unit | Mapped from Loqate sub-building after nested capture |
| Billing | Google Cloud project, Maps quotas and SKUs | Mapbox token, Search Box suggest and retrieve | Loqate credits, Capture enabled on the key |
| Credentials | Merchant-owned Google API key | Merchant-owned Mapbox access token | Merchant-owned Loqate API key |
| Best fit | Stores already on Maps, or that want Places plus validation on one key | Stores already on Mapbox, or that want search without Places or Capture | Stores already on GBG, or that need nested Capture for apartments |
| Works without validation? | Yes. More typed addresses will fail later in fulfilment. | Yes. Same risk. Mapbox is autocomplete only. | Yes. Same risk. Capture is not Verify. |
| Can mix with another vendor’s validation? | Yes. Places plus Loqate Verify or Smarty is valid. | Yes. That is the usual Mapbox setup. | Yes. Capture plus Google Address Validation is valid. |
The validation vs autocomplete comparison is worth reading if you are still deciding which layer to enable first. Google Places vs Mapbox vs Loqate is the next decision: which network powers the dropdown.
Nested units: the autocomplete difference that matters
Stores often treat “Google at checkout,” “Mapbox at checkout,” or “Loqate at checkout” as a single feature. Each vendor is a search product. Only Loqate Capture is built around nested postal results.
| Product | How the customer picks an apartment |
|---|---|
| Google Places | Search against place data. Selecting a result fetches place details. A unit may be present. There is no dedicated building-then-unit drill-down. |
| Mapbox Address Autofill | Search Box returns streets and addresses. Selecting one retrieves the feature. A unit may be present. There is no nested Capture tree. |
| Loqate Address Capture | Structured postal search. For a building with many units, the customer can pick the building, then the apartment. Address Guard Pro maps Loqate’s sub-building into address line 2. |
If your failed labels are mostly missing unit numbers in dense housing, Loqate Capture is usually the stronger autocomplete. Flats, condos, and office suites are the usual reason stores pick it over Places or Mapbox.
If your customers already live in Maps-quality search, Google Places is usually enough. It is excellent at filling a complete street quickly, including mixed formatting and place-like names.
If you want search-quality street suggestions without putting Places or Capture on checkout, Mapbox is the usual third option. Address Guard Pro does not use Mapbox as a validation provider, so you will still connect Google, Loqate, or Smarty for the verify step.
You do not have to pair autocomplete and validation from the same vendor. Address Guard Pro keeps them as separate choices.
How each provider fills the WooCommerce form
The customer experience looks similar. The request pattern is not.
Google Places typically needs two steps: a suggestion list, then a place-details request for the selected place ID. Street, city, state, postcode, and country come from place components, not from the dropdown label.
Mapbox Address Autofill also needs two steps. Search Box suggest returns the dropdown. Mapbox does not put the full postal address in that list. A second Search Box retrieve request fetches street, house number, city, state, postcode, and country for that feature.
Loqate Address Capture returns structured capture results. Nested items can expand a building into units before the form is filled. When a unit is selected, sub-building belongs on address line 2 so the carrier sees the apartment, not only the street door.
On classic checkout, WooCommerce refreshes the form after country changes so the correct state field appears. On Checkout Blocks, the cart store is updated so shipping methods can recalculate. All three providers go through that same WooCommerce sync. The provider only changes which API supplied the components.
If the customer has already chosen a checkout country, that country should win. Otherwise a suggestion from another market fills the form, and shipping methods and tax look wrong. Limit autocomplete countries to the destinations in your shipping zones for all three vendors.
Coverage, search quality, and shipping countries
None of the three is “international” in the abstract. Coverage is about the countries you actually ship to, and how those countries write addresses.
Pick Google Places when:
- You already trust Maps results in your shipping countries
- Customers search the way they search in Google (street, building name, mixed formatting)
- You want one Maps project to cover many destinations without a second search contract
Pick Mapbox when:
- You already have a Mapbox account and want checkout to use the same token
- You want street and address suggestions, not businesses or points of interest
- You want search-quality Autofill and will validate with Google, Loqate, or Smarty
Pick Loqate Capture when:
- You already buy GBG data for those markets
- You need postal-grade formatting (especially UK, EU, and other postcode-heavy countries)
- Apartments, sub-buildings, and organisation names need to land in the right WooCommerce fields
Do not choose an autocomplete provider because a demo address in one city looked perfect. Test the destinations in your shipping zones: a capital-city street, a rural property, a new-build, and an apartment with a unit number. The provider that fills your order mix is the one that will save fulfilment time.
For a mostly US catalogue, also consider Smarty Autocomplete. Address Guard Pro supports it. Google Places vs Mapbox vs Loqate is still the usual international comparison.
Billing, keys, and who owns the usage
Address Guard Pro does not bundle provider usage. You connect your own credentials and keep control of API billing.
Google Places bills through a Google Cloud project. You enable Places API (New), create an API key, and restrict that key to the APIs you actually call. If you also use Google Address Validation, enable that API on the same key. Address Guard Pro calls Google from your WordPress server, so IP address restrictions on the site’s outbound IP are appropriate. An HTTP referrer restriction that only allows your domain will block server-side autocomplete even when a client-side Places widget on another plugin appears to work.
Mapbox bills through your Mapbox account. Search Box bills suggest and retrieve separately. Every dropdown open can cost a suggest. Every selection costs a retrieve. Address Guard Pro calls Mapbox from WordPress. The access token is not exposed in checkout JavaScript. A public token locked to HTTP referrers for your storefront domain can fail even when a client-side Mapbox map on the same site works. Allow the site’s outbound IP, or use a secret token with the matching restriction.
Loqate bills through your Loqate account. Capture and Verify are separate products on the key. A key that is only enabled for Verify will fail the autocomplete test. A key that is only enabled for Capture will fail the validation test if you also want Verify. Watch IP or URL restrictions, exhausted credits, and rate limits. Those surface as provider errors, not as a generic WooCommerce checkout failure.
Cost is usage, not a plugin fee. Keep it predictable on all three vendors:
- Enable autocomplete on the shipping address. Leave billing off unless invoices or tax IDs depend on a precise street.
- Set minimum characters to 3 so search does not fire on the first letter.
- Limit autocomplete countries to the destinations you ship to.
- Pair autocomplete with validation so fewer messy typed addresses hit the verify API.
- Set validation provider errors to Mark for review so a quota, credit, or network failure does not stop paid orders.
A Google-only stack is one Maps key (Places plus Address Validation). A Loqate-only stack is one Loqate key with Capture and Verify enabled. A Mapbox stack is always a mixed stack for deliverability: Mapbox for the dropdown, Google, Loqate, or Smarty for the check. That is fine when search quality and postal verification should come from different networks.
You can mix autocomplete and validation vendors
Autocomplete and validation do not have to come from the same company.
| Autocomplete | Validation | When it makes sense |
|---|---|---|
| Google Places | Google Address Validation | Simplest Google-only setup. One Maps key. |
| Loqate Address Capture | Loqate Address Verify | Simplest Loqate-only setup. Nested Capture plus postal Verify. |
| Mapbox Address Autofill | Google Address Validation or Loqate Verify | Search-quality suggestions without Places or Capture on the dropdown. |
| Google Places | Loqate Address Verify | Maps-quality search, GBG verification. |
| Loqate Address Capture | Google Address Validation | Nested unit capture, Maps verification. |
| Mapbox Address Autofill | Smarty | Search-quality suggestions with a US-focused validator. |
The usual reason to mix is an existing contract. You already pay for Places, you already pay for Mapbox Search Box, or you already pay for Loqate Verify. Address Guard Pro does not force you to buy the matching product from the same vendor.
Mapbox is the provider that must mix if you need a postal check. Address Guard Pro does not use Mapbox as a validation provider. Places and Capture can stand as autocomplete-only, but most stores that print labels still add the matching (or a mixed) verify step.
What WooCommerce still will not do
Native checkout can:
- Require country, street, city, state, and postcode
- Offer shipping methods from those fields
- Copy billing into shipping
Native checkout cannot:
- Suggest real addresses as the customer types
- Fill city and postcode from a selected street
- Drill from a building into apartment units
- Confirm that the building exists
- Standardize formatting for label purchase
- Keep original versus provider-normalized data on the order
Browser autofill is not Google Places, Mapbox, or Loqate. Autofill replays an address the customer saved earlier. It will fill a stale or incomplete address just as readily as a good one. A Places, Search Box, or Capture suggestion is structured search data. It is still not proof that a carrier will accept the address. Google Address Validation, Loqate Address Verify, and Smarty are the separate check against postal records.
How to connect any of the three in Address Guard Pro
The admin path is the same. Only the credentials change.
- Go to WooCommerce → Address Guard → Providers.
- Choose Google Places, Mapbox Address Autofill, or Loqate Address Capture.
- Enter the matching API key or access token.
- Optionally set Autocomplete countries to the markets you ship to.
- Click Test autocomplete provider.
- If you want a check before payment, choose a Validation provider on the same screen and run that test too.
- Enable autocomplete on the shipping address under Checkout. Start with minimum characters set to 3.
Do not enable autocomplete on checkout until the test you intend to use succeeds. A failed Google test is usually a missing Places API, a key restricted to HTTP referrers, or a billing problem. A failed Mapbox test is usually a token without Search Box, a URL restriction that blocks server requests, or exhausted quota. A failed Loqate test is usually Capture not enabled on the key, a restriction, or exhausted credits.
Full Mapbox steps, including token restrictions and live checkout tests, are in the Mapbox autocomplete guide. Google and Loqate pairing, including validation, is in the Google setup guide and the Loqate setup guide.
Keep this on the shipping address. That is the address on the label. Billing can stay quieter. A customer may bill to a registered office and ship to a street. Those forms should stay independent.
After the customer continues
Autocomplete only helps fulfilment if the filled address is the one you ship to, and if someone can see what happened when it was not.
Address Guard Pro stores the original address, the provider-normalized address when validation ran, the validation status, matched rules, and the checkout action. Open the order and check the Address Guard panel before you buy a label when:
- The status is unverified or invalid
- The customer was warned and continued
- A suggested address was shown and declined
- A Google, Mapbox, or Loqate API error occurred
If missing unit numbers keep leading to return-to-sender parcels, Loqate Capture may be a better dropdown than Places or Mapbox. If the dropdown is ignored and fake streets still pay, add validation. That loop is how you learn whether the autocomplete provider is actually reducing failed labels in your countries, rather than arguing about vendor marketing.
A decision guide
| Your situation | Start with |
|---|---|
| You already pay for Google Maps Platform | Google Places, plus Google Address Validation if you need a check |
| You already have a Mapbox account | Mapbox Address Autofill, plus Google, Loqate, or Smarty for validation |
| You already have a Loqate or GBG account | Loqate Capture, plus Loqate Verify if you need a check |
| You ship many apartments and need building-then-unit capture | Loqate Capture, with Loqate Verify or Google Address Validation |
| You want Maps-quality search without GBG | Google Places, then Google or Loqate for the check |
| You want search without putting Google or Loqate on the dropdown | Mapbox Address Autofill plus Google or Loqate validation |
| Your catalogue is mostly US and you already pay for Smarty | Smarty Autocomplete (optionally with any validation provider) |
| You only need PO box or house-number rules | Local rules first. Add autocomplete when typing mistakes still delay labels. |
| You are unsure and ship internationally | Connect the vendor you already bill. Enable shipping autocomplete. Review a week of orders before you switch. |
If you are choosing from a blank sheet, pick the simpler stack: one vendor you already pay for, shipping only, then add validation on warn. Switching later is a Providers screen change, not a checkout rebuild.
Common questions
Is Google Places the same as Mapbox Address Autofill or Loqate Address Capture?
No. All three are autocomplete. Places fills the form from Google place data. Mapbox fills it from Search Box features. Capture fills it from Loqate search and can nest a building into units. None of them is the validation step.
Is Google Places the same as Google Address Validation?
No. Places is the dropdown. Address Validation is the check before the order is placed. See Google Address Validation for WooCommerce.
Is Loqate Capture the same as Loqate Address Verify?
No. Capture is autocomplete. Verify is the postal check. See Loqate Address Validation for WooCommerce.
Does picking a Places, Mapbox, or Capture suggestion mean the address is validated?
No. A suggestion is structured capture from search data. Google Address Validation, Loqate Address Verify, and Smarty are separate checks against postal records. Run both layers if you need deliverability, not only a filled form.
Can I use Google Places with Loqate Verify, or Loqate Capture with Google Address Validation?
Yes. Autocomplete and validation are separate choices in Address Guard Pro. Mixing vendors is a normal production setup. Mapbox always needs a different vendor for validation.
Which is more accurate?
It depends on the country, the address format, and whether the failure is a typo, a missing unit, or a coverage gap. Test your shipping destinations. Do not pick an autocomplete provider from a single demo city.
Which is best for apartments?
Loqate Address Capture, when nested building-then-unit results matter. Places and Mapbox can still fill a unit when the selected result includes one. They are not the same nested Capture tree.
Does this work with Checkout Blocks?
Yes. Address Guard Pro supports Checkout Blocks and classic [woocommerce_checkout]. Test the type your store actually runs, including a phone-width viewport so suggestions are not clipped.
Will Google Places, Mapbox, or Loqate replace shipping zones?
No. Shipping zones decide which methods to offer. Autocomplete helps the customer enter country, state, and postcode so those zones can calculate. It does not decide whether the address is deliverable.
What if the API is down or over quota?
Checkout should still accept a typed address. If you also run validation, set provider errors to Mark for review so a billing, quota, credit, or network failure does not become a payment failure.
Do I need both autocomplete and validation?
If you print shipping labels, yes for most stores. Autocomplete makes the correct address easy to enter. Validation confirms it before payment. See WooCommerce address validation vs autocomplete.
What about API cost?
You pay the provider directly. Address Guard Pro does not resell lookups. Keep costs down by setting a minimum character threshold, limiting countries, and avoiding autocomplete on billing unless you need it.
Pick the dropdown, then check the address before payment
Google Places vs Mapbox vs Loqate for WooCommerce autocomplete is not a choice between three plugins that do different jobs. All three fill the shipping address while the customer is still typing. Google Places is the Maps Platform path: search the way customers already search, then optionally validate on the same key. Mapbox is the Search Box path: street suggestions without Places or Capture, then a separate validator. Loqate is the GBG path: nested Capture for buildings and units, then Verify if you want a postal check.
Choose the vendor you already pay for, or the one that covers your shipping countries and apartment formats best. Mix them if search and verification should come from different networks. Keep the dropdown on shipping, start with a working provider test, and add validation so fulfilment is not guessing.
Learn more about Address Guard Pro, or start with the setup guide: Get Started.