How to Combine Multiple SCORM Packages Into One

A pattern shows up again and again in L&D teams: a designer built five short courses — one per module — so each could be tracked separately. Then the client (or the budget) asks for all five to ship as a single SCORM upload, while still tracking each module. Merging SCORM packages sounds like it should be a button. In practice, done by hand, it means editing XML by candlelight.

Why combine packages at all?

• LMS upload and seat costs — some LMSes and SCORM hosting services charge per course, per registration, or per upload. Five separate uploads can cost five times as much as one.
• Learner experience — one enrollment, one launch, one progress bar instead of five tiles the learner has to find and complete in order.
• Administration — one course to assign, report on, and retire instead of five that can drift out of sync.
• Catalog hygiene — a single "Onboarding 2026" course is cleaner than five fragments with near-identical names.

The two ways to "combine" — and why the difference matters

There are two very different things people mean by "merge," and choosing the wrong one loses data.

1. Multi-SCO package (preserves per-module tracking)

A single package that contains multiple SCOs — each original course becomes one SCO inside one manifest. The LMS still tracks each SCO independently: completion and score per module are preserved. This is almost always what people actually want, because it keeps the reporting they built the separate courses to get in the first place.

2. Single fused SCO (one combined status)

Stitching the content into one SCO with a single completion status and one rolled-up score. Simpler for the learner, but you lose per-module granularity, and physically fusing two authoring-tool outputs into one running SCO is fragile. For most teams, the multi-SCO approach is the right answer.

What the manual process actually looks like

Even the organization that authored the SCORM standard documents merging as a manual procedure. The shape of it:

1. Unzip every package into its own subfolder so file paths do not collide.
2. Open each imsmanifest.xml and read out the resource and file declarations.
3. Build a new top-level manifest with one <organization> and one <item> per SCO, each pointing at its module folder’s launch page.
4. Give every item and resource a unique identifier — collisions between packages are the classic failure.
5. Set each SCO’s scormtype and href correctly, and re-check every relative asset path.
6. Zip the parent folder so the new manifest sits at the archive root, then validate.

A trimmed-down multi-SCO manifest looks roughly like this — one organization, two items, two resources, each with a unique identifier:

<organization identifier="ORG-1">
  <title>Onboarding 2026</title>
  <item identifier="ITEM-MOD1" identifierref="RES-MOD1">
    <title>Module 1 — Welcome</title>
  </item>
  <item identifier="ITEM-MOD2" identifierref="RES-MOD2">
    <title>Module 2 — Safety</title>
  </item>
</organization>
<resources>
  <resource identifier="RES-MOD1" type="webcontent"
    adlcp:scormtype="sco" href="module1/index_lms.html"/>
  <resource identifier="RES-MOD2" type="webcontent"
    adlcp:scormtype="sco" href="module2/index_lms.html"/>
</resources>

It reads simply, but the failure modes are unforgiving: a duplicate identifier, a path that points one folder too high, a manifest that ends up nested under a folder instead of at the root, a missing scormtype. Any one of these and the LMS rejects the package or silently fails to report module completion.

A note on SCORM 2004 sequencing

You might be tempted to use SCORM 2004 sequencing to force learners through modules in order. Be careful: many LMSes implement sequencing partially or not at all, so behavior you test in one LMS may not hold in another. If your only goal is "one upload, per-module tracking," a straightforward multi-SCO package without complex sequencing is the most portable choice.

Always validate the merged package

After merging, upload the package to a test LMS or SCORM Cloud and confirm three things: it launches, every module reports its own completion and score, and there are no missing-file errors. Reporting bugs from a bad merge are easy to miss until a real learner finishes and nothing shows up.

The faster path

ScormEdit combines packages in the browser without hand-editing any XML. Upload your separate course .zips, order them, choose to preserve per-module tracking, and it generates a single valid multi-SCO package with unique identifiers, correct paths, and the manifest at the archive root. You download one course that reports each module independently — and a record of exactly what was combined. It turns an afternoon of fiddly XML into a few minutes.