Answer: Open the story-player app, go to the Cards/Stories section, tap “Add New,” then either scan/write the physical story card (NFC/QR) or upload/select the audio file and metadata in the app. Save the new card and sync or write it to the player. Most systems use a short ID on the card that points to streamed or stored audio; if your player stores audio directly, you will also upload the audio (commonly MP3, up to 50 MB per story). Below are step-by-step instructions, troubleshooting tips, and notes for parents and B2B buyers.

How story cards work (quick overview)

• Two common architectures:
• Card-as-trigger: the physical card contains an ID (NFC tag or QR code). When tapped, the player requests audio from the app/cloud and streams it. Pros: small card memory, easy updates. Cons: requires Wi‑Fi/paired app for new content.
• Card-as-storage: the card stores audio data (MP3/WAV) and the player reads audio directly. Pros: offline playback. Cons: larger cards and file management required.
• Typical file formats accepted: MP3 (most common), WAV. Typical app/device limits: 16–320 kbps MP3, 44.1 kHz sample rate. Typical per-story size limit in many apps: 20–100 MB (commonly 50 MB). Device storage options: internal 512 MB–8 GB or microSD up to 32 GB.

Step-by-step: Adding a new story card (parent-friendly)

1. Prepare
2. Ensure your phone/tablet has the story-player app installed and updated.
3. Make sure the toy/player is powered on and paired (Bluetooth) or on the same Wi‑Fi if the player uses cloud streaming.
4. Check app permissions: Storage (to upload audio) and NFC (if you’ll write to cards).
5. Open the app and find “Cards / Stories / Library”
6. Tap the “Add” or “+” button — often labeled “Add New Story Card.”
7. Choose your method
8. Scan physical card: Select “Scan/Write Card” and hold the NFC card to your phone’s NFC area or scan the printed QR code. The app reads the card ID and shows current content or an empty slot.
9. Upload audio file: Choose “Upload Audio” or “Create Story.” Select an MP3/WAV from your device or record directly in-app.
10. Enter metadata
11. Add title, narrator name, recommended age range (e.g., 3–6 years), image/cover art, and any tags (bedtime, learning, adventure).
12. Configure playback
13. Set repeat options, volume limit (parental control), and whether the card will stream or store audio locally.
14. Save and sync
15. Save the card in the app. If needed, tap “Write to Card” to encode the NFC tag (typical write time < 5 seconds).
16. Sync to the player: either the player will automatically fetch new stories when the card is scanned, or you can push content via Bluetooth/Wi‑Fi—confirm progress in the app.
17. Test
18. Tap the new card to the player and ensure playback starts. If offline storage was used, disconnect Wi‑Fi and test again.

Troubleshooting common issues

• App can’t write to card: Ensure NFC permission is enabled and your phone supports NFC writing (not all phones do). Try a different phone if possible.
• Player doesn’t recognize card: Check that the card type (NTAG216, MIFARE) is supported by your model; some players support only specific tag types.
• Audio won’t play or is choppy: Verify file format/bitrate (convert to MP3 128 kbps, 44.1 kHz for best compatibility). If streaming, check Wi‑Fi strength.
• Upload fails: Watch file size limits in the app (commonly 50 MB). Compress or split long stories.
• Too many cards: Some players support 50–200 card IDs; others can handle thousands when using cloud streaming. Check model specs.

Tips for parents

• Use clear cover art and age tags to organize a library—this makes it easier for children to find favorite stories.
• Set volume limits and bedtime timers in-app to protect hearing and manage screen-free routines.
• Keep backups of custom audio files (cloud or local) in case you need to re-upload or provision a replacement device.

Notes for B2B buyers and OEM/ODM considerations

• For bulk/custom deployments, look for features such as:
• Batch provisioning: support for CSV/Excel import of metadata and bulk card encoding (saves time when creating 100+ cards).
• API/SDK: allows integration with content management systems for over-the-air content updates.
• Storage options: devices with microSD support (up to 32 GB) enable more offline content per device.
• Custom branding/firmware: many manufacturers support custom apps, voice fonts, and preloaded content.
• Compare capacities: card-as-trigger systems scale better for large libraries because cloud storage offloads device memory; card-as-storage systems are ideal for low-connectivity settings.

For OEM/ODM sourcing of kids story machines, contact Toyvao at sales@toyvao.com or WhatsApp +86 186 8106 4480.