A PRICAT is the product catalogue message TRAEDE sends to your B24-connected customers. Every item in it is built from five kinds of elements: property, dimension, priceBase, priceBracket, and presentation. This article explains what each one is, and how to control which TRAEDE data goes into them from Settings → Connectors → B24.

This article covers properties, goods classes, and dimension codes. For order and ship dates, pre-order pricing windows, and which products (drops) are sent, see Send PRICAT to B24 below.

Static B24 property defaults

Use this when B24 or a customer needs a fixed value on every item, and it doesn't depend on any TRAEDE data — for example a flat VAT rate.

1. Go to Settings → Connectors and open the B24 connector.
2. Under Static B24 property defaults, add a new row.
3. Enter the B24 property name, for example VAT_NO.
4. Enter the fixed value, for example 25.
5. Click Save.

Every item in the PRICAT will now include:

<property name="VAT_NO">25</property>

Tip: No TRAEDE field is involved here — the value is hardcoded and identical for every product.

Custom PRICAT property mappings

Use this when the value should come from a TRAEDE field and can differ per product — for example gender, collection, or season. You choose which TRAEDE field feeds the property, and can set a fallback value for products where that field is empty.

1. Under Custom PRICAT property mappings, add a new row.
2. Set the TRAEDE field to the field holding the value, for example the Gender product custom field.
3. Set the B24 property name to what B24 expects, for example gender.
4. Optionally set a Default value, for example Unisex.
5. Click Save.

If the Gender field is filled in on a product, that value is sent. If it's empty, TRAEDE falls back to the default:

<property name="gender">Unisex</property>

Example: sending Collection as a property

If B24 asks you to add Collection as a property, the setup is the same pattern:

1. Under Custom PRICAT property mappings, add a new row.
2. Set the TRAEDE field to the custom field that holds your collection name, for example Collection.
3. Set the B24 property name to Collection — use exactly the name B24 asked for.
4. Leave Default value empty, unless B24 requires the property to always be present, in which case set a sensible fallback such as NOOS.
5. Click Save.

The next PRICAT sent will include, for each item:

<property name="Collection">Basic</property>

Tip: Whenever a customer or B24 asks for "field X as a property", this is the section to use — match their exact property name so their system recognizes it.

Adding XML attributes to a property

Some properties need more than a value — B24 also expects attributes like registry, set, code, or language on them. Each mapped property has its own XML attributes section for this.

For example, a WeightUnit property with a g code, a weightUnit set, and Supplier registry looks like this in the PRICAT:

<property name="weightUnit" code="g" set="weightUnit" registry="Supplier"/>

1. Open the property mapping you want to add attributes to.
2. Under XML attributes, choose a TRAEDE field per attribute if the value should vary by product, or enter a fixed value if it doesn't.
3. Leave an attribute empty to skip it — empty attributes aren't sent.
4. Click Save.

Important: When a TRAEDE field is selected for an attribute, its value is used. Otherwise the fixed value you entered is sent.

Goods classes

Goods classes let you send B24's classification codes — used for things like customs, taxonomy, or category-based reporting on the customer's side — alongside each item.

1. Under Goods classes, add a new row.
2. Choose the B24 goods class set you need to populate.
3. Map it to the TRAEDE product or variant custom field that holds the matching code.
4. Click Save.

Each row produces one <goodsClass> element on every item in the PRICAT.

Dimension code mappings

Dimensions like Size and Color are normally sent with just their text value, for example:

<dimension name="Color" registry="Supplier">Black</dimension>

If a customer needs a standardized code alongside the value — for example a colour code from their own system — use a dimension code mapping instead of relying on the attribute's built-in value code.

1. Under Dimension code mappings, add a new row.
2. Select the dimension, for example Color.
3. Map it to the TRAEDE custom field that holds the code for that dimension.
4. Click Save.

When the mapped field has a value, it's used as the code attribute on that dimension:

<dimension name="color" code="2215">Black</dimension>

If the field is empty, TRAEDE keeps the attribute value's default code instead.

Settings reference

Related articles

• [LINK: Send PRICAT to B24 — order and ship dates, pre-order pricing windows, and product filters]
• [LINK: Previewing and downloading a PRICAT before sending — check the XML before it goes to a customer]