CodeCanyon Google Checkout Address Suggestion And Autocomplete For WooCommerce - WordPress Plugin

Configuration Guide for CodeCanyon Google Checkout Address Suggestion And Autocomplete For WooCommerce

CodeCanyon Google Checkout Address Suggestion And Autocomplete For WooCommerce solves a narrow but painful ecommerce problem: it helps customers fill in their shipping and billing addresses faster at checkout. This guide does not repeat the product listing. Instead, it walks through store preparation, connecting Google Places, configuring WooCommerce fields, validating the result with a test order, and troubleshooting cases where address suggestions do not appear.

This plugin belongs to the category of WooCommerce checkout extensions. Its value shows up not in the admin panel, but at the moment a customer types an address: less manual entry, fewer typos, and fewer incomplete addresses in orders. It is also important to understand the tool's limits. It does not replace a shipping service, does not verify whether delivery is available to the selected address, and does not correct your store's business logic.

Compatibility with checkout field editors deserves special attention. The CodeCanyon page lists support for YITH WooCommerce Checkout Manager and Checkout Field Editor, but those combinations require careful validation of custom field names and JavaScript loading order. This is one of those cases where installation may look successful at first, while address suggestions on the live checkout work only partially.

What problem address autocomplete solves in WooCommerce

In a standard WooCommerce checkout, the customer manually fills in the country, street, house number, city, state, and ZIP/postal code. That is manageable for short local deliveries, but stores serving many regions tend to see the same types of mistakes: the wrong postal code, the city entered in the state field, an address without a house number, or extra notes crammed into the first address line. This plugin adds a suggestion field and uses the Google Places API to offer addresses as the customer types.

After a suggestion is selected, the data is mapped into the standard WooCommerce fields. In the ideal flow, the customer types a few characters, picks the right address, confirms an apartment or office number in the second line, and moves on to payment. The main benefit of the plugin is not a decorative suggestion box, but cleaner address data in the order.

Where the impact is most noticeable

• In stores with physical delivery, where an address mistake leads to follow-up calls and order re-confirmation.
• In stores handling international or cross-region orders, where address formats vary by country.
• On sites with a high share of mobile orders, where long address forms are slower to complete.
• In projects where staff manually check the postal code, city, and state before sending the order to fulfillment.

The plugin does not make an address legally verified. Google Places returns structured components, but address formats differ, and in some countries the city may come back not as a standard city value but as a postal locality or district. That is why, after installation, you should test several real addresses from your delivery zones.

Who this product is for and when to choose a different solution

This plugin is worth considering for store owners using the classic WooCommerce checkout who need a fast way to add address suggestions without building a custom provider. The product page lists support for billing and shipping addresses, suggestion language selection, country-based result restrictions, and compatibility with popular checkout field managers.

It is especially useful if the store already uses standard WooCommerce fields or a carefully configured checkout field manager. In that kind of setup, the extension handles one clear function without forcing you to rebuild the entire checkout flow.

When to be more cautious

If your checkout is built with WooCommerce blocks, a custom builder, or is heavily modified by the theme, test compatibility on a staging copy first. WooCommerce documentation describes a separate address-autocomplete architecture for modern providers, while older plugins are often designed for the classic form and standard field names. The CodeCanyon page lists compatibility with WooCommerce 6.x-9.x and WordPress 4.9-6.7, but that is not the same as guaranteed support for every visual checkout builder.

You should not treat this plugin as a replacement for full address validation. If your business must verify delivery availability down to a specific building, warehouse district, courier zone, or apartment format, you will need additional validation through your shipping service or a specialized address validation service.

Practical rule: autocomplete speeds up address entry, but the final delivery decision should come from your checkout logic, shipping service, or manual staff review.

What to check before installation

Preparation matters more than the installation itself. If the Google API is not enabled, the key is not restricted by domain, or the checkout does not use the expected fields, the plugin may install successfully, but customers will never see suggestions. Below is a checklist worth going through before you upload the ZIP archive.

WordPress and WooCommerce versions, and the checkout type

The CodeCanyon page lists the product as compatible with WooCommerce 6.x-9.x and WordPress 4.9-6.7. If your site is already running on a newer stack, do not draw conclusions from the version number alone. First enable the plugin on a staging copy and test the full checkout flow from cart to order creation.

• Open the checkout page in the WordPress editor and verify whether it uses the classic [woocommerce_checkout] shortcode or the Checkout block.
• Make sure the theme is not replacing standard address fields with custom markup that drops the usual WooCommerce field names.
• Check that the billing_address_1, billing_city, billing_postcode, billing_country, and corresponding shipping fields are not disabled.
• If you use a field manager, document the current field order in advance and export the settings if the field manager plugin supports that.

Google Cloud and the API key

Suggestions require a Google Maps Platform key with the capabilities needed for Places and for loading the JavaScript library on the site. Google documentation emphasizes that keys should be restricted both by application type and by API. For a website, that usually means restricting it by HTTP referrer, in other words, by the store domain.

Do not place an unrestricted key on a production site. Google explicitly warns that the project owner is responsible for any charges caused by misuse of an unrestricted key. For a WordPress store, the safer approach is to create a separate key for the public-facing site, allow both production and staging domains, enable only the required APIs, and set up budget alerts in Google Cloud.

Privacy policy and customer data

Address suggestions mean that part of the typed address text is sent to Google in order to return matching options. This is not payment data and not order contents, but if your store has strict privacy requirements, that fact should be reflected in your privacy policy. This is especially important for sites serving customers in regions with separate personal data processing requirements.

Installation and initial validation without risking live orders

Magerips documentation describes two standard installation methods: uploading the ZIP through the WordPress admin panel and manually uploading the plugin folder to wp-content/plugins. For most store owners, the safer option is to use Plugins - Add New - Upload Plugin, because WordPress will unpack the archive itself and show an error if the wrong package was selected.

1. Create a site backup or perform the installation on a staging copy.
2. Open Plugins - Add New - Upload Plugin.
3. Select the plugin archive from the CodeCanyon package. The documentation lists the filename as rp-address-suggestion.zip.
4. Click Install Now, then Activate Plugin.
5. Go to WooCommerce - Address Suggestion and make sure the settings page opens without errors.

After activation, do not turn on every mode at once. First confirm that the settings page is accessible, the API key can be saved, and the checkout loads without JavaScript errors. Only then should you enable autocomplete for billing and shipping.

Quick post-install check: the checkout page should open without a blank screen, the browser console should not show Google Maps JavaScript API errors, and the address fields should remain available for manual input even when autocomplete is turned off.

Address Suggestion settings map after installation

The public product documentation does not describe every setting in detail, but the CodeCanyon page and Magerips help materials confirm the main areas: the Google key, address field text, suggestion language, billing and shipping enablement, country restrictions, and compatibility with field managers. Below is a practical configuration order that reduces the risk of breaking checkout.

Enable only one address block first

Start with the billing address. Enable suggestions for billing, save the settings, and test the checkout page. If the field works, then enable shipping. This order makes troubleshooting easier: if you turn on both blocks at once and hit an error, it is harder to identify the conflict.

Suggestion language and field text

The CodeCanyon page states that the administrator can change the address text and choose the suggestion language from the Google-supported options. For a Russian-language store, for example, it makes sense to use a label the customer immediately understands, such as "Start typing your address." At the same time, the data returned by Google may vary depending on the selected language, the country, and the quality of the underlying regional data.

Do not make the label too long. The field sits inside checkout, where the customer is already looking at a lot of required information. The best field text explains the action rather than advertising the feature.

Restricting suggestions by country

If the store ships only to a limited list of countries, enable suggestion restrictions. This reduces irrelevant results and lowers the risk that a customer selects an address outside your delivery area. The product changelog specifically mentioned fixes for certain countries, so whenever you change the country restriction, test several real addresses.

Do not confuse suggestion restrictions with delivery restrictions. The suggestion box may hide unsupported countries, but WooCommerce shipping rules still need to be configured separately in shipping zones.

When to use country restriction hooks

The product page provides hooks for restricting results separately for billing and shipping addresses. Use them only if the built-in settings are not enough and you know where your custom code is stored. The safest location is a child theme or a separate code snippets plugin. Before adding the snippet, create a backup and test it on a staging checkout.

add_action('rpgaac_search_in_specific_billing_country', function() {
    return 'US';
});

add_action('rpgaac_search_in_specific_shipping_country', function() {
    return 'US';
});

Replace US with the required two-letter country code. If suggestions disappear after adding the snippet, disable it and go back to configuring the restriction through the plugin interface. Do not edit the plugin files directly, because those changes will be lost during an update.

How Google Places, address components, and WooCommerce fields work together

Google Places Autocomplete returns more than a single string. It returns a set of address components. Google examples show that after a suggestion is selected, you can receive components such as the street number, street name, city, state, country, and postal code. WooCommerce, in turn, stores addresses in separate billing and shipping fields. The plugin's job is to connect those two worlds.

In practice, that means the quality of the result depends on three things: what Google returned, which fields are available in checkout, and how the plugin mapped those components into WooCommerce. If a country uses an unusual address format, one component may land in the wrong field or not be returned at all. Google specifically notes that address components vary by region, so testing needs to be local.

Which fields to check after selecting a suggestion

• Address line 1 should receive the street and house number if Google returned that data.
• Address line 2 is best left available for an apartment, office, entrance, or building section.
• City should match the locality your shipping process actually needs.
• State or region should be saved in the format WooCommerce expects for the selected country.
• Postcode should be filled only if the suggestion data includes a postal code.

If the postal code or state field is sometimes empty, that does not always mean the plugin is broken. Sometimes Google does not return that component for the selected option, and sometimes WooCommerce expects a different state value. In those cases, it is better to leave manual field editing enabled and provide a clear hint for the customer.

Compatibility with Checkout Field Editor, YITH, and modified fields

This product matters not only for standard checkout setups. The CodeCanyon page lists support for YITH WooCommerce Checkout Manager and Checkout Field Editor. For Checkout Field Editor, the developer specifies that you need to add fields named billing_address_rpgaac and shipping_address_rpgaac. This is a key detail that is often missed: visually, the field may exist, but if its technical name is different, the plugin will not be able to use it as expected.

How to configure the field in a checkout field manager

1. Open your checkout field manager settings.
2. Create a separate address suggestion field in the billing section named billing_address_rpgaac.
3. Create the same type of field in the shipping section named shipping_address_rpgaac.
4. Place the field before the standard first address line so the customer selects a suggestion first and can then refine the details.
5. Save the settings and test checkout as a guest, not only while logged in as an administrator.

Do not remove the standard WooCommerce fields immediately after adding the suggestion field. Autocomplete should feed data into the regular order address fields. If you hide or remove part of those fields, you may end up with a polished-looking form but an incomplete address in the order.

What to check when using YITH WooCommerce Checkout Manager

YITH lets you change fields, order, labels, placeholders, and display conditions. That is convenient, but any conditional hiding of address fields affects autocomplete. If a field appears only after the customer selects a country or customer type, make sure it already exists at the moment the Google suggestion is chosen. Otherwise, JavaScript may try to populate a field that is not yet on the page.

Safe approach: first make autocomplete work with the default fields, then re-enable conditions, field reordering, and visual adjustments one by one.

Practical example: a test order with address autocomplete

The example below is not just about checking whether a suggestion appears. It is about validating the full customer flow. The goal is to confirm that the suggestion populates the fields, WooCommerce accepts the order, and the admin panel stores an address that is actually usable for delivery.

Goal

Get a working checkout where the customer starts typing an address, selects a suggestion, confirms the apartment or office details, places a test order, and the store manager sees correct billing and shipping data.

Preparation

• A simple product with a non-zero price and available shipping has been created on the site.
• A test or otherwise safe payment method is enabled so no real money is charged.
• WooCommerce shipping settings include a shipping zone for the country you are testing.
• The Google API key is saved in the plugin settings and restricted to the staging site domain.

Validation steps

1. Open the store as a guest or in a private browser window.
2. Add the test product to the cart and proceed to checkout.
3. Start typing a known address from your delivery zone into the suggestion field.
4. Select one option from the Google dropdown list.
5. Check which fields were populated automatically: street, city, state, postal code, and country.
6. Manually add an apartment, office, or other local reference in the second address line if needed.
7. Place the test order and open it in the WooCommerce admin panel.

Expected result and an important detail

The order should store the regular WooCommerce fields, not just the raw text from the suggestion field. If the admin panel shows an incomplete address, go back to checkout and check which exact fields did not populate. A common reason is that the field is hidden by the checkout field manager, renamed, or shown only after a country is selected.

Result check: success means not just seeing a suggestion in the browser, but getting a correct address in the created order with no shipping errors for the selected zone.

Checking performance, cache, and behavior on the live site

The plugin adds a JavaScript dependency and calls Google while the customer is typing an address. Normally this should not slow down the entire site, because the functionality is needed only on checkout and on account address pages if support is enabled there. But on optimized stores, conflicts can appear because of minification, deferred script loading, or aggressive caching.

What to exclude from optimization

If suggestions stop appearing after you enable an optimizer, do not disable all caching immediately. Check whether Google Maps scripts, WooCommerce checkout scripts, and the plugin scripts are being merged into a single file. Scripts like these are often sensitive to load order.

• Exclude the checkout page from full-page caching if that has not already been done.
• Disable deferred loading for the Google Maps JavaScript API and the plugin script on the checkout page.
• Do not move checkout scripts all the way to the bottom of the page if that prevents suggestions from initializing.
• After every change, clear the optimization plugin cache, CDN cache, and browser cache.

Testing across different roles and cart states

Test checkout as a guest, as a registered customer with a saved address, and as a user selecting a different shipping address. If account page support is enabled, also test the address editing section in My Account. The product changelog mentions added support for the account page, but the actual behavior still depends on the theme and WooCommerce settings.

Troubleshooting common address suggestion issues

Most issues with plugins like this tend to look the same: the field is visible but suggestions do not appear; suggestions appear but fields do not populate; the order is created but the address is incomplete. The symptoms are similar, but the causes are not. Below is a troubleshooting map you can work through without editing the plugin files.

Typical symptoms and safe checks

Symptom	Likely cause	What to check	How to fix it
The field is visible, but the address list never appears.	The key is not working, the required API is not enabled, or the request is blocked by a domain restriction.	The checkout page browser console and errors such as MissingKeyMapError, ApiNotActivatedMapError, RefererNotAllowedMapError.	Check the key in Google Cloud, enable the required APIs, and add both production and staging domains to the allowed referrers.
Suggestions appear, but the address is not mapped into the fields.	WooCommerce fields are hidden, renamed, or modified by a checkout field manager.	Whether the standard billing and shipping fields exist, and whether billing_address_rpgaac and shipping_address_rpgaac are used with Checkout Field Editor.	Restore the standard fields, disable display conditions during testing, then re-enable changes one at a time.
The address is populated, but shipping is unavailable.	WooCommerce does not have a shipping zone for the selected country, state, or postal code.	WooCommerce - Settings - Shipping, shipping zones, and postcode rules.	Configure shipping zones separately. Autocomplete does not create shipping rules.
Suggestions disappeared after site optimization.	Minification or deferred loading broke the JavaScript load order.	Optimizer exclusions for checkout, the Google Maps JavaScript API, and the plugin scripts.	Disable combining and delay for checkout scripts, clear caches, and run the test again.
In some countries, the postal code or city fills inconsistently.	Google returns address components in a regional format that does not match WooCommerce expectations.	Several real addresses from your target countries, especially the city, state, and postal code components.	Leave manual field editing available, clarify the instruction for the customer, and limit countries only where the flow has been tested.

If the error is related to the Google API, use the official Maps JavaScript API error table as your reference. It helps you distinguish between a missing key, referrer restrictions, quota limits, and an API that was never enabled. That is much faster than disabling WordPress plugins at random.

When CodeCanyon Google Checkout Address Suggestion And Autocomplete For WooCommerce is the right choice

This plugin makes sense if your store runs on WooCommerce, sells physical goods with shipping, and struggles with manual address errors. It is especially useful where checkout stays close to standard WooCommerce and the address fields have not been rebuilt from scratch. Before going live, verify the Google key, domain restrictions, shipping countries, billing and shipping scenarios, and behavior after caching is enabled.

If testing shows that suggestions appear consistently, the address is saved correctly in the order, and the customer can still manually add an apartment or office detail, you can move on to deployment on the live site. For a safe rollout, first download the ZIP archive, deploy it on a copy of the store, and run a complete test order from start to finish.

The bottom line is simple: this product is worth choosing not for a nicer-looking checkout field, but for less manual typing and cleaner WooCommerce address data. If your store needs strict address validation, a block-based checkout architecture, or a regional address database, compare it with alternatives before installing it on the live site.