Retail Sales Trend Explainer

Ask the weekly sales question; get pulled data, trend tables by category/store/period, and a plain read — with caveats.

Build an agent that answers retail sales-trend questions end to end. It uses a data agent to query the sales dataset and code interpreter to analyze and explain the trends — by category, by store, across periods — turning the recurring "how did we do?" into a fast, consistent readout with the tables and the plain-language interpretation together. Results are grounded in the queried data, not estimated.

This is a query → analyze → explain pattern using markdown-header structure. Headers separate the highlights, the supporting tables, and the caveats so a manager can scan to what they need. The data agent fetches grounded numbers; code interpreter computes the period-over-period and segment comparisons. The defining discipline is causal restraint in a seasonal domain — the agent reports that a category rose or a store outperformed and frames likely drivers (seasonality, a promo window) as context to consider, not proven cause, because retail movement has many overlapping causes a single pull can't isolate. Edge cases cover empty result sets, very large pulls, and incomplete periods (don't compare a partial week to a full one).

This pattern applies anywhere recurring sales questions deserve a fast, grounded read. Common scenarios for this pattern:

• Weekly and monthly sales reads
• Category-performance comparisons
• Store and region comparisons
• Seasonality checks
• Period-over-period trend summaries

This manifest uses: data agent, code interpreter

How to build single-shot agents using markdown headers prompt structure for trend highlights + tables output.

This agent manifest is sample code subject to Azure's licensing terms for Distributable Code under the Universal License Terms for Online Services .

IMPORTANT! This manifest is for educational and experimentation purposes. Resulting agents are not production ready. Review all provided resources and carefully test agent behavior in the context of your use case. Agents you create may be subject to legal and regulatory requirements, may require licenses, or may not be suitable for all industries, scenarios, or use cases. By using any manifest, you are acknowledging that resulting agents and other output are solely your responsibility, and that you will comply with all applicable laws, regulations, and relevant safety standards, terms of service, and codes of conduct. Learn more .