FOR ERP INTEGRATORS AND IMPLEMENTATION PARTNERS
Your clients already record their surplus. They see it every time someone runs an ageing report, and then nothing happens, because no one owns the process that would turn it into cash. You already have the data access, the field mapping and the client trust that a recovery project needs. Dead Stock supplies the workflow that sits on top.
Pilot
Referral, implementation and technology partner models. A first client pilot can run from a CSV export.
A four-column diagram: client environment data, the partner scoping, mapping, validating and configuring, the Dead Stock recovery layer, and the client outcome of approved offers, matched demand and recovery reporting, with a dashed path showing the partner reporting outcomes to the client.
WHY THIS IS WORTH YOUR TIME
Not a reseller pitch. These are the reasons an implementation partner would build this into their own offering.
PARTNER MODELS
Commercial terms depend on the partner role, attribution and deployment model.
Implementation revenue stays with the partner. Platform terms are agreed separately.
Terms depend on the deployment model and on who owns the client relationship.
DELIVERY METHOD
This is the method, not a marketing timeline. Every step has a deliverable a client would recognise.
PilotIn development
Find the category where surplus is known, quantifiable and safe to release. Usually procurement already knows which one it is.
One category, existing fields, no cleanup. The messier the sample, the more useful the test.
Match client columns to the inventory schema. This is your core competence and the step that most determines pilot quality.
Establish what is present, what is missing and what is inconsistent, before anyone forms an expectation.
Categories in scope, exclusions, ageing and movement thresholds, safety-stock protection.
Run enrichment on the sample and take the results through client review.
Pricing policy set, visibility chosen, offers approved and released at the agreed scope.
Measure against the baseline agreed at the start, and decide with the client whether to widen the scope.
An eight-step partner delivery timeline from identifying the use case through export, field mapping, quality validation, rule configuration, enrichment and approval, launch and outcome reporting.
TECHNICAL STARTING POINTS
The integration path is chosen after the pilot has proved the value, not before it. Reversing that order is how surplus projects die in a scoping workshop.
PilotIn development
Named ERP vendor connectors are not advertised. A vendor name will be published only when a connector has run end to end in a live deployment and the status has been verified with the vendor. If you have already built one, that is exactly the conversation the technology partner model exists for.
ENABLEMENT KIT
Materials you can put in front of a client without rewriting them first.
The enablement kit is delivered on partner onboarding. Items are added as they are produced; nothing on this list is a placeholder for something that does not exist yet.
Eight cards naming the partner enablement materials: demo environment, sales one-pager, discovery checklist, data sample template, field mapping templates, architecture sheet, pilot proposal template and co-branded material.
Partner commercial terms depend on the partner role, attribution and deployment model.
Attribution is agreed in writing at the point of introduction, before any client conversation happens. That is the part worth getting right early.
Any system your client can export from. Dead Stock deliberately does not publish a supported-vendor list, because a list implies a tested connector and none has been verified for public use yet. The path is the export or the feed, and your mapping expertise is what makes it work.
No. A connector is an optimisation for something already proven. A first pilot on a controlled export tells the client more, faster, and at a fraction of the cost.
Yes, and it is the recommended route. One category, existing fields, no cleanup beforehand.
In the implementation partner model, you do. You scope the data path, map the fields, validate quality and run the pilot with the client. Dead Stock supplies the platform, the enrichment and the workflow behind it.
Referral, implementation and technology. The specific terms depend on the role, on attribution and on who carries the deployment. They are agreed in writing before a client conversation starts.
Yes, within the implementation and technology models. Co-branded material is available on request once attribution is agreed.
It stays yours. Dead Stock is not looking to displace the partner who owns the account, and the responsibility model on the how-it-works page is written down precisely so that this does not become an argument later.
Only what the client approves in the export. A sample is normally inventory master data and movement history for one category. No financial system data, no personal data, and nothing outside the agreed category.
Tell us which systems you work with and which client situation prompted this. The first conversation is technical, not commercial.