Electronic 531 and 560 Overview for THD Suppliers

1
Electronic 531 and 560 Overview for THD Suppliers

• 2007 Supplier Partnership Meetings
• Data Management Workshop
• THD, Merchandising Operations

2
Overview Objectives
You Can Do It. We Can Help.

• Objectives
• What is an E531 and an E560
• Preparing an E531 or E560 for submittal
• Basic Business rules for SKU maintenance
• The difference between SKU maintenance at the
  Market-level, versus Vendor-level
• SKU status explanations lifecycle
• Vendor-level status changes (TF, DC, Host)
• SKU Store Exceptions
• How to access this document via THDs Supplier
  website

Objectives
3
What is an E531 and an E560?
You Can Do It. We Can Help.

• What is an E531 and an E560?
• The E531 and E560 reports are electronic versions
  of hard-copy reports originating from THDs data
  system. They are widely-used and understood by
  Merchants, Merchant Assistants and most THD
  Suppliers. They are used (predominantly) to
  review SKU data and pricing information.
• The E531 shows Supplier-specific data about a SKU
  including
• BYO Market
• SKU Status
• SKU attribute information, including part ,
  buy pack, weight, cube
• Cost Retail
• The E560 shows SKU store exception data and SKU
  status
• SKU Store exception data- store locations where
  the SKU is available for replenishment
• These reports can be requested by contacting the
  appropriate category Merchant or Merchant
  Assistant

Report Definitions and Use
4
Electronic, or E 531
You Can Do It. We Can Help.
E531
Supplier specific data
The E531 shows supplier-specific SKU data
5
Electronic, or E 560
You Can Do It. We Can Help.

• E560

SKU Store Exception data
The E560 shows SKU store exception (availability)
data
6
Submitting an E531 or E560 for Maintenance
You Can Do It. We Can Help.

• Preparing the E531 or E560 for submittal
• All supplier-specific data columns (i.e. E531)
  are followed by a blank column. Requestors
  should enter new data (to update) in the blank
  column (i.e. changing part nbr, status, buy pack,
  weight, freight class).
• Maintenance should NEVER be indicated in columns
  with existing data.
• Changes reflected in columns with existing
  data WILL NOT BE PROCESSED.
• Ex To indicate a part number change, use the
  New Part Number column on the 531 do not
  indicate the change in the existing, Part
  Number column.
• All blank or non-applicable columns should be
  hidden - DO NOT DELETE COLUMNS.
• Important Note Deleting columns impacts THDs
  ability to electronically proof the data
• after data-entry. Requests/reports with deleted
  columns may be returned to the requestor
• to be corrected, prior to data entry.
• All rows requiring no maintenance MUST BE
  DELETED, prior to submittal.
• Important Note Rows that are left on the
  report that dont require maintenance create
  confusion as to which rows need to be maintained,
  and may delay execution, while clarification is
  obtained.

Submission standards for accurate, timely
processing
7
Basic Business Rules for SKU Maintenance
You Can Do It. We Can Help.

• Business rules to apply when requesting SKU
  maintenance
• The difference between SKU status changes at the
  Market-level versus the Vendor-level
• SKU/Market Level Changes - changes at this level
  affect all vendors attached
• to the SKU, including the following changes
• Clearance
• SKU/Store Exceptions
• In Season and Out of Season Dates
• Ex At the Mkt-level, one SKU may be attached to
  multiple vendors. A SKU may only be clearanced
  at the SKU/Market level, NOT at the individual,
  vendor level.
• SKU Vendor/Market Changes - changes at this level
  only affect your specific vendor attributes
  (Supplier-specific- - seen on the 531)
• Status
• SKU attributes (i.e. Part, Buy Pack, Cost,
  Weight,etc)
• Note Request a 531 at the vendor level to see
  SKU/vendor information specific to your vendor
  only.

Business rules for maintenance requests
8
SKU Status Life-Cycle
Business rules SKU Status Explanations
9
(TF) Vendor Status Changes
You Can Do It. We Can Help.

• Examples of Status Change Requests
• Changing status when a market uses a Transit
  Facility (TF)

Supplier TF status should ALWAYS match
Look for TF in the Vendor Name column
Example of a TF Vendor status change using the
E531
10
(DC) Vendor Status Changes
You Can Do It. We Can Help.

• Changing Status when a Market uses a Distribution
  Center (DC)

Supplier is Inactive at store market level
(stores dont order directly from Supplier) DC
is active at store and DC market level (stores
order product from a DC)
DCs have their own market number
Example of a DC Vendor status change using the
E531
11
(Host) Vendor Status Changes
You Can Do It. We Can Help.

• Changing Status when item is on allocation (Host
  Active) in a Market

Supplier is Inactive at the market-level Host
Vendor number is Active at market level
Host Vendor number is 700000xx (xx dept number)
Merchants own ordering and allocation for
Host Active SKUs stores are not able to order
Host Active SKUs. These SKUs are (typically)
set-up for auto-replenishment, from the Host
(corporate-level).
Business Rules for SKU Status Requests
12
SKU Store Exceptions
You Can Do It. We Can Help.

• Changing SKU Store Exception Data - ADDING Stores
  to exception

Adding stores in this column will add the SKU to
these store(s) assortment (make them available
for replenishment)
IMPORTANT NOTE COMPARE the store count in the
Total Stores ( in the market ) column to that
in the Total On Exception column. You CANNOT
put the SKU on exception for all stores in the
market by listing/ adding all stores to the
Store Exception and/or Allow - Add Stores
column(s). This is an invalid request. See
slide 14 for instructions on how to put the SKU
on exception for ALL stores in a market.
Making a SKU available (on exception) for
replenishment in a store(s)
13
SKU Store Exceptions
You Can Do It. We Can Help.

• Changing SKU Store Exception Data - REMOVING
  stores from exception
• (taking the SKU out of the stores
  assortment/making it unavailable for
  replenishment)

Adding stores in this column will remove the SKU
from these stores assortment
Making a SKU unavailable for replenishment in a
store/s
14
SKU Store Exceptions
You Can Do It. We Can Help.

• Changing SKU Store Exception Data - Removing ALL
  Stores from exception
• Removing ALL STORES from exception
  automatically puts the SKU ON exception at the
  market-level, making the SKU available (in the
  assortment), for ALL stores in that market.

Important Note 1) REVIEW current SKU/Market
status. To make the SKU available to ALL stores
in the market, the SKU must be A (active) at
the market-level (in the SKU Status column).
2) INDICATE Remove All Stores/Yes from
exception. This will remove exceptions at the
store-level, automatically putting the SKU on
exception (making it available to all stores) at
the market-level.
Making a SKU available for ALL stores in a market
15
Supplier Website
You Can Do It. We Can Help.

• To view this document on-line, go to The Home
  Depots Supplier website
• https//suppliercenter.homedepot.
  com
• Select Supplier Services, Merchandising and
  click on the link called SKU Maintenance
  Overview

Accessing this document on-line