Moodle can launch and track SCORM or AICC packages, but it does not turn ordinary files into SCORM. The ZIP must be exported by an authoring tool and contain a valid manifest. Tracking also depends on what the package reports to Moodle.
Check the package before upload
- Use a supported SCORM package, commonly SCORM 1.2.
- Keep the exported package zipped.
- Confirm
imsmanifest.xmlis at the expected package level, not hidden inside an extra folder. - Test the package in the authoring tool or a reference test environment.
- Know whether it reports completion, pass/fail, score and suspend data.
Moodle does not fully support SCORM 2004. If the authoring tool offers several standards, check Moodle’s current compatibility documentation before publishing.
Add a SCORM activity
- Open the course and turn on Edit mode.
- Select Add an activity or resource.
- Choose SCORM package.
- Enter a name and learner instructions.
- Upload the ZIP in the Package section; do not unzip it first.
- Configure appearance, grading, attempts and completion.
- Save and display.
You can also drag a SCORM ZIP onto a course section and choose the SCORM option. A course that contains only one package may use the Single activity course format.
Configure appearance
Choose whether the package opens in the current or a new window. New windows depend on popup permissions and can be awkward on mobile. Review stage dimensions, table of contents, navigation controls and attempt-status display with the actual package.
Choose the grading method
Moodle offers Learning objects, Highest grade, Average grade and Sum grade. Match the method to the data the package sends. If the package reports status but no raw score, Learning objects may be more meaningful. If it reports a raw score, set an appropriate maximum grade and test the gradebook conversion.
Manage attempts carefully
Set the allowed attempts and decide whether Moodle uses the first, last, average or highest attempt. Avoid Force new attempt unless opening the activity should always create another attempt. Ensure learners can reach the content-structure page if they need the Start new attempt control.
Configure activity completion
Completion can depend on viewing, receiving a grade, passing or reaching the package’s reported status. Test the rule from start to finish. A package may display its own “complete” screen without sending the completion value Moodle expects.
Test tracking with a learner account
- Start and partially complete an attempt.
- Exit using the package’s supported control.
- Reopen and confirm resume data.
- Finish the package.
- Check the SCORM report, gradebook and activity completion.
- Repeat on the browsers and devices learners use.
Why SCORM tracking fails
- Package will not load: invalid or nested manifest, blocked popup or mixed content.
- Progress is lost: package does not commit values, session ends unexpectedly or content is cross-domain.
- Completion never updates: package reports a different status/value than the Moodle rule expects.
- Score is wrong: grading method or maximum grade does not match the package output.
- More attempts are unavailable: the previous attempt is not reported completed/passed or the entry page is bypassed.
Use SCORM API debugging only for a controlled test user and turn it off after diagnosis; broad debugging can produce large logs and expose technical data.
Updating a package
Back up the course and preserve the original ZIP. Replacing a package can affect resume data, identifiers and reports. Test the new export against existing attempts in staging. For externally hosted packages, cross-domain browser security can prevent tracking.
Final advice
Treat the authoring tool, package and Moodle activity as three separate layers. Verify each one before changing the next. For a course shell that frames SCORM content clearly on desktop and mobile, explore Themes Almond Moodle themes.
Source check: Verified against Moodle 5.3’s official SCORM activity and SCORM settings documentation.
