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
- 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
- Hiding promotion types
- Discounts [BETA]
- Custom promotions
- Coupons
- Promotion engine
- Marketing overview [Legacy]
- Promotions [Legacy]
- Creating a volume discount promotion [Legacy]
- Using calculate discount activity [Legacy]
- Custom promotion development [Legacy]
- Markets
- Metadata Plus
- Notifications
- Orders
- Order system overview
- Order manipulation
- Order processing
- Calculating orders
- Extending order classes
- Changing default implementation
- Rounding totals for different currencies
- Order notifications
- Order events
- Searching for orders
- Order object model and database diagram [Legacy]
- Order management classes [Legacy]
- Order addresses [Legacy]
- Shopping cart [Legacy]
- Checkout process [Legacy]
- Recurring orders [Legacy]
- Changing order number sequence [Legacy]
- Taxes [Legacy]
- EPiServer.Commerce.Sample guideline [Legacy]
- 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
- Find integration
- Security
- Shipping
- Warehouses and inventories
- Inventory requests
- Database changes for Commerce inventory service
- Warehouses and inventories examples
- Multi-warehouse implementations
- Multi-warehouse features
- Workflows and activities
Catalog object model and database diagram
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 Data Transfer Object (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
The runtime object model is primarily used during runtime, and Entry is the main object that you most likely work with.
Database diagram
The following diagram shows an overview of the Catalog Management system database.
Last updated: Oct 12, 2015
