Partner Certifications That Expire, and Why They Should

A partner certification is a claim you are making to a customer on a partner’s behalf. The expiry date is what keeps it true.

---

Partner certification programs tend to start with the content — build the course, write the quiz, issue the certificate — and treat validity as a formality set at the end. It is the opposite: the validity rule is the part that determines whether the certificate means anything, and it should be decided before the first course is written.

What a certificate actually asserts

When a partner displays your certification, they are telling a customer that your company vouches for their competence with your product. That is a real claim and it has a shelf life, because your product changes and people move on.

A certificate with No expiry asserts that competence permanently. For a foundational credential — understands what the product is for, can run the basic motion — that may be correct. For anything touching current mechanics, pricing, or a specific cloud’s rules, it is a claim that quietly becomes false without anybody noticing.

Validity, then renewal

Two settings, and the second only appears once the first is not “No expiry”:

Validity — No expiry, 6 months, 1 year, 2 years, or 3 years. The useful question is not “how long is generous” but how long until this content would be wrong. A certification covering marketplace listing mechanics ages faster than one covering your product’s value proposition, and they should not carry the same validity.

Renewal — once there is an expiry, you choose between:

• Manual retake. The learner renews voluntarily. Honest, and it means lapses happen. Appropriate where the credential is a differentiator the partner wants to keep.
• Auto re-enroll. The learner is re-enrolled automatically when the certificate expires. Appropriate where the certification gates something — access, a tier, a deal-registration privilege — and a lapse would have consequences you would rather prevent than discover.

The choice is really about who bears the cost of a lapse. If it is the partner, manual retake is fine. If it is your customer, auto re-enroll is the honest setting.

The branding fields are not decoration

A certificate carries a name, a description, background/text/accent colours, optionally a background image and a logo, and an Issued by line naming the team that stands behind it.

Two things worth knowing before you build one:

• The image fields take a hosted URL, not a file upload. Put your logo wherever your team hosts images first, then paste the link. This is the step that most often stalls a certificate half-built.
• “Issued by” is a real attribution. It is the name a customer reads when a partner shows the credential. Naming a specific team — Partner Enablement, say — is more credible than the company name alone, and it tells a partner who to ask when they have a question.

Attach it to a course, then check who holds it

A certificate is created independently and then assigned to a course, which keeps the credential and the content separate — a course can be revised without rebuilding the certificate.

Republishing a course does not update anyone already certified. A learner who completed the previous version stays tied to the version they completed. That is the right behaviour — you cannot retroactively claim somebody passed material they never saw — but it means a substantive course revision needs a deliberate decision about whether existing holders should retake it, and the validity period is the lever that forces the question.

The last step is the one programs skip: check who is certified. A certification program with no periodic look at who currently holds what is a program that cannot answer the only question a customer will ask — is the person working on my deployment actually certified today?

Frequently asked questions

Should partner certificates expire?

Usually yes. A certificate covering current product mechanics, pricing or cloud-specific rules becomes false as those change. “No expiry” is defensible for a foundational credential about what the product is for.

What is the difference between manual retake and auto re-enroll?

Manual retake means the learner renews voluntarily and lapses can happen. Auto re-enroll re-enrolls them automatically when the certificate expires. Choose by who bears the cost of a lapse — the partner, or your customer.

How long should a partner certification be valid?

Ask how long until the content would be wrong. Validity options are 6 months, 1 year, 2 years and 3 years, and a certification covering marketplace mechanics should carry a shorter one than a certification covering your product’s value proposition.

Can I upload a logo to a certificate?

No — the background image and logo fields take a hosted image URL rather than a file upload. Host the image first, then paste the link.

Does republishing a course update people already certified?

No. A learner who completed the previous version stays tied to the version they completed and is not updated automatically. A substantive revision needs a deliberate decision about whether existing holders should retake it.

Takeaways

• Decide validity before writing the course; it is what makes the credential mean something.
• Match the validity period to how fast the content goes stale, not to what feels generous.
• Manual retake where the partner bears a lapse; auto re-enroll where your customer does.
• Image fields take hosted URLs, not uploads — the usual place a certificate stalls.
• Review who currently holds what. A certification nobody audits answers no question worth asking.

More on running partner training in the partner relationship management overview.