Why manual platform search is not enough
On a directory or marketplace, buyers still need to test keywords, open supplier profiles, compare pages, and decide whether a company is actually relevant. The hard work is not finding a list; it is judging fit.
MapleBridge focuses on whether buyer demand and supplier capability are clear enough to compare: product scope, MOQ, certification, packaging, samples, timing, and target market.
| Manual search | MapleBridge matching |
|---|---|
| Search keywords first, judge later | Structure the brief first, then match |
| Many leads, mixed intent | Fewer candidates, each with a fit reason |
| Buyer checks MOQ, certification, packaging | Those fields are part of the match |
| Titles and categories can mislead | High semantic matches with conflicts move into review |
Fields the system tries to structure
A matchable sourcing request needs more than “looking for a factory.” It needs enough context for a supplier to respond with a realistic answer.
| Field | Why it matters |
|---|---|
| Product and use case | Prevents similar words from hiding different buyer intent |
| Quantity and MOQ boundary | Shows whether a supplier can handle sample, small batch, or first PO |
| Certification and market | US, Canada, EU, electronics, kids products, and cosmetics differ |
| Packaging and private label needs | Signals whether OEM, ODM, labeling, or packaging support is required |
| Sample and timeline | Separates capability from practical execution |
| Contact and language | Determines whether email introduction is appropriate |
Matching cannot rely only on broad category gates
Broad categories are useful for obvious errors, but they should not discard every high-semantic-score candidate. Some adjacent or upstream/downstream matches deserve review.
At the same time, semantic similarity alone is not enough. A request for pet leather care products should not automatically notify a leather goods factory just because both mention leather.
- Clear match: key fields align and the pair can move toward notification.
- High score with conflict: keep in the candidate pool or review queue.
- Clearly unrelated: record the reason and keep the original intent for future matching.
When email notification should happen
Email is a late-stage action. The system should confirm the pair is not test data, not a duplicate, and not blocked by category, use-case, or capability conflicts.
That keeps the platform from turning every possible lead into noise. Uncertain but useful candidates stay available for later review or rematching.
| State | Handling |
|---|---|
| High score and key fields align | Create a match and notify both sides with duplicate protection |
| High score but category or use-case conflict | Move to candidate pool or human review |
| Too many missing fields | Retain the intent and revisit after more data or new supply |
| Already notified | Do not resend; keep duplicate or skipped reason |
FAQ
Is MapleBridge a supplier directory?
No. It is designed to structure sourcing intent and supplier capability before matching, not to make users browse endless listings.
Does a high AI score always send email?
No. High semantic score with category, use-case, certification, or capability conflict should go to review instead of automatic notification.
Why keep unmatched demand?
A demand that has no good supplier today may become matchable when a better supplier profile appears later.