LMS
One multilingual SCORM package for the LMS
If each language is already a finished course, stop uploading five catalog items. Merge them into a single SCORM package with a launcher learners actually use.
This is not a translation job
Translation starts from one source course and produces a new language. A multilingual SCORM package starts from language versions you already have — a Swedish zip, a German zip, an English zip — each authored, QA’d, and signed off. The LMS problem is catalog clutter: five course objects, five enrollments, five completion reports for what is really one course.
Merging those zips into one export is the fix. Learners pick a language once. The LMS tracks one activity. Admins update one item when you ship a new version.
What the combined package includes
- One zip the LMS imports as a single course object.
- A launcher so the learner chooses a language before the content starts.
- Stable identifiers so completion still belongs to that course.
- Optional branding — logo, colors, title — so the selector looks like your academy.
When to translate first instead
Merge finished artifacts. If you only have an English Storyline export and you need Spanish, translate that course first. Then merge the language zips if the LMS should expose one catalog item.
How do I make a multilingual SCORM package for the LMS?
Upload each language zip into a merge project, add a language launcher, and export one SCORM 1.2, SCORM 2004, or xAPI file. The LMS sees a single course.
Is this the same as translating a course?
No. Translation creates a new language from one source zip. A multilingual SCORM package combines language versions you already have so the LMS does not host one course per language.
What if I only have an English Storyline export?
Translate that course first, then merge the results if learners should pick a language inside one LMS item.
Step-by-step: How to merge multilingual SCORM courses into one LMS package