Frequently Asked Questions
updated September 19, 2025
After I upload my SCORM package to Scoop, does it automatically appear in my LMS, or do I still need to create a course shell in my LMS and link it to the new content?
After a SCORM package is uploaded, it can be used immediately in your LMS. Scoop does not create the course shell automatically in your LMS when a new SCORM package is uploaded, unless we configure this integration for you.
If you are interested in automating this then please contact us to discuss details. Our team has lots of experience automating business workflow with integrations between systems.
Do I need to specify a course identifier when I upload a SCORM package to Scoop?
No. A course identifier is automatically generated from the name of your zip file, so you do not need to remember this step.
This means the only thing you need to think about when you upload a new SCORM package is the name of your zip file. Scoop simply converts the file name to lower case, and replaces non-alphanumeric characters with hyphens (so the file name is URL-friendly) —- and that becomes your Scoop course ID.
How do I manage multiple versions of the same course?
Whenever you upload a new file with a unique name, the new file becomes a fresh new course. This means you can manage multiple versions of the same course with a simple naming convention.
For example, suppose you have 3 versions of a Ladder Safety course. You can append a version number to the name of each SCORM package, so it's always clear what version you are referencing:
- ladder-safety-v1.zip
- ladder-safety-v2.zip
- ladder-safety-v3.zip
If I replace existing content in Scoop, is the change automatically reflected in my LMS?
Yes. If you upload a SCORM package with a file name that is identical to the name of a package you uploaded previously, then the new content replaces the old content. This change is reflected immediately and automatically in your LMS.
If I replace an existing course with new content, is the old original content still available in Scoop as a backup?
No. If you upload a SCORM package with a file name that is identical to the name of a package you uploaded previously, then the original content is entirely overwritten, and no backup or archive is made by the system.
In this scenario, if learners have completed the course with the original content, then their certificate of completion remains valid, but if learners have started and not completed the original content, then they will have to restart the course from the beginning.
If you want to preserve original content for a course replacement, then adopt a file-naming convention that takes this into account.
For example, you can append a version number or a date to the name of each SCORM package file. File names might look like this:
- First Aid v24.zip
- First Aid v25.zip
- Falling Down Rabbit Holes 2024-12-31.zip
- Falling Down Rabbit Holes 2025-02-04.zip
- Falling Down Rabbit Holes 2025-09-12.zip
You are not required to use lowercase and hyphens in the file naming convention on your computer. Some customers decide to follow this convention so the file name exactly matches the course identifier that Scoop assigns to it, which makes it easy to match copies on their computer to copies they have uploaded.