@Carlos @Andy
Thank you for taking the time to respond and clarify the situation.
First, I would like to sincerely thank iMusician for the extensive music distribution infrastructure and backend system you have built. I understand that operating such a broad music distribution ecosystem requires considerable technical and operational work, and I genuinely appreciate the effort behind it.
At the same time, I would like to respectfully raise a broader concern regarding the transparency and accessibility of your metadata and distribution requirements.
Your official guidance provides information about basic requirements such as Title Casing and capitalization. However, some important requirements that can directly affect whether a release is accepted by Apple are much more difficult to find.
For example, information concerning the use of Latin and non-Latin characters within a title appears to be spread across different forum discussions and support responses, rather than being clearly presented in one centralized and official reference.
What concerns me most is that, within the iMusician Community Forum itself, creators may have to search through, read, and piece together information from forum posts that are more than a year old in order to discover an important requirement that can directly affect the delivery of their music.
Creators should not have to search through years of community discussions to discover a rule that may determine whether their release is accepted.
Essential submission requirements should be clearly available before a creator prepares and submits their music, rather than being discovered only after an Apple rejection.
This becomes even more difficult when a release has already entered Submitted / Locked status. If the creator cannot edit the metadata and cannot easily reach a human support representative, the creator is left waiting while trying to determine what went wrong through previous forum discussions and other users’ experiences.
We also attempted to seek assistance through the support email channel, but this did not provide a practical resolution or a clear path forward. From the creator’s perspective, this can result in an endless cycle of waiting — waiting for a response, waiting for clarification, waiting for the release to be unlocked, and waiting again for the issue to be resolved.
Meanwhile, the creator is left searching through old Community Forum discussions, sometimes going back more than a year, simply to understand the requirements that caused the rejection in the first place.
This should not become an endless waiting process for creators who have already paid for a distribution service.
The people experiencing this uncertainty and waiting are the creators, not the platform.
I say this with respect for the people working behind iMusician. My intention is not to criticize the individuals behind the platform, but to ask for a better and more transparent system for the creators who rely on it.
I sincerely hope iMusician will consider creating a public, centralized, comprehensive, and continuously updated Creator Metadata & Distribution Requirements Center, where all creators can clearly find the relevant requirements, common rejection reasons, examples, and a clear path to human support when a release is rejected or locked.
This information should be easy to find and available before submission, rather than requiring creators to search through a year or more of Community Forum discussions.
I truly appreciate the scale of iMusician’s music distribution infrastructure and the work required to maintain it.
I simply hope that the transparency of the information provided to creators, and the accessibility of human support, can grow alongside that infrastructure.
The goal is not to make the process more complicated. It is the opposite:
Give creators the rules clearly before submission, so that everyone can avoid unnecessary rejection, confusion, waiting, and repeated support requests.
Thank you again for taking the time to read and consider this feedback. 
