Supplier Intelligence Monitor

Supplier Intelligence Monitor

Analyze ImportYeti, Thomasnet, Alibaba, and supplier-directory records into sourcing opportunities, risk scores, capability tags, and watchlist actions.

This Actor is for procurement teams, importers, Amazon sellers, industrial sales teams, and sourcing agencies that already collect supplier records but need a repeatable way to prioritize them.

Workflow Hub

Use the public Supplier Intelligence demo script for the first run: two supplier records become capability tags, risk score, opportunity score, and recommended sourcing actions. Sourcing teams can start from the supplier shortlist intelligence use case or the Supplier Intelligence alternatives page. The proof GIF shows the sourcing shortlist path before connecting an ImportYeti-style shipment export, Thomasnet-style supplier list, or marketplace sourcing dataset.

Proof preview: watch the public-safe sample become buyer-ready output before you run the Actor.

Use the public-safe sample input JSON when you open the Store run form so the first run starts from copy-ready input.

Need the copy-first launch path? Open the sample-first Store handoff to copy the input before returning to the tracked Store run form.

60-Second First Run

1. Start with two supplier records that turn into a shortlist and capability-gap score, using the linked demo before connecting a larger supplier list.
2. Check capability tags, risk score, opportunity score, missing proof, and recommended sourcing action.
3. Route the action rows into a sourcing shortlist, verification queue, or procurement follow-up list before scheduling a broader run.

What You Learn

• Which suppliers look like stronger sourcing opportunities
• Which suppliers need risk review before outreach
• Which capabilities appear in supplier profiles
• Which suppliers mention export activity, certifications, manufacturing, or industrial specialization
• What sourcing action to take next

Use Cases

• Supplier shortlisting
• Competitor sourcing research
• ImportYeti-style shipment dataset enrichment
• Thomasnet or Alibaba supplier list scoring
• Procurement watchlists and sourcing-agent workflows

Input

Provide supplier records inline or pass an Apify datasetId from another supplier scraper.

{
  "defaultCategory": "electronics",
  "suppliers": [
    {
      "supplierName": "Pacific Components",
      "description": "ISO certified electronics manufacturer with export shipments and custom assembly capacity.",
      "shipmentCount": 120,
      "country": "Taiwan"
    }
  ],
  "maxSuppliers": 100
}

Output

Each dataset item is one analyzed supplier profile:

{
  "status": "succeeded",
  "recordIndex": 1,
  "billingEventName": "supplier-profile-analyzed",
  "supplierName": "Pacific Components",
  "category": "electronics",
  "country": "Taiwan",
  "shipmentCount": 120,
  "capabilities": ["manufacturing", "export", "certification", "industrial"],
  "riskScore": 20,
  "opportunityScore": 100,
  "recommendedAction": "Prioritize Pacific Components for sourcing research; capabilities suggest a strong fit: manufacturing, export, certification."
}

The run also writes a SUMMARY key-value-store record with supplier counts and capability counts.

FAQ

Does this scrape supplier directories?

No. It analyzes supplier records you provide inline or through an Apify dataset from another Actor. It is a sourcing intelligence layer, not an ImportYeti, Thomasnet, Alibaba, or IndiaMart scraper.

What input do I need for the first run?

Use the Store example with defaultCategory and one or more supplier records. Supplier name and description are the most useful fields; country, shipment count, rating, website, and certifications improve scoring.

What do I get back?

One dataset item per analyzed supplier, including capabilities, risk score, opportunity score, and recommended sourcing action. The run also writes a SUMMARY record.

Who is this for?

Procurement teams, importers, Amazon sellers, industrial sales teams, and sourcing agencies that need recurring supplier shortlists and risk triage.

When is it commercially chargeable?

The configured paid event is supplier-profile-analyzed at $0.04, scheduled for 2026-05-26T21:05:10Z. Run a small paid smoke after activation before promoting high-volume use.

Pricing

Default monetization model: pay per event.

Recommended chargeable event:

• Event name: supplier-profile-analyzed
• Event meaning: one successfully analyzed supplier profile
• Store price: $0.04 per analyzed supplier profile
• Pricing activation: scheduled for 2026-05-26T21:05:10Z

Successful rows are pushed only after the charge path allows the event. Run a paid smoke after the scheduled activation time before promoting the listing.

Limitations

• This MVP analyzes supplier records; it does not scrape ImportYeti, Thomasnet, Alibaba, or IndiaMart directly.
• Source schemas vary. The Actor recognizes common fields such as supplierName, companyName, description, country, shipmentCount, rating, and website.
• Demand is narrower than review and jobs actors, so use it for focused sourcing workflows.

Automation And Agent Use

• Run a supplier scraper first, then pass its dataset ID to this Actor.
• Schedule watchlist analysis for target categories.
• Send high-opportunity suppliers to a sourcing spreadsheet or CRM.
• Send high-risk suppliers to a verification queue.

Local Development

python3 -m pip install -r requirements.txt
ACTOR_TEST_PAY_PER_EVENT=true apify run --purge --input-file examples/smoke-input.json