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.
DISPATCH
Sell the course. Keep the control.
If you license courseware to other organisations, dispatch delivers it into their LMS while the content, the seat count, and the kill switch stay with you.
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.
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.
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.
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.
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 priced separately from the self-serve plans, because courseware businesses don't fit a one-size tier. Tell us how many customers and registrations you deliver, and we'll give you a straight answer — start the conversation. For the mechanics of how a dispatch package behaves inside an LMS, read SCORM dispatch, explained.
Start with one file.
Upload something you already have and see it as a package, with the conformance report and the runtime log alongside it.
→ upload handbook.pdf parsing … 14 sections building manifest … validating … 0 errors, 2 notes ✓ handbook-scorm2004.zip ✓ preview link ready