Power BI Dashboard + Automated Reporting Pipeline — Marketplace Sales Data

Power BI Reporting — Freelancer Brief ________________________________________ Background We are UK fashion retailer operating across multiple online marketplaces. We are migrating from our current marketplace integrator to a new platform, going live on 29 July 2026. An external source currently produce’s all of our marketplace sales reporting. When we migrate, that reporting stops. We need to rebuild it internally using Power BI, pulling data directly from the new integrator exports. We have Power BI Pro licences in place. All reports will need to be built from scratch — no existing PBIX file will be provided. ________________________________________ Data Source The new integrator will produce scheduled CSV/XLSX exports covering all marketplace order and sales data. These will be dropped to a specified location on a scheduled basis. Data covers: • 6-7 marketplace channels • 3 brands • Weekly sales exports • Daily sales exports Core fields available in exports: week number, week commencing date, channel name, store ID, style code, description, season, category, colour, size, EAN, sales units, sales value, retail price, cost, returns units, returns value, gross sales units, gross sales value, stock units, brand, gender (Attr: Shopify Gender), replenishment units, on-order units. ________________________________________ Reports Required The scope splits into two parts: one Power BI dashboard, and five automated spreadsheet outputs. ________________________________________ Part 1 — Power BI Dashboard Weekly Sales Summary Three versions Each version to include: • Headline KPIs (sales £, units, returns, ASP) vs last year • 13-week rolling sales tracker • Channel and store breakdown • Category analysis • Gross sales and returns by category • Colour split • Returns rate trend • Best sellers overall and by channel ________________________________________ Part 2 — Automated Spreadsheet Outputs These are structured data files currently produced manually or by external sources. They need to be automated — generated from the integrator's data and delivered on schedule. Format should match the existing Excel templates we will provide as reference. 1. Weekly Sales by Channel Simple weekly table: sales £ and units by channel/store for categories side by side. Weekly, delivered Monday AM. 2. Sales by Style (Rolling Weekly) Style-level view with a rolling 5-week window. Produced separately for our brands. Fields: style code, description, brand, season, category, sales units per week (rolling 5), total units, ASP, stock, cover, sell-through %, replenishment, on-order. 3. channel specific by Style Same structure as Sales by Style but filtered to specific channel only. Week column headers to use relative labels (CW, CW-1, CW-2 etc.). 4. Sales by EAN Granular barcode-level data. Fields: week, channel, style, colour, size, EAN, sales units, sales value, cost, retail price, returns units, returns value. 5. Daily Sales by Barcode Daily transaction file at EAN level. Fields: branch, date, barcode, sales value, sales units. One file per day, delivered pre-7am daily. ________________________________________ Delivery Requirements • Weekly reports to be emailed every Monday AM. • Daily barcode file to be available before 7am daily • Scheduled email subscriptions to named internal recipients • All reports to show vs LY comparisons — note: We have no historical data at go-live. A solution for populating LY data is required (either data load before go-live or a manual upload approach) ________________________________________ Recipients / Stakeholders Reports are used by: Womenswear team, Menswear team, Ecommerce leads, and senior management. Multiple recipients with different report types. We will map this in detail with the successful candidate. ________________________________________ Existing Assets Note: no existing PBIX file will be available. All reports are a full build. ________________________________________ What We Need From You • Review of the data source structure and confirmation of approach • Build of the Power BI dashboard (three brand versions) • Build of the five automated spreadsheet outputs, matched to our existing Excel templates • Data pipeline connecting CSV/XLSX exports to both the dashboard and the file outputs • Set up of scheduled delivery — dashboard via email subscription, spreadsheet files to a specified location or via email • Solution for LY data • Handover documentation so we can maintain and update the reports internally going forward ________________________________________ Timeline Go-live is 29 July 2026. We need the reports functional and tested before that date. We have approximately 5 weeks from now. This is a hard deadline. ________________________________________ ________________________________________ Scope Questions for Candidates Please confirm in your proposal: 1. Your approach to building the data pipeline from CSV/XLSX file drops into both Power BI and automated spreadsheet outputs 2. What tool you would use to generate and schedule the spreadsheet outputs (Power Automate, Python, or other) 3. How you would handle LY comparisons with no historical data at go-live 4. Whether you are comfortable working to a fixed go-live deadline of 29 July 5. Fixed price or hourly — and your estimate for this scope, split between the dashboard and the spreadsheet automation if possible