Spreadsheets vs dismantling software.

1. Where spreadsheets work — and where they stop

Spreadsheets work well for a one-person, one-yard operation with a single channel and weekly cadence. The state of the yard fits in one tab. Stock fits in another. Orders fit in a third. As long as one person owns the workbook, the workbook reflects reality. The owner has the whole yard's state in their head and in the workbook; the workbook is the visible echo of the operator's own working memory.

The failure mode begins with the second editor. Two people editing the same workbook produce two states. The mismatch is invisible until a part is sold twice or a vehicle is depolluted twice. By the time it surfaces, the trail to who did what and when is gone — the spreadsheet's revision history is by file, not by row, and the row the buyer asked about may have been edited by either operator at any point in the day.

The failure mode worsens with the second channel. A spreadsheet that drives one storefront can be kept aligned by force of will. A spreadsheet that drives two storefronts and a counter sale is already out of date the moment a part sells on any one of them. The yard discovers the gap when a buyer pays for a part the yard cannot ship — a process that does not scale up because each failure costs a relationship.

2. Concrete failure modes

The patterns below come up in every audit of a spreadsheet-run yard. They are not abstractions. They are the reasons the yard hires a developer to build a database after the third painful month.

• Stock drift — a part is sold on PrestaShop and the spreadsheet still shows it on the shelf. The buyer pays for a part the yard cannot ship.
• Grading inconsistency — two inspectors apply two rubrics. The buyer of a B-grade headlight gets the A-grade unit from the other inspector and the returns rate climbs.
• Missing audit trail — a vehicle is depolluted on Monday and the certificate is dated Friday because the spreadsheet only updates when someone remembers. An inspector cannot tell which event came first.
• Lost parts — a part is dismantled but never makes the spreadsheet. It sits on a shelf for a year, not listed and not findable.
• Pricing staleness — a price last updated six months ago is the price the sales operator quotes today. Margin compresses without anyone noticing.
• Channel desync — three storefronts and one spreadsheet means three storefronts in three states.
• Compliance gaps — depollution certificates and CoDs produced in Word against the spreadsheet do not survive a meaningful inspection.

3. What dismantling software replaces them with

Purpose-built dismantling software replaces the spreadsheet stack with a single source of truth, a workflow-aware state model, and a chain of custody from VIN to invoice. Stock state is event-driven, not file-based. Two operators editing the same vehicle see each other's changes; the audit trail records who did what and when. Reservations and returns ripple through stock automatically. Channel sync is event-driven, not weekly.

The same shift applies to compliance. Depollution certificates and Certificates of Destruction are produced from inside the workflow that actually performed the depollution. The paperwork is a query against existing data, not a separate authoring exercise.

4. The transition itself

The transition out of spreadsheets is the part most yards under-budget. Vehicles, parts, customers, and recent orders need migrating; staff need training; integrations need standing up. Migration tools help, but the bigger cost is the cutover discipline — running both systems for a short window, choosing the platform as the source of truth, and accepting that the spreadsheet becomes a read-only archive at the cutover date.

Sustain360 runs the cutover as a staged plan with the named professional services team. Most Single-Yard cutovers complete inside two to four weeks; Multi-Yard cutovers are six to twelve weeks depending on integration scope.

5. The compliance gap, in detail

Compliance is the place a spreadsheet-run yard most reliably fails an audit. EU ELV directive evidence requires a per-vehicle record with depollution actions, operator identification, dates, material streams by weight, and downstream transfer notes — a level of detail no spreadsheet maintains organically. UK ATF audits ask for the same shape against the DVLA's Certificate of Destruction filings. The audit asks the yard to reconstruct the chain from a hundred separate documents and tabs.

Purpose-built platforms produce the audit-grade record as a query against the workflow that actually performed the work. Depollution certificates are generated by the depollution stage itself, signed at the moment the operator completes the state transition, and stored against the source VIN indefinitely. Certificates of Destruction are filed to the DVLA from the report stage with the audit trail attached. An inspection becomes a CSV export with the current filter applied, not a week of authoring effort.

The cost of the compliance gap is rarely the inspection itself — it is the operator time the yard spends preparing for one. A platform that turns the audit into a query saves the time the yard would otherwise spend reconciling spreadsheets, Word documents, and a year of paperwork.

6. When spreadsheets still win

A pre-revenue operator with one vehicle a month does not need dismantling software. A consulting analyst evaluating yard performance against three different KPIs may rightly do that work in a spreadsheet because the spreadsheet is the better analytic surface for the question. The argument here is not that spreadsheets are bad — it is that they stop scaling at a point most yards reach faster than they expect.

Spreadsheets also remain a perfectly good output format. Every grid in Sustain360 exports to CSV with the current filter applied, and accounts and operations teams routinely keep their reconciliation work in spreadsheets after the cutover. The system of record moves, but the analytic surface stays portable. Treat the spreadsheet as one tool in the kit, not as the yard's source of truth.

7. A short decision rubric

If you can answer yes to two or more of the questions below, the spreadsheet stack has stopped scaling and dismantling software pays for itself within the year.

• Do two or more people edit the same workbook?
• Do you list parts on more than one channel?
• Do you handle ELV or ATF paperwork against a regulator?
• Have you sold a part you could not ship in the last quarter?
• Has your returns rate climbed without an obvious cause?
• Do you employ a dedicated person for reconciliation between systems?
• Are you within a year of opening a second yard?