# Catalogue

## Introduction

Catalogue is a document used to electronically exchange detailed product and price information between a supplier and its trading partners, including retailers and distributors.

Suppliers use the catalogue document as an e-catalog or digital catalog to deliver the full catalog of their products and pricing electronically, rather than through a paper catalog.

---

## Recommended formats

Below is a list of catalogue formats recommended by us.

!!!success Note
All formats recommended by us are actively maintained, based on open standards, offer good supporting documentation and validation artefacts.
!!!

#### Peppol BIS Catalogue 3.1

Peppol **B**usiness **I**nteroperability **S**pecifications (BIS) are technical specifications that can be implemented in existing eProcurement solutions and eBusiness exchange services to make them interoperable between disparate systems.

Peppol BIS defines a set of information elements (business terms) and business rules to ensure that requirements are fulfilled and to clarify any option that would otherwise be left open to implementers to decide on.

They are [developed and maintained by OpenPeppol](https://peppol.eu/) and are one of the most commonly used open standards today.

[!ref Specification](https://docs.peppol.eu/poacc/upgrade-3/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/catalogue/Peppol%20BIS%20Catalogue%203.1)

#### Pagero UN/EDIFACT PRICAT D96A

UN/EDIFACT is an international standard for electronic data interchange (EDI) developed for the United Nations and approved and published by UNECE, the UN Economic Commission for Europe.

The EDIFACT standard provides a set of syntax rules to structure, an interactive exchange protocol and provides a set of standard messages which allow multi-country and multi-industry exchange of electronic business documents. EDIFACT is widely used across Europe, mainly due to the fact that many companies adopted it very early on.

More general information can be found here [UNECE: Introducing UN/EDIFACT](https://unece.org/trade/uncefact/introducing-unedifact).

We develop and maintain our own **M**essage **I**mplementation **G**uidelines (MIG) for UN/EDIFACT D96A.

A specification is being written and will be available soon. Until then, please [contact us for more information](../get-support.md).
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/catalogue/Pagero%20UNEDIFACT%20PRICAT%20D96A)

---

## Supported formats

Below is a list of catalogue formats supported - but not necessarily recommended - by us.

#### EHF Catalogue 3.0

[!ref Specification](https://anskaffelser.dev/postaward/g3/spec/current/catalogue-3.0/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/catalogue/EHF%20Catalogue%203.0)

#### IFS XML Catalogue

[!ref Specification](https://www.ifs.com/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/catalogue/IFS%20XML%20Catalogue)

#### Svekatalog 2.0

[!ref Specification](https://skr.se/sfti/standarder/rekommenderadestandarder/avfordameddelanden.52834.html)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/catalogue/Svekatalog%202.0)

---

## Customer specific formats

We can build support for any proprietary/closed source format you and your ERP system may require.

For more information, please see the [proprietary or closed source formats section](index.md#proprietary-or-closed-source).