Money attributes

What a money attribute holds — an amount in the one currency you set on the attribute — how to set its Currency, what changing it does, and what import and export do with the amount.

A money attribute holds an amount of money, such as 129.95, in the currency set on the attribute, such as euros. Every product’s amount in that attribute is in that currency. The amount is stored as a number. The currency is stored with the attribute, not with each amount.

Use it for a fixed amount that describes a product, such as a deposit, a recycling fee or a declared customs value. For the amount a product is sold for — retail, wholesale, in several currencies, with validity dates — use prices instead: see Money attributes and prices.

What a money attribute holds

Part	Where it is set	What it is
Amount	Per product or product variant, in the product editor	A decimal number. It can be negative. The product editor keeps every decimal place you type.
Currency	Once per attribute, in the attribute’s settings	An ISO 4217 currency code, such as `EUR` or `CHF`. Optional — but set it: see Set the currency.

To keep amounts in two currencies, create two money attributes, for example Deposit EUR and Deposit CHF.

A money attribute can be translatable. It then holds one amount per language, all in the attribute’s one currency. Like the type, this is chosen when the attribute is created and cannot be changed later.

Create a money attribute

Go to Settings → Attributes & sections and select a section.
Click New attribute and choose Money.
On the General tab, enter its Name — the Code is filled in from it — and decide whether it is Translatable.
On the Settings tab, choose the Currency — see Set the currency.
Click Done, then Save the section.
Enable the attribute in Settings → Product types where you need it.

The type can’t be changed after the attribute is created. To turn an existing attribute into a money attribute, see Attributes & sections → Change attribute type.

Set the currency

Currency is on the attribute’s Settings tab, after Default value. Choose the currency from the list; it names each currency in the app’s language, followed by its ISO 4217 code, such as Swiss Franc (CHF).

Set it when you create the attribute. A money attribute without a currency shows its amounts as bare numbers, with no currency anywhere in the app.

Where the amount shows

Every screen writes an amount the same way: the number, then a space and the attribute’s currency code, such as 129.95 EUR. The number has at least as many decimal places as the currency uses — two for euros, none for yen — and every further decimal place stored, never rounded: 129.90 EUR, 1,200 JPY, 1,234.567 EUR. Without a currency it is the number alone, with the decimal places it has, such as 5 or 1,234.567. Digits are grouped and separated the way the app’s own language writes numbers, for example 1.234,567 EUR when the app is in German.

Where	What you see
Product editor	The amount in the input, with the currency code after the input. Without a currency there is no code.
Product list column	The amount and the currency code. With List product variants off, a product’s row lists the amounts of its product variants, separated by commas: `129.95 EUR, 99.00 EUR`.
Custom entity list column	The amount and the currency code. A translatable attribute has no column in that list.
Brand portal product list, and a product’s own page	The amount and the currency code.

A column’s header names the attribute, not the currency; each cell names the currency.

Import and export

An import reads the amount as a number. Map the column onto the money attribute as you would a number. The currency comes from the attribute, so the column needs only the amount. With the default Data format, where the decimal separator is .:

In the file	Stored
`12.50`	`12.50`
`12.50 EUR`	`12.50` — the currency text is dropped
`$9.00`	`9.00`

Only the mapping step looks at the currency. On Map columns, a column whose amounts carry another currency than the attribute’s — or two currencies, when the attribute has none — is not suggested for the attribute, and a remembered mapping that places it there is marked with how many rows it would import wrong. If you map such a column yourself, the import does not check the currency: a column of US dollar amounts mapped onto a euro attribute is stored as euros. How decimal and thousands separators in the file are read is set under Data format on that step — see Import products.

An export carries the amount without the currency. In a feed or a template the money attribute is a plain number, record.<code>. If the receiving system needs the currency code, add it yourself — in a template, write the code as text next to the amount.