The Morning Ritual Nobody Loves

Every morning in retail, somewhere between 8am and 10am, someone pulls yesterday’s sales figures, checks the weather, tries to recall which promotion was running, consults the calendar for bank holidays, paydays, school terms or other significant trading periods and then drafts a few paragraphs for the leadership team. It is usually rushed and almost always takes longer than it should.

What if it simply arrived? Automatically and intelligently, every morning before the first meeting of the day.

The Opportunity

For a business, understanding why yesterday happened is just as important as knowing what happened. That contextual layer, the weather, the retail calendar, the live promotion, is exactly where AI earns its place.

By connecting a well modelled Data Warehouse or Data Lakehouse to a large language model (LLM) API, orchestrated through a Microsoft Fabric Notebook, it is possible to generate a board ready daily sales narrative automatically. The commentary draws on everything that influenced trading that day and lands in the right inbox or Teams channel before the first meeting of the morning.

What Powers the Commentary

Each morning, a notebook assembles a structured set of inputs and passes them to a LLM, which returns a finished narrative. Those inputs typically include:

  • Sales performance: yesterday’s net sales, transaction count, and average transaction value versus the same date last year and versus budget, at both a total and category level
  • The retail calendar: Bank Holidays, seasonal peaks, pay days and where the business sits within each trading period
  • Weather: temperature and conditions across key store geographies, measured against seasonal averages
  • Promotions: what was live yesterday, and whether any campaign communications went out
  • Stock availability: whether key seasonal lines were in stock, particularly during peak trading periods

A “prompt” configuration table held within the Warehouse or Lakehouse gives the business full control over what the AI produces and how it communicates. The tone, the word count, which KPIs to surface, and the thresholds that define whether performance is on plan, slightly behind, or a concern are all configurable within a config table.

No dashboard joins all of this into a sentence. But an LLM can.

Foundations Have to Come First

None of this works without a robust, reliable Data Warehouse or Data Lakehouse underneath it, with properly modelled dimensions and facts. This is often the step most organisations overlook.

A LLM will produce confident, fluent commentary regardless of whether the data it has been given is trustworthy. The old saying, garbage in, garbage out has never been truer. Prior year comparatives, budget data, and promotional history all need to be clean, well modelled, and available on time every morning.

AI simply amplifies data problems, it does not fix them.

What the Output Looks Like

Here is an example of the kind of commentary this solution could deliver each morning:

“Net Sales yesterday were £312,800, up 11.3% on last year and 7.6% ahead of budget, the strongest Monday performance since October-25. The mid-season sale, which launched Saturday, is clearly driving incremental volume, with transaction count up 14.2% year-on-year. Average transaction value is down slightly at £28.60, reflecting the promotional mix. Homewares and Menswear are leading the uplift. Month-to-date the business is £890k ahead of budget with three days of the period remaining.”

Clear, contextual, and ready to share before the day has begun.

Why It Matters

When this process is automated, the commentary arrives at the same time every morning regardless of who is on leave. It is always contextually aware. It knows where the business sits in the trading calendar, it knows it rained in the South East, it knows the promotion changed on Saturday. Ultimately, it shifts the analyst role from describing what happened to acting on what the AI has already described.

That is a meaningful change in how time and expertise are deployed.

Tags: , ,