ATPCO supports major and minor versions of Product Catalog. Versions are not backward-compatible.

• A version is assigned to every product, bundle, fare data link, and retailer record in Product Catalog.
• ATPCO will support the current version of Product Catalog, along with two previous versions.
• Different catalog owners can be on different versions of Product Catalog.
• A catalog owner can be in only one version of Product Catalog at any given time, and all of its products, bundles, fare data link and retailor records must be in the same version.
• If a catalog owner wants to start using the next version of a product, all existing data records will first have to be transformed to the new version. This applies to both major and minor versions.

📝 ATPCO will provide scripts for transforming/migrating data from the current version to the newer version.

Major Versions

A major version would be prompted by a ‘wholesale’ transformation of existing data. Here is an example of a change that would warrant a major version change, such as from version 1.0 to version 2.0.

• Version 1.0: Prior to 2025, products and product rules were separate records, and product rules could be reused across multiple products. The same principle applied to the rules for bundles and retailer records.
• Version 2.0: Beginning in 2025, product rules are now embedded within their respective products and cannot be reused. The same change was made to the rules for bundles and retailer records.

Minor Versions

A minor version change would occur as a result of a localized change that impacts a small sub section of the data set. For example, switching Passenger Type Code from the transition state of Product Catalog to the end state would cause a minor version change, such as from version 1.0 to 1.1.