Channel Performance Data Feeds User Guide

About this guide 

This guide provides you information about how to access and use the Channel Performance data feeds that are available for all the Walmart Luminate Charter clients.

This guide comprises the following sections:

Data governance 

All assets of Walmart including data feeds are highly sensitive information. The sharing and storage of Walmart’s assets must adhere to the legal terms outlined in the Master Service Agreement (MSA) between the supplier and Walmart Inc.  

The following are some of the best practices for the data governance of Walmart’s assets: 

  • Ensure the privacy and security of Walmart’s data by having strong controls and guardrails in place. 
  • Ensure that Walmart’s data is protected and secured with limited access, which is accessible only on a need-to-know basis. For compliance purposes, this is subject to an audit. 
  • Ensure that the Risk Mitigation or Risk Management plan is in place in case of data risk or leak.  
  • Ensure strong adherence to Data Governance standards, policies, and processes.  

Intended audience 

This document is intended for the primary data teams of supplier companies who want to access the key data points to understand the sales performance of their product/brands/categories across different distribution channels at Walmart.  

The primary data teams of the supplier company comprise: 

  • Developers 
  • Solution integrators 
  • Testers 
  • Partner onboarding personnel, and others.  

List of acronyms 

The following table lists acronyms that are used in this document.  

Acronym Definition 
AUR Average Unit Retail 
CVI Customer Value Index 
DSV Direct Ship Vendor 
GCP Google Cloud Platform 
GMV Gross Merchandise Value 
GTINGlobal Trade Identification Number 
MDS Minimum Data Set 
OPD Online Pickup and Delivery 
ORCOrganized Retail Crime 
POS Point Of Sale 
UPC Universal Product Code 

Channel Performance data feeds 

Walmart provides several data feeds to help its suppliers collect and analyze data about their products or related categories across various distribution channels. Providing access to this data at a channel level helps suppliers make better decisions to improve the overall performance of their products. 

The Channel Performance data feeds are available to all Walmart Luminate Charter clients on a weekly basis. Since data feeds are generated within a day, they contain the most recent data.  

The Item access that the Channel Performance data feed provides is driven by the Walmart Luminate Charter Clients Global Trade Identification Numbers (GTINs) ownership. Walmart Luminate Charter Clients will be presented with the Items that they own based on their Global Locator Number (GLN ) to GTIN to Walmart Items mapping.   

Storage and structure of data feeds  

Channel Performance data feeds are stored in Google Cloud Storage (GCS) bucket created by Walmart. Each supplier has a separate storage bucket that has supplier-based data files. Each data feed has a trigger file. The file and folder structure of the data feed is outlined in the Trigger File and Folder Structure section.  

Trigger file and folder structure 

The Channel Performance data feeds collect and deliver trigger files to an encrypted Walmart storage bucket that Walmart provides to its suppliers. 

The storage bucket assigned to each supplier has multiple folders. One of the folders in the trigger folder has multiple trigger files corresponding to each data feed. Each trigger file is in the JSON format and contains the location or path to the data feed with other metadata. The presence of a trigger file ensures the availability of a data file.

Also, the Trigger files will be stored under a folder with the Walmart week number when they were run. Walmart week number(wmt_week_nbr) starts from Saturday to Friday.

Trigger files for the latest week run can be found in the drop location as shown below: 

gsutil ls {Vendor_Bucket}/trigger/weekly/{wmt_week_nbr}/* 

The folder structure for different data feeds is as follows: 

Trigger folder structure for Weekly data feeds 

Store Attribute 

{Vendor_Bucket}/trigger/weekly/{wmt_week_nbr}/storeattribute/wmt_weekly_storeattribute_ run_dt={process_run_date}.json  



Store Sales 




Item Attribute 

{Vendor_Bucket}/trigger/weekly/{wmt_week_nbr}/itemattribute/wmt_weekly_itemattribute_ run_dt={process_run_date}.json 



Omni Sales 




Prod Dimentsion

{Vendor_Bucket}/trigger/weekly/{wmt_week_nbr}/proddimension/wmt_weekly_proddimension _run_dt={process_run_date}.json



Trigger folder structure for History data feeds  

Store Sales 




Omni Sales 




Trigger folder structure for Adhoc data feeds 

Store Sales 

{Vendor_Bucket} /trigger/adhoc/{wmt_week_nbr}/storesales/wmt_adhoc_storesales_run_dt={process_run_date}_startdate={start_date}_enddate={end_date}.json 



Omni Sales 

{Vendor_Bucket} /trigger/adhoc/{wmt_week_nbr}/omnisales/wmt_adhoc_omnisales_run_dt={process_run_date}_startdate={start_date}_enddate={end_date}.json



Metadata within the trigger file 

Sample for Store Attribute 

“FeedName" : "storeattribute", 
"OutputGcs" : " {Vendor_Bucket}/weekly/{wmt_week_nbr}/storeattribute/run_dt={process_run_date}/", 
"RowCount" : "6162", 
"ExpiryDate" : {process_run_date} + 42 days 

Types of data feed 

Item Attributes data feed 

The Item Attributes data feed provides information about Item attributes for the given Walmart (WM) Item including hierarchy and supplier details.  

The following table provides the Item attributes data feed type and its dimension. 

Feed type Dimension 
Refresh Frequency Weekly 
Data Grain Walmart Item Number 
Incremental Data Snapshot 
File Format ORC 

Feed structure 

The following table provides the Item Attributes data feed structure. 

Business name Data type Primary key 
Walmart Item Number  bigint          
Store Item Id bigint 
Ecomm Prod ID bigint  
Vendor Number Int  
Accounting Department Number  int              
Walmart Department ID  int     
Item Status Code char (1)  
Item Name  varchar (1600)     
Fineline Description varchar (80)  
Item Start Date  date              
Item End Date date  
Item Type Code  smallint          
Walmart UPC Number decimal (18,0)  
Walmart UPC Description decimal (18,0)  
Item Type Description varchar (80)  
All Links Item Description varchar (25)  
All Links Item Number Int  
All Links  Store Item Id Int  
Base Unit Retail Amount  decimal (11,2)     
Never Out Indicator  tinyint           
Warehouse Min Order Quantity  int               
Pallet Height Quantity  smallint          
Pallet UPC Number  decimal (15,0)     
Warehouse Pack Quantity  int               
Warehouse Alignment Type Description  varchar (80)       
Warehouse Pack Length Quantity  decimal (9,3)      
Warehouse Pack Width Quantity   decimal (9,3)      
Warehouse Pack Cubic Quantity  decimal (9,3)      
Warehouse Pack Height Quantity  decimal (9,3)      
Vendor Department Number  smallint          
Vendor Min Order Quantity  int               
Vendor Pack Quantity  int               
Vendor Pack Weight Quantity  decimal (18,4)     
Vendor Pack Length Quantity  decimal (9,3)      
Vendor Pack Width Quantity  decimal (9,3)      
Vendor Pack Height Quantity  decimal (9,3)      
Vendor Sequence Number  smallint          
Omni Segment Number Int  
Omni Segment Description String  
Omni Department Number Int  
Omni Department Description String  
Omni Category Number Int  
Omni Category Description String  
Omni Category Group Number Int  
Omni Category Group Description String  
Omni Subcategory Number  int               
Omni Subcategory Description   string            
Vendor Stock ID varchar (20)  
Vendor Name varchar (250)  

Product Dimension data feed 

The following table provides the Product data feed type and its dimension.

Feed type Dimension 
Refresh Frequency Weekly 
Data Grain E-comm Prod ID 
Incremental Data Snapshot 
File Format ORC 

Feed structure 

The following table provides the Product Dimension data feed structure. 

Business name Technical nameData type Primary key 
Ecomm Prod ID catlg_item_idbigint 
Product Name prod_nm string   
Ecomm UPC Number ecom_upc_nbrstring 
Part of Bundle (Y/N) kit_comp_indsmallint  
Street Date street_d date  
Customer Average Rating Value cust_ratg_avg_valdecimal (4,3)  
Customer Rating Count cust_ratg_cnt decimal (15,0)  
Put Eligibility Indicator elig_put_ind
S2H Eligibility Indicator elig_s2h_ind
Current Replenishment Flag  own_repl_indsmallint  
CVI Have It Indicator  cvi_have_it_indsmallint  
Current Display Status lifecyc_status_nmstring 
Offer Start Date offr_start_dt
Offer End Date offr_end_dtdate  
Current Lowest Ship Method shpg_mthd_chrg_arraymap <string,string> 
Current Price Display Code price_type_nm
Current S2H Ship Charge shpg_chrg_amt
decimal (18,5)  
Walmart Order Department Number rpt_hrchy_lvl1_id int  
Walmart dot com Category Description   rpt_hrchy_lvl3_descstring 
Omni Segment Number omni_seg_nbr int  
Omni Segment Description omni_seg_desc
Omni Department Number omni_dept_nbr
Omni Department Description omni_dept_desc
Omni Category Number  omni_catg_nbr
Omni Category Description omni_catg_desc
Omni Category Group Number omni_catg_grp_nbr int  
Omni Category Group Description  omni_catg_grp_descstring  
Omni Subcategory Number omni_subcatg_nbr int               
Omni Subcategory Description omni_subcatg_desc
Company Codeop_cmpny_cdstring

Omni Sales Measures data feed 

The Omni Sales Measures data feed provides information about the Omni sales from all six channels* at an item or a date granularity. 

The following table provides the Omni Sales Measures data feed channel and its fulfillment type or service channel. 

Store/Online Fulfillment type or Service channel 
Store BIS (Buy in Store) 
Store PUT (Pick Up Today) 
Store OPD (Online Pickup and Delivery) 
Store SFS (Ship from Store) 
Online S2H (Ship to Home) 
Online S2S (Ship to Store) 
*Note: Marketplace is not part of the data feed. 

The following table provides the Omni Sales Measures data feed type and its fact feed. 

Feed type Fact feed 
Refresh Frequency Weekly 
Data Grain Walmart Item Number,  E-comm Prod ID, Service Channel,  Business Date, and Vendor Number 
Incremental Data Affected Dates+ Last 7 days 
File Format ORC 

Feed structure 

The following table provides the Omni Sales Measures data feed structure. 

Business name Type Primary key 
Walmart Item Number bigint 
 Ecomm Prod ID bigint 
Service Channel varchar (8) 
Company Code varchar (8)  
Business Date date 
Vendor Number string 
Vendor Name string  
WM Year Week Number int  
Order Channel Name varchar (20)  
Current Year AUTH Based GMV Amount decimal (11,2)  
Last Year AUTH Based GMV Amount decimal (11,2)  
Current Year AUTH Based Net Sales Amount decimal (11,2)   
Last Year AUTH Based Net Sales Amount decimal (11,2)  
Current Year AUTH Based Item Quantity decimal (11,2)  
Last Year AUTH Based Item Quantity decimal (11,2)  
Current Year Shipped Based GMV Amount decimal (11,2)  
Last Year Shipped Based GMV Amount decimal (11,2)  
Current Year Shipped Based Net Sales Amount decimal (11,2)  
Last Year Shipped Based Net Sales Amount decimal (11,2)  
Current Year Shipped Based Quantity  decimal (11,2)  
Last Year Shipped Based Quantity  decimal (11,2)  
Current Year AUR decimal (11,2)  
Last Year AUR decimal (11,2)  
Add to Cart int  
Delta Flag varchar (01)  

Store Attributes data feed 

The Store Attributes data feed provides information about the given store number for all store attributes such as location, manager details, and so on.  

The following table provides the Store Attributes data feed type and its dimension. 

Feed type Dimension 
Refresh Frequency Weekly 
Data Grain Store Number 
Incremental Data Snapshot 
File Format ORC 

Feed structure 

The following table provides the Store Attributes data feed structure. 

Business name Type Primary key 
Store Number Integer 
Store Name varchar (100)   
Geo Region Code char (2)   
Manager Name varchar (80)   
Phone Number char (18)   
Store Type Description varchar (40)   
Company Code String  

Store Sales Measures data feed 

The Store Sales Measures data feed provides information about all the store sales at item, channel, store, or date level. 

The following table provides all the Store Sales data feed channels and their fulfillment type.  

Channel Fulfillment type 
Store BIS (Buy in Store) 
Store PUT (Pick Up Today) 
Store OPD (Online Pickup and Delivery) 
Store SFS (Ship from Store) 
*Note: Marketplace, Ship 2 Home (S2H) and Ship 2 Store (S2S) are not part of the feed. 

The following table provides all the Store Sales data feed types and its fact. 

Feed type Fact 
Refresh Frequency Weekly 
Data Grain Business date, Walmart Item number, Store number, the service channel 
Incremental Data Last seven Days + affected Dates 
File Format ORC 

Feed structure 

The following table provides all the Store Sales data feed structures. 

Business name Data type Primary key 
Store Number integer 
Walmart Item Number  bigint 
 Store Item Id  integer  
Service Channel varchar (20) 
Business Date Date 
Vendor Number string  
Vendor Name string  
WM Year Week Number int  
Company Code varchar (8)  
Current Year POS Sales decimal (11,2)   
Last Year POS Sales decimal (11,2)   
Current Year POS Quantity  decimal (11,2)   
Last Year POS Quantity  Decimal (11,2)   
Current Year AUR decimal (11,2)   
Last Year AUR decimal (11,2)   
Delta Flag Varchar (01)  

Delivering data feeds 

To deliver the Channel Performance data feeds to its suppliers, Walmart uses a Google Cloud Storage bucket. The following diagram shows the complete data delivery mechanism of exchanging the data with external suppliers by using the GCS bucket. 

Graphical user interface, application, Word

Description automatically generated
Data Delivery Mechanism

Sharing data with suppliers 

To begin the process of sharing data, Walmart and the supplier have shared the responsibility of setting up the data delivery pipeline that needs to follow these steps: 

  1. Walmart creates and shares a dedicated storage bucket and service account for each supplier.  
  2. Walmart restricts access to storage buckets created in its environment by adding the service account to the permissions of the bucket.  
  3. Walmart provides every supplier with a JSON key corresponding to the GCP service account and bucket address. This JSON key is subject to change at regular cadence for better security. These changes are promptly communicated to suppliers. 
  4. Walmart shares the JSON key as an attachment in a secure email. The suppliers can download the JSON key by following steps from the Obtain Service Account JSON key from Secure and Encrypted email section given below.
  5. Walmart notifies the supplier of data availability in the corresponding bucket through an email and a trigger file. 
  6. Walmart follows a standard trigger file naming convention and folder structure for each feed. 
  7. Multiple folders are created in the storage bucket based on the refresh type and data feeds. 
  8. Walmart shares the schedule for data feed delivery to the supplier.  

Downloading data from Walmart storage bucket 

To download data feeds from the Walmart storage bucket, the supplier can do the following:

  • Obtain the service account JSON key from a secure and encrypted email
  • Set up Google Cloud SDK 

Obtaining service account JSON key from secure and encrypted email 

To access Walmart-owned data buckets, suppliers will receive the service account JSON key through a secure email.  

Note: Activating the service account is a one-time activity at the time of onboarding.  

To view the contents of the secure email, follow these steps: 

  1. The suppliers will receive an email from in their inbox. As it is a secured email, the content looks as follows: 
  2. The user is requested to click the Click here link, where the user will be authenticated as a registered user to view the email content.
    1.  For the first time, users are required to register themselves to access the secure email. See the screenshot below. 
    2. After filling in all details, enter the validation code. You will receive this validation code via another email to your email ID at the same time. See the screenshot below. 
  3. After the successful login, the following email is visible.  
    Important: Refrain from forwarding this email to anyone for security reasons. 
  4. Click Read the message and then click Sign in with One Time passcode in the subsequent screen.
    A form will open to enter a One Time Passcode (OTP). This passcode will be sent via another email from MS Office Encryption to the supplier’s same email ID. 
  5. After providing the passcode, the decrypted email content will be accessible and users are requested to download the attachment JSON key file. 
  6. Remember to check the status of your email if it shows “SECUREMAIL” prefix and an attachment.  
  7. The attached JSON file contains the service account information. Therefore, keep it at a secure location. Also, refrain from making any changes to this file as it may cause issues in accessing the GCP bucket. In case of any issues, report to

Setting up Google Cloud SDK 

  1. Set up Google Cloud SDK (gcloud and gsutil) in the respective supplier systems where you want to copy the file. Use google sdk install to install the Google SDK at the location where you want to copy the file. 
  2. Activate the service account provided by Walmart by using the following command and replace the path to a key file and keyfile.json with the path that you placed the service account JSON key. This key is the one that is shared by Walmart to the supplier via a secure method. This step is used to authenticate any operation performed on Walmart’s Google Cloud Storage.  


Navigate to the bin directory under the google-cloud-sdk path in the system and activate the service account. 

- cd <path to google-cloud-sdk >/bin/
- gcloud auth activate-service-account --key-file=’<path to keyfile>/<keyfile.json>'

Best practices  

  1. Activate the service account for every new session. For more information, refer to step 2 from the above section. 
  2. Always prefer to use the -m option in the gsutil cp command since it inherently generates multiple threads for a faster copy for huge data transfers. With the multi-threading option, the transfer speed is high as compared to regular copies. It takes around 3 mins to transfer 1GB of data (subject to network bandwidth). 
  3. For security reasons, sharing, forwarding, or editing the service key JSON file is not allowed. 

Email notifications 

At the time of onboarding, week over week, the suppliers will be notified of the summarised status of the feeds. This email is generated when the last feed’s SLA for that week is reached. At this time, the email is auto-generated with the subject as “Your data feed is Ready” or “Your data feed is in progress” depending on the consolidated status of all feeds for that week. 

This will convey feeds status at the time of SLA, the date until which the data is available for supplier’s access.  Suppliers can unsubscribe to notifications by accessing the unsubscribe link in an email.  

When data feeds are in progress 

When data feeds are ready

Using data feeds 

After the cloud SDK is downloaded and service accounts are activated as mentioned above, the suppliers are ready to consume the data feeds.  

To get started: 

  • Identify the status of the data feeds 
  • Identify the meta information and location of feeds from the trigger file 
  • Connect to transfer the data into Supplier’s ingestion layer
  • Reconcile the received file from Meta information from the trigger file 
  • Delta processing for incremental feeds on supplier’s stage layer
    • Omni Sales Measures  
    • Store Sales Measures 
  • Data distribution for Item Attributes and Product Dimension feeds 
  • Data distribution for Omni Measures data feed 
  • Flatten the data for a full historic refresh on the supplier’s consumption layer 

Identifying the status of feeds 

Every data feed is expected to be available for supplier’s consumption on its agreed SLA time. The suppliers need to download the respective feed’s trigger file from the Walmart storage.  The availability of the trigger file ensures the respective feed’s availability. Access the actual data feeds only when the trigger file is available. 

Command to check for a trigger file  

 gsutil –ls <full-gcs-ath-of-trigger-file>  


gsutil  -ls  gs://{Walmart GCS bucket}/folder1/a/b/c/abc.txt <gs://{Supplier GCS Bucket}>/folder2/a/abc.json 

Proceed further only when this step is successful.  

Identifying the meta information and location of feeds 

The supplier uses the following command to read the trigger file and access the meta-information, such as: 

  • Feed name 
  • Total number of records in the data feed 
  • Location of the data feed 
  • Feed’s expiry date 

Command to access the trigger file 

Use gsutil –cat <full-path-of-trigger-file>  


gsutil -cat  gs://{Walmart GCS bucket}/folder1/a/b/c/abc.txt <gs://{Supplier GCS Bucket}>/folder2/a/abc.txt 

Identify the metadata information, such as GCS location, record count, and others. 

Connecting to transfer data into supplier’s ingestion layer

Activate the service account every time a new session is opened for transferring the data. To activate the service account, refer to step 2 from the Setting up Google Cloud SDK section. The feeds are copied to the supplier’s environment by using the gsutil tool. The gsutil cp command allows you to copy data from the GCS bucket to your local file system. 


To transfer a regular copy, use the following command:

gsutil cp -r {SOURCE} {DESTINATION}  

If you have many files to transfer, you can perform a parallel multi-threaded/multi-processing, copy by using the top-level gsutil -m option. 


To transfer a Multi-Threading copy, use the following command: 

gsutil -m cp -r   gs://{Walmart GCS bucket}/folder1/a/b/c/abc.txt {Vendors local Directory} 

Reconciling the received file from meta-information 

Read the trigger file to retrieve the data feed file location and record count of the feed. Reconcile the meta-information with the data feed. If the reconcile is successful, then copy data feed to supplier stage and repeat for all records in data feeds. If the reconcile is unsuccessful, then repeat the data transfer process for that data feed. 

Delta processing for incremental feeds on supplier’s stage layer 

Certain data feeds will have the column “delta_flag”. Values of the delta flag can be any one of “I”, “U’ or “D”. This flag is to identify the incremental changes to the data from the previous snapshot that was shared. The following data feeds have the delta flag and need to follow the processing as detailed: 

  • Omni Sales Measures  
  • Store Sales Measures 

“I” represents that this is the first time Walmart has sent the data for this item for a given date (maybe store/item/channel/date). The consumer needs to insert such records into their process. 

“U” represents that this is an update to an existing record that was sent previously by Walmart for that item on a given business date (maybe store/item/channel/date). The consumer needs to update this data into their process. 

“D” represents that this is a deleted record that was sent previously by Walmart for that item on a given business date (maybe store/item/channel/date). The consumer needs to delete this data in their process. 

The supplier’s ingestion layer is the raw data layer that has data as provided by Walmart on that particular week. This data needs to be processed with the delta flag and fed into the supplier’s stage layer. 

For every record in the stage layer, check if that record already exists in the supplier’s data and process the feed accordingly to the delta flag. Here is the supplier’s stage layer workflow.  

There can be two Error cases: 

  • Record for a particular key (grain) already exists in the Supplier Stage and that has delta flag = “I” in Supplier Ingestion Layer 
  • Record for a particular key (grain) does not exist in the Supplier Stage and that has delta flag equals to “U’ or “D” 

You will see any of the above two cases proactively in Walmart. 

Distributing data for Item Attributes and Product Dimension data feed 

The item attributes and product dimension data feed received by the Supplier is the latest snapshot and contains only the attributes related to the items and products supplied to Walmart as of the current date. If there are items that were historically supplied by the supplier to Walmart and are no longer being supplied as of the current date, then the attributes related to those items are not sent in the feed. 

Distributing data for Omni Measures data feed 

The Omni Measures data feed has only the measures for items that are currently supplied to Walmart as of the current date. If there are transactions related to items that were historically supplied by the supplier to Walmart but are no longer supplied as of the current date, then those transactions are not sent as part of the Omni Measures feed received by the supplier. But if the supplier explicitly requests the measures related to items that were historically supplied by the supplier, then going forward (that is, after the feed is shared for the first time) Walmart will accommodate the request. Flatten the data for a full historic refresh. 

Attributes and measures are sent as a different data feed, as a reason they must be joined together by using the Primary and Foreign Keys to derive the flattened data. 

Omni Sales Measures with facts 

To get a flattened view of the Omni Sales of an item/channel grain with items/product-hierarchy and other attributes, join Fact Feed Table with Item Feed and Product Feed by using the following join condition. 

Where, for store channels with Item Feed- Join Key on Walmart Item Number. 

For E-comm channels with Product Feed, join Key on E-comm Prod Id. 

Store Sales Measures with facts 

To get a flattened view of Store Sales at an item/store/date grain with store attributes and item-hierarchy and other attributes, join Store Fact Table with Store Dimension and Item Dimension by using the following join condition. 

Where, Join Key = Store Sales to Store Dimension on Store Number to Item Dimension on Store Sales. Walmart Item Number = Item. Walmart Item Number.