Your ERP Thinks a Pallet Is a Product. Let That Sink In.

The consultant arrived on Monday. She was very nice. She had a PowerPoint. The PowerPoint had 47 slides. Slide 1 said "ERP Implementation — ITAD Module" and had a picture of a warehouse that looked nothing like your warehouse, because your warehouse has bad lighting in Zone C and a forklift with a dented bumper, and the warehouse in the picture had track lighting and a woman in a hard hat who appeared to be smiling at a clipboard.

By Friday, you had a project plan, a timeline, and a budget. €80K for the implementation. Six months. The consultant was confident. Your CFO was relieved. Finally, a real system. No more FileMaker. No more Raymond.

Six months later, a pallet of mixed-grade HP EliteBooks with three different keyboard layouts — AZERTY, QWERTY, and QWERTZ, because the lot came from a multinational — was registered in your new ERP as a single "product" with a quantity of 1 and a description that said "HP laptop." Not "HP EliteBook 840 G8." Not "mixed grade." Not "three keyboard layouts." Just "HP laptop." Quantity: 1.

The ERP isn't broken. The ERP is working exactly as designed. The ERP was designed for a world where products are identical, countable, and interchangeable. A pallet of HP EliteBooks is none of those things.

The Vocabulary Mismatch

Here is a non-exhaustive list of things your ERP doesn't have a word for:

Mixed-grade lot. The ERP has "products" and "product variants." A variant might be "colour: blue" or "size: large." It does not accommodate "grade: B, except for 12 units that are C because the palmrests are scratched and 3 that are D because the screens flicker." That's not a variant. That's a situation.

Per-drive erasure status. The ERP tracks serial numbers, sure. But it tracks one serial number per product. A laptop with two SSDs, each needing independent erasure and certification? The ERP suggests creating two "products." One for each drive. Attached to… the laptop somehow. It gets complicated fast and nobody likes where it ends up.

Grading freshness. The grade you assigned six weeks ago may no longer be accurate. Battery health degrades. Cosmetic assessments age. The ERP has no concept of a grade that expires. Grades are facts. Grades in ITAD are opinions with a shelf life.

Chain of custody. The ERP tracks warehouse movements: location A to location B. It does not track the reason for the movement, the person who authorised it, or the compliance implications. In ITAD, a device moving from "processing" to "quarantine" is not the same as moving from shelf 3 to shelf 4. The ERP thinks it is.

An ERP that has been "customised for ITAD" is not an ITAD system. It's a general-purpose system that has been argued with until it stopped complaining.

The Consulting Sessions

When the vocabulary mismatch became apparent, the consultant came back. More sessions. More PowerPoints. More "we can configure that." The word "configure" did a lot of heavy lifting. What it meant in practice was: we'll add custom fields until the system approximates what you need, at which point it will be too customised to upgrade and too specific to support.

Three consulting sessions later, you had a system that technically tracked grades (in a text field), sort of handled multi-warehouse (with a location prefix hack), and could generate erasure reports (if someone exported a CSV and ran it through a Python script that your IT manager wrote one weekend).

Total cost: €80K implementation plus €45K in consulting sessions plus €12K in annual customisation maintenance plus the salary of one person who spends 30% of their time working around limitations instead of doing their actual job. That's not a solution. That's an arms race between your requirements and the ERP's willingness to pretend it understands them.

Why ERPs Fail at ITAD

The fundamental problem isn't technical. It's conceptual. ERPs are built on the assumption that your business sells products. Products are defined, manufactured, warehoused, and sold. Each product has a SKU. Each SKU describes an identical item. The inventory count tells you how many you have. Simple.

ITAD doesn't sell products. ITAD processes individual assets. Each one is unique. Each one has its own serial number, its own condition, its own history, its own grade, its own erasure status, its own chain of custody. A "pallet of 50 Dell Latitude 5430s" is not 50 identical items. It's 50 individual stories that happen to share a model number. An ERP treats them as 50 copies of one thing. ITAD treats them as 50 different things that merely look similar.

That conceptual gap is what €80K and three consulting sessions couldn't bridge. Not because the consultant was bad. Because the gap is architectural, and no amount of custom fields can turn a product-based system into an asset-based one.

---

Your ERP is excellent software. For manufacturing. For retail. For distribution. For any business where products are identical and interchangeable. ITAD is not that business. Your pallet is not a product. Your grade is not a variant. Your erasure certificate is not an attachment.

The consultant was right about one thing, though: you did need a real system. You just needed one that was built for this.