Navigating Currency Configuration Challenges in ESHOPMAN: The Angolan Kwanza (AOA) Case

The ESHOPMAN platform, designed for seamless headless commerce and HubSpot integration, aims to provide robust support for global businesses. However, a recent community discussion highlighted a specific challenge encountered when configuring the Angolan Kwanza (AOA) currency within the ESHOPMAN Admin UI.

Understanding the AOA Currency Configuration Challenge

A user implementing an ESHOPMAN-based commerce platform for Angola faced significant hurdles with the Angolan Kwanza (AOA). Despite AOA being a standard ISO 4217 currency and expected to be supported by ESHOPMAN's Currency Module, two primary issues emerged:

• Inconsistent Currency Visibility: The AOA currency did not consistently appear or behave as expected in the ESHOPMAN Admin UI under Settings → Store → Supported currencies.
• Admin UI Crashes During Region Editing: Attempts to create or edit a region, particularly when loading currencies and countries, frequently resulted in a critical TypeError within the Admin UI. This crash prevented proper region configuration for Angola.

The user noted that these problems occurred even with a clean, standard ESHOPMAN installation, suggesting the issue was not related to custom plugins or modifications but rather to core platform behavior.

Troubleshooting Attempts and Persistent Issues

To address these challenges, the user undertook several troubleshooting steps, including leveraging the ESHOPMAN Admin API and Store API for direct database interaction:

• Manual AOA Addition via Admin API: Attempts were made to manually add AOA to the supported currencies using backend scripts interacting with the ESHOPMAN Store API. An example approach involved updating supported_currencies with:

  {  currency_code: "aoa",  is_default: true}

• Clean Installations: Multiple fresh installations of ESHOPMAN were performed, utilizing clean PostgreSQL databases and fresh migrations, without any custom storefronts or plugins.

Despite these efforts, the issues persisted and often led to further complications:

• The Admin Region Editor continued to crash with the TypeError: Cannot read properties of undefined (reading 'code'), pointing to problems during currency/country mapping within the UI.
• Even after manual intervention, AOA's visibility remained inconsistent in the Admin UI.
• The store's currency state sometimes became unstable, leading to unexpected behavior in region editing and currency selectors.

Community Insight and Impact

This detailed report highlights a crucial area for ESHOPMAN users, especially those expanding into diverse international markets. The consistent reproduction of these issues across clean installations strongly suggests a fundamental challenge within the ESHOPMAN Admin UI's handling of currency and region configurations, particularly how it loads, maps, and relates country and currency data.

While a direct solution was not found within the discussion, this insight is invaluable for the ESHOPMAN community. It serves as a critical alert for merchants and developers considering or implementing ESHOPMAN for regions like Angola, emphasizing the need to thoroughly test currency and region configurations. It also points to an area where core platform enhancements could significantly improve the out-of-the-box experience for global commerce.

The impact extends beyond Angola, potentially affecting other regions or currencies that might encounter similar data handling discrepancies in the Admin UI. Understanding these limitations and the troubleshooting attempts that did not yield a stable solution is key for planning and deploying robust ESHOPMAN storefronts via HubSpot CMS.