DEV Community

MapleBridge.io
MapleBridge.io

Posted on Edited on

How I Built an AI-Powered B2B Supplier Matching Platform (MapleBridge.io)

Editorial update — 22 September 2026: This article discusses a technical design, not the current product's supplier-discovery capabilities. MapleBridge is a procurement workspace for buyers using their own supplier contacts: create an RFQ, invite suppliers, receive their quotes and compare responses. It does not provide a verified supplier directory or automatic supplier introductions.

Correction to the original product description

The original version described a cross-verified supplier database assembled from four marketplaces, automatic compliance matching and better matching accuracy. Those statements were not supported by evidence presented in the article and should not be treated as available MapleBridge capabilities. They have been removed, along with the blanket pricing claim.

MapleBridge.io is a procurement workspace. Buyers bring their supplier contacts, create an RFQ, invite suppliers and compare the quotes they receive.

The underlying sourcing problem

When supplier responses arrive in different formats, a buyer may need to reconcile product specifications, quantities, currencies, packaging, lead times and exclusions before comparing prices. A supplier listing alone does not settle these questions.

A structured request helps each invited supplier answer the same commercial questions. Missing information should remain visible rather than being filled with assumptions.

Historical matching architecture

The original technical idea was:

Buyer brief → Intent parser → Structured requirements
            → Candidate comparison → Evidence and open questions
Enter fullscreen mode Exit fullscreen mode

This is a design illustration, not the workflow of an operating supplier-discovery service.

The earlier stack discussion used FastAPI and SQLite and considered QWEN and OpenAI models for bilingual parsing. It did not establish a benchmark showing one model to be better or a completed verification system. The transferable lesson is to validate extracted fields and preserve the original wording for review.

For example, "custom silicone phone case with logo" and "OEM mobile accessories" may be related, but that similarity says nothing by itself about tooling, order quantity, price or the supplier's ability to deliver.

What supplier verification would actually require

The previous article's verification code was a sketch, not a working integration with business registries, customs records or marketplace databases. Appearing on several websites is not independent proof of manufacturing capability.

A more honest example keeps claimed information separate from checks:

# Illustrative record structure, not an implemented verification service.
supplier_review = {
    "supplier_reference": "EXAMPLE_ONLY",
    "submitted_company_name": None,
    "submitted_documents": [],
    "independent_checks": [],
    "unresolved_questions": [],
    "status": "not_verified"
}
Enter fullscreen mode Exit fullscreen mode

An implementation would need authorized data sources, evidence dates, entity matching, human review and a clear way to record unresolved findings. The current workspace does not supply a pre-verified factory database.

Product and channel requirements

Requirements differ by the actual product, destination and selling channel. A model-generated label such as "compliant" cannot establish that a product is ready to import or sell.

An RFQ can instead ask suppliers to state:

  • the exact product and specification being quoted;
  • quantity, unit price, currency and quote validity;
  • packaging and labeling included in the price;
  • production lead time and delivery terms;
  • available documents for the buyer's requested checks;
  • exclusions, assumptions and items needing confirmation.

The buyer still needs to determine the applicable requirements and review the evidence. MapleBridge does not certify suppliers or products.

What the current workflow does

  1. The buyer prepares an RFQ.
  2. The buyer invites their own supplier contacts.
  3. Suppliers submit their quotations.
  4. The buyer compares the responses and follows up on missing details.

This is not automatic supplier discovery, a marketplace introduction service or a guarantee of order fulfillment. No matching-performance result or pricing promise is made in this article.

Further reading


Related MapleBridge links

Top comments (0)