How to Set Up SCORM Content Dispatch to Multiple LMSs

If you sell or distribute training content to organizations that each run their own LMS, you face a fundamental logistics problem: how do you deliver the same course to dozens of different systems while retaining visibility into learner progress? The answer is content dispatch — a pattern that lets you host content once and distribute lightweight launch packages to any number of client LMSs.

What Is Content Dispatch?

Content dispatch separates where content is hosted from where content is launched. Instead of sending a full SCORM ZIP to each client, you send a small dispatch package — a thin SCORM wrapper that, when launched inside the client’s LMS, redirects to the content hosted on your platform. All runtime data (completion, scores, time) flows back through your hosting layer, giving you a single source of truth across every client.

This model is essential for training companies, content marketplaces, association education programs, and any organization that sells or licenses courseware to external customers.

The Old Way: ZIP and Pray

Before dispatch, the standard workflow for distributing SCORM content looked like this:

1. Export a SCORM ZIP from your authoring tool.
2. Email or upload the ZIP to each client.
3. The client’s LMS admin imports the package manually.
4. Learners complete the course inside the client’s LMS.
5. You have zero visibility into completions, scores, or engagement — the data lives entirely inside the client’s system.

When you need to update the course, you re-export the ZIP, re-send it to every client, and hope they re-import it. Version drift is inevitable. Tracking is nonexistent. Support requests multiply because each client runs a different LMS version with different SCORM quirks.

The Dispatch Way

With content dispatch, the workflow becomes:

1. Upload your SCORM package to AllureConnect once.
2. Create a dispatch for each client with per-client configuration (license limits, expiration dates, allowed domains).
3. Share the dispatch link or export a lightweight dispatch ZIP that the client imports into their LMS.
4. When a learner launches the course in the client’s LMS, the dispatch wrapper redirects to AllureConnect-hosted content. The SCORM runtime runs on AllureConnect’s infrastructure.
5. All tracking data flows back to your AllureConnect dashboard, segmented by client. You see completions, scores, and time across every dispatch from a single view.

Step-by-Step Setup with AllureConnect

1. Upload Your SCORM Package

Upload your SCORM 1.2 or SCORM 2004 package via the dashboard or the REST API. AllureConnect validates the manifest, extracts metadata, and hosts assets on a global CDN. The package is now ready to be dispatched.

2. Create a Dispatch

A dispatch ties a specific SCORM package to a specific client. You configure per-client controls at creation time:

• License limit — maximum number of unique learners who can launch the content.
• Expiration date — automatically disables the dispatch after a certain date.
• Domain allowlist — restricts launches to specific domains (e.g., only from the client’s LMS domain).

Here is an example of creating a dispatch via the AllureConnect API:

curl -X POST https://api.allureconnect.com/v1/dispatches \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "packageId": "pkg_abc123",
    "name": "Acme Corp - Compliance Training Q2",
    "licenseLimit": 500,
    "expiresAt": "2026-12-31T23:59:59Z",
    "allowedDomains": ["lms.acmecorp.com"],
    "tags": ["client:acme", "course:compliance-q2"]
  }'

The API returns a dispatch ID and a launch URL. You can also export a dispatch ZIP — a minimal SCORM package that the client imports into their LMS just like any other course.

3. Share with Your Client

You have two options for getting the dispatch into the client’s LMS:

• Dispatch ZIP — download a lightweight SCORM package (typically under 50 KB) that the client imports into their LMS. This works with any SCORM-compliant LMS without custom integration.
• LTI 1.3 link — if the client’s LMS supports LTI, you can provide an LTI launch URL instead. This avoids the SCORM import step entirely.

4. Monitor Per-Client Analytics

The AllureConnect dashboard shows analytics segmented by dispatch. For each client you can see total launches, unique learners, completion rate, average score, and average time spent. You can also query this data via the API for integration with your own reporting tools.

Per-Client Controls

Dispatch is not a one-time operation. After creating a dispatch, you retain full control:

• Revoke access — disable a dispatch instantly if a client’s contract expires or they violate terms.
• Update content — upload a new version of the SCORM package and all dispatches automatically serve the latest version. No re-export, no re-import.
• Adjust limits — increase or decrease license limits, extend expiration dates, or modify domain allowlists via the API or dashboard.

Dispatch vs Direct Hosting vs ZIP Export

When to Use Content Dispatch

Dispatch is the right pattern whenever you need to deliver the same content to multiple organizations while retaining control over hosting, versioning, and analytics. Typical use cases include:

• Training companies selling courseware to enterprise clients.
• Associations distributing continuing education to member organizations.
• Software vendors embedding training in customer onboarding.
• Compliance teams distributing mandatory training across business units with separate LMS instances.

If you only host content for your own learners on a single LMS, direct hosting via AllureConnect’s launch URLs is simpler. But the moment you have a second client or a second LMS, dispatch pays for itself in reduced support overhead and unified analytics.