A clear brief is not just more text
A clear request lets a supplier decide whether it is a fit. “Looking for pet products” is too broad. “Private-label pet leather care and cleaning products for the US market, small first order, branded packaging” is matchable.
The system looks for product use case, target market, quantity, certification, packaging, sample needs, delivery timing, and buying stage.
| Vague request | More matchable request |
|---|---|
| Looking for earbuds factory | 500 FCC Bluetooth earbuds for US Amazon FBA, sample first, custom packaging |
| Need beauty packaging | Low-MOQ private-label serum bottles or cream jars for a US indie beauty brand |
| Looking for pet products | Private-label pet leather care or cleaning products for US pet-brand channels |
| Need apparel supplier | Small-batch yoga apparel with fabric, size chart, hangtag, and North America fit support |
How fields affect matching
Each field changes the matching decision. Missing one field does not always block a match, but too many missing fields reduce confidence.
| Field | What it affects |
|---|---|
| Product scope | Whether suppliers serve the same product and use case |
| MOQ or first order size | Whether the supplier can actually accept the order |
| Certification | Whether the supplier fits the US, Canada, or another target market |
| Packaging and brand | Whether OEM, ODM, label, carton, or FBA support is needed |
| Sample requirement | Whether both sides can start with lower risk |
| Timeline | Whether the match is practical, not just similar |
How incomplete briefs should be handled
If the direction is clear but fields are incomplete, the request should not disappear. It can be retained, completed later, or rematched when new supplier capability appears.
If quick-action button text such as Skip or publish now appears in the message, it should be treated as interface intent, not as part of the core sourcing need.
- Clear direction with missing fields: keep for completion or lower-confidence matching.
- High semantic score with conflict: move to candidate pool instead of sending email.
- Quick-action text: treat as operation metadata, not core_need.
- Unrelated text: clean and record the reason.
What suppliers are more likely to answer
Suppliers can answer faster when a request states what is needed, how many units, where it will be sold, what certification matters, whether the buyer wants samples, and whether packaging is custom.
MapleBridge does not promise a purchase or a sale. It makes the first comparison clearer for both sides.
- Describe the product use case, not only keywords.
- Include first order size or acceptable MOQ range.
- Mention target country and channel such as Amazon FBA, Shopify, or wholesale.
- List required certifications or certification uncertainty.
- State packaging, label, private-label, and sample needs.
FAQ
Will incomplete demand be discarded?
It should be retained when the direction is clear, then completed or rematched later.
Why should quick-action button text stay out of core_need?
Because text such as Skip or publish now is an interface action, not the buyer's sourcing requirement.
Can Chinese demand match English supplier profiles?
Yes, after the fields are structured and cross-language semantic matching is applied.