DISTROBOLT

DISTROBOLT ARTIST GUIDES

Cancel an upcoming release without losing the record

Stopping an upcoming release involves more than cancelling an announcement. Establish whether the release is still a draft, has been delivered or has already appeared anywhere, then document the appropriate withdrawal request.

Keep three actions separate

Cancelling a creative-service order, requesting that a distributor stop delivery and confirming store withdrawal are different actions. None should be assumed to complete the others. Record the reason, authorised requester, release identifier and destinations. Do not erase the source files or accepted collaborator agreements while the request is being resolved.

Ask for the route that matches delivery status

Contact DistroBolt with the actual release reference and urgency. Ask whether delivery can still be stopped or whether a store removal request is necessary. Do not promise collaborators that the release cannot appear simply because a request was submitted. Near launch, maintain a destination-by-destination observation record.

Notify the people managing the campaign

Pause scheduled public posts, update the press contact and check any paid campaign or service commitment separately. A distribution request does not itself establish entitlement to a refund. The existing DistroBolt Premium terms also distinguish subscription cancellation from account deletion or release removal; cancelling billing is not a substitute for a release-specific request.

Preserve a closed release record

Keep the final files, dates, submitted metadata, support correspondence and observed outcome. Mark the project cancelled or postponed without reallocating historical royalties or replacing a collaborator’s accepted share. If you return to the music later, review the original identifiers and any existing store entries before creating a new delivery. A confirmation on one destination is not proof of worldwide removal.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

Continue your release planning

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.