Compatibility baseline
Identify the released hardware, firmware, code ranges and package set.
Grow the Product Line Without Losing Compatibility.
Add books, card decks, languages, packaging variants or new SKUs through controlled code, audio, firmware and production changes.
Version control
Separate existing and new audio, artwork, language and SKU files.
Expansion testing
Check new content with retained and current production samples.
Repeat-order change review
Document component, material, label and packaging differences before release.
Treat every expansion as a controlled product change.
New content can affect memory, code allocation, firmware, printed files, pack-out and compatibility even when the plastic housing stays the same.
New content pack
Add books, cards or stickers while keeping the existing hardware platform.
New language SKU
Control translated artwork, audio libraries, labels and packaging identity.
Hardware refresh
Review component or charging changes against content and previous approvals.
Repeat order
Confirm released files, approved substitutions and current production evidence.
Build expansion on a documented compatibility baseline.
The previous approved product, firmware and content map provide the starting reference for every new title, deck, language or repeat order.
Review your requirements
Released hardware
Model, electronics, memory, charging, controls and approved components.
Firmware version
Code ranges, modes, playback rules and content-package compatibility.
Content library
Existing and new scripts, audio, artwork, touchpoints and language versions.
SKU identity
Product label, package artwork, accessories, barcode and carton marks.
Change record
Difference, reason, risk review, evidence and approval status.
Create more value from an approved platform.
Content and SKU expansion can extend the product line without repeating every structural development step, provided compatibility remains controlled.
New book titles
Add stories, vocabulary or curriculum content to an OID ecosystem.
Replacement card decks
Offer new topics or replenish worn and lost learning cards.
Language editions
Reuse the platform with controlled audio, artwork, labels and SKU versions.
Retail refresh
Update color, package artwork or set contents while reviewing change impact.
Separate reusable assets from work that must be repeated.
An expansion quote should identify which hardware, firmware, artwork and tests remain valid and which require new work.
Request a scope review| Decision | What we confirm | Why it changes the quotation |
|---|---|---|
| Baseline reference | Previous model, order, sample and files | Determines what can be reused confidently. |
| Content change | New topics, languages, touchpoints and audio | Changes file work, memory and proofing. |
| Hardware change | Components, controls, charging or housing | May change compatibility and validation. |
| SKU change | Color, label, accessories and packaging | Changes materials, artwork and minimums. |
| Order plan | Expansion quantity and repeat forecast | Changes component, print and commercial planning. |
From requirements to production.
Each stage has a tangible output so product, content and commercial decisions stay connected.
- 01
Baseline audit
Collect the previous approved sample, files and order configuration.
- 02
Change definition
List new content, language, hardware, package and market requirements.
- 03
Compatibility sample
Test the new package with retained and current product references.
- 04
Controlled release
Approve versioned files, differences and repeat-order inspection points.
Product and production evidence
Use retained references to verify compatibility.
A repeatable expansion process compares new samples against the approved product and controlled content package.Physical references support platform and version comparison.
New content and product changes reviewed together.
SKU, package and carton identity checked before dispatch.
Bring the previous reference into the next project.
The more clearly the current released configuration is identified, the less uncertainty surrounds the expansion.
- Previous order, model or approved sample reference
- Current firmware and content package if available
- New titles, topics, language or SKU requirements
- Compatibility and replacement expectations
- Expansion quantity, market and launch timing
Frequently asked questions.
Practical answers for an initial project review. Final commercial and technical terms belong in the written quotation and approved specification.
Can a new book work with previously sold reading pens?
Potential compatibility depends on the released firmware, code ranges, memory and content system. It should be verified with retained samples rather than assumed.
Can we add a new language without changing the hardware?
Sometimes, if memory, firmware and user-selection behavior support it. Artwork, audio, labels and SKU identity still require controlled updates.
Can replacement cards be sold separately?
Yes, when card recognition, database mapping, packaging and compatibility with the installed device base are confirmed.
What should be checked on a repeat order?
Review components, materials, firmware, files, labels, accessories, packaging and approved substitutions against the previous released configuration.
Does a package redesign require a new product sample?
At minimum, a physical pack-out sample is recommended. Product or compliance impact depends on whether the set contents, labels, protection or configuration change.
Extend the product line from a controlled baseline.
Send the previous product reference and planned expansion so compatibility, new work and repeat-order controls can be reviewed together.