Ecommerce version_price_in_u_s_d_enabled

[TheRefineryAU]

Does anyone know why the ecommerce generates columns for currency? eg version_price_in_u_s_d_enabled. I need to change to AUD and its broken my db.

[JorkDev]

That column is expected with @payloadcms/plugin-ecommerce.

The plugin is multi-currency and it creates a separate price field per currency (e.g. priceInUSD, priceInGBP, etc). On SQL/PG those field names get snake_cased into columns like price_in_u_s_d_*. If your collection has Versions/Drafts enabled, versions are stored under a version object in a separate *_versions table/collection, so you’ll also see the version_ prefix (e.g. version_price_in_u_s_d_enabled).

To switch to AUD you need to update the plugin config and run a schema migration (or reset the DB in dev). Example:

import { ecommercePlugin } from '@payloadcms/plugin-ecommerce'

const AUD = {
  code: 'AUD',
  decimals: 2,
  label: 'Australian Dollar',
  symbol: '$',
}

ecommercePlugin({
  currencies: {
    supportedCurrencies: [AUD],
    defaultCurrency: 'AUD',
  },
})

[TheRefineryAU]

Is the initial price field Price then? with that i get Price {{{currency}}} showing in the backend

[JorkDev]

It’s not a plain price field, the plugin creates currency-specific ones like priceInUSD / priceInUSDEnabled. So for AUD it should be priceInAUD, which on Postgres becomes columns like price_in_a_u_d_*.

The Price {{{currency}}} bit looks separate though. That seems more like the admin label interpolation isn’t resolving properly.

So I’d treat it as two issues: schema changed when the currency changed, and the admin label may be stale/bugged.

If you changed currencies on an existing SQL DB, you’ll need to update the schema to match, or reset the DB in dev and test from clean.