Set up PRICAT mapping
How to create your first PRICAT mapping to map article data from price catalogues to the matching Shopify fields.
A PRICAT (price catalogue) contains only variants — no products. A mapping defines how multiple lines are grouped into a Shopify product and which PRICAT field is copied into which Shopify field. This guide walks you through your first mapping.
Prerequisites
Section titled “Prerequisites”- Initial setup (email account, locations, GLNs) is complete.
- At least one PRICAT message has been received. Without a sample message, the mapping has no example values and no live preview.
Opening the mapping
Section titled “Opening the mapping”A mapping is created automatically per shop the first time you open it. You can reach it in one of three ways:
- Under Settings → PRICAT settings, click Edit mapping.
- Under Messages → PRICAT, use the button to configure the mapping.
- From within a single PRICAT message’s detail view — that message is then already selected as the mapping’s test message.
Choosing a test message
Section titled “Choosing a test message”At the top of the PRICAT source fields column, choose a test message. It provides the example values next to each source field and drives the live preview. Without a test message, example values and the preview stay empty.
Grouping variants into products
Section titled “Grouping variants into products”EDIFACT PRICAT lines only contain variant data, not a separate product. Group variants by sets which field (or combination of fields) groups lines into one shared product — lines with the same value become one product with multiple variants.
The default is supplier article number. Other presets are available for style number, barcode and article description. Use Custom to combine several fields freely, for example article number and color, if each color should become its own product instead of a variant of the same product.
If your catalogue only contains simple products without variants, choose None – one product per line (no variants). Each PRICAT line then becomes a standalone Shopify product with a single default variant, with no variant options (color, size) at all.
Mapping Shopify fields
Section titled “Mapping Shopify fields”In the Shopify fields column, map product and variant fields — for example product title, description, vendor/brand, product type and URL handle at the product level, and SKU, barcode, price, cost and the options (color, size) at the variant level.
Every field has a text input where you write free text and use the + button or @ autocomplete to insert PRICAT source fields as placeholders — you can also combine them, for example brand and article name together as the product title. For Price and Cost, map the recommended retail price (SRP) or purchase price (NTP) from the catalogue.
For the product description, there’s also an Automatic option: the app composes the description itself from existing fields (product type, material, fabric, season, model, style number, description text) instead of using your own template.
Mapping product metafields (optional)
Section titled “Mapping product metafields (optional)”Use + Add metafield to map additional PRICAT fields to a Shopify metafield — either one already defined in Shopify or a newly defined one. The value is composed from placeholders and free text the same way as the Shopify fields above.
Checking the preview and saving
Section titled “Checking the preview and saving”The third column shows a live preview: up to five products as they would result from the current mapping and the selected test message, expandable down to the variant level (options, barcode, SKU, price, cost) including the mapped metafields. Check here whether the result matches your expectations before saving.
Save using the save bar at the top. The mapping then applies immediately to newly processed PRICAT messages — there’s no separate test or approval step; the live preview is the test.
Next step
Section titled “Next step”For an overview of how PRICAT messages are processed in general, see PRICAT (price catalogue). If a message stays in error status, see Troubleshooting.
