Package Audiobooks for Divibib Onleihe Without Freezing Retail Calendars

German-speaking public libraries still buy digital audiobook licenses through Onleihe — and Divibib is the company behind that lending surface. Divibib’s publisher pages cite cooperation with more than 1,500 publishers into over 3,800 Onleihe libraries and over one million active Onleihe users per year (divibib — Verlage und Onleihe). Onleihe has served public libraries across Germany, Austria, Switzerland, and other German-speaking communities since 2007 (OverDrive — Divibib acquisition). On 11 August 2026, OverDrive announced it acquired Divibib GmbH from ekz-Group so Onleihe libraries and readers can, over time, move onto Libby — while OverDrive already cites more than 600 Libby library partners across the DACH region with nearly ten million digital checkouts through Libby in 2025 alone (OverDrive — Divibib acquisition). On the aggregator side, Author’s Republic lists Divibib under Preferred Sales Channels (Author’s Republic — Distribution Agreement tab). The trap is treating “Preferred Sales checked once” as “borrowable in every Onleihe library and every other library app tonight.”

This guide is about Divibib Onleihe audiobook distribution: aggregator Preferred Sales packaging, DACH library masters, disclosure, and a clean split from optional wide retail and other library calendars.

Key Takeaways

• Most presses reach Divibib / Onleihe through approved aggregators or publisher supply — not a universal self-serve Onleihe publisher console.
• Package for library license discovery (findable title record, honest narrator line), not unlimited “streaming everywhere” language.
• Separate three clocks: files ready, delivered to Divibib partners, and licensed/borrowable inside an Onleihe library’s catalog.
• Produce on pricing, automate kicks via docs, and keep store calendars separate (distribution).

Who this is for

• Trade and midsize publishers packaging DACH library audio without freezing Audible or Apple Books calendars
• Rights and ops leads choosing which Preferred Sales library destinations to enable per ISBN during the Onleihe → Libby transition
• Agencies coordinating client catalogs that already ship masters and need a Divibib checklist distinct from OverDrive/Libby US, Hoopla, BorrowBox, and Odilo tickets

If your next upload is OverDrive / Libby public-library packaging in other markets, use the library digital catalogs guide. For Hoopla, BorrowBox, cloudLibrary, or Odilo, use those dedicated posts. This post assumes you can produce masters and need the Divibib / Onleihe path to stop colliding with retail promises.

Before you begin

What you need:

• Frozen manuscript and listen-checked chapter masters
• Clear audio rights for the German-speaking (and any other Onleihe) territories you care about
• An audiobook aggregator that lists Divibib under Preferred Sales — or a direct publisher supply relationship into Onleihe
• Unique audiobook identifiers and metadata aligned to any ebook twin
• AI / digital-voice disclosure ready if you use synthetic narration
• A decision: Divibib-now vs Divibib-later relative to Audible, Apple Books, OverDrive, and other library partners
• Time: production can be same-day once text is frozen; Preferred Sales partner ingest is not
• Difficulty: Intermediate — specs ride your partner feed; “sent” vs “licensed in an Onleihe catalog” is the hard part

Step 1: Separate Onleihe from retail launch day

Do not put “live on Onleihe” on the same sticky note as “masters delivered.”

Author’s Republic groups Divibib with other Preferred Sales retailers — not as a Music Channel — alongside destinations such as Overdrive, Hoopla, Follett, Mackin, and Odilo (Author’s Republic — Distribution Agreement tab; Author’s Republic — our partners). Build the archive once; run Divibib as its own ticket.

For the broader reminder that files ready ≠ store live, keep the distribution timelines guide handy for stakeholders.

Step 2: Choose a Preferred Sales or supply path before you promise a date

Most presses will not open a personal Onleihe merchant desk on day one. Confirm which path you actually hold:

Information gain: Teams that copy-paste an OverDrive checklist onto Divibib invent a single “library” surface that aggregator partner tables treat as a distinct Preferred Sales destination. Name Divibib / Onleihe in the ticket before marketing drafts a “live in every German library” email.

Step 3: Package for library licenses, not a consumer storefront guess

Divibib’s public positioning for publishers is digital lending into public libraries — e-books, e-audios (Hörbücher), e-paper, and related formats — with libraries selecting licenses from a Medienshop rather than every title auto-appearing for every patron (divibib — Verlage und Onleihe). Use that framing when stakeholders ask “is this like Audible?”

Freeze synopsis, language, and honest narrator credits before you enable the partner. Thin library records get skipped even when the audio is fine.

Step 4: Produce masters that survive phone-speaker library listening

Onleihe patrons often listen on phones and tablets through the Onleihe app or web player. QC for that context.

1. Freeze chapter breaks that match the printed TOC.
2. Keep opening/ending credits identical to the narrator metadata line.
3. Spot-check proper nouns on phone speakers — commute noise is the real room.
4. Archive sample approval beside the ISBN packet before you enable Divibib Preferred Sales.

Price production from pricing. Character-based AI pipelines make multi-title library batches forecastable once text is frozen; partner clocks still belong on a separate sheet.

Step 5: Disclose AI narration without freezing production

If you use AI or digital voice, disclose it in the aggregator fields and keep credits identical to the narrator line librarians and listeners will see.

For trade ONIX List 19 packaging aimed at retailers, cross-link the AI narration disclosure metadata guide. For multi-retailer storefront display QA after partners go live, use the retailer disclosure display QA guide.

1. Gate voice samples in writing before full production.
2. Map the approved sample to aggregator disclosure fields.
3. Keep opening/ending credits identical to metadata.
4. Archive the disclosure decision with the ISBN packet.

Step 6: Account for the OverDrive transition without freezing today’s ticket

OverDrive’s August 2026 announcement is clear that Onleihe libraries and readers will continue to have access throughout the transition, and that partners will, over time, utilize OverDrive’s platform (OverDrive — Divibib acquisition). That does not mean your ops sheet should wait for a final Libby migration date before packaging masters.

1. Keep Divibib Preferred Sales (or direct Onleihe supply) as the named path on today’s ticket.
2. Ask your aggregator how Divibib deliveries map during the transition — do not invent a second “Libby DACH” checkbox from a press release.
3. Separate “Onleihe networked” from “this ISBN licensed by a specific Verbund.”
4. Update stakeholder language when OverDrive and ekz-Group publish partner timelines — not when social posts speculate.

Divibib packaged ≠ every DACH library already licensed your title.

Step 7: Verify Onleihe availability before marketing speaks

Author’s Republic is explicit that after aggregator approval, individual platforms can take roughly 5 to 60 days, and the aggregator is not notified when each surface goes live — you must check partners yourself (Author’s Republic — our partners).

1. Record the submit date and which Preferred Sales group included Divibib.
2. Spot-check Onleihe / partner search in a priority market after the lower bound of your path’s window.
3. If missing past the upper bound, open a ticket with the aggregator — not with a random consumer library help form.
4. Keep marketing copy on “submitted to Divibib / Onleihe partners” until you can confirm a findable listing in the markets you care about.

Category and metadata corrections also ride partner refresh cycles. A same-hour browse check is not proof of failure.

Step 8: Ship production on a different clock than Divibib ingest

Production can finish the same day the manuscript freezes when you use AI narration with human listen QC. Aggregator review and Divibib ingest still own the library clock.

Automate project creation and production starts from docs when coordinators need repeatable kicks. Keep the human gate on partner choice, territory rights, AI disclosure, and listen QC — then park retail promises under distribution.

FAQ

Is Divibib the same as OverDrive or Hoopla?
No. Author’s Republic lists Divibib as its own Preferred Sales Channel alongside Overdrive, Hoopla, and others (Author’s Republic — Distribution Agreement tab).

Can presses upload audiobooks directly to Onleihe?
Most presses use an aggregator that lists Divibib or a publisher supply relationship Divibib already supports (divibib — Verlage und Onleihe; Author’s Republic — our partners).

Does the OverDrive acquisition change today’s packaging checklist?
It changes the long-term reader app story (Onleihe → Libby over time). It does not erase the need for a named Divibib Preferred Sales / supply ticket, listen-checked masters, and availability verification (OverDrive — Divibib acquisition).

Does Divibib packaged mean the title is live on Audible, Apple Books, or US Libby?
No. Keep optional retail and other library paths on separate calendars (distribution).

How should AI narration be disclosed?
Complete aggregator AI / digital-voice fields and match credits; use the disclosure metadata guide for ONIX trade packaging.

DACH library markets reward teams that treat Divibib / Onleihe as a packaging system: aggregator Preferred Sales path, honest separation from retail, disclosure, transition-aware stakeholder language, and availability checks. Your advantage is not a louder “German libraries” headline — it is a consumption-ready title whose retail calendar still moves while Onleihe partners ingest.