Skip to main content

Codes, Expiration, Redemption & Refunds – Partner Guidance

For partners operating under Learnerbly’s checkout code model, this guidance covers code supply, management, redemption, and refunds, and explains the roles of both Learnerbly and partners to ensure learners have a seamless experience.

Written by Galina Grkovikj
Updated over 2 weeks ago

1. How the Checkout Code Model Works

  • Partners provide Learnerbly with batches of codes in advance.

  • Learnerbly distributes codes to users when purchased on the platform.

  • Partners invoice Learnerbly monthly for the codes sold during that period.

  • Code batches may be supplied at different times, and each batch may carry a different expiration date.

Because batches are issued on different dates, expiry timelines may vary across partners and individual allocations.


2. Code Expiration & Distribution Management

Learnerbly actively monitors all code expiration dates.

To protect the learner experience, we:

  • Track expiry timelines for all supplied batches

  • Avoid distributing codes that are close to expiration

  • Request replenishment from partners when batches are nearing expiry

  • Learnerbly aims to provide learners with approximately 30 days of validity from the date a code is issued to them.

Access instructions sent to learners state that codes should be redeemed within 30 days of issuance.


Partner responsibility:

  • Clearly communicate the expiration date of each batch supplied

  • Notify Learnerbly of any changes to validity periods

  • Provide advance notice of constraints affecting redemption timelines

Failure to notify Learnerbly of changes to code validity may result in temporary suspension of code distribution until updated details are confirmed.


3. Redemption Experience & Website Changes

To ensure learners can successfully redeem codes, partners must inform Learnerbly in advance of any changes that could impact the redemption process. This includes, but is not limited to:

  • Updates to the redemption flow or UX

  • Changes to where or how codes are entered

  • Modifications to account creation requirements

  • URL or landing page updates referenced in instructions

  • Website redesigns, rebranding, or platform migrations

Advance notice allows Learnerbly to:

  • Update learner instructions promptly

  • Test revised redemption flows

  • Prevent failed redemptions and reduce support cases

Failure to notify Learnerbly of material changes that impact redemption may result in temporary suspension of code distribution until updated instructions are reviewed and confirmed.



4. Refund Eligibility

  • Codes cannot be refunded once redeemed.

  • In exceptional cases, Learnerbly may coordinate with partners to determine if a redeemed or unused code can be invalidated and a refund issued.

Refunds are considered on a case-by-case basis, taking into account the nature of the digital resource and whether it meets Learnerbly’s refund criteria.


5. Refund Timeframe

  • Learnerbly users must submit refund requests within 14 days of purchase or code issuance.

  • Requests received after this period will not be considered.


6. Partner Role in Refunds

  • All refund requests must be handled through Learnerbly, since purchases occur on the platform.

  • If a Learnerbly user contacts a partner directly, the partner should redirect the user to Learnerbly.

  • Learnerbly will coordinate with the partner to determine appropriate next steps.


7. Steps for Processing Refunds

To ensure a smooth and consistent process:

  1. Record the Refund Request
    All learner refund requests are logged in Learnerbly’s tracking system for accurate record-keeping and follow-up.

  2. Request Code Invalidation
    Learnerbly will contact the relevant partner to request invalidation of the code associated with the refund. This prevents the code from being redeemed after a refund is issued.

  3. Confirm Refund Status
    Once the partner confirms that the code has been invalidated, Learnerbly will process the refund to the learner.

Partner role:

  • Respond promptly to invalidation requests

  • Communicate any issues or exceptions that may impact processing

This ensures refunds are handled efficiently, maintains integrity of code distribution, and protects both learners and partners.


8. Communication

For updates related to code batches, expiration dates, redemption flow changes, or refunds, please contact:

Did this answer your question?