Interpreting Data and Making Judgements
What Does Interpreting Data Mean?
Interpreting retail data means more than simply reading a number off a chart. It means actively asking: what story does this data tell, and what does it mean for the business? In the exam you will be given stimulus material — tables, bar charts, line graphs or pie charts — showing figures such as sales revenue, footfall, profit or market share. Your job is to filter and select the information that is most relevant, analyse what is happening, and explain the significance of what you find.
Spotting Trends, Patterns and Anomalies
A trend is the overall direction data moves across a period of time. A trend may be upward (sales increasing quarter by quarter), downward (footfall falling year on year) or relatively flat. When writing about a trend, refer to specific figures from the data: "Sales revenue rose from £120,000 in January to £185,000 in March, indicating a clear upward trend." This approach shows you can select and use data precisely.
A pattern is a repeating feature in the data — often linked to seasonality. For example, a fashion retailer may consistently record its highest sales in November and December each year because of Christmas shopping, and a dip in January as consumer spending falls after the festive period. Recognising seasonal patterns matters because it helps a retail business plan staffing, stock levels and promotions appropriately. By contrast, an anomaly is a data point that does not fit the expected pattern. For instance, if footfall was rising steadily but dropped sharply in one specific week, the retailer needs to investigate why — perhaps a competitor ran a major sale event, or the store experienced a temporary closure. Identifying anomalies and offering a credible reason is a skill highly rewarded in extended-answer questions.
When interpreting retail data, look for three things: trends (the overall direction across time), patterns (repeating features often linked to seasonality) and anomalies (unexpected data points that break the trend). Always quote specific figures when describing what you see.
Comparing Time Periods and Stores
Exam questions frequently ask you to compare two stores, two time periods or two product lines. A strong comparison does three things: it states what is being compared, it uses figures to quantify the difference, and it draws a conclusion about what the difference means. For example: "Store A recorded footfall of 4,200 per week compared with Store B's 2,800 — Store A attracted 50% more customers. This suggests Store A's location in a busy shopping centre gives it a significant competitive advantage over Store B's high street position." Notice how the answer moves from data to implication — this is what the higher mark bands require.
When comparing time periods, percentage change calculations add precision to your interpretation. If a retailer's profit fell from £60,000 in 2023 to £45,000 in 2024, the percentage change is −25%, which is more informative than saying "profit fell." You may also be asked to compare qualitative data — for example, customer satisfaction scores from a survey — alongside quantitative figures. Qualitative data cannot be calculated in the same way, but it can be evaluated for themes: if customers repeatedly mention long queuing times, that is a pattern in qualitative data that points to a specific operational problem.
Drawing Conclusions from Charts and Figures
Drawing a conclusion means stating what the data tells you about the health and performance of the retail business. Conclusions should be: specific (linked to the actual figures provided), logical (following from the evidence) and business-focused (explaining the implication for the retailer). Avoid vague statements such as "sales went up so the business is doing well" — instead write: "The 18% rise in sales revenue between Q2 and Q3 suggests the summer promotional campaign successfully converted increased footfall into purchases, improving profitability." This type of conclusion references the data, gives a reason and explains the business significance.
A well-structured conclusion from retail data has three parts: (1) reference to specific figures, (2) a reason that explains the trend or change, and (3) the business implication — what it means for the retailer going forward. Weaker answers miss stage 2 or stage 3.
Making Judgements and Recommending Solutions
Making a judgement means using your interpretation of the data to decide what the retail business should do next. Common retail business issues you may be asked to solve include: falling sales revenue, high levels of unsold stock, poor footfall, declining profit margins and growing customer dissatisfaction. For each issue, your judgement must be rooted in the data you have been given — not just general business knowledge.
For example, if the data shows that footfall is highest on Saturday but online sales are growing every month while in-store sales are flat, a well-supported judgement might be: "The data suggests customers are shifting towards online purchasing. The business should invest in improving its website and introducing a click-and-collect service to retain customers who prefer the convenience of online ordering while still driving visits to the physical store." This judgement is justified by the data (online growth, flat in-store), proposes a specific solution (website improvement, click and collect) and explains how the solution addresses the issue.
Justifying Your Recommendation with Data
Justification is the final step: explaining why your recommendation is the right one, using evidence from the data and your knowledge of the retail industry. A strong justification evaluates both the potential benefits and any risks. For instance: "Introducing a loyalty scheme is recommended because the data shows repeat customer visits have declined by 12% over six months, suggesting customers are shopping with competitors. A loyalty scheme could incentivise repeat purchases, increasing customer retention and stabilising revenue. However, the business must consider the cost of running the scheme against the projected increase in sales — if margins are already under pressure, a poorly managed loyalty scheme could reduce profitability further." This balanced justification evaluates qualitative evidence (customer behaviour), quantitative evidence (the 12% fall) and considers a counter-argument — the hallmarks of a Mastering-band response.
When you are given a mix of qualitative and quantitative data, treat them as complementary sources of evidence rather than as separate tasks. Quantitative data (sales figures, footfall counts, percentages) tells you the scale and direction of a problem. Qualitative data (customer comments, satisfaction ratings, survey themes) tells you the reason behind the numbers. For example, if the quantitative data shows a 20% drop in sales and the qualitative data includes customer comments about poor product choice, the qualitative data explains the quantitative trend. In your answer, weave both together: "Sales fell by 20% (quantitative), which is consistent with customer feedback identifying limited product range as the main dissatisfaction (qualitative). This suggests the priority solution is to broaden the product range rather than reduce prices." This integrated approach is expected at the higher mark bands.
In extended-answer questions, it is entirely valid — and impressive — to acknowledge that the data supports more than one solution and then make a reasoned choice between them. For example, if the data shows both falling footfall and rising returns, a retailer might consider improving store layout to attract more visitors or improving quality control to reduce returns. You would note that both issues exist, then judge which is the more urgent priority given the data — perhaps the footfall decline is steeper and therefore the bigger financial threat. Making a clear, justified choice rather than sitting on the fence is what separates a Secure answer from a Mastering one. Always end with a definitive recommendation, even if you have acknowledged the complexity.