POST RELEASE DATA CLEANUP SOP [ Last Updated: 06/21/2023 ]

It is the responsibility of the CSS Team to ensure that the Data on their divisional jobs is as clean as possible each week
before it is processed by the QA Team. In order to ensure that your data is as clean as possible, please follow these
steps once each division is released each week. This process should be completed by 12:30 PM the day after the
division Releases.

Before beginning your cleanup, please take a moment to look through the PDFs for your division and note any special
pricing situations that might be present. Some things to look for include, FREE offers, SAVE_BUY_wRETAIL, SAVINGS
SPEND_wRETAIL, and offers that do not show any sort of actual pricing information (KRGR_CREATIVE). If you know
these types of offers are on your division, you will know to look for them as you proceed through your cleanup process.

1. Check MMNs
Before starting anything, you will want to compare Marketing Message Names (MMNs) in Aproove with those
in LAGO to be certain that all MMNs received in Aproove were placed correctly into LAGO.
a. Open Aproove

b. In the Search bar at the top of the screen, enter

the 4-digit numerical week of the job you are
working on and hit enter.

c. Scroll down the list of results and select the job you are working on.

d. On the next screen, go to the menu bar on the Upper

Right of the screen and select Reporting -> Tag Form
Export – Excel

e. You should get a Pop Up Window like the one shown on the
right. Use the Drop Down menu to select ALL and then click
the Download button at the bottom.
f. Once the Download is complete, you should see
your downloaded report in the Lower Left corner of
your browser window. Click on this to open the
report in Excel.

g. When the Report opens, Go to DATA in the Menu bar and select the Filter button to apply a filter to
all columns of the report.

h. Move to Column I and use the Down Arrow in the Header Row of that
column to open the Filter Menu for that column.

i. Uncheck everything except for Marketing Message Name

j. You should now be left showing only rows that say “Marketing
Message Name” in that column.

k. Looking at Column J (Form Field Comment) you should now see a list of MMN numbers.
Count the number of MMNs that are listed and make note of the number.
 l. Now open you job in LAGO and navigate to Elements -> All

m. In the Right Upper Canvas, scroll until you find the column for MMN. Click on the header bar to
sort by this column.
a. You should now be able to count the number of MMNs in
LAGO.
b. Compare the MMNs in Aproove to the MMNs present in
LAGO.
i. If the numbers are the same, then you are good
ii. If there are more MMNs in LAGO than in Aproove, you
are good
iii. If there are more MMNs showing in Aproove than in LAGO, please go back to
Aproove, find the MMNs that are not in LAGO and get into the LAGO on their correct
Offers.
c. Once any MMN issues are resolved, you can go back to the main LAGO Explorer menu and
begin the full Post Release Cleanup process.

2. Clear Unplaced Components

Open LAGO Explorer and select the Job you wish
to clean in the Project List.

Make sure all project variants are selected in the

Right Lower Canvas.
 Click on the Globe & Broom tool
in the upper right tool bar of the Upper Canvas.

When the pop-up window appears,

make sure you have these settings.

Delete Global/Local Components –

should be set to Global and local

Delete by – should be set to

Component type and match the settings at the left.

Then click [OK]

Once you click [OK] you will get 1 of 2 possible results.

No Components Found
This means there are no unplaced components in the job.
That’s great. Select [NO] and go to the next step.

XX Components Found
The tool has found a number of unplaced components still
in the job. Click [YES] to remove them from the job and
move on to the next step.
3. Confirm EVENT ID
Still on the Project List, look in the right Upper Canvas and find the Kroger Event ID.

Confirm that this matches the Event ID in NGPP. If it does not, please update it so that it matches.

4. Check for Errors in the Version Code Strings

Double Click to open the job in LAGO Explorer.
On the Left side, navigate to Documents > Standard > All
and then expand the ALL folder to show the individual pages in
your job.

Expand and page that show [?]

so that you can see the versions

Look at the Version Code String for variant of each page

and check for the following:
a. make sure all version codes are separated by a comma
b. make sure there are no additional / extra commas,
either between codes or at the end
c. make sure there are no extra spaces
d. if you have version codes that include the number zero (0)
or the letter (O), make sure the correct character is used
in each code

5. Check for Bogus Pages

At the top of the Left Canvas, just above the Articles folder,
there is a drop-down menu. By default, it should be set to “All”

Drop this down and select “Base” – this will isolate all of the
pages in the list to only show the Base variant.
 Expand your pages under Documents > Standard > All
so that you can see the Elements within each page.

Scroll down to confirm that there are elements within each of

your pages.

If you find a page that only contains a Page Element and a

_CreativeElement, verify that the page is supposed to be
Creative only.

Any pages that do not have any Elements, should be removed

at this time because they are not real pages in the ad.

When you are done with this check, please go back to the drop-
down and set it back to “All”

6. Check Elements for Errors

6A. Check For Elements on Pages that no longer exist.

In the Left Canvas, navigate to Elements > All
but DO NOT expand this folder in the Left Canvas.

Also adjust your divider so that you can just see the Page Numbers
of the pages in your job.

In the Right Upper Canvas, adjust your layout so that all the following columns
are visible: WP From, Project Variant, Name, Underline Copy,
State, Element Layout, With Card, Info, and Disclaimer

Sort by WP From
Starting at the top with Page 1, scroll down the list, looking for any Page
numbers that do not correspond to a Page number in your Left Canvas.

In the example, the highlighted Page 13 elements no longer have a

corresponding Page 13 in the job on the Left. These are Orphan Elements and
should have been removed when the page was removed. When you find Orphan Elements, please delete them and
move to Page 0

This also applies to the Page 14 that can be seen in the example below the highlighted selection.

6B. Check for Elements that have been Disabled but NOT Moved to Page 0

Sort by State
Scroll down the list until you find the Elements listed as Deleted
Confirm that all of the Deleted Elements are on Page 0
If they are not, please move them to Page 0.
6C. Check for Elements that have Duplicate or Missing Articles

Go to the top of the Element list and select the first Element.
In the bottom canvas, select the Assigned Articles tab.
Make sure that the first Element in the list has 1 Article showing in the Assigned Articles tab.
- If there is NO ARTICLE – an article needs to be created for the element*
- If there are TWO OR MORE ARTICLES – verify that these are legitimate articles. Most Elements should
have ONLY ONE ARTICLE. In the case that an Element needs more than 1 article, those articles should
be for completely separate page variants

The example below shows an element with two articles. Both articles are assigned to all variants of the page.
This is incorrect – one of these is erroneous and needs to be removed.

* All elements should have an article EXCEPT for the following three
- Page Elements
- Elements that begin with an underscore (_) – _Creative Element, _ABEV Creative, etc.
- Elements with _KRGR_CREATIVE as Element Layout

6D. Check for Elements with Leading Spaces or Spelling Errors

Sort by Name in the Right Upper Canvas and Look through the Name and Underline Copy fields of each
element looking for Extra Spaces at the beginning of the field copy or for errors in spelling – this can also
include word duplication.

Even if these were introduced by the PCOE / Client, please correct any obvious misspellings at this time and
remove any extra spaces at the beginning of the copy.
6E. Check Active Elements for correct Element Layout, Components, and FREE offers

Sort by Element Layout in the Right Upper Canvas and

select the Thumbnails tab in the Right Lower Canvas

Use the up and down arrow keys on your keyboard to scroll

through each Active Element individually.

Look at the Price Point Component in the Thumbnails and

compare it to the Element Layout Name in the Element Layout
column.

If they do not match, you need to update the

Element Layout Name in LAGO.

Pay special attention to %_Off vs SAVE% and which type of

Netdown is being shown.

* If you see a FREE Offer – It probably needs to go away. FREE

offers should be non-placeholdered static copy on the parent
offer. All images for both the parent offer AND the FREE
portion, should be included in the parent offer.

* If you see an Active Element with NO COMPONENTS in

Thumbnails, that Element needs to be deleted and moved to
Page 0

For Example – these do not match.

This Element Layout should be SAVE% not %_Off
because the PPT Component on the page is a SAVE %

When you get to the Creative Elements (any element with an underscore [_] at the
beginning of the name - _CreativeElement, _ABEV Element, etc.) – these should
NOT have an Element Layout but should still have Components in Thumbnails if it is
an Active Element. If they do not have Components, delete and move to Page 0

When you get to the Page Element – these should NOT have an Element Layout AND should NOT have any
Components in Thumbnails. If you find Components in the Thumbnails of a Page Element, move the
Component to the appropriate Element and ask a PA to open the page and place the Component.
6F. Confirm Disclaimers on all Elements that Need Them

Update all Views in LAGO

Sort by Info

Compare the Info column with the Disclaimer column

a. If the Event in the Info column is a MEGA event, a Buy X, Save Y style event, or other such Event that
shows up on the page with an Event-Wide disclaimer, the offer in LAGO SHOULD NOT HAVE THE
DISCLAIMER.

b. If the Event type is WDD, MUSTBUY, Baby-Event, Self-Care Event, or some other event type where
each offer has its own individual disclaimer that appears directly with the offer on the page, (including
BD04 ABEV where the Net Down disclaimer is at the bottom of the page,) then that unique disclaimer
should be present for those offers.

Sort by Element Layout

c. Double Check ABEV disclaimers. Make sure they are present and make sure they are correct.

d. Make sure there are NOT Disclaimers on offers that should not have them – this includes any creative
direction from NGPP that may still be in the Disclaimer field for some reason.

e. Add any missing Disclaimers and remove any that are not needed.

(continued next page)

6G. LOYALTY Offers

For any offers that have been combined into a flattened or consolidated component – where all of the images
and pricepoint component are grouped together as a single graphical component instead of separate
individual items – There are several things you need to do in order to make sure the Data is accurate for these.

First look at the Thumbnails in LAGO

a. All individual images must also be in the Element AND placed on the page. You can look at the
Components tab to determine whether or not they are placed. If they are NOT placed, please send the
page to the Pas for those images to be placed.

b. In addition to the individual images, if the offer is a Feature or SubFeature, the

Element thumbnails should include an OfferType component that includes the
word Feature or SubFeature as appropriate. If this is not present (or not placed –
see above) please send the page back to Pas to be placed.

Select the consolidated offer graphic in the Thumbnails and click on the eyeball icon
on the upper right of the lower canvas. This will open a large preview of the
consolidated offer graphic.

a. Look at the Mainline, Underline, With Card, & Disclaimer on the preview graphic and make sure the
information in LAGO matches this.

b. If the preview graphic does not have a Mainline, you can either use a single [SPACE] in the ML in LAGO,
OR you can put the UL into the ML and leave the UL blank.

c. If the preview graphic does not have a UL, make sure the UL in LAGO is blank.
d. “With Card*” should NOT be part of the UL. In the provided example, the With Card* copy goes in
the With Card field, and everything else below it is the UL.

e. If the offer is a 3-Day Only sale – or other event with different start / end dates from the main ad –
make sure that the Start and End dates are entered into the Coupon Start Date and Coupon End Date
in the Element Edit screen.

f. For Holiday Sales (usually top of IA06), make sure that the Feature callout appears in the name of the
price point component. Otherwise make sure this Element also has the OfferType component
mentioned above.
7A. Use FileMaker Tool to Check Pricing

Open the Kroger LAGO Prod-Processor (KLP)

Go to the REPORTING tab

Click on the button in the 3rd Row, 3rd Column

“PRICE ELEMENT LAYOUT NAME CHECK”

If there is any data showing in the lower portion of the window, click on the “RESET” button
Once the Data is cleared out, you can set up you fields as shown below.

Campaign Name = ENTERPRISE

Event Name = The Job you are currently working

Include ABEV = Check YES

AFTER ALL THREE FIELDS ARE SET – then Click IMPORT

FileMaker will take a few minutes to Import the Data from your job. Once all of the Data is imported, then you
will want to Click on the “SHOW ALL” button, and then the “SHOW ISSUES” button.

[continued on next page]

The resulting view will display all of the things that FileMaker thinks may be errors.
However, it is not always correct, so you will need to examine each item and determine if there is an error.

This column shows the If you are sure that the Element Layout name in
Element Layout currently LAGO is correct (check back in LAGO to verify) then
listed in LAGO you can look at the Pink Highlighted boxes, to see
what fields FileMaker thinks are incorrect.
This column shows what FileMaker thinks the
Element Layout should be, based on the Article
fields present

When you have identified an error, go back to LAGO and fix it.

When you think you have corrected all of the errors back in LAGO, reset the FileMaker tool with the RESET
button. Then re-import the job and hit SHOW ISSUES to verify.

Continue to correct errors back to LAGO, reset the tool, re-import and verify until no more errors are found.

Example Errors with explanations can be seen on the next page.

EXAMPLE FILEMAKER TOOL PRICING ERRORS

In this example we can see that the Element Layout in LAGO is _KRGR_2FOR so FM is expecting to see values in Ad Retail and
Quantity. Since there is nothing in Quantity, FM thinks that the Element Layout should be _KRGR_STD instead.

In this case, FM is correct, and the CSS should go back to LAGO and change the Element Layout from _2FOR to _STD.
You can reference the Page, Version, and Mainline columns to help identify which Element to fix in LAGO.

This example shows the Element Layout name in LAGO as _KRGR_%_OFF so FM expects to see something in the Percent Off field.
Instead, the Save Percent field is populated, making FM think this should be a _KRGR_SAVE%

For this item, the CSS needs to double check LAGO and probably the eProof to see which type of offer is really on the page. If it is a
% Off, the they need to move the value in the Article from Save Percent to Percent Off in LAGO. If, instead, the offer is a Save %,
then the Element Layout name needs to be corrected in LAGO.

In this example, the Element Layout in LAGO is _KRGR_STD so FM expects to see the Ad Retail field populated and nothing else.
FileMaker even agrees this should be a _KRGR_STD, but thinks there is an error because of the UOM field populated.

As a CSS, you know that sometimes the _STD ppt has an UOM and sometimes it doesn’t. If you know that this offer is supposed to
have UOM, then you can ignore this “error.”

This example shows a _KRGR_FINAL COST WUB 2FOR. FileMaker sees the Sale Price, Quantity, and Buy Quantity fields filled out and
agrees that this is the correct Element Layout. However, it is flagging the Ad Retail as an error. This is because WUB Element
Layouts no longer need an Ad Retail. Please clear all WUB Ad Retails, whether WUB 2FOR or WUB STD

7B. Double Check UOM, Asterisks

Once you have finished correcting all of the pricing errors back to LAGO, click on the SHOW ALL button once
more so that all offers are displayed.

Use your mouse to scroll down the list, looking at the UOM column as you go. Make sure that all of the UOMs
are capitalized properly (all caps for ENT divisions, lowercase for MARI)

Also make sure that all UOMs that need Asterisks (*) have them.

Make any needed corrections to the job in LAGO.

8. Check Articles

Go back to LAGO Explorer and, in the Left Canvas, Navigate to Articles > All
but DO NOT expand the folder in the Left Canvas.

In the Right Upper Canvas,

Sort the Articles by the NAME column.

Looking at the NAME column, you should

only see Block IDs or PH
- No PH-
- No Product Name

If you see ANYTHING other than Block ID

or PH in the NAME column, you need to
change it to PH

Once you have completed this step, your job should be ready for the QA Team to pick up and process.

Once it is processed, the QA Team will provide feedback to let you know anything they found that was missed, or any
other errors that the CSS Team may need to look out for in the future. Make sure this is completed by 12:30pm on the
day after the division is Released. If you cannot get it done by the deadline, for any reason, make sure to reach out to
the QA Team before the 12:30 deadline and let them know you need more time.

On the next page, you will find a list of the most common errors found on weekly jobs. Most of these can be eliminated
through this process. Some can only be eliminated by managing your data correctly throughout the ad cycle.
MOST COMMON ERRORS

Element Errors

- Unplaced Components
- Version Code strings with extra or missing commas or spaces
- Version Codes misspelled
- Pages that were Deleted from the Ad, but not Removed from the Job in LAGO
- Orphan Elements (Elements that were left in the Job after a Page is Deleted, but not moved to Page 0)
- Deleted Elements that have not been moved to Page 0
- Misspelled words in ML / UL
- Leading Spaces in ML / UL
- Incorrect Element Layout Name
- Elements missing Disclaimers
- Elements with Disclaimers that are not needed
- Elements missing Element Layout Name
- Elements with no Components (need to be deleted and moved to Page 0)
- Elements with no Articles (exception to this is _KRGR_CREATIVE)
- WDD Elements either missing or wrong Loyalty indicator (With Card & Digital Coupon)

Pricing Errors

- Missing UOMs
- Missed UOM Capitalization
- UOMs on any kind of 2FOR (except UOM_2FOR)
- UOMs on other Element Layouts where not needed (%_OFF, SAVE%, BOGO, etc.)
- Missing Buy Quantity (Netdowns and WUB)
- Incorrect Buy Quantity (Netdowns and WUB)
- Missing asterisk (*) on Netdown UOM
- Ad Retail on any WUB
- Articles with a Product Name instead of a Block ID or PH
- Extra Articles on an Element (each element should have only 1 article.)
- Articles attached to multiple different Elements