All guides

Catalog Operations

How to Reconcile a Batch of Spotify Audiobook Submissions

Close a batch title by title: match your submission register to Catalog, use Alerts CSV for exceptions, and count only editions verified from the listener side.

6 min readFrom our operating notebook
Four cloth audiobook sleeves marked with a check, hourglass, red bar, and empty frame sit beside a lined ledger.
Original editorial illustration

Close the batch against the titles you meant to submit

Our work takes multiple Google-generated audiobook packages through Spotify submission, then tracks them in the catalog and reporting workflow. A count alone can’t tell you whether the right editions went live. One missed title and one unexpected listing can leave the total unchanged.

Start with your own submission register. Match each edition to Catalog, use the Alerts CSV to find exceptions, then verify listener availability separately. This is a batch-control method, not a claim that Spotify provides a complete batch export. The worked example below is fictional.

1. Freeze the submitted set and keep attempts separate

Create one row per intended audiobook edition for the batch, with a local key that won’t change when a subtitle changes. Record the organization, author, edition or language, asset revision, exact submission timestamp with time zone, and any Spotify identifier or audiobook ISBN you actually have. Leave unknown fields blank; don’t invent an identifier.

Separate being ready to upload from having submitted. Record actual submission evidence and keep a saved but unsubmitted draft out of the submitted total. A later attempt to correct the same edition belongs in that row’s history, not in the count as another book.

Give each row an owner and next check time. If you split work among operators, record who handles exceptions before anyone changes a listing. That prevents one operator from troubleshooting a title while another uploads it again.

2. Match Catalog in both directions

Work inside the organization recorded for the submission. Prefer a known Spotify identifier or an edition-specific ISBN, and confirm the title and contributors. If there’s no stable identifier, compare several fields and inspect the actual record. A normalized title can find candidates, but it should not decide which edition to mark complete.

Work from the submitted list toward Catalog to catch missing matches, and check candidate Catalog records back against the list to catch unexpected items. An entry from the backlist is not a new batch success. Keep uncertain rows and unexpected records separate until resolved.

Spotify’s U.S. upload help says a submitted title can briefly appear in Drafts and may be absent from Catalog for up to 24 hours while processing. Its separate listener guidance is within three business days. The November 19 Spotify for Authors blog describes a first title taking three to five days while the payment profile is set up, and later titles usually going live in under 24 hours. Treat these as different descriptions, not a single deadline or an instruction to resubmit.

3. Join alerts as exceptions, not as the inventory

Spotify lets you download an Alerts CSV from Catalog. Keep a dated copy and associate its alerts with the correct edition using the evidence available. If the CSV doesn’t carry the field you need, confirm the match in Catalog instead of assuming a fixed CSV schema. Several alerts for one title are still one title in your totals.

Processing failures and availability issues may need action. A presentation issue can coexist with a title that is available to listeners. Additional information may not require a change. Read the affected file or field and suggested action before deciding how to classify a row.

No alert does not mean verified live. A title can be processing, absent from the view, or untested on the listener side. Keep alerts linked to the row, but base its release status on the combination of Catalog evidence and the actual listener check.

4. Work one batch, including the ambiguous row

Suppose five fictional titles in the same organization were submitted in sequence on a Tuesday. The timestamps below are example entries, not service targets. At the next check, record each row once in the outcome totals:

  • B-01 · 09:00 Central · Verified. A listener with existing access opens the exact edition and starts a chapter in the intended market.
  • B-02 · 09:04 Central · Verified, with a separate presentation issue. The exact edition is available; assign the cosmetic fix without subtracting the verified release.
  • B-03 · 09:12 Central · Pending. Submitted earlier and temporarily absent from Catalog. No listener proof yet; give it another check, not another upload.
  • B-04 · 09:20 Central · Blocked. Catalog shows an availability alert, and a check in the intended market confirms the edition is unavailable. Assign the affected field and recheck after the documented fix.
  • B-05 · 09:26 Central · Unmatched. Two plausible titles differ by subtitle and language. Resolve the edition against the original package before using either link.

5. Report the proof, not just the count

The example checkpoint accounts for five submissions: two verified, one pending, one blocked, one unmatched. It also carries one presentation issue on a verified title. Report any unexpected Catalog records separately; they never offset an unmatched submission.

Where Catalog shows the title, Spotify documents a way to copy its listener URL using Open audiobook in Spotify. Open that exact destination and check the edition and cover. Record the market, date and what you could confirm: page visible, sample playable, purchase offered, or playback confirmed with existing access. A visible page or a playable sample does not establish full access. If you can’t test the availability you’re reporting, leave it unverified. For a scheduled release, a pre-save page is not a live release.

Cap the handoff at what another person needs to act: edition key, issue, latest evidence, owner, and next check. If a title stays unresolved past the relevant window, bring the original submission time, matching evidence and exact alert to the appropriate support route. Don’t send an entire private catalog when a few affected records will do.

Sources and further reading

Official documentation checked for this guide. Platform policies and reporting details can change.