DEV Community

Flowup Insights Team
Flowup Insights Team

Posted on

Ask for these five fields before you accept a 7-Eleven sales file

This working note is from the Flowup Insights Team. We help brands and distributors read 7-Eleven Thailand performance without treating a monthly total as a diagnosis. The field list below is what we ask for before we agree that a file is usable.

The first sales file you receive after listing is often a monthly total, sometimes split by region. That number cannot tell you whether a handful of stores are carrying the SKU, whether the zeros are empty shelves, or whether a promotion ran in stores that had no stock. If you accept that file as the basis for the next spend decision, you will argue about the wrong thing.

Do not start by asking for "more data"

"More data" is how a request dies in a thread. Ask for a weekly extract with five fields, named plainly, for the SKU you actually listed:

  1. Store identity — a code or name you can recognise from one week to the next.
  2. Units sold in the week.
  3. Whether the store was supposed to carry the SKU in that week.
  4. A stock or availability flag, even a rough one, so that a zero can be read as "no demand," "no stock," or "not yet ranged."
  5. Any promotion or display flag that was on in the week, even if it is only a yes or no.

If the distributor can add a delivery or replenishment date, take it. If they cannot, do not block the file for that reason. The five fields above already change the conversation.

We laid out how to turn those fields into a weekly table, and the misreadings that usually follow, in How to track 7-Eleven sales by store. Use that guide when you sit down with the first extract; this note is about getting a file that is worth sitting down with.

How to make the request so it actually arrives

Put the five fields in the body of an email or in the meeting note, not in a slide titled "data needs." Offer to accept a simple spreadsheet. Agree the weekday the extract will arrive, and agree that the first version can be imperfect as long as the fields are stable.

If the other side says the chain will not give store-level sales, ask what they can give that still distinguishes stores with stock from stores without it. A mid-level file that keeps that distinction is more useful than a national total that looks official.

Write down, in the same request, what you will not use the file for. You are not asking to audit the distributor. You are asking to avoid funding ads or discounts in a week when the product was not on the shelf.

What to do in the first week you have the file

Do not start with a chart of total sales. Sort the stores into three groups: those with stock and movement, those with stock and almost no movement, and those with no usable stock. The third group is an operations list, not a marketing list. The second group is where a shelf walk or a pack-recognition check belongs. The first group is the only baseline you should use when someone later asks whether a promotion "worked."

If the file is missing the stock flag, you cannot finish that sort. That is the moment to go back and ask for field four again, not the moment to build a dashboard around a single column of units.

Once the groups exist, the next spend decision gets simpler. You either repair availability, repair visibility in the quiet stores that had stock, or you have a fair baseline for a test. A file that cannot support those three paths is not yet a sales file you should accept.

Flowup Insights Team · a field list for teams reading 7-Eleven Thailand sales

Top comments (0)