Skip to content
Joe Rzepiejewski edited this page Mar 14, 2024 · 3 revisions

📣 What is the purpose of the Commerce Data Models?

Let's start off with our first release containing our Unified Order Schema (UOS).

The Unified Order Schema (UOS) is a data model initially designed by the Daasity (http://www.daasity.com/) team that helps accelerate development of analytical capability by normalizing all commerce data: eCommerce, Marketplace, Retail and Wholesale. The normalized schema was designed to support complex fulfillment logic like split shipments and multiple delivery groups and be extensible for edge cases like product customization or personalization.

UOS is split into core tables, required to support an order across multiple commerce channels, and secondary tables that are required to provide functionality to the business. Core tables are built off the concepts of Customer, Product, Order, Fulfillment and Location which all required components of a consumer product purchase.

For product, Brands will use different naming conventions for their merchandising hierarchy from Class, Category, Sub-Category to Style or Product (which can have different meaning) and Item or SKU. This Commerce schema limits tables to Product (want some might call a Style) and Product Variant (what some might call an Item or SKU).

Clone this wiki locally