← All work

Related commerce workstream / Commerce & customer onboarding

Activation Codes as a Fulfillment Architecture

Fulfillment architecture within the checkout and onboarding work

The platform needed to represent a completed purchase before all account, registration, or recipient information was available. This work introduced activation codes between checkout and final setup, giving the buyer or recipient a way to complete the remaining steps later.

The contribution at a glance

Our role
Fulfillment modeling, backend implementation, and commerce integration.
Work delivered
Activation-code issuance and redemption, deferred assignment, and shared fulfillment across purchase channels.
Simplified view of the work
  1. 01

    Complete the purchase

    Record what was purchased before final setup or assignment.

  2. 02

    Issue activation

    Make the entitlement available to the buyer or recipient.

  3. 03

    Assign and redeem

    Complete registration or activation when the person is ready.

Scope & current status

A detailed workstream from the checkout and customer-onboarding engagement.

See the full checkout and fulfillment case

The challenge

Payment, registration, and assignment were treated as one event. That made buying for someone else or completing setup later difficult. Additional sales channels also needed a consistent way to hand purchases into the platform without reproducing the original onboarding sequence.

The approach

The fulfillment model introduced an activation code representing what had been purchased. Order and payment handling could complete before final registration or assignment, while activation provided a defined path to connect the purchase to the appropriate account or record.

The implementation covered code generation, storage, validation, and redemption, alongside account mapping and order handling. Stripe Checkout and Shopify-compatible paths used the same fulfillment rules.

The work in detail

  1. 01

    Separate purchase from setup

    Allow a completed purchase to exist before the information needed for final registration or assignment is available.

  2. 02

    Implement activation

    Define code issuance, validation, and redemption as part of the fulfillment workflow.

  3. 03

    Connect sales channels

    Use common backend fulfillment behavior for supported direct and partner purchase paths.

  4. 04

    Support the eventual user

    Let the buyer or recipient finish setup at the appropriate point in their journey.

The outcome

The platform could hold a completed purchase for later setup and support gifting or purchases for someone else. Shared activation behavior connected the supported sales channels to the same fulfillment process.

Why it matters

Products and services that require later setup need a clear relationship between payment and activation. Representing those steps separately lets the buying experience fit the customer while preserving the information needed to deliver what was purchased.

Related work