A washing machine shows up on the dock. Two hours later it is fifteen sellable parts — a motor, a control board, a pump, a door latch, an agitator, a set of wiring harnesses. Each part has to be sorted, documented, and listed for sale.
Sorting is the first call: which parts are worth keeping, which get scrapped, and where the keepers go on the shelf. Documenting is the record: a SKU, a photo, a location, and an answer to “what does this fit?” Listing is the marketplace step: a title, a price, and a live listing on eBay or Shopify.
The same shape repeats with every inbound unit, every day.
We built Ordovee to streamline that process — to make sorting faster, documentation easier, and listings quicker to get live. One system tracks every step from disassembly to sale.
What is Structured Disassembly Management?
Structured Disassembly Management (SDM) is a category of software for operations that take whole units apart and sell the parts. It tracks three things at once: the disassembly workflow, the parts inventory that results, and the fitment linking each part to the units it fits. Ordovee is a Structured Disassembly Management platform — we named the category because our own work needed it.
The shape of disassembly work
Disassembly is its own discipline. Inbound equipment arrives — appliances, vehicles, HVAC units, powersports, marine engines, computers, lawn and outdoor equipment. Each part runs the same checklist: photo, ID, SKU, bin, listing on eBay or Shopify.
A single inbound unit can become forty sellable parts. Each one is one-of-one until the next donor unit arrives. The catalog is long-tail by definition — most parts sell slowly but profitably, sometimes months after the part hit the shelf.
That work has a particular shape:
- High SKU count, low quantity per SKU. A disassembly operation with two hundred donor units already has thousands of distinct parts. Most have a quantity of one.
- Identification is half the job. A pump from a 2018 Whirlpool is a different part than a pump from a 2014 Whirlpool. Knowing what fits what is the difference between a part that sells and a part that sits.
- Marketplace selling is the default. eBay, Shopify, occasionally Reverb or Mercari. Buyers search by the model they own — which means the catalog has to be wired up with fitments before listings convert.
- The warehouse is the operation. Bins, shelves, labels, a scanner, a printer. The software has to keep up with the floor.
Where the friction shows up
Walk through a typical teardown day before purpose-built software exists for it:
- An inbound unit comes in for teardown. Each part needs a SKU. The SKUs end up on a sticky note, a clipboard, or in someone’s notebook.
- The parts go into a staging bin labeled “to-be-listed.” Some have tags. Some don’t. The lister has to identify each one again at listing time.
- Listing means opening eBay, searching for similar parts, typing the title, uploading photos, setting the price. Five to ten minutes per part. Forty parts off one donor is half a day at the keyboard.
- A part sells. The shelf quantity drops by one. The eBay quantity drops by one — if the integration is keeping up. The spreadsheet might get updated, or might not.
- A customer asks “do you have a window regulator for a 2019 Sienna?” Someone walks to the shelf. Or checks their memory of what came off the donor unit two months ago.
- A new hire arrives. The knowledge of what came off which donor lives in one person’s head. Onboarding takes weeks.
Each of these is a place where time leaks, mistakes get expensive, and the system lives in someone’s head instead of in the software.
Want to see what the alternative looks like? Walk through the product overview →
What we set out to build
Two halves, given equal weight from the start: inventory management and catalog cross-reference.
The inventory side is the ledger — every count, every move, every adjustment recorded permanently. The system of record lives in one place. Counts roll forward whether the part is sitting in a starter bin during the first week of setup or in a labeled location three months later.
The catalog side is the compatibility layer — every part linked to the units, vehicles, or equipment it fits. Once a part is mapped, “do you have one for a 2019 Mercury 90hp?” becomes a search that returns a list. The compatibility mapping guide covers how the wiring works.
Both halves talk to each other. A buyer searches by the model they own on eBay. Ordovee knows which SKUs match. The marketplace shows the part is in stock because the mirror and the automation engine kept eBay’s quantity current. The order comes in, gets reserved, gets picked, gets shipped, and the ledger records every step.
How that shows up in the product
The decisions made at the start are the decisions you see everywhere now:
- The ledger is the system of record. Every count, every move, every adjustment is permanent. The screens you see are derived from it. The ledger explainer covers how that works in practice.
- SKU normalization is built in. Bulk SKU generation for blank fields, leading-zero protection, case normalization, duplicate warnings. The SKU strategy guide covers why this matters.
- Compatibility runs in parallel. Fitment search from either direction — find every part that fits, or find every model a part fits.
- Marketplace sync is structured. eBay and Shopify listings get mirrored, orders get imported, quantities get pushed back. The automation engine runs on its own schedule and saves a bookmark so it picks up exactly where it left off.
- You start where you are. One bin, one shelf, one connected marketplace, one CSV import. The system returns value from the first piece you add. Warehouse Organization, One Shelf at a Time walks through the gradual approach.
- The floor is treated as the operation. Scanner-first picking, location labels, handheld workflows, label printing. The desktop is for reports — the floor is where parts move. The scanner-first picking guide walks the warehouse half.
That is what designing for disassembly actually means inside the product. Not a feature list — a shape.
Why this niche deserves its own tool
Disassembly sits in a corner of resale with a specific profile: high SKU diversity, low quantity per SKU, marketplace-driven sales, long-tail inventory aging, fitment-driven discovery, and a physical workflow where the bin is what’s real on the warehouse floor. Appliances, vehicles, HVAC, powersports, marine, electronics, heavy equipment, restaurant equipment — each industry has its own donor units, its own fitments, its own buyer search patterns. The common thread is the workflow: unit in, parts off, listed, tracked, shipped.
Every design decision in Ordovee traces back to that profile. The ledger handles the inventory record. Compatibility handles the catalog record. The automation engine handles the marketplace plumbing. The handheld workflows handle the floor.
If that describes your operation, the rest of the guide explains how each piece fits together. Start with ledger-based inventory and compatibility mapping — those two cover the load-bearing concepts.
Wondering if ODV is the right fit for your disassembly operation? Let’s find out together — we’ll walk your own SKUs and marketplaces through the workflow, so you can see what it does with your data.
How do you keep track of parts when you part something out?
Give each part a SKU the moment it comes off the unit, tie it to the donor unit it came from, and record its location — one system of record instead of a spreadsheet only one person can read. From there, listing, picking, and counting all read from the same record.
→ How the inventory records underneath work: Ledger-based inventory → How the catalog cross-reference is built: The catalog you build → Want to talk through your disassembly workflow? Let’s talk
See Ordovee in your operation.
The fastest way to know if ODV fits your shop is to see the workflow with your own data — no slides, no scripted demo.