Plenty of teams do not start from one English zip. They already have a Swedish package, a German package, and an English package — each authored, QA’d, and signed off. The LMS problem is not translation. It is catalog clutter: five course objects, five enrollments, five completion reports for what is really one course.
Merging those packages into a single SCORM export is the clean fix. Learners pick a language once. The LMS tracks one activity. Admins update one item when you ship a new version.
When merge is the right move
Use a merge project when the language versions already exist as separate zips. That is common after a vendor delivered per-language Storyline files, or after years of duplicating the authoring project. Translation projects are for the other case: you have one source package and you need a new language.
Mixing the two is how packages get messy. Do not translate inside a merge unless you meant to. Merge finished artifacts. Translate the source, then merge the results if the LMS should expose one course.
What a combined package needs
- One zip the LMS can import as a single SCO or course object
- A launcher page so the learner chooses a language before the content starts
- Stable identifiers so completion and suspend data still belong to that course
- Optional branding — logo, colors, title — so the selector looks like your academy, not a generic menu
The launcher is not decoration. Without it, the LMS has no honest way to present multiple language packages as one experience. With it, the learner path is obvious: pick language, take the course, complete once.
How to ship it
Upload each language zip into a combination project. Set the course title and organization title the LMS will display. Configure the launcher if you want branded selection. Export SCORM 1.2, SCORM 2004, or xAPI, then upload that one file.
Keep the language zips themselves in the project so the next update is a replace-and-export, not a scavenger hunt across old LMS backups. The merge is the multilingual SCORM package you give the LMS. The per-language zips remain the sources you maintain.