A Power BI dashboard is only as trustworthy as the data rules behind it. In a JCars Logistics case study, author Victoria Ndei describes a workflow that starts with checking a raw vehicle-sales CSV, then cleaning and modelling it before building interactive report pages. The project offers a practical example of how to structure analysis; it does not independently verify JCars Logistics’ company-wide financial or operational performance.
What the case study covers
Ndei’s walkthrough describes an end-to-end business intelligence project using a CSV with vehicle sales, customer, financial, operational and location-related information. The sequence is useful: investigate the source, make transformations explicit, build a model, define measures, create report pages, and then interpret results in context. Each stage affects the next; a mistaken currency conversion or duplicate transaction can flow through to a KPI and influence a branch comparison.
As an Amazon Associate I earn from qualifying purchases.
The article is an account of an individual project. Its workflow and observations should be attributed to the author rather than presented as audited JCars Logistics results. A separate public repository describes a different project, so its dataset figures and conclusions must not be merged with this case.
Why inspect the CSV before building visuals?
The walkthrough reports checks for missing and blank values, nulls, repeated records, invalid or negative numbers, text in numeric fields, inconsistent currency symbols and labels, “K” and “M” suffixes, inconsistent dates, placeholders, out-of-range ratings, discount formats and category values. These are not merely formatting issues: they can change sums, counts and comparisons.
#1 Best Overall
An unusual value is a reason to investigate, not automatic proof of an error. A negative amount, for example, might reflect a legitimate adjustment or a data problem. The analyst should understand the field and check the business context before changing or deleting a record.
Document transformations rather than hiding them
Ndei describes setting data types, cleaning text, handling blanks and placeholders, standardizing numeric and monetary fields, cleaning discount and rating values, standardizing dates, and applying business rules. Recording these decisions makes the resulting measures easier to interpret and reproduce. Silent changes can alter later KPI totals and the conclusions drawn from them.
How the project defines revenue and missing values
For its reporting, the case uses Kenyan Shillings and defines revenue as:
Recommended Free Tools
Rank #2
Revenue = Units Sold × Unit Selling Price × (1 − Discount) + Delivery Fee
This is the project’s documented calculation, not a confirmed JCars accounting policy. The author says missing discounts were treated as zero, missing delivery and logistics fees as zero, and missing ratings as a neutral value of 3. Those are analytical assumptions: they may be workable for a particular report, but they should be visible to report users because different choices can produce different results.
The author also says foreign-currency labels were not converted where a defensible exchange rate could not be established. That avoids implying that amounts in different currencies are directly comparable. Before aggregating monetary fields, an analyst needs a supported conversion rule or must keep the currencies separate.
How the data model supports analysis
The described model uses a central FactSales table and dimensions for vehicle, customer, location and date. The fact table holds transaction-level measures; the dimensions provide descriptive attributes for filtering and grouping. This separation can make the report easier to maintain and lets the same measures be evaluated across different slices.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe article describes reusable DAX measures spanning revenue, units, orders, average order value, costs, gross profit, profit margin, profit per vehicle, customer activity, ratings, delivery and logistics, returns, cancellations, discounts, payment, ranking and time analysis. These measures only answer reliable questions when their definitions and transaction grain are consistent. In particular, an order count should not accidentally count multiple line items as multiple orders.
What the report lets a reader investigate
The report is organized from an executive overview toward more detailed analysis. Its described features include sales analysis, profitability and branch comparisons, branch drill-through, operations and customer experience, investigations and exceptions, and management insights. Slicers cover year, month, branch, location, vehicle type, make, model and payment method; the author also describes page navigation, a branch tooltip, interactive filtering and drill-through.
Rank #4
The author frames the analysis around questions such as:
- How does profitability vary across branches?
- How do discounts relate to profitability?
- How does revenue vary by payment method?
- What operational patterns exist around returns and cancellations?
- How does performance change over time?
These are useful questions for exploring the report, not claims that the case established a particular answer. Branches, vehicle types or periods should be compared using consistent filters and definitions, and revenue should be read alongside costs, profit, margin and operational indicators.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →What can—and cannot—be concluded
The case recommends looking beyond revenue to costs, gross profit, margin, profit per vehicle, delivery and logistics, returns and cancellations. It also treats unusual records as investigation signals: validate them against source records and business context before excluding them or recommending action. This helps prevent a dashboard from turning uncertain data into an overly confident management conclusion.
A separate public GitHub repository describes a different project with 276 rows and 32 columns, and discusses currency ambiguity, conflicting revenue fields, missing data, spelling variants and questionable transactions. That repository reports that its own gross-margin interpretation changed after two suspicious transactions were excluded. These details belong to that separate project; they are not dataset specifications or verified performance results for Ndei’s case or JCars Logistics.
Neither project independently establishes audited, company-wide JCars results or the provenance of the underlying data. The useful takeaway is methodological: investigate data quality, state assumptions, model transactions and descriptive attributes deliberately, and make conclusions no broader than the evidence supports.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
