You stopped ordering. But were there loose ends?

Supplier offboarding is the structured end of a supplier relationship: settling open orders, disputes, and credits, revoking access, deactivating the supplier across systems, and retaining the records. In Clover it runs as a workflow with owners and deadlines, so relationships end cleanly instead of fading half-open.

Deactivating a supplier in your ERP flips a status flag. It doesn't settle the open orders, recover the credits you're owed, revoke portal and system access, or capture why the relationship ended. Clover runs offboarding as an actual process: every loose end becomes an owned task, the deactivation syncs across your systems, and the reason is retained on record. The ERP flag is the last step, not the whole job.

Because half-ended relationships carry cost and risk: stray invoices that still get paid, credits never recovered, portal access never revoked, and quality lessons that vanish with staff turnover. A structured close settles the money, ends the access, and keeps the reason on record.

Ending a relationship touches procurement, AP, quality, and IT, which is exactly why it usually falls through the cracks, with each team assuming another handled it. Clover assigns every step an owner and a deadline, so final orders, disputes, credits, document retention, and access removal each have someone accountable, and nothing closes until all of it does.

No. Deactivation ends activity, not history. The full relationship record (documents, disputes, performance, and the documented reason for ending it) is retained under your retention rules, so a future re-engagement decision starts informed.

Yes. Reactivation starts from the retained record, and you can require a fresh assessment first, so a supplier dropped for cause doesn't slip back in through a new buyer who never heard the story.