Home Course home Curriculum Learner dashboard Skill tree Business projects Datasets Final project

The dataset library

Eleven datasets built for this course — 24,252 rows in total. They are generated rather than scraped, which means they are free of licensing problems and free of personal data, but they are not toy data: they carry real seasonality, genuine margin differences between categories, attrition that correlates with tenure and satisfaction, and in one case a deliberate set of data-quality faults for you to fix.

Every file is plain UTF-8 CSV with a header row, so it loads cleanly into Power BI Desktop, Excel, Python or anything else.

Start with two files
If you only download two, take bwb-retail-sales.csv (the course's main fact table, used from Module 0 to Module 11) and bwb-messy-customers.csv (the deliberately dirty file that every Power Query lesson uses). The dimension tables — products, customers, stores, date — join to the sales file to form the star schema you build in Module 4.
Retail Sales Transactionsbwb-retail-sales.csv15,067 rows13 columns1.3 MB

Two full years (Jan 2024 – Dec 2025) of order-line transactions for a mid-sized multi-channel retailer selling across six product categories, five regions and three channels. Contains real seasonality — a November peak, a February trough — and category margins that differ enough to make the analysis interesting. This is the course's primary fact table.

Columns & data types
ColumnData typeMeaning
OrderIDTextOrder identifier. One order can have several rows — one per product line.
OrderDateDateDate the order was placed. Use this for time intelligence.
ShipDateDateDate the order shipped. A second date column, for the role-playing dimension lesson.
CustomerKeyTextForeign key to bwb-customers.csv.
ProductKeyTextForeign key to bwb-products.csv.
StoreKeyTextForeign key to bwb-stores.csv. Blank for non-store channels.
ChannelTextOnline, Retail Store or Partner.
QuantityWhole numberUnits sold on this line.
UnitPriceDecimalList price per unit before discount.
DiscountDecimalDiscount rate applied, 0 to 0.30.
NetSalesDecimalRevenue after discount. The measure you will sum most often.
COGSDecimalCost of goods sold for this line.
ProfitDecimalNetSales minus COGS. Pre-computed so you can validate your own DAX.
Questions this dataset can answer
  • Which category generates the most revenue, and is it also the most profitable?
  • How did monthly revenue trend across the two years, and where is the seasonal peak?
  • Which region has the highest revenue per customer?
  • What share of revenue comes from discounted orders, and does discounting improve profit?
  • Which products account for the top 20% of revenue?
Used in
Install Power BI Desktop & Build Your First ReportConnecting to Excel & CSVCore Business Measures: Sales, Profit, Margin, AOV
Healthcare Encountersbwb-healthcare-encounters.csv3,000 rows14 columns357 KB

One year of hospital encounters: department, admission type, length of stay, cost, severity and outcome. Length of stay and cost vary systematically by department, which makes utilisation and cost-per-encounter analysis meaningful rather than noise.

Columns & data types
ColumnData typeMeaning
EncounterIDTextPrimary key — one row per encounter.
PatientIDTextPatients can appear more than once. Distinct count matters here.
AdmitDateDateAdmission date.
DischargeDateDateDischarge date.
DepartmentTextSeven clinical departments.
AdmissionTypeTextEmergency, Elective, Referral or Transfer.
LengthOfStayDaysWhole numberDays between admit and discharge. Zero means same-day.
PatientAgeWhole numberAge at admission.
PatientGenderTextRecorded gender.
OutcomeTextDischarge outcome, including 30-day readmission.
TotalCostDecimalTotal encounter cost.
PayerTypeTextPrivate, public or self-pay.
SeverityScoreWhole number1–5 clinical severity.
Readmitted30DayTextYes / No flag.
Questions this dataset can answer
  • Which department has the highest cost per encounter, and is severity the cause?
  • What is the 30-day readmission rate, and does it vary by admission type?
  • How does length of stay distribute — is the mean misleading here?
  • Which departments show the widest cost variation for similar severity?
Supply Chain Purchase Ordersbwb-supply-chain.csv2,200 rows21 columns319 KB

A year of purchase orders across seven suppliers and four warehouses, with promised versus actual lead times, fill rates and closing stock. Delivery performance genuinely varies by supplier, so supplier scorecards produce a real ranking rather than noise.

Columns & data types
ColumnData typeMeaning
PurchaseOrderIDTextPrimary key.
OrderDateDateDate the PO was raised.
PromisedDateDateDate the supplier committed to.
ReceivedDateDateDate goods actually arrived.
SupplierKeyTextSupplier identifier.
SupplierNameTextSupplier display name.
SupplierCountryTextCountry of origin.
WarehouseKeyTextReceiving warehouse identifier.
WarehouseNameTextWarehouse display name.
WarehouseRegionTextRegion the warehouse serves.
ProductKeyTextJoins to bwb-products.csv.
ProductCategoryTextProduct category.
QuantityOrderedWhole numberUnits ordered.
QuantityReceivedWhole numberUnits actually received — fill rate is derived from this.
PurchaseCostDecimalCost of the order.
PromisedLeadDaysWhole numberCommitted lead time.
ActualLeadDaysWhole numberActual lead time.
DelayDaysWhole numberActual minus promised. Negative means early.
DeliveryStatusTextOn Time, Late or Severely Late.
ClosingStockUnitsWhole numberStock on hand after receipt.
SupplierQualityScoreDecimalSupplier quality rating out of 5.
Questions this dataset can answer
  • Which suppliers miss their promised lead time most often?
  • Does a higher quality score actually correlate with on-time delivery?
  • Which warehouse absorbs the most late deliveries?
  • What is the fill-rate distribution, and which category is worst affected?
HR Employee Recordsbwb-hr-employees.csv1,200 rows15 columns117 KB

Employee master data for a 1,200-person company: department, level, salary, tenure, satisfaction, performance and attrition. Attrition is not random — it correlates with short tenure, low satisfaction and specific departments, so the analysis produces findings worth acting on.

Columns & data types
ColumnData typeMeaning
EmployeeIDTextPrimary key.
EmployeeNameTextDisplay name.
DepartmentTextSeven departments.
JobLevelTextAssociate, Mid, Senior, Lead or Director.
HireDateDateStart date. Tenure is derived from this.
ExitDateDateBlank for current employees — a genuine null to handle.
AttritionTextYes / No. The target of the analysis.
AnnualSalaryWhole numberBase salary.
EducationTextHighest qualification.
GenderTextIncludes a 'Prefer not to say' category — handle it honestly.
AgeWhole numberAge in years.
SatisfactionScoreWhole number1–5 self-reported survey score.
PerformanceRatingWhole number1–5 manager rating.
WorkModeTextRemote, Hybrid or On-site.
RegionTextOffice region.
Questions this dataset can answer
  • Which department has the highest attrition rate, and is the difference material?
  • Does satisfaction score predict attrition better than salary does?
  • What is the tenure profile of leavers versus stayers?
  • Is there a pay gap by level once department is controlled for?
Customer Dimensionbwb-customers.csv900 rows5 columns42 KB

The customer master: region, segment and signup date. Clean, one row per customer, with a proper key. Use it to slice the sales fact by geography and segment.

Columns & data types
ColumnData typeMeaning
CustomerKeyTextPrimary key. Joins to bwb-retail-sales.csv.
CustomerNameTextDisplay name.
RegionTextNorth, South, East, West or Central.
SegmentTextConsumer, Small Business or Enterprise.
SignupDateDateFirst registration date — useful for cohort analysis.
Questions this dataset can answer
  • Which segment has the highest average order value?
  • Do customers who signed up earlier spend more over time?
Date Table (reference)bwb-date-table.csv731 rows14 columns47 KB

A complete, gap-free date table covering 2024–2025 with calendar and fiscal attributes. Provided as a reference so you can compare it against the one you build yourself in DAX or Power Query — building your own is the better habit.

Columns & data types
ColumnData typeMeaning
DateDateOne row per day, no gaps. This is the key column.
YearWhole numberCalendar year.
MonthNumberWhole number1–12. Use this to sort MonthShort correctly.
MonthShortTextJan, Feb, Mar … Needs Sort By Column set to MonthNumber.
MonthNameTextFull month name.
QuarterNumberWhole number1–4.
QuarterTextQ1–Q4.
WeekOfYearWhole numberISO week number.
DayNameTextMonday … Sunday.
DayOfWeekWhole number1 = Monday. Sort key for DayName.
IsWeekendTextYes / No flag.
YearMonthTextYYYY-MM, handy for a continuous month axis.
FiscalYearWhole numberFiscal year starting 1 July.
FiscalMonthWhole number1–12 where 1 = July.
Questions this dataset can answer
  • How does a fiscal-year view change the picture versus calendar year?
  • Which weekday generates the most revenue?
Finance — Actuals vs Budgetbwb-finance-actuals-budget.csv722 rows8 columns56 KB

Two years of monthly actual and budget amounts by account and cost centre. Revenue accounts are positive, cost accounts are negative — the sign convention real ledgers use, and the one that breaks naive SUM measures.

Columns & data types
ColumnData typeMeaning
PeriodStartDateFirst day of the month the amounts belong to.
AccountCodeTextGeneral-ledger account code.
AccountNameTextHuman-readable account name.
AccountTypeTextRevenue, COGS or OpEx — drives the sign convention.
CostCentreTextOwning cost centre.
BudgetAmountDecimalPlanned amount for the period.
ActualAmountDecimalActual amount for the period.
VarianceDecimalActual minus Budget. Pre-computed so you can check your DAX.
Questions this dataset can answer
  • Which cost centres are consistently over budget?
  • What is the gross margin trend by month?
  • Does favourable revenue variance offset unfavourable cost variance?
  • Which single account drives the largest absolute variance?
Messy Customer Exportbwb-messy-customers.csv280 rows8 columns26 KB

A deliberately dirty extract — the kind of file that actually lands in your inbox. It combines two exports, so it contains duplicate rows and duplicate customer IDs. Country is spelled 25 different ways for 6 real countries. Dates use five different formats. Revenue mixes currency symbols, thousands separators and blanks. Status has 7 spellings for 3 real states. Emails are missing, malformed or padded with whitespace. Every Power Query lesson uses this file.

Columns & data types
ColumnData typeMeaning
CustomerIDTextIntended to be unique — it is not. Duplicates are your first clue.
FullNameTextSome entries have double spaces, trailing spaces, or ALL CAPS.
EmailTextBlank in some rows, malformed in others, whitespace-padded in others.
CountryText25 distinct spellings for 6 real countries.
SignupDateTextLoads as text because five date formats are mixed together.
LifetimeRevenueTextLoads as text: currency symbols and thousands separators present.
PhoneTextFour different formatting conventions.
StatusText7 spellings for 3 real states (Active, Inactive, Churned).
Questions this dataset can answer
  • How many genuinely distinct customers are in this file?
  • What is total lifetime revenue once the column is numeric?
  • How many customers are Active once status is standardised?
  • Which rows should be rejected rather than repaired, and why?
Used in
Power Query Fundamentals & Data ProfilingData Types, Columns, Duplicates & Row FiltersReplacing Values, Nulls & Quality ChecksSplitting & Merging Columns
Product Dimensionbwb-products.csv114 rows6 columns6 KB

The product catalogue: category, subcategory, list price and unit cost. A clean dimension table with a genuine primary key — exactly what a star schema needs.

Columns & data types
ColumnData typeMeaning
ProductKeyTextPrimary key. Joins to bwb-retail-sales.csv.
ProductNameTextDisplay name for the product.
CategoryTextOne of six top-level categories.
SubcategoryTextFiner grouping inside the category. Builds a natural hierarchy.
UnitPriceDecimalCurrent list price.
UnitCostDecimalCurrent unit cost.
Questions this dataset can answer
  • Which subcategories carry the widest price range?
  • What is the theoretical margin per category before discounting?
Wide Monthly Sales (cross-tab)bwb-wide-monthly-sales.csv30 rows3 columns4 KB

Sales by category and region with twelve month columns spread across the row — the shape a finance team hands you from Excel. Power BI cannot use this directly. Unpivoting it into long format is the whole point of the exercise.

Columns & data types
ColumnData typeMeaning
CategoryTextProduct category.
RegionTextSales region.
Jan-2025 … Dec-2025DecimalTwelve month columns. These need to become two columns: Month and Sales.
Questions this dataset can answer
  • What does this table look like after Unpivot Other Columns?
  • Why can you not build a month trend line from the file as delivered?
Used in
Group By, Pivot & Unpivot
Store Dimensionbwb-stores.csv8 rows5 columns0 KB

Eight physical stores with format and opening year. A small dimension, useful for demonstrating that a dimension does not need to be large to be valuable.

Columns & data types
ColumnData typeMeaning
StoreKeyTextPrimary key. Joins to bwb-retail-sales.csv.
StoreNameTextDisplay name.
RegionTextRegion the store sits in.
StoreFormatTextFlagship, Standard or Compact.
OpenedYearWhole numberYear the store opened — lets you compare mature vs new stores.
Questions this dataset can answer
  • Do flagship stores out-earn standard stores per square metre of format?
  • How do stores opened in 2023–24 compare against mature stores?