You are browsing documentation for version 5.0 of OroCommerce, OroCRM, and OroPlatform, maintained until August 2024 and supported until March 2026. See version 5.1 (the latest LTS version) of the Oro documentation for information on latest features.
See our Release Process documentation for more information on the currently supported and upcoming releases.
Manage Web Catalogs in the Back-Office
This section is part of the Content Management Concept Guide topic that provides a general understanding of the tools that help manage the content of your websites, such as web catalog, landing page, content blocks, widgets, and WYSIWYG editor.
Web Catalog is a content management tool that helps build highly personalized custom versions of your websites by mixing in category pages, product pages, landing pages, and pre-existing system pages in different variations based on the customer account information, their customer group, or language preference.
With the OroCommerce web catalog and content tree, you can organize the target website structure to gain an improved purchasing experience and use a set of in-place SEO tools to make it reachable for your target audience.
The web catalog content nodes may be of the following types:
- System page - one of the standard eCommerce website pages (e.g. sign in, user profile, open orders, etc).
- Product - direct link to product details.
- Product Collection - a dynamically generated group of products that are stored as a data segment.
- Category - a category of the master catalog.
- Landing page - a custom landing page created in the Marketing > Landing Pages section.
To view all web catalogs, navigate to Marketing > Web Catalogs in the main menu.
See the following topics for more details on how to create and manage web catalogs:
- Create a Web Catalog
- Edit a Web Catalog Content Tree
- Enable a Web Catalog Globally and per Website.
- Customize Web Catalog Contents for Localization, Customer or Customer Group
- Preview Web Catalog
- Build a Custom Web Catalog From Scratch (Example)
- Use Web Catalog Nodes as Root Nodes (Example)