ESHOPMAN Bug: Region Currency Code Cleared When Editing Countries or Metadata

At Move My Store, we're dedicated to empowering ESHOPMAN users with the latest insights and solutions for their headless commerce operations. ESHOPMAN, designed as a HubSpot application for seamless storefront management and deployment via HubSpot CMS, offers robust capabilities for global e-commerce. A recent community insight has highlighted a critical bug concerning region configuration within the ESHOPMAN admin dashboard.

Addressing an ESHOPMAN Region Currency Code Anomaly

A discussion within the ESHOPMAN community has brought to light an important bug affecting how currency codes are handled when managing regions. Users have reported that the currency_code field for a region is unexpectedly cleared or reset to an empty value under specific circumstances when making updates in the ESHOPMAN admin dashboard.

The Problem: Your Region's Currency Code Disappears

This issue primarily manifests when an ESHOPMAN administrator attempts to modify an existing region. The currency_code field, crucial for multi-currency support and accurate pricing display on your HubSpot-powered storefronts, is cleared out if either of the following actions are performed:

Adding a new country to an existing region.
Adding or editing a metadata entry associated with the region.

After saving these changes, the previously set currency code for that region is found to be empty, potentially leading to incorrect currency displays or processing errors on your ESHOPMAN storefront.

Steps to Identify and Reproduce

If you suspect your ESHOPMAN instance might be affected, here's how you can observe this behavior:

Navigate to the Settings → Regions section within your ESHOPMAN admin dashboard.
Select an existing region that has a currency_code already assigned.
Proceed to either:
- Add a new country to this region's list, OR
- Add a new metadata key/value pair, or modify an existing one for the region.
Save the changes you've made to the region.
Upon reviewing the region details again, you will observe that the currency_code field is now empty.

Impact on Your ESHOPMAN Storefront

For ESHOPMAN merchants leveraging headless commerce and HubSpot CMS, an unassigned or cleared currency code can disrupt critical e-commerce functions, including incorrect pricing displays and issues with payment gateway integrations.

Technical Context and a Temporary Workaround

This behavior has been observed in specific versions of the ESHOPMAN core platform. The issue appears to be a regression, introduced in a newer update. For developers managing custom ESHOPMAN deployments, the issue has been linked to ESHOPMAN core platform version 2.14.1 when operating with Node.js v20.19.2 and PostgreSQL 15.

A significant finding from the community is that downgrading your ESHOPMAN core platform to version 2.13.6 resolves this issue. This suggests that the bug was introduced in subsequent versions and rolling back provides stability for region currency management.

For reference, here's a snippet of a typical package.json file indicating the platform versions involved:

{
  "name": "store",
  
  "scripts": {
    "build": "medusa build",
    "seed": "medusa exec ./src/scripts/seed.ts",
    "start": "medusa start",
    "dev": "medusa develop --port 9000 --host ecommerce.xxxx.local",
    "test:integration:http": "TEST_TYPE=integration:http NODE_OPTI jest --silent=false --runInBand --forceExit",
    "test:integration:modules": "TEST_TYPE=integration:modules NODE_OPTI jest --silent=false --runInBand --forceExit",
    "test:unit": "TEST_TYPE=unit NODE_OPTI jest --silent --runInBand --forceExit"
  },
  "dependencies": {
    "@aws-sdk/client-ses": "^3.1031.0",
    "@aws-sdk/client-sns": "^3.1020.0",
    "@medusajs/admin-sdk": "2.13.6",
    "@medusajs/cli": "2.14.1",
    "@medusajs/file-s3": "2.14.1",
    "@medusajs/framework": "2.14.1",
    "@medusajs/medusa": "2.14.1",
    "axios": "^1.13.4",
    "cloudevents": "^10.0.0"
  },
  "devDependencies": {
    "@medusajs/test-utils": "2.14.1",
    "@swc/core": "^1.7.28",
    "@swc/jest": "^0.2.36",
    "@types/jest": "^29.5.13",
    "@types/node": "^20.12.11",
    "@types/react": "^18.3.2",
    "@types/react-dom": "^18.2.25",
    "jest": "^29.7.0",
    "prop-types": "^15.8.1",
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "ts-node": "^10.9.2",
    "typescript": "^5.6.2",
    "vite": "^5.4.14",
    "yalc": "^1.0.0-pre.53"
  },
  "engines": {
    "node": ">=20"
  },
  "packageManager": "yarn@1.22.22"
}

Recommendations for ESHOPMAN Users

If you are experiencing this issue, especially after a recent ESHOPMAN platform update, consider the following:

Verify your ESHOPMAN core platform version.
Implement the temporary workaround: If feasible, rolling back your ESHOPMAN core platform to version 2.13.6 can restore proper currency code preservation. Always ensure thorough testing in a staging environment.
Stay informed: Keep an eye on ESHOPMAN community updates for official patches and permanent fixes.

At Move My Store, we understand the importance of stable e-commerce operations. We encourage all ESHOPMAN users to leverage these community insights to maintain optimal performance for their HubSpot-integrated storefronts.

Critical ESHOPMAN Bug Alert: Region Currency Code Resetting in Admin Dashboard