Try it now Login

Message type

UN/EDIFACT PRICAT

Price/sales catalogue message. It is published in 60 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

Open the D24A PRICAT specification
Message
PRICAT
Directory versions
60
Latest
D24A

Sending and receiving

Exchange PRICAT with your trading partners

The specification tells you what a valid PRICAT looks like. Sending and receiving one means mapping it to the system that holds the data, agreeing the format with each partner, and handling the messages that come back when something is rejected. XEDI does the mapping, validation and transport.

7 integrations on this site document PRICAT handling:

Adobe Commerce PRICAT mapping and transport BigCommerce PRICAT mapping and transport IndiCater Hospitality PRICAT mapping and transport Connect Internet Solutions PRICAT mapping and transport OrderWise PRICAT mapping and transport Shopify Plus PRICAT mapping and transport SYSPRO PRICAT mapping and transport

Specifications

PRICAT in every directory version

A trading partner names both the message and the directory, for example D00A PRICAT, because the segments differ between versions. Open the one your partner specified.

60 directory versions

Related messages

Messages in the PRI set

UN/EDIFACT groups related documents under a shared three-letter stem. These usually appear together in one trading flow.

PRIHIS UN/EDIFACT message.

Frequently asked questions

What is the PRICAT message?

Price/sales catalogue message. It is one of the UN/EDIFACT message types, identified by the six-letter name PRICAT in every directory version that publishes it.

Which directory version of PRICAT do I need?

The one your trading partner specifies. PRICAT is published in 60 directory versions and the segment detail differs between them, so a mapping built for one version is not automatically valid for another.

How do I send a PRICAT message?

Map the data from the system that holds it into the segment structure the agreed directory version defines, then transport it by the route the partner uses, commonly AS2 or SFTP. XEDI handles the mapping, validation and transport, and surfaces the acknowledgements and errors that come back.

Sources and further reading