Kids’ AI toys · talking plush & companions · OEM / ODM · Shenzhen

Story plush · Tap to play

NFC story plush OEM — turn “new series” into a content update instead of a new mould

Most toy categories grow by shipping new moulds. A tap-to-play story product grows by shipping new cards, and the cards cost a fraction of a tool and can be in stores in weeks. That economic fact is the whole reason this form factor is worth building: the toy is bought once, the library is bought repeatedly, and every new card works on every plush already in a child’s room. The engineering that makes it work is unglamorous — reader range under fabric, card authentication, offline caching, and a back office that maps a card ID to a playlist without shipping firmware.

Who usually comes to us

IP holders with a story library

Dozens of characters already written and drawn, and no physical product that lets a four-year-old choose between them without reading.

Publishers and audio content companies

You sell audio already and want a physical retail presence where the shelf does the recommending.

Toy brands with a character line

A plush that currently only exists as a soft object, and a way to add a reason to keep buying into the same character.

Travel and museum retail

Location-specific content sold as a souvenir: a card per city, per exhibit, per season — content that cannot be bought online.

Designing the deck, not just the toy

The physical product is half of it. The other half is a purchase model a retailer can explain in one sentence and a parent can repeat at home.

Character cards

One card, one character, a signature story and a voice. The core of the deck, and the part a child asks for by name.

Series cards

A run of stories around a theme — seasons, holidays, a location. Cheaper per card, bought in packs, and the mechanism that makes a library grow.

Charms and wearables

The same tag in a form a child can hang on a backpack, so the content travels without the plush. Higher margin, higher breakage, so the loop has to be the failure point.

Price the deck so the second purchase is smaller than the first. The mistake is a card that costs a third of the toy: parents stop, and the library stops with them.

From a tap to a sound, in order

  1. 01

    Read and authenticate

    The reader polls, gets a UID, checks the signature locally, and only then asks the server. A clone fails here, before anything is spoken.

  2. 02

    Resolve the card to a playlist

    Server returns what this card plays for this product and this market, plus a cache instruction. Offline, the device uses the cached copy and a version check reconciles later.

  3. 03

    Start in under a second

    A confirmation sound begins before the first word of the story, so the child gets an answer to the tap immediately. Silence for two seconds reads as broken.

  4. 04

    Handle the boring cases

    Card already playing, card not licensed for this product, battery low, Wi-Fi off, two cards tapped at once. Each one needs a sound, not an error code — and each one is a support ticket you decide not to receive.

What decides whether a tap-to-play product gets played twice

01

The read has to work through the plush

Reader range collapses through fabric, stuffing and a hand holding the toy. A tap that only works on a table at the right angle is a tap a child will not repeat. Coil size, position relative to the belly surface and the thickness of the seam are fixed early — and the same coil must not be blocked by the battery or the speaker magnet.

02

Cards are a security problem, not a sticker

The moment the product sells, someone will write a blank tag with a hotel key card and put it in a rival’s packaging. Authenticated tags, a signing scheme in firmware and a server-side check of which card IDs are valid for which product are what stop a grey-market deck from playing in your toy.

03

One action, no menu, no screen

The interaction budget is a single tap by a three-year-old who cannot read. That rules out pairing modes, hold-for-two-seconds and anything that needs a phone nearby. If a step needs an explanation, it is the wrong step — and the explanation will be given to a child by an adult who has also not read the manual.

04

Content mapping lives on the server

A card ID resolves to a playlist in your back office, not in firmware. That is what lets you re-theme a card for a season, retire a story, run a regional edition and fix a mis-timed track without a firmware campaign — and it is the difference between a content business and a hardware business with content attached.

05

It has to survive a two-year-old

Cards get bent, chewed, left in a pocket and washed. Charms get swung. The mechanical answer is thicker stock, rounded corners, a laminated face and a charm that fails at the loop rather than at the tag. The content answer is that the plush keeps working when a card dies: no card, no error, just a default story.

Directions to start from

Two ways to develop with us

Your art on an existing story platform

A plush body already in production, your character artwork on the fabric and your content in the deck. New tooling limited to print and packaging.

Best for: Proving the deck model with a small first series.

New character on the proven core

New pattern, new ears, new voice set, reused reader, audio path and power architecture. The engineering risk is in the fabric, which is where the value is.

Best for: The character is the product and the electronics are the plumbing.

Full development

New electronics, new reader geometry, an authored content model, the back office and the card production spec — including the authentication scheme and the print files.

Best for: A content model that has no equivalent on the shelf, such as a location-based library.

Platforms

Bring the AI stack your market needs

Our firmware is decoupled from any single provider. Depending on where you sell, your data-residency rules and your budget, we connect the device to the right LLM, speech and IoT cloud. These are the kinds of services we have integrated.

For China

  • Baidu AI Cloud Solution sales partner Cloud AI and voice services
  • Mainstream Chinese LLMs Several to choose from, per project
  • Speech recognition & synthesis Major speech engines
  • IoT provisioning & branded app Device setup and app under your brand
  • Audio / video storage & delivery Audio / video cloud for content

For global markets

  • Leading overseas LLMs Chosen per market and language
  • Realtime voice dialogue Realtime voice models
  • Neural speech synthesis Speech recognition and natural voices
  • Device connectivity & fleet management Connect and manage devices at scale
  • EU / US data hosting Data kept in the region you sell in

Questions buyers ask

Do parents need an app to use it?

Not to play. Tap and it plays — the whole point of this form factor is that it works with no phone in the room. The app is for the adult side: choosing which stories are on the device, setting listening time and quiet hours, buying new cards, and seeing what was played.

Can the plush work offline, away from Wi-Fi?

Yes. Card content is cached on the device, so the plush plays in a car, on a plane and in a hotel with a captive portal. Connectivity is for getting new content and for the parent’s view, not for making the toy work.

Can we use our own cards rather than buying them from you?

Usually yes, if the tag specification, the data layout and the authentication keys match what the firmware expects — we publish that spec. What we will not do is accept an unauthenticated tag, because a deck that anyone can clone turns a content business into a giveaway.

How many cards should a first series have?

Fewer than feels commercial. A starter deck of a handful of characters, each with enough content to be revisited, teaches you more than thirty cards a child tries once. The card is a purchase decision made by a parent in a shop — the deck has to be understandable from the packaging alone.

Is the story-machine hardware really already in production?

Yes — the board, audio path and reader come from a children’s story-machine platform we have built and shipped. That means your project starts from tooling that has already been revised and a yield curve that has already been measured, which is time you do not pay for twice.

Tell us what you want to build

The category, your market, a quantity and whether an IP is involved is plenty for a first answer. Samples available; proven products are available as OEM, custom ones as ODM. Development and sample arrangements are agreed together once we understand the project.

Start a conversation
WhatsApp