One pipeline shape. As many workflows as your floor needs.
A full refurbishment line and a wipe-only rig don't belong on the same checklist. Define separate workflows for each, decide which stages run in every one, and let reCore route every device to the right one automatically.
The eight-stage pipeline
Same order, every time. Configurable stage by stage.
Most ITAD teams enforce process consistency with a laminated checklist taped to the bench, or nothing at all. A device skips a step because a technician was in a hurry, and nobody finds out until an audit does.
Every reCore workflow is built from the same eight stages, always in the same order. You decide which stages a given workflow runs and how each one is configured. What you can't do is reorder them or skip ahead: intake always precedes diagnostics, wipe always precedes grading, and so on.
| Stage | What happens |
|---|---|
| Intake | Asset tag or PO capture, automatic hardware discovery |
| Diagnostics | Hardware tests across every major component |
| Stress test | Multi-core burn-in under load |
| Wipe | Data sanitization, per drive |
| Imaging | OS image deployment |
| Grading | Cosmetic and functional grading |
| Quality gates | Decides where the device goes next |
| Post-actions | Labels, certificates, end-of-line handling |
A wipe-only rig can run just intake and wipe. A full refurb line runs all eight. Both are the same underlying pipeline, configured differently.
A workflow per line, not per exception
Start from a preset, or build your own.
Operations rarely run one process. A facility might process trade-in laptops on one line and enterprise off-lease servers on another, each with different stages, different wipe standards, and different grading rubrics.
reCore ships with system presets that cover the common cases out of the box: a full ITAD refurbishment line, a headless wipe rig, and a diagnostics-and-QA-only line.
- Use a system preset as-is, or clone it and adjust the copy to your own process
- Build a workflow from scratch for a process none of the presets cover
- Every workflow you create is scoped to your organization; presets are shared but read-only
- Change a workflow at any time. Devices already in flight keep the workflow they started with
Where each workflow applies
Configured once, resolved automatically, every time.
Deciding which process applies to which device shouldn't be a manual judgment call made fresh every morning. reCore resolves the right workflow for every device the moment it connects, based on rules you set once.
A workflow can be pinned to a specific batch, a specific station, a vendor, or a device type. When more than one rule could apply, the most specific one wins:
| Priority | Match |
|---|---|
| 1 | The batch the device belongs to |
| 2 | The station it connected to |
| 3 | The vendor it came from |
| 4 | The device type it reports |
| 5 | Your organization's default workflow |
| 6 | reCore's system default |
The dashboard's "Where they apply" view shows every rule in this order, so you can see exactly which workflow a device will get before it ever connects, not after.
Quality gates decide what happens next
Structured outcomes, not a spreadsheet of exceptions.
After wipe and grading, every device needs a disposition: resell it, refurbish it, harvest it for parts, or destroy it. Deciding that by hand, per device, is where throughput dies on a busy floor.
The quality gates stage encodes that decision into the workflow itself. Configure the outcomes your operation actually uses, and every device is routed to one automatically based on its test results and grade.
- Define your own outcome labels: ready for resale, needs refurbishment, parts harvest, recycle
- Route on test results, grade, or both
- Every device carries its outcome forward to labels, reporting, and certificates
See it in action
Start Free Trial