London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
Navigation [hide]
[expand]
- Architecture
- Business Foundation
- Generating typed business foundation classes
- SQL Meta Model
- Business Meta Model
- MetaClassManager class
- MetaType class
- MetaClass class
- MetaField class
- MetaFieldBuilder class
- MetaEnum class
- Meta Class references
- Extending meta models
- Exporting and importing meta models
- Working with SQL Records
- Working with entity objects
- Filtering and sorting
- Caching
- Catalogs
- Catalog object model and database diagram
- Guidelines for working with catalogs
- Catalog product search
- Displaying products
- Product associations
- Catalog data sources
- Importing catalog data
- Defining package items
- Event-driven catalog indexing
- Catalog database partitioning
- Configuration
- Content
- Product variants
- Bundles and packages
- Categorizations
- Related entries
- Catalog events
- Commerce rendering templates
- Catalog content provider
- Content-based campaigns
- Assets and media
- Customers
- Deployment
- Deploying Commerce to Azure Web Apps
- Deploying Commerce to Amazon
- Single server deployment
- Load balancing deployment
- Performance optimization
- Events
- Globalization
- Initialization
- Logging
- Marketing
- Campaigns [BETA]
- Discounts [BETA]
- Workflows [BETA]
- Calculating orders [BETA]
- Order repository [BETA]
- Marketing overview
- Promotions
- Creating a volume discount promotion
- Using calculate discount activity
- Custom promotion development
- Markets
- Meta Data Plus
- Notifications
- Orders
- Order object model and database diagram
- Order management classes
- Extending order classes
- Order events
- Order addresses
- Order notifications
- Shopping cart
- Checkout process
- Recurring orders
- Changing order number sequence
- Searching for orders
- Taxes
- EPiServer.Commerce.Sample guideline
- Payments
- Pricing
- Reports
- Routing
- Scheduled Jobs
- Search
- Customizing search
- Configuring facets and filters
- Creating a search provider
- Configuring Solr search provider
- Configuring EPiServer Find search provider
- Security
- Standard roles
- IRegistar
- Membership Registrar
- AspNet Identity Registrar
- Customer Contact Registrar
- Configuring membership providers
- Authorization and authentication
- Shipping
- Warehouses and inventories
- Inventory requests
- Database changes for Commerce inventory service
- Warehouses and inventories examples
- Multi-warehouse implementations
- Multi-warehouse features
- Workflows
ARCHIVED This content is retired and no longer maintained. See the latest version here.
Catalog object model and database diagram
Note: This feature has been obsoleted in the latest version of the product.
The Catalog Management system has two primary APIs: the DTO Based API and the Object Based API, where the Object Based API relies on the underlying DTO API.
DTO object model
The DTO API is the core catalog API and primarily used directly in the catalog administration and indirectly through the Object API.
Runtime object model
This object model is primarily used during runtime, and Entry is the main object that you will most likely work with
Database diagram
Below is an overview of the Catalog Management system database.
Last updated: Oct 21, 2014
