Geo Controller integrates with WooCommerce’s geolocation, price formatting, payment gateway, and order data systems.
Because WooCommerce supports different checkout implementations, payment providers, themes, and caching configurations, some integration features may behave differently between stores.
This guide explains the main compatibility considerations and provides practical troubleshooting steps.
WooCommerce Integration Requirements
Before troubleshooting, verify that:
- WooCommerce is installed and active.
- Geo Controller is installed and active.
- WooCommerce integration is enabled in Geo Controller’s settings.
- The relevant Geo Controller feature is available under your license.
- The WooCommerce and Geo Controller versions meet the published compatibility requirements.
- Any required payment gateway or related extension is installed and configured.
Classic Checkout and Checkout Blocks
WooCommerce provides different checkout implementations, including traditional shortcode-based checkout and the newer Cart and Checkout Blocks.
Geo Controller includes integrations with classic checkout hooks and WooCommerce Store API order processing hooks.
However, not every feature uses the same rendering and execution mechanisms.
Currency Conversion
Geo Controller’s built-in price conversion relies on WooCommerce PHP price-formatting hooks.
Some blocks generate pricing interfaces using JavaScript and Store API data, so converted price output may differ from classic WooCommerce templates.
Payment Gateway Restrictions
Geo Controller uses WooCommerce’s available payment gateways filter to apply country-based restrictions.
Supported Store API integrations can use this filtering mechanism, but each individual payment provider must support the checkout implementation.
Order Location Logging
Geo Controller includes integration points for saving location information during both classic checkout and Store API checkout processing.
Stores should still verify that order information is correctly saved with their active checkout configuration.
High-Performance Order Storage (HPOS)
WooCommerce High-Performance Order Storage uses dedicated order tables instead of relying exclusively on WordPress post storage.
Geo Controller uses WooCommerce order APIs when reading and writing supported order information, allowing compatibility with HPOS and traditional WooCommerce order storage.
For stores migrating to HPOS, test order creation and verify that the GEO Location Info panel displays the expected information.
Converted Prices Are Not Appearing
If visitors are not seeing localized currency prices:
- Verify that Geo Controller’s WooCommerce integration is enabled.
- Check the selected Currency conversion options mode.
- Confirm that Geo Controller returns geographic and currency conversion information for the visitor.
- Check whether the visitor’s currency differs from the WooCommerce store currency.
- Test the output on a traditional WooCommerce product page.
- Check whether your current page uses blocks or another JavaScript-based pricing component.
- Temporarily exclude the test page from full-page caching to identify possible cache-related differences.
For additional details, see Currency Options.
Incorrect Currency or Unexpected Price Formatting
Check the WooCommerce store’s base currency and the exchange rate returned by Geo Controller.
Review the following settings:
- Currency conversion mode.
- Conversion percentage adjustment.
- Price rounding configuration.
- WooCommerce currency position.
- Decimal separator.
- Thousand separator.
- Number of decimal places.
If another currency conversion extension is installed, check whether both plugins are attempting to modify the same price output.
Remember that a localized display currency does not automatically change the currency used to complete a payment.
Payment Method Is Missing
If a payment gateway is not available during checkout:
- Verify that the payment gateway is installed, enabled, and correctly configured in WooCommerce.
- Open WooCommerce → Settings → Payments Control.
- Review the geographic rule configured for the affected gateway.
- Check the customer’s selected billing country.
- Confirm that the payment provider supports the customer’s country and transaction currency.
- Check whether the gateway supports Classic Checkout, Checkout Blocks, or both.
- Test with a guest customer and a logged-in customer.
Geo Controller applies additional geographic availability rules but does not override the payment gateway’s own restrictions.
Incorrect Customer Country
If WooCommerce appears to use an unexpected country, verify the country returned by Geo Controller and compare it with the customer’s WooCommerce billing information.
Possible causes include:
- VPN or proxy usage.
- Incorrect visitor IP detection.
- Cloudflare or reverse-proxy configuration.
- Previously saved WooCommerce customer information.
- Customer session data.
- Cached content generated for another geographic location.
Keep in mind that IP geolocation is approximate and cannot reliably determine a customer’s precise physical location.
Geolocation and Taxes
Geo Controller supplies geographic information to WooCommerce but does not independently calculate tax rates.
If taxes appear incorrect, review WooCommerce’s tax settings, configured tax classes and rates, customer address information, and the geographic values returned by Geo Controller.
Do not use IP geolocation alone as evidence of a customer’s legal tax residence.
Page Caching and Geographic Personalization
Full-page caching can affect geographically personalized content when a page generated for one visitor is reused for another visitor.
This can result in incorrect country information, currency displays, or other location-specific elements appearing on a cached page.
Review your WordPress caching plugin, server-level caching, and CDN configuration when troubleshooting location-dependent behavior.
For checkout-related pages, follow WooCommerce’s caching requirements to avoid caching cart, session, and customer-specific information incorrectly.
Express Payment Buttons
Some payment providers display express-payment buttons outside the standard WooCommerce checkout payment gateway list.
These buttons may require separate compatibility testing because their availability and rendering behavior can be controlled by the provider’s own JavaScript or checkout integration.
Do not rely exclusively on hiding a frontend button as enforcement of a payment restriction. The provider and checkout must also validate payment availability.
What to Include in a Support Request
If you need technical assistance, provide:
- Geo Controller version.
- WooCommerce version.
- WordPress and PHP versions.
- Active theme.
- Classic Checkout or Checkout Blocks configuration.
- Affected payment gateway, if applicable.
- Relevant Geo Controller and WooCommerce settings.
- Steps required to reproduce the issue.
- Relevant PHP warnings or browser console errors.
Do not publish customer IP addresses, payment credentials, or other sensitive information in public support requests.
Contact Support
If the issue remains unresolved, visit the Geo Controller Contact & Support page.