sc_orders

In this article

• Summary
• Supported Use Cases
• When not to use the view

Summary

The sc_orders view serves as the hub for all order transactions. In this view, you will find granular information about any collected order, including when the order was placed, who placed the order, the value of the order, corresponding fulfillment status (if available), and associated digital marketing campaigns (if available).

• View Grain: Order-level transactions. Each record should have a unique order identifier
• Primary (Composite) Key(s):
  • scid
• Foreign Key(s): 
  • cuid
  • sku or common_sku
  • campaign_id 
  • order_date 

The scid field can be used as a joining condition with other views in SoundCommerce if those views contain the scid field. Generally speaking, the order_id field may also be used as a joining condition. However, be cautious with using just order_id as different channels may reuse order_id values. The scid takes channel and source into consideration, which provides a truly unique identifier. 

Supported Use Cases

The following use cases are examples and only provide a subset of all potential use cases that can be addressed with data found in sc_orders and other views. This list should not be assumed to be comprehensive. 

• I am interested in identifying my first-time and/or repeat customers. From these, I would like to isolate those customers who have only placed their order(s) using a promotional code. 
• I want to identify the top 5 shipping states that have the highest contribution profit. From this, I would like to see which source and medium drove those sales. 
• I want to identify the top shipping region with the highest number of canceled orders and understand the average canceled value for those orders. 

When not to use the view

This view contains order-level data. While it contains much information beyond just the order (i.e. aggregated customer historical sales, campaign source and medium, fulfillment statuses, etc.), all of this data has been aggregated to the order-level.

This view does not necessarily contain specifics about the following:

• Campaign-related metrics (i.e., clicks, impressions, conversions)
• Fulfillment-related metrics (i.e., shipment partner, tracking number, fulfillment breakdown of constituent items)
• Item-related metrics (i.e., sku-level price, sku-level cost, sku-level discounts)
• Product-related metrics (i.e., warehouse inventory for a given product)
• Customer PII-related values (i.e., first and last names, emails, phone numbers, addresses)

Joining this view with other views that are more granular (i.e., the item-level or fulfillment-level views) will cause duplicate records from the order view. Be careful when aggregating after joining with a more granular view as aggregate order measures will likely be inflated. 

Joining this view with other less granular views (i.e., the customer views) will result in duplicated data values found in the less granular view. Be careful when aggregating after joining with a less granular view as the measures found in the less granular view will likely be inflated.

Return to SoundCommerce Retail Modules