Data Transfer Spec

Customer Data Transfer
Specification (Kroger).
Revision: V3.1k
May 13, 2020
i
Data Transfer Spec.
Table of Contents:
1. INTRODUCTION. .................................................................................................................................... 1
1.1. ITEM INCLUSION:.................................................................................................................................. 1
1.2. BACK DATA: ........................................................................................................................................ 1
1.3. REFERENTIAL INTEGRITY: .................................................................................................................... 1
1.4. CHANGES FROM V1.1: .......................................................................................................................... 1
1.5. SUBSCRIPTION LEVEL........................................................................................................................... 2
1.6. SUMMARY OF FILES.............................................................................................................................. 3
1.7. FILE FORMATTING. ............................................................................................................................... 4
1.8. MISC: ................................................................................................................................................... 4
1.9. DATA TRANSMISSION. .......................................................................................................................... 5
2. MASTER FILES........................................................................................................................................ 6
2.1. CASE MASTER. ..................................................................................................................................... 6
2.2. ITEM MASTER. ..................................................................................................................................... 7
2.3. STORE MASTER. ................................................................................................................................... 8
2.4. WAREHOUSE MASTER. ......................................................................................................................... 9
2.5. STORE PRODUCT MASTER. ..................................................................................................................10
3. STORE DATA. .........................................................................................................................................11
3.1. DAILY POS, DAILY POS RESTATEMENT, AND DAILY POS HISTORY....................................................11
3.2. EXPECTED PRICE. ................................................................................................................................12
3.3. SALES PLAN. .......................................................................................................................................13
3.4. STORE BALANCE ON HAND, SHELF. .....................................................................................................15
3.5. STORE DELIVERIES. .............................................................................................................................16
3.6. DERIVED OUT OF STOCK EVENTS (FORMERLY SHELF SCAN AUDIT) ....................................................16
3.7. WEEKLY COMPETITIVE POS SALES FILE .............................................................................................17
3.8. AD WEEKLY COMPETITIVE POS SALES FILE .......................................................................................18
3.9. DAILY STORE AUTHORIZATION AND PLANOGRAM ASSOCIATION ........................................................19
4. WAREHOUSE DATA. .............................................................................................................................19
4.1. WAREHOUSE INVENTORIES. ................................................................................................................19
4.2. WAREHOUSE ORDERS. ........................................................................................................................21
4.3. WAREHOUSE SUBSTITUTIONS. .............................................................................................................22
5. DEMANDVIEW MEASURES. ................................................................................................................23
5.1. DEMANDVIEW STORE MEASURES. ......................................................................................................23
5.2. DEMANDVIEW STORE FORECASTS.......................................................................................................25
5.3. DEMANDVIEW WAREHOUSE MEASURES. ............................................................................................27
5.4. DEMANDVIEW WAREHOUSE FORECASTS.............................................................................................27
6. CONTROL DATA. ...................................................................................................................................28
6.1. MANIFEST. ..........................................................................................................................................28
6.2. ZIP CONTAINER. ..................................................................................................................................28
ii
Data Transfer Spec.
Revision History
Revision Date Author Purpose of Revision
V1.1f 04/16/2011 Wayne Levy In spreadsheet form.
V1.2 04/28/2011 Brian Rock Converted to document form.
Various cosmetic field name changes.
Include Warehouse identifier with Local Vendor ID to ensure
validity.
Added DV_Ad_Type field to DemandView Store Measures file.
V1.2a 04/29/2011 Brian Rock Sales Plan file frequency will be daily, not weekly.
Store Master file frequency will be ‘on change’, not weekly.
Item Master file frequency will be ‘on change’, not weekly.
V1.2b 05/02/2011 Brian Rock Fixed a duplicate field name, On_Order_Qty, in DemandView Store
Forecasts file.
Renamed and clarified the meaning of Fcast_Store_Order_Qty field
in DemandView Warehouse Measures.
V1.2c 05/16/2011 Brian Rock Added section 1.8 Data Transmission.
All master files now sent with daily frequency.
Expanded Ad_Type_Code_2 definition in Sales Plan file.
Conformed DV_Ad_Type in Sales Plan file to the definitions in
DemandView Store Measures and Forecast files.
Updated the definition of all DV_Ad_Type fields.
Store Master Mgt_Zone changed to Varchar(2).
V1.2d 06/08/2011 Brian Rock Removed key field indicators from Store Deliveries file layout.
V1.2e 05/13/2020 Brian Rock
V1.2f 07/24/2013 Jim Martin Updated section 2.1 Case Master to include Consumer UPC
Updated section 3.4 Store Balance on Hand for history
Added section 3.6 Shelf Scan Audit
Added section 3.7 Weekly Competitive Sales File
Updated section 4.1 Warehouse Inventories to include Case Pack
and Store Quantities
Updated section 5.1 DemandView Store Measures to default alert
values to “0”
V1.2g 11/20/2014 Stacy Simonds Modified back data availability.

V1.2h 1/22/2016 Brian Hardner Integrated SATH specification into this document. Adjusted Shelf
Scan Audit verbiage to reflect the change from Audit to derived M6
OOS measure.
Updated duration for POS back data history.
V1.2i 10/3/2016 Jim Martin Section 1.5 Added Subscription level table
Section 3.4 Added missing data from prior day, if received in current
day, will be provided on current day transfer
Section 3.5 Removed highlights for “Delivery Date”
Section 3.8 Removed source tables. Removed sample file format.
V2.2j 11/16/2017 Jim Martin Updated 3.3 Sales Plan for changed Ad_Type_Code_2 values
V3.1k 05/07/2020 Evan Palazzolo Updated as 84.51° Data Transfer Spec
DemandView™ is a trademark of Market6, Inc.
iii
Data Transfer Spec.
1. Introduction.
What follows is Version 1.2h of the specification for standard Data Transfer file layouts.
1.1. Item Inclusion:

Item inclusion in the data files defined herein is based upon Kroger Corporate Vendor Codes, which are provided by Kroger
in various data feeds and which are associated with particular Consumer UPC’s, Base UPC’s and Case UPC’s.
For DSD items, the association between Kroger Corporate Vendor Codes and items is made by individual store.
A Market6 Customer ID is, in turn, associated with a collection of Kroger Corporate Vendor Codes and this association
drives selection of the items included in a set of Data Transfer files.
Note that a Kroger Corporate Vendor Code may be associated with one or more local Kroger Warehouse Vendor ID’s, which
will likely differ across warehouses.
A Kroger Corporate Vendor Code may also be associated with one or more D&B Vendor Codes when the relevant products
are DSD.
1.2. Back Data:

Back data is available only for POS Daily sales.
84.51° can provide 12 months of back history.
1.3. Referential Integrity:

For timing reasons, there is a remote possibility that referential integrity may not be assured for items and stores because the
associated master files are obtained from Kroger on a weekly basis and may lag sales of the relevant products or in the
affected stores. It is therefore possible to have stores and or items with daily POS movement that are not represented in their
respective master files.
The same may be true for POS history, which may contain items or stores that are no longer reflected in current masters.
Every effort has been made to include stores in the store master that have closed over the past two years or so, but it is
conceivable that some may have been missed.
1.4. Changes From V1.1:

Version 1.2 data files no longer contain a Vendor_ID key value as this was found to cause data integrity problems. This field
has been repurposed to contain a Retailer_ID so as to avoid changing the field structure of all affected files.
All Master Files will be provided every day, even when the file is received from Kroger on a weekly basis, so that new
information will be forwarded as soon as available. For example, the Kroger Corporate Vendor Codes associated with a
customer may change mid-week, resulting in updated Item Master information.
Other minor changes have been listed along with file definitions.
1
Data Transfer Spec.
1.5. Subscription Level
The following table lists each Data Transfer file type, the Subscription Level at which each file is available, along with the
frequency of each file.
Frequency of Bronze & Silver Gold & Platinum Platinum subscribers

Delivery (B/S) (G/P) subscribers with Advanced Supply
subscribers with no fees Chain package
with fees
associated
store_master Daily x x
item_master Daily x x
daily_pos Daily x x
store_product Daily x x
daily_pos_restate Daily x x
store_shelf Daily x x
daily_audit Daily x x
warehouse_master Daily x x
case_master_v2 Daily x x
whs_substitutions Daily x x
whs_boh Daily x x
expected_price Daily x x
whs_orders Daily x x
sales_plans Daily x x
store_deliveries Daily x x
comp_weekly_pos Weekly x x
comp_weekly_pos_restate Weekly x x
sath Daily x x
kdp_store_forecast Daily x
kdp_whs_forecast Daily x
kdp_store Daily x
kdp_whs Daily x
2
Data Transfer Spec.
1.6. Summary of Files.
Table Freq Description File Name

MASTER FILES
Case Master Daily A master file about case packs, by Warehouse. case_master_DATATRANSID_yyyyMMddhhmmss.fi
l
case_master_v2_DATATRANSID_YYYYMMddhhmmss
.fil
Item Master Daily A master file about consumer UPCs, by Division. item_master_DATATRANSID_yyyyMMddhhmmss.fi
l
Store Master Daily Store master file. store_master_DATATRANSID_yyyyMMddhhmmss.f
il
Warehouse Master Daily Warehouse master file. warehouse_master_DATATRANSID_yyyyMMddhhmm
ss.fil
Store Product Master Daily Product master file, by Store. store_product_DATATRANSID_yyyyMMddhhmmss.
fil
STORE DATA
Daily POS Daily Daily Sales by Division/Store/Consumer UPC. daily_pos_DATATRANSID_yyyyMMddhhmmss.fil
Daily POS Restatement Daily Restated Daily Sales by Division/Store/Consumer UPC. daily_pos_restate_DATATRANSID_yyyyMMddhhm
mss.fil
Daily POS History One Historical Daily Sales by Division/Store/Consumer UPC. daily_pos_hist_SEQ#_DATATRANSID_yyyyMMddh
Time (Back data.) hmmss.fil
Expected Price Daily Daily POS Price by Division/Store/Consumer UPC expected_price_DATATRANSID_yyyyMMddhhmmss
.fil
Sales Plan Daily Planned Prices, Advertising, and Display by sales_plans_DATATRANSID_yyyyMMddhhmmss.fi
Division/Store/Consumer UPC. l
Store Balance on Hand, Daily Daily balance on hand, and shelf measures by store_shelf_DATATRANSID_yyyyMMddhhmmss.fi
Shelf Division/Store/Base UPC. l
Store Deliveries Daily Deliveries to Stores from Warehouses, by Base UPC/Case UPC store_deliveries_DATATRANSID_yyyyMMddhhmm
(will include DSD in the future). ss.fil
Shelf Scan Audit Data Daily Daily Kroger shelf audit to determine OOS conditions. daily_audit_DATATRANSID_yyyyMMddhhmmss.fi
Completed by BaseUPC. l
Weekly Competitive Sales Weekl Commodity competitive sales file to be made available weekly See specification below
File y
Daily Store Authorization Daily Store Item Authorization and Planogram Association sath_{DATATRANSID}_{yyyyMMddhhmmss}.fil
WAREHOUSE DATA
Warehouse Inventories Daily Warehouse inventories. whs_boh_DATATRANSID_yyyyMMddhhmmss.fil
Warehouse Orders Daily Orders from the Kroger Warehouse to Vendors. whs_orders_DATATRANSID_yyyyMMddhhmmss.fil
3
Data Transfer Spec.
Table Freq Description File Name

Warehouse Substitutions Daily Warehouse substitutions of store orders with a different case. whs_substitutions_DATATRANSID_yyyyMMddhhm
mss.fil
DEMANDVIEW™ MEASURES
DemandView™ Store Daily DemandView additional measures by Division/Store/Base kdp_store_DATATRANSID_yyyyMMddhhmmss.fil
Measures UPC.
DemandView™ Store Daily Forecasts of Store Demand, Orders, and Inventory by kdp_store_forecast_DATATRANSID_yyyyMMddhh
Forecasts Division/Store/Base UPC. mmss.fil
DemandView™ Daily DemandView Portal additional measures by Warehouse/Case. kdp_whs_DATATRANSID_yyyyMMddhhmmss.fil
Warehouse Measures
DemandView™ Daily Forecast of Store Orders and Consumer Demand by kdp_whs_forecast_DATATRANSID_yyyyMMddhhmm
Warehouse Forecasts Warehouse/Case. ss.fil
CONTROL DATA
Manifest Daily List of Files, and Vendor_IDs, with Summary Information manifest_DATATRANSID_yyyyMMddhhmmss.fil
Zip Container Daily Zip file containing all other files relevant to each day. DATATRANSID.zip
1.7. File Formatting.

All files have the following formatting attributes:
➢ ASCII text.
➢ Pipe delimited.
➢ Null represented by consecutive delimiter characters ||.
➢ No pipe after last field.
➢ Unix line termination format.
➢ Char(x) data types have exactly x characters.
➢ Varchar(x) data types have up to x characters.
➢ Decimal(x,y) data types have up to x digits, followed when needed by ‘.’ and up to y decimal places.
➢ Negative numbers are preceded by ‘-’.
1.8. Misc:
In the tables below that define file layouts, please note that green highlighted rows represent key fields. Deprecated fields have a red highlight, and new fields
have a blue highlight.
4
Data Transfer Spec.
1.9. Data Transmission.

One principal transmission mechanism is available for customers to receive Data Transfer files.
1. SFTP.
Customers should obtain the 84.51° server URL, and a user ID and password from their Client Service representative. If
customers prefer to authenticate by means of a digital certificate, that can also be accommodated.
Upon login, customers will be placed in their home directory on the 84.51° server.
A new data extract file will be placed in the customer’s SFTP home directory each day. This file will be a zip compressed file
containing 19 payload files as described herein.
The zip file will have a filename in the format {DATATRANSID}.zip, where {DATATRANSID} will be a unique number.
After a successful download and integrity check, 84.51° recommends that customers delete the file from the server. Doing so
will eliminate the need for customers to maintain logic on their side to prevent downloading a file more than once.
84.51° will remove to archive any file that remains in a customer’s SFTP home directory for more than 7 days.
5
Data Transfer Spec.
2. Master Files.
2.1. Case Master.

File name: case_master_ %DataTranID%_%DataTranFileTimestamp%.*
case_master_v2_ %DataTranID%_%DataTranFileTimestamp%.*
Measure Description Data Type Example

Vendor_ID Local Warehouse Vendor ID. Varchar(20) 04431
Whs_No Kroger warehouse number. Char(3) 011
Case_UPC Case UPC code. Char(13) 0005200000339
KLN Kroger Line Number. Varchar(20) 00524
Case_Desc Case description. Varchar(50) PRPL SINGLES KIWI STRWBRY
Units_Per_Case Units per case. Integer 12
Warehouse definition. (May not agree
with the Vendor’s perspective.)
Always 1 for Peyton warehouses.
Ref_Date Reference date for this record. Date 2011-03-23
Corp_Vend_Code Kroger internal corporate vendor Varchar(20) K0002943
code.
Corp_Vend_Name Kroger corporate vendor name. Varchar(50) QUAKER SALES & DISTB INC
Discontinue_Date Date after which this warehouse no Date 9999-12-31
longer order this product.
9999-12-31, if none.
Store_Pack Store pack. (Units) Integer 12
Typical store order quantity.
Number of retail units per store
shipping unit.
Inner_Pack_Qty Inner pack quantity. Integer 1
Number of Store Packs per case.
Not valid for Peyton warehouses.
Cons_UPC Consumer UPC code. Char(13) 0005200000339
Notes:
Includes only warehoused products.
Case pack from the Vendor’s perspective should be (Store_Pack * Inner_Pack_Qty), except for Peyton warehouses, but this is
not always the case in the data received from Kroger. For Peyton warehouses, no true case pack or case pack calculation is
provided by Kroger.
84.51° is working to get true Vendor-perspective case pack information and will add a corresponding field as soon as feasible. A
field with the Consumer UPC contained within the case may also be added in a future version.
Changes from V1.1f:

Data Type changes:
Vendor_ID from Char(9) to Varchar(20)
KLN from Char(6) to Varchar(20)
Case_UPC from Char(14) to Char(13)
Case_Desc from Char(65) to Varchar(50)
Corp_Vend_Code from Char(5) to Varchar(20)
Corp_Vend_Name from Char(65) to Varchar(50)
Changes for version 1.2f

Added consumer upc to end of file. Please note that cases with multiple consumer upc’s, such as shippers, will not be complete.
Available until October 14, 2013
6
Data Transfer Spec.
2.2. Item Master.

File name: item_master_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Retailer_ID Retailer ID. Varchar(20) KROGER
Ref_Date Reference date for this record. Date 2011-03-08
Div_No Kroger division number. Char(3) 011
Cons_UPC_Desc Consumer UPC description. Varchar(50) PRPL SINGLES KIWI STRWBRY
Cons_UPC_Size_Desc Consumer UPC size description. Varchar(15) 24 OZ
Cons_Active_Cd Consumer UPC active status code. Char(1) A = Active
D = Deactivated
X = To Be Deleted
Cons_Qty_UOM Consumer UPC POS quantity unit of Char(1) U = Units
measure. W = Weighed
X = Unknown
Base_UPC Kroger SKU Code. Char(13) 0005200000339
Base_UPC_Desc Kroger SKU description. Varchar(50) PRPL SINGLES KIWI STRWBRY
Default_Case_UPC Prominent replenishment Case UPC in Char(13) 0005200000339
division.
Dept_Cd Department Code. Char(2) 01
Dept_Desc Department Description. Varchar(50) 01 GROCERY
Sub_Dept_Cd Sub Department Code. Char(2) 01
Sub_Dept_Desc Sub Department Description. Varchar(50) 01 GROC-ALL OTHER
Commodity_Cd Commodity Code. Char(3) 035
Commodity_Desc Commodity Description. Varchar(50) 035 WATER -
(SPARKLING&STILL)
Sub_Commodity_Cd Sub Commodity Code. Char(5) 18211
Sub_Commodity_Desc Sub Commodity Description. Varchar(50) 18211 STILL WATER FLVRD
DRNK/MNRL WT
Default_Whs Prominent Warehouse for Division. Char(3)
Deprecated. Will be left blank.
Notes:
A given Base UPC may include more than one Consumer UPC.
Changes from V1.1f:

Data Type changes:
Retailer_ID from Char(9) to Varchar(20)
Cons_UPC from Char(14) to Char(13)
Cons_UPC_Desc from Char(125) to Varchar(50)
Cons_UPC_Size_Desc from Char(15) to Varchar(15)
Base_UPC from Char(14) to Char(13)
Base_UPC_Desc from Char(125) to Varchar(50)
Default_Case_UPC from Char(14) to Char(13)
Dept_Desc from Char(65) to Varchar(50)
Sub_Dept_Desc from Char(65) to Varchar(50)
Commodity_Desc from Char(65) to Varchar(50)
Sub_Commodity_Desc from Char(65) to Varchar(50)
7
Data Transfer Spec.
2.3. Store Master.

File name: store_master_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Store_No Store number. Char(5) 00057
Store_Banner Store banner. Varchar(20) DILLON STORES
Check_Lane_Qty Checkout lane quantity. Integer 5
Sales_Square_Feet Square feet of selling area. Integer 15313
Phone_No Store phone number. Varchar(15) 3167882809
Address Store address. Varchar(50) 200 GREENWAY
City Store city. Varchar(50) DERBY
County Store county. Varchar(50) SEDGWICK COUNTY
State Store state. Varchar(20) KS
Zip Store zip code. Varchar(20) 67037
Open_Date Store open date. Date 1977-06-30
Open_Flag Store open flag. Char(1) Y = open
N = closed
Close_Date Store closed date. Date 9999-12-31
If not closed, 9999-12-31
Major_Type_Code Major store type code. Char(1)
Major_Type_Desc Major store type description. Varchar(50) CONVENTIONAL FOOD
Sub_Class_Code Store sub-class code. Char(2)
Sub_Class_Desc Store sub-class description. Varchar(50)
Acc_Active_Code Store accounting active code. Char(1)
Total_Square_Feet Total square feet. Integer
MSA_Code Metro Statistical Area code. Char(5) 48620
MSA_Desc Metro Statistical Area code Varchar(50) WICHITA, KS
description.
Blo_No Block Number. Char(4)
Adv_Week_Start Weekday of Major Ad break. Char(1) 1 = Sunday
2 = Monday
etc.
Mgt_Zone Kroger Management Zone code. Varchar(2) 02
Div_ID Division ID code. Integer
Div_Desc Division description. Varchar(50) Dillon
Mgt_Div_ID Management Division ID. Integer
Mgt_Div_No Management Division number. Char(3) 615
Mgt_Div_Desc Management Division description. Varchar(50) Dillon
Region_ID Region ID. Integer
Region_Code Region code. Char(1) W = WEST
E = EAST
C = CENTRAL
J = JAY-C
U = UNASSIGNED
Region_Desc Region description. Varchar(20) CENTRAL
Gas_Open_Date Gas station open date. Date 9999-12-31
If none, 9999-12-31
Gas_Close_Date Gas station closed date. Date 9999-12-31
If not closed, 9999-12-31
Gas_Flag Gas station flag. Char(1) N = No gas station
Y = Has gas station
Store_Open_Hour_Mon Store open time Monday. Char(4) 0700
Store_Close_Hour_Mon Store close time Monday. Char(4) 2200
Store_Open_Hour_Tue Store open time Tuesday. Char(4) 0700
Store_Close_Hour_Tue Store close time Tuesday. Char(4) 2200
Store_Open_Hour_Wed Store open time Wednesday. Char(4) 0700
Store_Close_Hour_Wed Store close time Wednesday. Char(4) 2200
8
Data Transfer Spec.

Store_Open_Hour_Thu Store open time Thursday. Char(4) 0700
Store_Close_Hour_Thu Store close time Thursday. Char(4) 2200
Store_Open_Hour_Fri Store open time Friday. Char(4) 0700
Store_Close_Hour_Fri Store close time Friday. Char(4) 2200
Store_Open_Hour_Sat Store open time Saturday. Char(4) 0700
Store_Close_Hour_Sat Store close time Saturday. Char(4) 2200
Store_Open_Hour_Sun Store open time Sunday. Char(4) 0700
Store_Close_Hour_Sun Store close time Sunday. Char(4) 2200
Notes:
Kroger stops sending master data when a store closes, so the data for closed stores is accurate only as of the last date for which
information was received from Kroger.
May add a Store_Name field if enough customers request it. Deprecated fields would be eliminated at the same time.
Changes from V1.1f:

Data Type changes:
Store_Banner from Char(20) to Varchar(20)
Phone_No from Char(10) to Varchar(15)
Address from Char(25) to Varchar(50)
City from Char(20) to Varchar(50)
County from Char(15) to Varchar(50)
State from Char(2) to Varchar(20)
Zip from Char(9) to Varchar(20)
Major_Type_Desc from Char(17) to Varchar(50)
Sub_Class_Desc from Char(15) to Varchar(50)
MSA_Desc from Char(20) to Varchar(50)
Mgt_Zone from Char(2) to Varchar(2)
Div_Desc from Char(21) to Varchar(50)
Mgt_Div_Desc from Char(21) to Varchar(50)
Region_Desc from Char(10) to Varchar(20)
2.4. Warehouse Master.

File name: warehouse_master_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Whs_Desc Kroger warehouse description. Varchar(50) RALPHS - PARAMOUNT
Notes:
None.
Changes from V1.1f:

Data Type changes:
Whs_Desc from Char(14) to Varchar(50)
9
Data Transfer Spec.
2.5. Store Product Master.

File name: store_product_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Base_UPC Base UPC code. Char(13) 0005200020200
Case UPC Case UPC code. Char(13) 0005200020200
Will be ‘DSD’ for items that are DSD
only.
Whs_No Warehouse from which this store Char(3) 022
orders this item.
Will be ‘999’ for items that are DSD
only.
Notes:
A given Base UPC may include more than one Consumer UPC.
Some DSD items may not be included in this file.
Changes from V1.1f:

Removed Base_UPC from key.
Data Type changes:
Whs_No from Char(2) to Char(3)
10
Data Transfer Spec.
3. Store Data.
3.1. Daily POS, Daily POS Restatement, and Daily POS History.
File name: daily_pos_{DATATRANSID}_{yyyyMMddhhmmss}.fil
File name: daily_pos_restate_{DATATRANSID}_{yyyyMMddhhmmss}.fil
File name: daily_pos_hist_{SEQ#}_{DATATRANSID}_{yyyyMMddhhmmss}.fil

POS_Date POS date. Date 2011-03-08
Date on which sales occurred.
Sales_Qty Sales quantity. Decimal 13.00
Denoted in Sales UOM. (15,2)
Sales_Qty_UOM Sales quantity unit of measure. Char(1) U = Units
W = Weighed
POS_Ave_Unit_Prc Average Unit Price paid. Decimal 5.42
(8,2)
Sales_Amt Net sales dollar amount. Decimal 70.46
(15,2)
Gross_Margin_Amt Gross Margin dollar total. Decimal 0.00
Will be set to 0.00 pending Kroger (15,2)
release approval.
Inv_Multiplier Inventory multiplier. Integer
Future use - NULL for now.
Estimated_Flag Estimated flag. Char(1) 1 = Estimated
Indicator that data was estimated. 0 = Actual
Restatement_Flag Restatement flag. Char(1) 1 = Restated data
Indicator that data was restated. 0 = Not restated
Notes:
Restatement file includes previous days that were restated by Kroger. The number of such days is governed by a Customer-
specific parameter which defaults to 28 days.
All quantities can have valid negative values.
In the history (back data) file name, {SEQ#} refers to a sequence number. This enables the data to be broken up into smaller
files, rather than a single, monolithic file that may exceed size constraints.
Changes from V1.1f:

Data Type changes:
Sales_Qty from Decimal(13,2) to Decimal(15,2)
11
Data Transfer Spec.
3.2. Expected Price.

File name: expected_price_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Price_Date Date on which these prices will be Date 2011-04-08
effective.
Loyalty_Unit_Price Unit Price with Loyalty Card. Decimal 1.25
(8,2)
Retail_Unit_Price Unit Price without Loyalty Card. Decimal 1.69
(8,2)
Notes:
None.
Changes from V1.1f:

Data Type changes:
12
Data Transfer Spec.
3.3. Sales Plan.

File name: sales_plans_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Eff_Date Date on which these promotion Date 2011-04-08
conditions will be effective.
Sales_Plan_Unit_Price Unit price in Sales Plan. Decimal 8.69
(8,2)
Unit_Price_UOM Unit price unit of measure. Char(1) U = Units
W = Weighed
Display_Indicator In-store display indicator. Char(1) Y = Yes
N = No
O = Optional
Display_Priority In-store display priority code. Integer 0
Ad_Type_Code_1 Ad Type code 1. Char(1) A = Advertised
R = Roller
Ad_Type_Code_2 Ad Type code 2. Char(1) A – Interior Page Feature
B – Internet/Digital
Feature
C- Interior Page Line
Item
P – Interior Page Coupon
N – Not on Ad
D – Front Page Feature
E – Front Page Coupon
F – Back Page Feature
G – Back Page Feature
H – Wrap Front Feature
I – Wrap Front Coupon
J – Wrap Interior Feature
K – Wrap Interior Coupon
L – Wrap Back Feature
M – Wrap Back Coupon
U – Display – Not
Featured
R – Not on Ad
S – Themed Insert Back
Ad_Version Ad version number. Integer 402

Ad_Description Ad description. Varchar(50) Main
Ad_Position Ad position. Integer
Ad_Priority Ad priority level. Integer 99
Ad_Sequence Ad sequence number. Integer 7001
Program_ID Program number. Long Int 18835726
Ad_Section_Desc Ad section description. Varchar(50) Supplemental Rollers
Media_Type_Code Media type code. Varchar(20)
DV_Ad_Type Market6 Ad Type classification. Integer 0 = No Ad
1 = Line item or equiv.
2 = Moderate
3 = Major
Notes:
Some ad attributes may be blank for some promotions.
Changes from V1.1f:

Data Type changes:
Sales_Plan_Unit_Price from Decimal(9,2) to Decimal(8,2)
Ad_Description from Char(65) to Varchar(50)
13
Data Transfer Spec.
Ad_Section_Desc from Char(45) to Varchar(50)

Media_Type_Code from Char(5) to Varchar(20)
Changes from V1.2i

Ad_Type_Code_2 from A=Interior Page Feature A – Interior Page Feature
B=Secondary Prominence B – Internet/Digital Feature
C=Interior Page Line Item C - Interior Page Line Item
D=Front Page Feature D – Front Page Feature
E – Front Page Coupon
F=Deli/Bakery Back Page
G – Back Page Feature
H=Wrap Front Feature H – Wrap Front Feature
I – Wrap Front Coupon
J – Wrap Interior Feature
K – Wrap Interior Coupon
L=Wrap Back Feature L – Wrap Back Feature
M – Wrap Back Coupon
N=Not on Ad N – Not on Ad
R – Not on Ad
S – Themed Insert Back
U – Display – Not Featured
14
Data Transfer Spec.
3.4. Store Balance on Hand, Shelf.

File name: store_shelf_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Inventory_Date Date of inventory measurement. Date 2011-04-08
Inventory_Time Time of Inventory measurement. Time 02:07:00
Inventory_Qty Inventory quantity. Integer 13
Denoted in Qty_UOM.
Qty_UOM Inventory quantity unit of measure. Char(1) U = Units
W = Weighed
Order_Flag Kroger CAO order authorization flag. Char(1) Y = Yes
N = No
R = Replenishment Only
POS_Host_Status POS host status flag. Char(1) A = Active
D = Discontinued
I = Inactive
X = To Be Deleted
Z = Active
Consumer_Case_Pack Consumer case pack qty. Integer
Get from Case Master.
Shelf_Capacity Shelf capacity qty. Integer 24
Shelf_Min Shelf minimum qty for order Integer 12
calculations.
Aisle_Location Aisle location code. Char(2) FR = Front
MI = Middle
BA = Back
Aisle Aisle designation. Varchar(10) 5
Shelf_No Shelf number. Integer 6
Position_No Shelf position number. Integer 25
Facings Facings count. Integer 2
Aisle_Orientation Aisle orientation code. Char(1) L = Left
R = Right
Notes:
This file will include the latest data that 84.51° receives from Kroger, which may not include all stores on a given day. This
happens because Kroger is not always able to acquire the data from all stores in time for the daily file transmission. It is possible
that some data will therefore be missing from each daily file.
Changes from V1.1f:

Data Type changes:
Aisle from Char(3) to Varchar(10)
Changes for version 1.2f:

A separate file will not be sent for missed store inventory data. However, it may possibly contain up to two days of store shelf
data if provided by Kroger.
15
Data Transfer Spec.
3.5. Store Deliveries.

File name: store_deliveries_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Delivery_Date Date delivered to store. Date 2011-04-08
Deliveries are worked to impact end Current date only vs. my
of day store inventory on this date. replenishment is all
Ship_Date Date shipped to store. Date 2011-04-08
Delivery_Qty Quantity delivered. Integer 1
Denoted in Qty_UOM.
Order_Qty Quantity ordered. Integer 1
Denoted in Qty_UOM.
Qty_UOM Order qty unit of measure. Char(1) C = Case
U = Units
Notes:
Currently only includes deliveries from Warehouses. DSD deliveries will be added in future.
This data is transactional in nature; therefore ‘key’ fields are not appropriate.
Changes from V1.1f:

Removed all key field indicators.
Data Type changes:
Qty_UOM from Char(4) to Char(1)
3.6. Derived Out of Stock Events (formerly Shelf Scan Audit)

File name: daily_audit_{DATATRANSID}_{yyyyMMddhhmmss}.fil
File name: daily_audit_hist_{SEQ#}_{DATATRANSID}_{yyyyMMddhhmmss}.fil
Retailer_ID Retailer ID Varchar (20) KROGER
Div_No Kroger Division Number Char (3) 021
Store_No Store Number Char (5) 00936
Base_UPC Kroger base upc code Char (13) 0007000008310
OBS_Date Occurrence date. Date 2013-04-08
Date the derived out of stock event
OBS_Time Occurrence time. Time 13:00:00
(Not currently available)
Future Measure To be held for possible future use Char (10) blank
Notes:
This feed has been repurposed from publishing “shelf scan audit events” as Kroger has discontinued wholesale collection of this
information across all of their divisions. This feed now contains the Kroger approved Market6 derived out of stock events.
This feed includes only items for which the supplier is the brand owner. Competitive items are not available in the file.
16
Data Transfer Spec.
3.7. Weekly Competitive POS Sales File

File name: comp_weekly_pos_%DataTranID%_%DataTranFileTimestamp%.*
comp_weekly_pos_restate_%DataTranID%_%DataTranFileTimestamp%.*

WE_POS_Date Fiscal Week ending date - Saturday. Date 2011-03-08
Sales_Unit_Qty Scan unit quantity. Integer 13
Denoted in units.
Sales_Unit_Amt Net sales dollar amount sold in units. Decimal 70.46
(15,2)
Calc: Sales Unit_Amt / Sales_Unit_Qty (8,2)
Sales_Lbs_Qty Scan pounds amount. Decimal 13.00
Denoted in pounds. (15,2)
Sales_Lbs_Amt Net sales dollar amount sold in pounds. Decimal 70.46
(15,2)
POS_Ave_Lbs_Prc Average Lbs Price paid. Decimal 5.42
Calc: Sales Lbs Amt / Sales_Lbs_Qty (8,2)
(SPARKLING&STILL)
DRNK/MNRL WT
Notes:
Commodity competitive sales file to be made available weekly after receiving Kroger Sunday POS file data on Monday. This
will allow us to recover the POS sales files which were unavailable during normal Sunday processing. Client will receive data
as outlined by current commodity level permissions.
A weekly restatement file should also be available similar to the daily POS file, but for anything missing from the previous week
at the time the weekly file is generated.
17
Data Transfer Spec.
3.8. Ad Weekly Competitive POS Sales File

File name: comp_ad_weekly_pos_%DataTranID%_%DataTranFileTimestamp%.*
comp_ad_weekly_pos_restate_%DataTranID%_%DataTranFileTimestamp%.*

WE_POS_AD_Date Ad Week ending date. Date 2011-03-08
Sales_Unit_Qty Scan unit quantity. Integer 13
Denoted in units.
Sales_Unit_Amt Net sales dollar amount sold in units. Decimal 70.46
(15,2)
Calc: Sales Unit_Amt / Sales_Unit_Qty (8,2)
Sales_Lbs_Qty Scan pounds amount. Decimal 13.00
Denoted in pounds. (15,2)
Sales_Lbs_Amt Net sales dollar amount sold in pounds. Decimal 70.46
(15,2)
POS_Ave_Lbs_Prc Average Lbs Price paid. Decimal 5.42
Calc: Sales Lbs Amt / Sales_Lbs_Qty (8,2)
(SPARKLING&STILL)
DRNK/MNRL WT
Notes:
Commodity competitive sales file to be made available weekly after receiving Kroger Sunday POS file data on Monday. This
will allow us to recover the POS sales files which were unavailable during normal Sunday processing. Client will receive data
as outlined by current commodity level permissions.
A weekly restatement file should also be available similar to the daily POS file, but for anything missing from the previous week
at the time the weekly file is generated.
18
Data Transfer Spec.
3.9. Daily Store Authorization and Planogram Association

File name: sath_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Retailer_ID Retailer ID Varchar (20) KROGER
Div_No Kroger Division Number Char (3) 021
Store_No Store Number Char (5) 00936
Base_UPC Kroger base upc code Char (13) 0007000008310
Authorization_Code Kroger assigned store Char (1) A=Authorized
U=Unauthorized
authorization code O=Authorized(override)
X=Unauthorized (override)
Authorization_Flag Derived authorization Char (1) A=1
O=1
Flag Else=0
POG_Name Planogram Name as Char (50) D011_L00000_D01_C022_V300_F016_M
X
defined by:
DVIS_POG..POG_HEADE
R..POG_NAME
POG_Revision_Date Date the planogram was Timestamp 2015-01-02 17:09:00
revised as defined by:
DVIS_POG..POG_HEADE
R..POG_CHG_DTM
Delivery Cadence: Daily
Filters: Own products only.

Notes:
• Standard update time for SATH is ~7:30 a.m.
• If we do not get a record in the data feed from Kroger for an item that we previously received, said item will not be
included in the current feed since we "close" the entry for this store-item.
• The store authorization data transfer should nullify the authorization measure for items that are not part of the latest
store authorization data feed. This is evidenced by a "dropped date" in the authorization reporting table.
• Planogram Name: If multiple planograms exist for a store item then each planogram shall be listed for a store item
(Cartesian / duplicate the store item). If no planogram exists for a store item then the resultant value shall be null.
• Planogram Revision Date: last date planogram was revised.
4. Warehouse Data.
4.1. Warehouse Inventories.

File name: whs_boh_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Inventory_Date_Time Date and time of inventory Date/Time 2011-04-08 01:58
measurement.
Inventory_Qty Warehouse Inventory. Integer 316
Denoted in Qty_UOM.
19
Data Transfer Spec.

Qty_UOM Inventory quantity unit of measure. Char(1) C = Cases
U = Units
Open_Store_Order_Qty Open store order qty. Integer 0
Denoted in Qty_UOM.
Qty_On_Order Qty on order with Vendor. Integer 0 only in MyReplenishment
Denoted in Qty_UOM.
Inner_Pack_Qty Inner pack quantity. Integer 1
Store_Pack Store pack. (Units) Integer 6
Notes:
There may be more than one inventory measurement per day in some warehouses. These are independent observations,
distinguished by the Inventory_Date_Time field, and should not be aggregated.
Changes from V1.1f:

Removed KLN from key.
Data Type changes:
Inner_Pack_Qty and Store_Pack are now included in transfer
20
Data Transfer Spec.
4.2. Warehouse Orders.

File name: whs_orders_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Purchase_Order_No Purchase order number. Varchar(20) 49321
Order_Qty Order quantity. Integer 90
Denoted in Qty_UOM.
Qty_UOM Order qty unit of measure. Char(1) C = Cases
U = Units
Order_Due_Date Date order is due at the warehouse. Date 2011-04-07
Ref_Date Reference date. Date 2011-04-09
Kroger data file creation date.
KLN Kroger Line Number Varchar(20) 23158
Cost_Per_Qty Cost per quantity UOM. Decimal 24.00
(15,2)
Inner_Pack_Qty Inner pack quantity. Integer
Store_Pack Store pack. (Units) Integer
Discontinue_Date Date after which this warehouse will Date 9999-12-31
no longer order this product.
Included as provided by Kroger with
NULL values replaced by ‘9999-12-31’.
Preferred source is Case Master.
Notes:
An order is overdue if Ref_Date > Order_Due_Date.
Changes from V1.1f:

Data Type changes:
Purchase_Order_No from Char(10) to Varchar(20)
21
Data Transfer Spec.
4.3. Warehouse Substitutions.

File name: whs_substitutions_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Original case UPC.
Begin_Date Begin date for substitution rule. Date 2010-12-27
End_Date End date for substitution rule. Date 2011-04-10 or today, if <
today omit
Replacement_Case_UPC Case that will replace (ship instead Char(13) 1007910050813
of) the Case_UPC.
Substitute case UPC.
Substitution_Method Substitution method rule. Integer 0=Always substitute
1=Ship orig til depleted
2=Ship sub until depleted
3=Shelbyville line item
4=Zero out (kill)
Substitution_Multiple Reserved for future use. Integer 1
Number of substitution cases per
original case.
Division receiving shipment.
‘000’ means all divisions.
Notes:
A value of ‘000’ in Div_No indicates that the rule applies to all Divisions when serviced by the applicable Warehouse.
Changes from V1.1f:

Data Type changes:
Replacement_Case_UPC from Char(14) to Char(13)
Substitution_Method from Unspecified to Integer
22
Data Transfer Spec.
5. DemandView Measures.
5.1. DemandView Store Measures.

File name: kdp_store_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Whs_No Warehouse from which this store Char(3) 181
orders this item.
DV_Date DemandView date. Date 2011-04-08
Sales_Qty Sales quantity. Decimal 4
Denoted in Qty_UOM. (15,2)
Sales_Amt Net sales Dollar amount. Decimal 3.16
(15,2)
Qty_UOM Sales quantity unit of measure. Char(1) E = Each
U = Units
W = Weighed
Base_Fcast Base unit forecast. (Calendar impact Decimal 3.5384
removed.) (15,4)
Denoted in Qty_UOM.
Turn_Fcast Turn unit forecast of sales absent Decimal 3.7511
promotion. (15,4)
Denoted in Qty_UOM.
Fcast Unit sales forecast. Decimal 4.1471
Reg_Unit_Price Regular Price as determined by Decimal 1.00
DemandView algorithm. (8,2)
Best_Offer_Unit_Price Best price offered to consumers. Decimal .79
(8,2)
Date_First_Seen Date that the item was first seen in Date 2011-01-31
DemandView.
Last_Sold_Date Date that the item was last sold. Date 2011-04-08
Last_Delivery_Date Date of last store delivery receipt. Date 2011-04-08
Plan_Unit_Price Price that was expected based on Decimal .79
Kroger Plans. (8,2)
Planned_Display_Fl Planned display flag. Char(1) 1 = Display planned
0 = No display planned
DV_Ad_Type Planned ad type. Char(1) 3 = Major ad
2 = Small ad
1 = Line ad
0 = No ad
Inventory_Value_Alert Inventory value alert flag. Char(1) 0 = Default
OOS_Alert_Fl Out of stock alert flag. Char(1) 0 = Default
Short_Sales_Alert_Fl Sales less than expected alert flag. Char(1) 0 = Default
Promo_Exec_Alert_Fl Promotion not executed alert flag. Char(1) 0 = Default
Excess_Inv_Alert_Fl Excess inventory alert flag. Char(1) 0 = Default
Low_Inv_Promo_Alert_F Low inventory promotion item alert Char(1) 0 = Default
l flag.
Unexp_Prc_Decr_Alert_ Unexpected price decrease alert flag. Char(1) 0 = Default
Fl
Order_Day_Fl Is order day flag. Char(1) 0 = Default
Order_Qty Order quantity. Integer 72
Denoted in Qty_UOM.
Deliv_Qty Delivery quantity. Integer 12
Denoted in Qty_UOM.
Includes distributions.
Distr_Qty Distribution quantity. Integer 0
Denoted in Qty_UOM.
Est_BOD_BOH Estimated beginning of day inventory Integer 15
balance on hand.
Denoted in Qty_UOM.
23
Data Transfer Spec.

Est_EOD_BOH Estimated end of day inventory Integer 23
balance on hand.
Denoted in Qty_UOM.
Est_DOS Estimated days of supply in store. Decimal 5.5
(6,2)
Target_EOD_BOH Targeted end of day inventory balance Decimal 30.4
on hand. (11,2)
Denoted in Qty_UOM.
Turn_Fcast_Std_Err Turn forecast standard error. Decimal 3.51
(11,4)
Promo_Fcast_Std_Err Promotion forecast standard error. Decimal .77
(11,4)
DV_Store_Auth DemandView store authorization. Char(1) 1 = Active
0 = Not active
Short_Sales_Alert_Val Sales less than expected alert value. Decimal 0.00
(9,2)
Promo_Exec_Alert_Val Promotion not executed alert value. Decimal 0.00
(9,2)
Excess_Inv_Alert_Val Excess inventory alert value. Decimal 0.00
(9,2)
Low_Inv_Promo_Alert_V Low inventory promotion item alert Decimal 2.06
al value. (9,2)
Unexp_Prc_Decr_Alert_ Unexpected price decrease alert Decimal 0.00
Val value. (9,2)
OOS_Lost_Units OOS lost sales in units. Decimal 0
OOS_Lost_Amt OOS lost sales amount. Decimal 0.00
Denoted in Dollars (9,2)
Promo_Fl Promotion flag. Char(1) 1 = On promotion
0 = Not on promotion
Notes:
None.
Changes from V1.1f:

Added DV_Ad_Type field. (Blue highlight, above.)
Data Type changes:
Reg_Unit_Price from Decimal(7,2) to Decimal(8,2)
Best_Offer_Unit_Price from Decimal(7,2) to Decimal(8,2)
Plan_Unit_Price from Decimal(7,2) to Decimal(8,2)
Turn_Fcast_Std_Err from Decimal(11,2) to Decimal(11,4)
Promo_Fcast_Std_Err from Decimal(11,2) to Decimal(11,4)
Alerts set to “0” as a default. Alerts are no longer generated.
24
Data Transfer Spec.
5.2. DemandView Store Forecasts.

File name: kdp_store_forecast_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Fcast_Create_Date Date forecast was created. Date 2011-04-08
Fcast_Date Date forecasted for. Date 2011-04-23
Deliv_Day_Fl Is delivery day flag. Char(1) 1 = Delivery day
0 = Not delivery day
Order_Day_Fl Is order day flag. Char(1) 1 = Order day
0 = Not order day
Fcast_BOD_BOH Forecasted beginning of day balance Integer 38
on hand.
Fcast_EOD_BOH Forecasted end of day balance on Integer 30
hand.
Base_Fcast Base unit forecast. (Calendar impact Decimal 2.662
removed.) (15,4)
Denoted in Qty_UOM.
Turn_Fcast Turn unit forecast of sales absent Decimal 4.202
promotion. (15,4)
Denoted in Qty_UOM.
Fcast Unit sales forecast. Decimal 7.795
Fcast_Unit_Price Expected unit price. Decimal 1.00
Will be set to 0.00 after 21 days. (8,2)
Fcast_Display_Fl Expected display flag. Char(1) 1 = Display expected
0 = No display expected
Fcast_Order_Qty Forecasted store order quantity. Integer 0
Denoted in Qty_UOM.
Reg_Unit_Price Regular Price as determined by Decimal 1.00
DemandView algorithm. (8,2)
DV_Ad_Type Expected ad type. Char(1) 3 = Major ad
2 = Small ad
1 = Line ad
0 = No ad
Fcast_Deliv_Qty Forecasted delivery quantity. Integer 0
Denoted in Qty_UOM.
On_Order_Qty Quantity currently on order. Integer 0
Denoted in Qty_UOM.
Promo_Fl Expected promotion flag. Char(1) 1 = Promotion expected
0 = Not on promotion
Exp_OOS_Fl Anticipated Out-of-Stock flag. Char(1) 9
Future values:
1 = Out-of-Stock expected without
intervention
0 = Otherwise
Exp_Excess_Inv_Fl Anticipated overstock flag. Char(1) 9
Future values:
1 = Overstock expected without
intervention
0 = Otherwise
Exp_OOS_Lost_Amt Anticipated Out of Stock value. Decimal 0
(9,2)
Exp_Excess_Inv_Val Anticipated overstock value. Decimal 0 Part of alerts
(9,2)
Notes:
Measures in light blue background will not be available in release 1.2, but will be included later, along with other measures
based on customer feedback.
The flag measures will have a value of 9, until they are included.
The unit measures with have a value of 0, until they are included.
25
Data Transfer Spec.
Changes from V1.1f:

Data Type changes:
Base_Fcast from Decimal(11,3) to Decimal(15,4)
Turn_Fcast from Decimal(11,3) to Decimal(15,4)
Fcast from Decimal(11,3) to Decimal(15,4)
Fcast_Unit_Price from Decimal(6,2) to Decimal(8,2)
Reg_Unit_Price from Decimal(6,2) to Decimal(8,2)
Exp_OOS_Lost_Amt from Integer to Decimal(9,2)
Exp_Excess_Inv_Val from Integer to Decimal(9,2)
26
Data Transfer Spec.
5.3. DemandView Warehouse Measures.

File name: kdp_whs_{DATATRANSID}_{yyyyMMddhhmmss}.fil

DV_Date DemandView date. Date 2011-04-08
Inventory_Qty Warehouse Inventory. Integer 2132
Denoted in Qty_UOM.
Qty_UOM Inventory quantity unit of measure. Char(1) C = Cases
U = Units
Fcast_DOS Estimated Days of Supply in Decimal 305.98
Warehouse. (6,2)
Fcast_Store_Order_Qty 31-Day store order quantity forecast. Integer 216
Denoted in Qty_UOM.
Notes:
None.
Changes from V1.1f:

Data Type changes:
5.4. DemandView Warehouse Forecasts.

File name: kdp_whs_forecast_{DATATRANSID}_{yyyyMMddhhmmss}.fil

Fcast_Create_Date Date forecast was created. Date 2011-04-08
Fcast_Date Date forecasted for. Date 2011-05-02
Order_Case_Pack Common case pack for store orders. Integer 12
Fcast_Store_Order_Qty Forecasted store orders quantity. Integer 2
Fcast_Store_Demand_Qt Forecasted store demand quantity. Integer 2
y
Order_Qty_UOM Forecasted store orders quantity UOM. Char(1) C = Cases
U = Units
Demand_Qty_UOM Forecasted store demand quantity UOM. Char(1) C = Cases
U = Units
Notes:
None.
Changes from V1.1f:

Data Type changes:
27
Data Transfer Spec.
6. Control Data.
6.1. Manifest.
File name: manifest_{DATATRANSID}_{yyyyMMddhhmmss}.fil

DataTransID Data transfer set ID. Integer 21205
File_Name File name. Varchar(65) store_master_21205_201104
080000.fil
Create_Date_Time File creation date and time. Date/Time 2011-04-16 20:06:07
Records Record count in file. Integer 2762
M6_Customer_ID Market6 customer ID. Integer 10015
Included for diagnostic and tracking
purposes.
Upd_Date_Time Record update date and time. Date/Time 2011-04-16 20:06:07
Notes:
None.
Changes from V1.1f:

Data Type changes:
Create_Date_Time from Date to Date/Time
6.2. Zip Container.

File name: {DATATRANSID}.zip
All other files will be delivered in a single, container .zip file named as above.
This file name can be customized in limited fashion to include custom text as follows:
{DATATRANSID}.{Custom Text}.zip
28

Data Transfer Spec

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Transfer Spec

Uploaded by

Copyright:

Available Formats

Customer Data Transfer

V1.2g 11/20/2014 Stacy Simonds Modified back data availability.

DemandView™ is a trademark of Market6, Inc.

1.1. Item Inclusion:

1.2. Back Data:

84.51° can provide 12 months of back history.

1.3. Referential Integrity:

1.4. Changes From V1.1:

1.5. Subscription Level

Frequency of Bronze & Silver Gold & Platinum Platinum subscribers

1.6. Summary of Files.

Table Freq Description File Name

Table Freq Description File Name

1.7. File Formatting.

1.9. Data Transmission.

2.1. Case Master.

Measure Description Data Type Example

Changes from V1.1f:

Changes for version 1.2f

2.2. Item Master.

Measure Description Data Type Example

Changes from V1.1f:

2.3. Store Master.

Measure Description Data Type Example

Measure Description Data Type Example

Changes from V1.1f:

2.4. Warehouse Master.

Measure Description Data Type Example

Changes from V1.1f:

2.5. Store Product Master.

Measure Description Data Type Example

Changes from V1.1f:

Measure Description Data Type Example

All quantities can have valid negative values.

Changes from V1.1f:

3.2. Expected Price.

Measure Description Data Type Example

Changes from V1.1f:

3.3. Sales Plan.

Measure Description Data Type Example

Ad_Version Ad version number. Integer 402

Changes from V1.1f:

Ad_Section_Desc from Char(45) to Varchar(50)

Changes from V1.2i

3.4. Store Balance on Hand, Shelf.

Measure Description Data Type Example

Changes from V1.1f:

Changes for version 1.2f:

3.5. Store Deliveries.

Measure Description Data Type Example

Changes from V1.1f:

3.6. Derived Out of Stock Events (formerly Shelf Scan Audit)

3.7. Weekly Competitive POS Sales File

Measure Description Data Type Example

3.8. Ad Weekly Competitive POS Sales File

Measure Description Data Type Example

3.9. Daily Store Authorization and Planogram Association

Measure Description Data Type Example

Delivery Cadence: Daily

Filters: Own products only.

4.1. Warehouse Inventories.

Measure Description Data Type Example

Measure Description Data Type Example

Changes from V1.1f: