- How do I decide which salvage cars to buy at auction?
- Buy the loss types that yield your short parts, not the cheapest lots. The dashboard scores supply-versus-demand coverage for every part, flags which front-end parts stay chronically short, and produces a ranked auction buying list naming the specific loss types and models to target next. For example, source end-of-life Fiat Uno and Palio to close a 47-unit gap.
- Why are my highest-demand parts always out of stock while other stock sits unsold?
- Your auction intake is misaligned with demand. Front-collision cars dominate the buying, and front-collision damage destroys exactly the parts customers order most: bumpers, hoods, headlamps, grilles, windshields, fenders. Rear, side and interior parts then pile up unsold. The fix is buying different loss types, not spending more.
- Does it connect to our ERP or database, or only work from spreadsheets?
- In this build the three inputs (vehicles bought, parts recovered, customer orders) are CSV datasets. The architecture supports live database or ERP connections through the Workflows layer without changing any of the six views, so demand and intake data flow in automatically once connected.
- How does it calculate whether a part is short or overstocked?
- It divides listed supply units by completed-order demand units to get a coverage score for each part. Below 85% is a shortage; above 125% is surplus that ties up cash. A part at 60% coverage means only six in ten orders for it can currently be filled, and the rest wait for stock.
- How does it know which cars to buy for a specific short part?
- For each short part, the app traces every listed unit back to the vehicle it came from, reads that vehicle's loss type, and counts which loss types yield the part most often intact. The top loss types and models become the auction buying instruction, sized to the exact unit gap for that part.
- Is this available to use now?
- This parts-sourcing dashboard is a demonstration build shown as a walkthrough, marked coming soon rather than generally available. It runs across six views (Overview, Intake, Demand, Revenue, Mismatch and Recommendation) on CSV datasets, and is built to connect to live systems through the Workflows layer when deployed.