Dear @BenLeong,
Thank you for addressing this. I would appreciate it if you could forward my case to the senior reviewers, as this is a very serious situation for my company. Once we receive a response to the support request, we will take the necessary steps moving forward.
Thank you for your understanding and assistance.
Reason: Submitting multiple items with only minor technical differences is not permitted. Please avoid uploading near-duplicate versions of the same template."
We would appreciate your clarification on this. For example:
-
If we have already published the Xintra Bootstrap HTML version, does this mean we are not allowed to submit technically different versions such as:
- Xintra in React
- Xintra in Next.js
- Xintra in Angular
- Xintra in Vue.js
- Xintra in PHP/Blade
-
Additionally, if Xintra Bootstrap HTML is already approved, are we also restricted from submitting a Tailwind CSS-based HTML version of Xintra?
These versions are built on different technologies and frameworks, but we want to ensure we are complying fully with your guidelines. Unfortunately, the review note did not provide enough detail, and itās currently unclear for authors how much variation is required to avoid being flagged as a ānear-duplicate.ā
Could you please clarify what is considered a valid submission vs. a near-duplicate under this policy? This means we should submit only one item that includes all versions, similar to how the Metronic template is submitted.
I would like to address a few concerns regarding the recent reviews and rejections of our items. As a company with over 7 years of experience, we have consistently worked to improve the quality of our products and the technical aspects of our templates. We have observed a few issues during the review process that I would like to highlight:
-
Technical Differences: We have submitted multiple versions of our templates (e.g., TypeScript and JavaScript versions) because many of our customers request and use different versions. Both versions take the same amount of development time, yet they are being rejected due to technical differences, which I believe is not a valid reason for rejection. For example, our Next.js App Router version and JavaScript versions are selling well, but we have received feedback that these are not accepted by the review team despite their demand in the marketplace.
-
Feedback and Communication: After re-submitting the Xintra ā NextJS App Router JavaScript Tailwind Admin Template Dashboard based on the feedback from the previous review, we were disappointed to receive a hard rejection without any additional comments or clarity from the reviewers. Similarly, the Yzen ā PHP Bootstrap Admin Dashboard Template was rejected without any comment after we released the PHP version. This lack of communication is frustrating, especially after investing significant time and effort into these submissions.
-
Xintra ā React TypeScript Tailwind CSS Admin Dashboard Template: We are particularly confused about the rejection of this template. There was no mention of any issues or feedback in the review, but it was rejected nonetheless. The only reason provided was ātechnical differences,ā which, as mentioned before, does not seem like a valid justification. The quality of the template has been reviewed multiple times, and we have received positive feedback from customers. I fail to understand why this particular version was rejected, especially when other versions (like React with JavaScript) have been successful. Could it be that the review process is based on a misunderstanding or an over-simplified approach? If there are quality issues, we would appreciate specific comments so that we can make necessary improvements.
-
Quality of Reviews: Our team consists of professionals, and we take great pride in delivering high-quality items. Over the years, we have successfully released over 350 products, and we are always open to improving based on constructive feedback. However, the current review process is not transparent, and the rejections feel like time wasters, especially when there is no clear explanation or understanding of what is actually expected. We have consistently followed best practices, and our portfolio reflects that.
-
Reviewer Expectations: It seems that the reviewers do not fully understand what customers are looking for or how the industry is evolving. We are developing items based on customer needs and adapting to new technologies like Next.js, React, TypeScript, and others. However, when we receive feedback such as ānot accepting technical differences,ā it becomes unclear whether we are supposed to limit ourselves to certain versions or not. This lack of clarity only adds to the frustration of both authors and customers.
-
Marketplace Goals: Both authors and the marketplace aim to provide a wide variety of projects that cater to different customer needs. Flexibility in technology and versioning is crucial, and rejecting new technologies without clear guidelines is detrimental to both authors and customers. We strive to meet the market demand, and we have seen consistent sales across multiple versions. Therefore, it is important for the review team to be more open to these variations.
-
Team Effort and Professionalism: Our team consists of over 35 professionals, and we are fully committed to delivering quality products. However, the current review process is causing disappointment, and many authors are struggling with the platform due to the lack of clarity and proper communication. We have already submitted support requests but are still awaiting a response. This prolonged delay is causing frustration among our team.
-
Current Submission ā Mamix - Asp.Net Core & MVC Tailwind Admin Dashboard Template: This item is still under review, but based on the current situation, I am not hopeful that it will be approved. Many authors, including ourselves, are starting to feel that the review process lacks transparency, and we are left uncertain about what is actually required for approval. This is causing many authors, including us, to reconsider their future on this platform.
In conclusion, we respectfully request that the review team provide clearer feedback, communicate better regarding rejections, and allow more flexibility in terms of the technologies and versions we are submitting. We are dedicated to delivering high-quality products and will continue to improve based on the right guidance.
This marketplace is our primary source of income, and after 7 years of dedicated work, the current situation is deeply affecting our business. We have always focused on this platform exclusively, but now we are questioning our future. The lack of clarity and consistent rejections are forcing us to reconsider our commitment.
Thank you for your time, and I hope to see more constructive feedback in the future.