How should rejected submissions be explained?
When a design idea does not fit, say so clearly. Keep the message simple. Protect the work and relationships.
StarbornHub is not another sofa list. It is a free-to-join growth system for independent furniture retailers. Rejection is part of a practical process that helps retailers make safer product choices and build market-fit scarcity.
We explain why a submission did not pass basic checks. We show what matters next. We do not publish private rules or payout details.
Why do some submissions get rejected outright?
We cannot approve every design. Some ideas do not align with factory limits or market needs.
A clear rejection protects your time and the market. It prevents costly development on ideas that cannot scale or that raise quality or transport risks.
Independent retailers must avoid hidden risks. StarbornFurniture provides the factory capability layer and has real production limits. StarbornHub sits between retailers and the factory as the mechanism that filters and supports ideas. Roger acts as the trust bridge, explaining choices in plain terms. Some submissions fail because the factory cannot build them reliably, because the materials or construction would create quality problems in real life, or because packing and transport would be too risky for a given market. Other times an idea simply does not fit the current product direction or category strategy. Rejection at this stage saves time and cost. It also protects the reputation of the retailer and the brand. We treat every submission with respect. We do not keep failed ideas in a loop of endless edits. That is not the role of StarbornHub. The system focuses on products that can be built, shipped, and sold with a good customer experience and sound margin. Explaining these practical reasons helps contributors and retailers aim at viable opportunities next time.
How should a rejection be communicated to a contributor?
Communication must be timely, concise, and respectful.
Tell contributors that the submission did not pass basic checks. Give clear, non-technical reasons. Offer next steps without promising detailed coaching or private numbers.
A simple email or message works best. Start by thanking the contributor for their effort. State that the submission did not pass the base review. Then give a short reason in plain language. Use phrases like “production risk,” “quality concern,” “logistics mismatch,” or “does not fit current product direction.” Avoid technical formulas and precise thresholds. Explain the general principle behind the decision. For example, note if the idea would require manufacturing changes that increase failure risk, or if it would not meet the kind of customer signal the marketplace is currently showing. Offer a path forward: contributors may submit new work in the future. Make it clear that a rejected submission does not block future ideas. Where useful, recommend general areas to explore next, such as simpler construction, clearer fit with local customer tastes, or designs that favor proven transport methods. Keep the tone supportive. The goal is not to shut people down. It is to guide them toward designs that have a realistic chance in market and in factory practice.
What kind of feedback should be public versus private?
Not all feedback belongs in a public note. Protect IP and personal data. Share useful principles, not private rules.
Public feedback should focus on general principles: design respect, why some issues matter, and what types of changes are more likely to succeed. Keep contract and payout details private.
When you give feedback, think about the audience. Public-facing reasons help the broader retail community learn. They also keep the marketplace honest and predictable. In public, explain that decisions are driven by long-term account value, customer-signal-backed priorities, city-level differentiation, and manufacturing practicality. Avoid publishing confidential terms, payment splits, eligibility rules, or specific metrics used to score submissions. Those belong in private channels. Also protect contributors’ creative work. Do not disclose detailed IP handling steps or contract clauses in public notes. Instead, say that creative contributions are respected and that accepted ideas will enter a proper development and IP review process. This level of clarity builds trust. It tells retailers and designers how the system treats original work while keeping sensitive details where they belong.
How can contributors and retailers use a rejection to improve outcomes?
Treat rejection as a data point. Use it to refine product choices and market approach.
A rejected submission can be a learning tool. Focus on market fit, simpler builds, and clear signals from customers. Use fair contribution records and city-level differentiation to guide new ideas.
When a submission is rejected, look at the reason in light of your retail strategy. If a design was flagged for production risk, consider designs that use proven joinery or standard materials. If the main issue was market fit, study local sales patterns and customer feedback to find the gap. StarbornHub values long-term account health. That means building a track record of fair contributions and sensible choices. Retailers should think in terms of product families that create scarcity and demand, not in one-off experiments that have low chance of success. Designers should respect the realities of manufacturing and retail logistics. Where possible, test key assumptions in small ways before full development—mockups, local surveys, or small-batch proofs. StarbornHub can support operational tasks like logistics advice and market-fit signals, but it is not an unlimited design clinic. Use the feedback to refine your brief, then resubmit with a design that answers the practical concerns. That is the path to better conversion and healthier margins.
Conclusion
Clear, respectful rejection protects creators and retailers. It guides better product choices. It keeps the market healthy while preserving trust and future opportunities.
