Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstalliTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antonina Wambui’s Power BI case study of JCars Logistics reports a dashboard built from 276 vehicle-sale transactions to examine revenue, profitability, customer behavior, regional performance, and operational exceptions. Its reported results—including KSh 1.48 billion in revenue and negative gross margins for several vehicle categories—are useful as investigation signals, not audited measures of company-wide performance. The quality of the source records, financial assumptions, and customer identifiers limits what the dashboard can establish.
What the JCars dashboard set out to answer
Wambui describes a project to turn vehicle sales records into an interactive report for management. Rather than present sales as one total, the report asks questions that require comparing financial and operational measures:
- Which vehicle categories produce high revenue but weak profitability?
- Which regions and branches contribute the most revenue, and how do logistics costs and delivery times compare?
- Is customer rating associated with transaction value?
- Which transactions have conflicting payment and delivery statuses?
- How much revenue comes from the largest customers?
These are related but distinct questions. Revenue describes the amount recorded from sales; it does not by itself show whether sales are profitable, operationally efficient, or supported by reliable data.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Why transaction grain and cleanup matter
One row represented one vehicle-sale transaction
The article says the starting dataset contained 276 transaction records and 32 columns. Each row represented one vehicle sale, with fields covering orders, customers, vehicles, geography, sales, finance, logistics, payment, and customer experience. That transaction-level grain makes it possible to compare individual orders and aggregate them by dimensions such as vehicle type, location, or customer—provided the records and identifiers are consistent.
#1 Best Overall
Reported data-quality problems
The author describes inconsistent order IDs and dates, implausible ages such as 0, 5, 121, and -5, mixed currencies, inconsistent category labels, questionable zero values, invalid vehicle years, varying discount formats, invalid ratings, alternate branch or yard names, and misspelled sales-representative names. These defects can affect grouping, totals, and calculated margins. For instance, two spellings of a branch can split its sales across separate labels; an invalid date can distort time-based comparisons.
How the project handled unreliable values
Wambui reports standardizing IDs and categories, converting valid dates and setting unrecoverable dates to null, and nulling ages or discounts considered unreliable. Vehicle years were corrected only where supporting evidence was available. The project also standardized currencies to KES using rates it lists as USD/KES 129.54, EUR/KES 147.84, and ZAR/KES 7.93. It does not identify the dates or an independent source for those rates, so they should be read as project assumptions—not current exchange rates. Some amounts marked with a corrupted “?” currency symbol were interpreted as USD when surrounding financial fields supported that interpretation.
Cleaning is not the same as verification: nulling an implausible value avoids treating it as fact, but it also removes information from calculations. Currency conversion and inferred currency labels can materially affect revenue and margin. The article notes that missing financial data and uncertain currency interpretation constrain its conclusions.
Free tools Windows power users keep installed
One-click scans. No signup required.
How the star schema organized the analysis
The source describes reshaping the flat records into a star schema centered on a FactSales table, linked to dimensions for Date, Customer, Vehicle, Location, Sales Rep, Payment, Lead Source, and Delivery Status. In the principal relationship pattern, one dimension row relates to many fact rows. This lets a report user filter or group transaction measures by a defined attribute rather than relying on repeated descriptive text in the raw table.
The model also has an important customer limitation: there was no unique customer identifier. The customer dimension was constructed from customer name, type, and age, so duplicate names, spelling variations, or changes in those fields could undermine customer-level grouping.
Measures reported in the project
The article lists DAX measures for total revenue, gross profit, gross profit margin, return rate, and logistics cost as a share of revenue. It defines gross profit as recorded revenue less units multiplied by unit cost. These measures inherit the quality of the underlying prices, costs, quantities, discounts, and currency assumptions. Where unit cost or unit selling price could not reliably be recovered, the resulting profitability figures require reconciliation before being treated as definitive.
Rank #3
What the five report pages covered
Wambui describes five pages, organized around different management questions:
- Business Overview: a summary of overall performance.
- Product & Sales Performance: product-level sales and profitability, including comparisons by vehicle type.
- Regional & Branch Analysis: geographic revenue and location performance.
- Customers & Sales Channels: customer concentration and lead-source comparisons.
- Operations & Exceptions: delivery, logistics, payment, and delivery-status issues.
The measures described across the report include revenue, gross profit and margin, units sold, delivery time, logistics cost, customer ratings, lead sources, and payment or delivery status. Reading these measures together is more informative than ranking categories by revenue alone: high sales can coexist with low or negative recorded margins, and a location’s revenue does not reveal its delivery performance or logistics burden.
What the article reports—and what the numbers mean
The following figures are outputs reported in Wambui’s DEV Community article; the available account does not establish them as audited or company-wide indicators. The article’s search result displays September 30 without a publication year.
Rank #4
| Reported measure | Figure in the article | How to interpret it |
|---|---|---|
| Total revenue | KSh 1.48 billion | Reported project total, subject to the source data and currency assumptions. |
| Top 10 customers | KSh 299.3 million, approximately 20% of revenue | Reported concentration among the ten largest customers; customer identity limitations affect grouping. |
| SUV revenue | KSh 845 million | Reported category revenue; revenue does not establish profitability. |
| Gross margin by vehicle type | SUV 8%; sedan -9%; crossover -6%; van -28%; truck -66% | Reported margins indicate categories to investigate, not verified economic performance. Negative values especially warrant checking costs, prices, discounts, currency conversion, and missing financial fields. |
| Average delivery time | Nairobi 26.29 days; overall 15.18 days | Reported averages in the dataset. They identify a difference to examine but do not explain its cause. |
| Payment and delivery inconsistencies | 14 transactions: 10 marked paid with delivery cancelled; four marked payment cancelled but delivered | Reported exception counts. The article says conflicts were flagged for investigation rather than silently corrected. |
There is a separate public LinkedIn profile excerpt attributed to Young Odhiambo describing a JCars Logistics dashboard built with PostgreSQL and Power BI. It reports a different scope and different values: 254 orders, 417 vehicles sold, KSh 1.38 billion in revenue, and a 21% gross margin. The available descriptions do not explain whether those figures reflect a different data version, scope, or project; they should not be combined with Wambui’s figures.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to use the findings without overstating them
Investigate revenue and margin together
The reported SUV result illustrates why a sales ranking is not a profitability ranking: the article gives SUVs the largest stated revenue and a positive reported margin, while several other vehicle types have negative reported margins. Before acting on category performance, reconcile source costs and prices, discounts, currency treatment, and missing values. A dashboard can expose where the records conflict; it cannot repair uncertain inputs merely by calculating a percentage.
Separate location performance from its causes
Comparing revenue, logistics cost, and delivery time by region or branch can reveal where performance differs. The reported Nairobi delivery average is higher than the dataset-wide average, but that comparison alone does not show why. Differences in product mix, route, order characteristics, or incomplete records could affect the result; the article does not establish a cause.
Best Value
Treat customer ratings as an association question
A visual comparison of transaction value and customer rating can show whether the two measures appear related in the records. It cannot establish that higher transaction values cause better ratings, or the reverse. Missing or unreliable ratings and customer identity limitations also affect how confidently such a pattern can be interpreted.
Use operational exceptions as a reconciliation queue
A paid order marked as delivery-cancelled and a payment-cancelled order marked delivered are not merely unusual chart values. They are records that need checking against source systems and business rules. Keeping the conflicts visible is more responsible than silently choosing one status, because an unverified correction would make the report look cleaner without making the underlying record more certain.
Source and scope
This case study is based on Antonina Wambui’s DEV Community article, “Turning Vehicle Sales Data into Actionable Business Intelligence: A Power BI Analysis of JCars Logistics”. The separate figures are described in a LinkedIn profile excerpt attributed to Young Odhiambo; they are not reconciled with Wambui’s account.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsQuick 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.
