New: the SCORM Central WordPress plugin. Put a course on any WordPress page and see who finished. Get the plugin →

Start free →
DISPATCH

Sell the course. Keep the control.

If you license courseware to other organisations, dispatch delivers your course into their LMS while the content, the seat count, and the kill switch stay with you. The customer imports a small SCORM launcher package; the course itself stays hosted here, under limits you set.

THE PROBLEM

Emailing zips to customers is how control disappears.

The moment a customer imports your zip, you lose the thread: no idea how many seats they use, no way to expire access when the contract ends, and every content fix means asking their LMS admin to re-import — again.

SEATS

Seat ceilings you set

License 500 seats, deliver 500 seats. Registrations count against the ceiling you set per customer, and you can see usage without asking anyone.

EXPIRY

Access that ends when the contract does

Set an expiry date or revoke a dispatch outright. The package in their LMS stops launching; there is nothing to chase down or un-install.

UPDATES

Fix content without a re-import

The dispatched package is a pointer to the course you host. Correct a typo or replace a module, and every customer runs the new version on next launch.

REPORTING

Completions flow back to their LMS

The customer's LMS still gets the SCORM reporting it expects — completion, score, progress — while your dashboard shows registrations across every dispatch.

Zip vs dispatch

What changes when you stop emailing zips.

Emailing a SCORM zipDispatch
Fixing a typoSend a new zip; every customer's LMS admin re-imports itChange the hosted course once; every customer gets it on the next launch
Seats usedUnknown unless the customer tells youCapped per customer and visible in your dashboard
Contract endsThe course keeps running in their LMSSet an expiry date or revoke; the launcher stops
Completion and scoreRecorded in the customer's LMS onlyRecorded in the customer's LMS, with registrations in your dashboard
Customer setupImport a zipImport a zip: a small launcher package
StandardWhatever you builtSCORM 1.2 or 2004, chosen per dispatch
HOW IT WORKS

Three steps per customer.

Build or upload the course once. Create a dispatch for the customer — standard, seat ceiling, expiry. Send them one small zip that imports like any SCORM package. That's the whole handoff.

Dispatch is included in the Business plan: $129.99 a month, or $1,248 a year. Every dispatch gets its own seat limit, expiry date, and a revoke switch. Delivering to a lot of organisations, or not sure Business fits? Book a call. For the mechanics of how a dispatch package behaves inside an LMS, read SCORM dispatch, explained.

Your hosted course, the customer's LMS, and completion reporting 01 · YOU HOST 02 · CUSTOMER LMS 03 · REPORTING runtime calls relayed through the launcher · completions back to their LMS one small launcher zip, imported once · registrations show in your dashboard Your hosted course Launcher package imported Completion and score Seat ceiling, expiry, revocation Update content, no re-import Recorded in the customer's LMS Usage visible to you per dispatch

Compatibility and prerequisites

Which LMS platforms support dispatch?
Any LMS that imports a standard SCORM 1.2 or SCORM 2004 package. The dispatch zip is an ordinary SCORM package with a small launcher inside, so there is no vendor plug-in for the customer to install.
What does the customer need on their side?
Permission to import SCORM packages, and learners whose browsers can reach the hosted course over HTTPS. The customer's LMS server itself never talks to us, so on-premises and firewalled LMSs work as long as the learner's browser has internet access. A locked-down corporate network may need our hosting domain on its allow-list.
Which standard should a dispatch use?
Whichever the customer's LMS imports most reliably — choose SCORM 1.2 or SCORM 2004 per dispatch, so one hosted course can be delivered as 1.2 to one customer and 2004 to another without rebuilding it.
What happens to learners mid-course when a dispatch expires?
The package stops launching from the expiry date or the moment you revoke it. Completions already recorded in the customer's LMS stay there; nothing is deleted on their side. Extend the expiry or lift the seat ceiling from your dashboard and it resumes.

Start with one file.

Upload a PowerPoint, PDF, or video you already have, build it as a SCORM package, and run it in the tester to see every call it makes.

→ upload  handbook.pdf
  rendering … 86 pages
  course … 1 lesson, 86 pages
  building … SCORM 2004 4th Ed
  validating … 0 errors
✓ handbook-scorm2004.zip