HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunityDoc feedbackLog In
GitHubNuGetDev CommunityDoc feedback


Direct database access usually is not a recommended practice. Instead, you should access this information either through the [Optimizely Service API](🔗) or the inventory APIs.

The database schema is considered an internal artifact of the system. Database schema changes may occur at any release without affecting the semantic versioning scheme. This means that a breaking change, such as changing tables or table names in the database schema, does not result in a major version update of Optimizely Customized Commerce.

See [Inventory requests](🔗) for information about accessing warehouse inventory information.

Database schema changes

The modifications to the database schema involve migration of information from the old WarehouseInventory table to the new InventoryService table. If you have reporting running against the old WarehouseInventory\*\* \*\*table, this table will not receive any new or updated information, but the existing information remains.

**Commerce 11 and higher**



**Commerce 10 and lower**



### Migration script

When you migrate data between the systems, the following script is executed.

**Commerce 11 and higher**



**Commerce 10 and lower**