That pallet of mixed-grade EliteBooks
in quarantine zone three?
We know where it is.
One system for everything between the dock and the deal. Receiving. Testing. Grading. Erasure. Storage. Shipping. Settlement. Built for people who know the difference between a pallet position and a prayer.
Not an ERP that needed three consulting sessions to learn what “mixed-grade lot” means. Not a warehouse system that thinks your lease return laptop and a forklift are the same SKU type. Software that was built in the warehouses. You can tell.
Sounds familiar?
Your current Tuesday afternoon.
On the left: what happens now. On the right: what happens when your tools were actually built for this job.
You ask Dave where that pallet of mixed-grade HP EliteBooks is. Dave is on lunch. Dave is always on lunch when you need him.
Rack B2, Position 3-1, Zone: Storage, Amsterdam Main. Dave can finish his sandwich.
"Grade B" means one thing to you, another thing to your buyer in Stockholm, and a third thing to the person who graded it before their second coffee.
Functional F2. Cosmetic C3. Battery B2. Data D0. Every buyer on the planet reads that the same way. Arguments over.
The R2 auditor asks for erasure records. You open your inventory system, then the Blancco portal, then a shared drive, then a folder called "Certificates 2025 FINAL (2)." The auditor is not impressed.
You give them a URL. They download a certificate per device. Per drive, actually — because the auditor knows that laptop had two SSDs and so does your system.
A lease return arrives from ING: 340 laptops, 12 pallets. The manifest says Dell Latitude 5430. You open the first box. ThinkPad T14. This is going to be a long day.
Scan against the manifest. Discrepancies flagged in real time. "Expected: Dell Latitude 5430. Received: Lenovo ThinkPad T14. Manifest line 47." Now it's the lessor's problem, not yours.
"Our system can't track which SSD was in which laptop." "Then how do you prove erasure per storage device?" "...We have a process." "Is it documented?" "...We have a spreadsheet."
Drive SN WD-2026-44821 was in Laptop RV-000003412. Erased at 14:22 on March 3rd. Method: NIST 800-88 Purge. Certificate: BLC-2026-4421. The auditor nods. You move on with your life.
The lease return has been sitting in receiving for three weeks. Nobody knows if it needs testing first or manifest verification first. The SLA was 10 business days. It's now day 15.
Receive → Verify manifest → Test → Grade → Calculate chargebacks → Generate settlement. Step 4 of 6. SLA: 10 days. Day 7. You're ahead of schedule. For once.
What Core does
Every step from dock to deal.
One database. Zero re-keying. When you scan an asset at receiving, it flows through testing, grading, erasure, storage, and settlement without anyone copying a serial number into a different system. Because life is too short for that.
Receiving & Check-in
Twelve pallets at the dock. A manifest that's already wrong. A driver who needs his truck back by 3pm. Scan the barcode. The asset appears, linked to the order, the client, the contract. Labels print. Serial numbers match — or don't, and the system tells you which ones before you've finished the first pallet.
Testing & Diagnostics
A laptop gets a battery health check. A server gets a RAID controller test. A phone gets a camera and FaceID test. Your ERP would give all three the same form and call it "quality inspection." We wrote different checklists because we've actually tested these devices. With our hands. In a warehouse. That smelled like cardboard.
Grading
You know that argument you've been having since 2019 about what "Grade B cosmetic" means? It's over. Functional grade. Cosmetic grade. Battery grade. Data security grade. Structured scales. When your buyer in Munich and your supplier in Copenhagen both see "C3," they're picturing the same scratches. Finally.
Data Erasure
NIST 800-88. Per drive, not per device — because that Dell Latitude with two NVMe drives needs two certificates, and your auditor knows it even if your current system doesn't. Blancco-compatible reports attach automatically. When the compliance team comes knocking, you hand them a link, not a filing cabinet.
Warehouse
Zones. Racks. Positions. Pallets. Not "Location: Building C" — actual warehouse topology where Rack A3, Position 2-4 means something specific and anyone can walk there and find it. Even the temp. Even on a Friday afternoon. Even during the Christmas rush when your three best people are skiing in Austria.
Workflows
A lease return laptop from Econocom needs different steps than a recycling-bound Dell server from your municipality contract. Different client, different SLA, different chargeback rules, different everything. Build the workflows. Assign the people. Track the SLAs. Know which step is late before the client calls to ask.
Contracts & Pricing
Per-unit pricing for the broker. Per-kilo for the recycler. Revenue share for the lease company. A hybrid model for that one client who insisted on something nobody had ever seen before and somehow got it approved. All of them in one system. With their SLAs, their chargebacks, their payment terms.
Logistics
Inbound: expected manifests, carrier tracking, dock scheduling. The driver calls to say he'll be two hours late — you adjust the dock slot and the warehouse team sees it instantly. Outbound: pick lists that actually match the rack positions, packing slips that don't require a PhD, and loading reports that your client can read without calling you.
Inventory
Every asset has a status. That status is earned, not assigned. You can't mark something "ready for sale" if it hasn't been tested, graded, and wiped. The system won't let you, because the system has met your optimistic sales team and has decided to trust the warehouse instead.
Settlements
The lease return is done. 340 laptops tested, graded, wiped. 12 failed. 4 missing from the manifest. The chargeback rules from the contract say €400 per missing device, €120 per cracked screen. The settlement calculates itself. You review it. The client reviews it. Nobody argues, because the numbers came from the same system both of you can see.
Why Core first
You can't sell what you can't verify.
When a buyer on ReVend Market sees “500 Grade B Dell Latitude 5420s,” Core has already confirmed they exist, are Grade B, have been wiped, and are sitting in Rack C1 at Amsterdam Main. The listing didn't come from a stock list someone exported on Tuesday. It came from the same database that tracked those laptops from the moment they rolled off the truck.
Market can't list what Core hasn't verified. Auction can't auction what Core hasn't graded. Escrow can't release funds until Core confirms delivery. That's not a policy. That's the architecture.
Not another ERP. Not another WMS.
Your ERP thinks a laptop and a forklift are both "products." Your WMS thinks a pallet of mixed-grade EliteBooks is a "unit." Your erasure tool has never heard of either system.
ReVend knows what a pallet of mixed-grade EliteBooks is. It knows each laptop inside it has a serial number, a grade, an erasure certificate, and a position in your warehouse. Because we built it for this. Only this.
Your custom FileMaker database costs €30K every time you need a new field. The developer who built it is either retired, expensive, or both.
A platform that ships updates continuously. The version you use in December is better than the one you started with in July. No developer required. No consulting sessions. No "we'll put that in the next release" that never comes.
Your three systems don't talk to each other. Your inventory says one thing, your erasure portal says another, and your sales team is quoting from a CSV they found on the shared drive.
One system. One truth. When a device is graded, the inventory reflects it. When it's wiped, the certificate attaches. When it's sold, it disappears from available stock. Everywhere. Instantly. Not "after the next sync job."
Ready to stop explaining ITAD to your ERP?
Founding members get 12 months free. We launch in July 2026.
Your spreadsheet won't miss you. We checked.