> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/data-models/unified-schemas/unified-retail-sales-urs.md). # Unified Retail Sales (URS) The **Unified Retail Sales (URS)** schema is Daasity’s core data model for **store-level retail sales, inventory, and wholesale data**. It ingests POS feeds, shipment data, and on-hand inventory reports from retailer partners and normalizes them into a consistent structure that enables cross-retailer analysis. URS provides a unified view of retail account activity by combining: * **Sell-Out (POS sales):** Units and dollars sold to consumers at the retailer. * **Inventory:** On-hand and on-order quantities reported at the retailer or store level. * **Sell-In (Wholesale):** Shipments from the brand into retailer warehouses or stores. All URS fact tables are standardized at a **daily grain** (location × product × day), even when retailer data is provided at weekly or other intervals. Supporting dimension tables for products, locations, and time periods ensure consistent joins and reporting across sources. The URS schema is designed to support account-level retail analytics across diverse retailer feeds, enabling brands to calculate metrics such as **velocity, % stores selling, sell-through, weeks of supply, and inventory turnover**. It serves as the **single source of truth for store-level retail performance** and is the foundation for retail-facing dashboards and reporting. ### Entity Relationship Diagram (ERD) [Click on this link to view](https://lucid.app/lucidchart/788f2c35-a18b-4d00-832b-40cb19ef494f/edit?viewport_loc=-3149%2C-1902%2C9422%2C4558%2CqThOlBkq6mBP\&invitationId=inv_e2b66b00-229f-47e0-8e8a-2e8fcbe97a71) the ERD for the Unified Retail Sales (URS) integration illustrating the different tables and keys to join across tables. ### Unified Retail Sales Tables [Invoice Sales](#invoice-sales) \[`urs.invoice_sales`] [Depletion Sales](#depletion-sales) \[`urs.depletion_sales`] [POS Sales](#pos-sales) \[`urs.pos_sales`] [Product Listings](#product-listings) \[`urs.product_listings`] [Product Listing Numbers](#product-listing-numbers) \[`urs.product_listing_numbers`] [Distribution Centers](#distribution-centers) \[`urs.distribution_center`] [Stores](#stores) \[`urs.stores`] [Current Inventory Levels](#current-inventory-levels) \[`urs.current_inventory_levels`] [Inventory Levels History](#inventory-levels-history) \[`urs.inventory_levels_history`] {% hint style="success" %} Within the `retailer_inventory.explore.lkml` file, you will see lines such as `include: "/views/bsd/*.view.lkml"`, `include: "/views/dm_retail/*.view.lkml"`, and others. These inclusions ensure that all relevant URS views—covering retailer inventory, product attributes, and business-specific customizations (BSD)—are available directly in this schema. This setup allows business users to analyze retailer inventory with both standardized URS fields and any brand-specific attributes that have been layered on. {% endhint %} ### Invoice Sales Purpose: Stores Sell In orders from Purchasing Partners. Tracks SKU Sell In Cases, Units and SKU Cost by Distributor or Retailer on the date the Order, Receipt or Invoice was created. Each row represents a unique **sell in** **x** **purchasing partner × product × day**. Table Name: `urs.invoice_sales` Table Type: Core | Column | Description | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | | SELL\_IN\_ID | Unique identifier for each Invoice Sales record. | | ORDER\_DATE | Date order was placed. | | RECEIPT\_DATE | Date order was placed and received by customer. | | INVOICE\_DATE | Date order was invoiced. | | PURCHASING\_PARTNER\_TYPE | "distributor" or "retailer". | | PURCHASING\_PARTNER\_ID | Unique combination of Store ID and Distribution Center ID. Links to `urs.stores` and `urs.distribution_center` | | LISTING\_SKU | SKU used by the retailer. Links to `urs.product_listing` | | LISTING\_SKU\_VENDOR\_FIELD | This contains the field from the POS sales that we are using for listing\_sku - ex: DPCI, TCIN, Vendor Number. | | VENDOR\_SKU\_VALUE | Vendor's reference number that links to their ERP. | | MASTER\_SKU | Vendor's SKU reference in their ERP. | | CASE\_QTY | Quantity in Cases as part of the Sell In. For data not originally in Cases a conversion factor from Units can be used to determine Case Qty. | | UNIT\_QTY | Quantity in Units as part of the Sell In. For data not originally in Units a conversion factor from Case Qty can be used to determine Unit Qty. | | SKU\_COST | Sku Cost as determined from the Vendor's data. Provided only if the source data contains this value. | | PRICE\_TO\_PURCHASING\_PARTNER | Price of the Sell In to the Purchasing Partner. Provided only if the source data contains this value. | ### Depletion Sales Purpose: Stores Depletion Sales orders from Purchasing Partners. Tracks SKU Depletion In Cases, Units and SKU Cost by Distributor on the date the Depletion was created. Each row represents a unique **depletion event x** **purchasing partner × product × day**. Table Name: `urs.depletion_sales` Table Type: Core | Column | Description | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | DEPLETION\_ID | Unique identifier for each Depletion Sale event. | | ORDER\_DATE | Date order was placed. | | DEPLETION\_DATE | Date order was shipped out of warehouse. | | RECEIPT\_DATE | Date order was placed and received by customer. | | INVOICE\_DATE | Date order was invoiced. | | DISTRIBUTION\_CENTER\_ID | Distribution Center ID. Links to `urs.distribution_center` | | RETAILER | The store identifier used by the retailer. | | STORE\_ID | Unique identifier for each store location. Links to `urs.stores` | | STORE\_NAME | Name of an individual store, if store-level data is available. | | UPC | UPC of the product used by the Retailer. | | LISTING\_SKU | SKU used by the retailer. Links to `urs.product_listing` | | LISTING\_SKU\_VENDOR\_FIELD | This contains the field from the POS sales that we are using for listing\_sku - ex: DPCI, TCIN, Vendor Number | | VENDOR\_SKU\_VALUE | Vendor's reference number that links to their ERP. | | MASTER\_SKU | Vendor's SKU reference in their ERP. | | PRICE | Price of the product. Provided only if the source data contains this value. | | PRICE\_TO\_DISTRIBUTOR | Price of the product to distributor. Provided only if the source data contains this value. | | SKU\_COST | Sku Cost as determined from the Vendor's data. Provided only if the source data contains this value. | | DOLLAR\_SALES | Depletion Sales in Dollar value. Generally converted to your preferred account currency. | | UNIT\_SALES\_AMOUNT | If SKU is single unit then quantity otherwise case size \* case units | | CASE\_SALES\_AMOUNT | If SKU is case then # of cases otherwise NULL | | UNIT\_QTY | Quantity in Units as part of the Depletion Sale. For data not originally in Units a conversion factor from Case Qty can be used to determine Unit Qty. | | CASE\_QTY | Quantity in Cases as part of the Depletion Sale. For data not originally in Cases a conversion factor from Units can be used to determine Case Qty. | | UNITS\_PER\_CASE | Default to "1", unless source data contains a different value. | ### POS Sales Purpose: Store Sell Out orders from Brick & Mortar or Digital Purchasing Partners. Tracks SKU Sell Out Cases, Units and SKU Cost by Retailer on the date the date of the sale. Each row represents a unique **sell out** **x** **purchasing partner × product × day**. Table Name: `urs.pos_sales` Table Type: Core | Column | Description | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | SALES\_ID | Unique identifier for each POS store by SKU | | SALES\_DATE | Sales of the POS Sale | | CHANNEL | Brick & Mortar or Digital | | RETAILER | The retailer or account name (e.g., Target, Whole Foods). | | STORE\_ID | Unique identifier for each store location. Links to `urs.stores` | | STORE\_NAME | Name of an individual store, if store-level data is available. | | UPC | Global barcode identifier, used to align retailer data with syndicated sources. | | LISTING\_SKU | SKU used by the retailer. Links to `urs.product_listing` | | LISTING\_SKU\_VENDOR\_FIELD | This contains the field from the POS sales that we are using for listing\_sku - ex: DPCI, TCIN, Vendor Number. | | MASTER\_SKU | Vendor's SKU reference in their ERP. | | PRICE | Price of the product. Provided only if the source data contains this value. | | PRICE\_TO\_RETAILER | Price of the product to retailer. Provided only if the source data contains this value. | | SKU\_COST | Sku Cost as determined from the Vendor's data. Provided only if the source data contains this value. | | UNIT\_SALES\_AMOUNT | If SKU is single unit then quantity otherwise case size \* case units. | | CASE\_SALES\_AMOUNT | If SKU is case then # of cases otherwise NULL. | | UNIT\_QTY | Quantity in Units as part of the Sell In. For data not originally in Units a conversion factor from Case Qty can be used to determine Unit Qty. | | CASE\_QTY | Quantity in Cases as part of the Sell In. For data not originally in Cases a conversion factor from Units can be used to determine Case Qty. | | UNITS\_PER\_CASE | Default to "1", unless source data contains a different value. | | ORIGINAL\_CURRENCY | Currency reported by the source (e.g., USD, CAD). | | CURRENCY\_CONVERSION\_RATE | Rate used to convert from original to converted currency. | | CONVERTED\_CURRENCY | Target currency after conversion. | ### Product Listings Purpose: Captures product and brand details for reporting. **Each row represents a unique entity (brand or product)**, and includes hierarchical product classification fields. Table Name: `urs.product_listings` Table Type: Core | Column | Description | | -------------------- | -------------------------------------------------------------------------------------- | | PRODUCT\_LISTING\_ID | Unique identifier for each product listing. | | LISTING\_SKU | SKU used by the retailer. | | RETAILER\_NAME | The retailer or account name (e.g., Target, Whole Foods). | | VENDOR\_SKU\_VALUE | Vendor's reference number that links to their ERP. | | MASTER\_SKU | Vendor's SKU reference in their ERP. | | PRODUCT\_NAME | Syndicated item or brand descriptor (may include category totals or “All Other” rows). | | UPC | Global barcode identifier, used to align retailer data with syndicated sources. | | BRAND\_NAME | Brand associated with the syndicated record. | | DEPARTMENT | Hierarchical product classification standardized across all retailers. | | CATEGORY | Hierarchical product classification standardized across all retailers. | | SUBCATEGORY | Hierarchical product classification standardized across all retailers. | | PRODUCT\_CLASS | Hierarchical product classification standardized across all retailers. | | PRODUCT\_TYPE | The type of product | | PRODUCT\_SIZE | Numerical size value related to unit of measure. | | PACK\_COUNT | Numeric value of unites in a multipack (default is *typically* 1). | | WEIGHT | Numerical size value related to weight. | | WEIGHT\_UOM | Generic unit of measure (ex: ounces, lbs). | | CREATED\_AT | Date the product listing was created at, if available. | | UPDATED\_AT | Date the report was last updated at. | ### Product Listing Numbers Purpose: Stores product identification fields. **Each row represents a unique entity (brand or product).** Table Name: `urs.product_listing_numbers` Table Type: Core | Column | Description | | ----------------------------- | ------------------------------------------------------------------- | | PRODUCT\_LISTING\_NUMBERS\_ID | Unique identifier for each product listing number. | | LISTING\_SKU | SKU used by the retailer. Links to `urs.product_listing` | | RETAILER\_NAME | The retailer or account name (e.g., Target, Whole Foods). | | VENDOR\_SKU\_TYPE | indicates which type of identifier is being used (ASIN, TCIN, etc). | | VENDOR\_SKU\_VALUE | Vendor's reference number that links to their ERP. | | CREATED\_AT | Date the product listing was created at, if available. | | UPDATED\_AT | Date the report was last updated at. | ### Distribution Centers Purpose: Stores information related to a Retailer Distribution Center. **Each records represents a unique Distribution Center** Table Name: `urs.distribution_center` Table Type: Core | Column | Description | | ------------------------ | ---------------------------------------------------------------- | | DISTRIBUTION\_CENTER\_ID | Unique identifier for each Distribution Center. | | PARTNER\_TYPE | "Distributor" | | WAREHOUSE\_OWNER | UNFI, KeHE, etc.. | | WAREHOUSE\_NAME | Name of the Warehouse | | ADDRESS1 | Address component for Distribution Center. | | ADDRESS2 | Address component for Distribution Center. | | CITY | Address component for Distribution Center. | | STATE | Address component for Distribution Center. | | COUNTRY | Address component for Distribution Center. | | ZIPCODE | Address component for Distribution Center. | | CONTACT | Contact for the Distribution Center, generally name or position. | | EMAIL | Email address of the Distribution Center | | PHONE | Phone Number of the Distribution Center. | | CREATED\_AT | Date the Distribution center was first created in reporting. | | UPDATED\_AT | Date this record was last updated at. | ### Stores Purpose: Stores information related to a Retailer Store. **Each records represents a unique Retailer Store Name.** Table Name: `urs.stores` Table Type: Core | Column | Description | | ------------------ | -------------------------------------------------------------- | | STORE\_ID | Unique identifier for each store location. | | PARTNER\_TYPE | "Retailer" | | RETAILER\_NAME | The retailer or account name (e.g., Target, Whole Foods). | | STORE\_NAME | Name of an individual store, if store-level data is available. | | REGION | Name of the region the store occupies. | | RETAILER\_DIVISION | Name of the division the store occupies. | | ADDRESS1 | Address component for Retailer. | | ADDRESS2 | Address component for Retailer. | | CITY | Address component for Retailer. | | STATE | Address component for Retailer. | | COUNTRY | Address component for Retailer. | | ZIPCODE | Address component for Retailer. | | CONTACT | Contact for the Retailer, generally name or position. | | EMAIL | Email address of the Retailer. | | PHONE | Phone number of the Retailer. | | CREATED\_AT | Date the Retailer was first created in reporting. | | UPDATED\_AT | Date this record was last updated at. | ### Current Inventory Levels Purpose: Captures the inventory for the most recent inventory related data load. **Each record represents a unique distributor or retailer partner product.** Table Name: `urs.current_inventory_levels` Table Type: Core | Column | Description | | --------------------------- | -------------------------------------------------------------------------------------------------------------- | | INVENTORY\_SNAPSHOT\_ID | Unique identifier for each inventory record. | | SNAPSHOT\_DATE | The date the inventory snapshot represents. Normalized to daily grain. | | PURCHASING\_PARTNER\_TYPE | "Distributor" or "Retailer" | | PURCHASING\_PARTNER\_ID | Store\_ID from `urs.stores` or Distribution\_center\_id from `urs.distribution_center` . | | UPC | Global barcode identifier, used to align retailer data with syndicated sources. | | LISTING\_SKU | SKU used by the retailer. Links to `urs.product_listing` | | LISTING\_SKU\_VENDOR\_FIELD | This contains the field from the POS sales that we are using for listing\_sku - ex: DPCI, TCIN, Vendor Number. | | VENDOR\_SKU\_VALUE | Vendor's reference number that links to their ERP. | | MASTER\_SKU | Vendor's SKU reference in their ERP. | | ON\_HAND\_QTY | Quantity of product physically on hand at the location on the given date. | | COMMITTED\_QTY | Quantity of product physically committed at the location on the given date. | | AVAILABLE\_QTY | On Hand Qty - Committed Qty | | ON\_ORDER\_QTY | Quantity of product currently on order but not yet received. | | IN\_TRANSIT\_QTY | Quantity of product currently in transit to retailer, warehouse, etc.. | | BACK\_ORDER\_QTY | Quantity of product that cannot be fulfilled as it is out of stock. | ### Inventory Levels History Purpose: Stores each historical inventory snapshot. **Each record represents a unique distributor or retailer partner product, and unique date.** Table Name: `urs.inventory_levels_history` Table Type: Core | Column | Description | | --------------------------- | -------------------------------------------------------------------------------------------------------------- | | INVENTORY\_SNAPSHOT\_ID | Unique identifier for each inventory record. | | INVENTORY\_DATE | The date the inventory snapshot represents. Normalized to daily grain. | | PURCHASING\_PARTNER\_TYPE | "Distributor" or "Retailer" | | PURCHASING\_PARTNER\_ID | Store\_ID from `urs.stores` or Distribution\_center\_id from `urs.distribution_center` . | | UPC | Global barcode identifier, used to align retailer data with syndicated sources. | | LISTING\_SKU | SKU used by the retailer. Links to `urs.product_listing` | | LISTING\_SKU\_VENDOR\_FIELD | This contains the field from the POS sales that we are using for listing\_sku - ex: DPCI, TCIN, Vendor Number. | | VENDOR\_SKU\_VALUE | Vendor's reference number that links to their ERP. | | MASTER\_SKU | Vendor's SKU reference in their ERP. | | ON\_HAND\_QTY | Quantity of product physically on hand at the location on the given date. | | COMMITTED\_QTY | Quantity of product physically committed at the location on the given date. | | AVAILABLE\_QTY | On Hand Qty - Committed Qty | | ON\_ORDER\_QTY | Quantity of product currently on order but not yet received. | | IN\_TRANSIT\_QTY | Quantity of product currently in transit to retailer, warehouse, etc.. | | BACK\_ORDER\_QTY | Quantity of product that cannot be fulfilled as it is out of stock. | For guidance on analyzing your own retailer data (POS, Inventory, and Wholesale) and how to use URS in reporting, please see our Knowledge Base articles under: [Retail Analytics 101](https://help.daasity.com/start-here/analyzing-your-data/retail-analytics-101).