Skip to main content

Ecommerce platform

Open a merchant → Overview → Merchant card. The row is Ecommerce platform with ⓘ About the ecommerce platform. Read-only until you click Edit Merchant in the page header (inline on the card).

Click Ecommerce platform​

  1. Merchants → open the merchant → Overview.
  2. Click Edit Merchant. The value becomes a dropdown: Shopify, WooCommerce, Magento, Custom, plus any already-used custom names, then Other….
  3. Built-in pick: choose Shopify, WooCommerce, Magento, or Custom, then Save Changes.
  4. Custom name: choose Other… (Other (custom) in the dropdown). The name field placeholder is e.g. BigCommerce, Wix, Squarespace. Helper: Tracked for analytics. Cannot match a built-in platform name (Shopify, WooCommerce, Magento, Custom).
  5. Blank Other… name on save: Ecommerce platform: please enter a name for "Other…", or pick one of the listed platforms.
  6. Built-in name typed as custom: Ecommerce platform: "…" is a built-in platform and can't be used as a custom name. Pick it from the list instead.

Ecommerce Settings and Pay Monthly views show this field read-only — change it on the Merchant card.

Where to find it​

Merchant detail → Merchant card → Ecommerce platform. Edit via Edit Merchant.

Ecommerce Settings and Pay Monthly views show this field read-only — change it on the Merchant card.

What it controls​

Drives Tier-A page detection and platform-default selectors / events at runtime (ECOM_PLATFORM_DEFAULTS).

Built-in platforms with wired runtime defaults:

  • Shopify
  • WooCommerce
  • Magento
  • Custom

Selecting a built-in swaps in that platform’s tested defaults.

Other (custom names)​

Pick Other… (Other (custom) in the dropdown) to name a platform we do not yet have wired defaults for (e.g. BigCommerce, Wix, Squarespace).

The inline helper reads: Tracked for analytics. Cannot match a built-in platform name (Shopify, WooCommerce, Magento, Custom).

  • The custom name is stored and shown to other admins (analytics / future first-class support).
  • It cannot collide with a built-in name (case-insensitive).
  • Runtime behaviour matches Custom (global defaults) — only the label differs.

Where it is stored​

Single source of truth:

  1. Merchant profile via the merchants API (ecommerce_platform).
  2. Mirrored into the runtime env config (finmatch-merchant-config.json) so the storefront sees the same value.