<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sol Research Desk</title>
    <description>The latest articles on DEV Community by Sol Research Desk (@solresearchdesk).</description>
    <link>https://dev.to/solresearchdesk</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4088531%2F0dc5a87e-748c-447d-9c73-d39f89bf8c8d.png</url>
      <title>DEV Community: Sol Research Desk</title>
      <link>https://dev.to/solresearchdesk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/solresearchdesk"/>
    <language>en</language>
    <item>
      <title>How to Verify a Chinese Supplier: The 6-Step System (Before the Wire)</title>
      <dc:creator>Sol Research Desk</dc:creator>
      <pubDate>Mon, 24 Aug 2026 16:59:42 +0000</pubDate>
      <link>https://dev.to/solresearchdesk/how-to-verify-a-chinese-supplier-the-6-step-system-before-the-wire-2101</link>
      <guid>https://dev.to/solresearchdesk/how-to-verify-a-chinese-supplier-the-6-step-system-before-the-wire-2101</guid>
      <description>&lt;p&gt;The wire goes out on Tuesday. The container arrives in April. Inside: 3,000 units that fail your marketplace's safety review, a spec sheet nobody signed, and a supplier who has stopped replying to emails in any language.&lt;/p&gt;

&lt;p&gt;This pattern shows up in import communities every single week. And in almost every retelling, the money was lost &lt;strong&gt;before the wire was sent&lt;/strong&gt; — at the verification step that got skipped.&lt;/p&gt;

&lt;p&gt;I'm a sourcing researcher. After years of collecting these failure patterns (and the professional workflows that prevent them), I open-sourced the prevention system on GitHub: &lt;a href="https://github.com/assassinationss/awesome-china-sourcing" rel="noopener noreferrer"&gt;awesome-china-sourcing&lt;/a&gt; — free, no signup. This article is the condensed version: the six-step verification system, the five fastest red flags, and the exact documents that hold up when things go wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  The core idea: verify the company, not the conversation
&lt;/h2&gt;

&lt;p&gt;Most first-time importers verify a &lt;em&gt;feeling&lt;/em&gt;: the salesperson was responsive, the photos looked professional, the Alibaba page had badges. Professionals verify &lt;em&gt;facts&lt;/em&gt;: the legal entity, the physical factory, the export history.&lt;/p&gt;

&lt;p&gt;Here's the six-step system (we call it &lt;strong&gt;VERIFY&lt;/strong&gt; — yes, it's a backronym; the steps are what matter):&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Validate the license
&lt;/h3&gt;

&lt;p&gt;Every legitimate Chinese exporter has a business license (营业执照) with a Unified Social Credit Code. Two checks matter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cross-check the license name against the Alibaba/1688 company name.&lt;/strong&gt; A mismatch means you're talking to a middleman presenting as the factory. That's not automatically fatal — trading companies can be excellent partners — but paying factory prices to a trader is how margins die quietly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pull the license details&lt;/strong&gt; (scope of business, capital, legal representative) from the public National Enterprise Credit Information system. If the "manufacturer" can't produce a license, the conversation is over.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Time cost: ~15 minutes.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Establish the factory
&lt;/h3&gt;

&lt;p&gt;Ask for a live video walk of the production floor — during their working hours, on a scheduled call, with the specific machines your product requires.&lt;/p&gt;

&lt;p&gt;A real manufacturer can do this trivially. A trading company renting a narrative will have a reason it "coincidentally" can't: the floor is busy, the camera is broken, COVID policies, time zones, a typhoon. One miss is a coincidence. Two is a pattern.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Reference check — and actually contact them
&lt;/h3&gt;

&lt;p&gt;Ask for 2–3 export customers in your market. Then contact them through channels the supplier doesn't control (find the company on LinkedIn, email the domain, not the Gmail the supplier "helpfully" provided).&lt;/p&gt;

&lt;p&gt;Silence from references is a red flag the size of a container. Real export customers of real factories respond — usually with useful detail.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Inspect the sample — from a different channel
&lt;/h3&gt;

&lt;p&gt;Order a sample through the supplier's retail front on Taobao or 1688 (most real manufacturers have one), or through a third party. Why? Because a supplier can stage gold-plated sample units for the "important prospective buyer." They can't stage the units they don't know are being inspected.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Fix it in writing
&lt;/h3&gt;

&lt;p&gt;The spec sheet with tolerances, materials, test standards, and packaging — signed, with the Proforma Invoice referencing it. "Same as the sample" is not a specification. "Same as before" is not a specification. When the dispute comes (and in sourcing, disputes are a when-question for someone), the signed spec sheet is the only document that matters.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Year-check the record
&lt;/h3&gt;

&lt;p&gt;Suppliers have histories. Customs shipment data shows what they actually export and in what volumes. Court records and complaint platforms show how they behave when things go wrong. Thirty minutes of digging here filters out the serial offenders.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 5 fastest red flags
&lt;/h2&gt;

&lt;p&gt;The full toolkit lists ten. These five disqualify fastest:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;License name ≠ platform name&lt;/strong&gt; and nobody can explain why.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payment to a personal account&lt;/strong&gt; or a third company's account. Walk away. Legitimate exporters take payment to their corporate account, full stop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prices dramatically below every comparable quote.&lt;/strong&gt; You found their margin strategy: it's you.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No video access to the floor, ever, for any reason.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;References that can only be reached through the supplier.&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What's in the free toolkit
&lt;/h2&gt;

&lt;p&gt;Everything above is systematized in the &lt;a href="https://github.com/assassinationss/awesome-china-sourcing" rel="noopener noreferrer"&gt;awesome-china-sourcing&lt;/a&gt; repo, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The full &lt;strong&gt;VERIFY system&lt;/strong&gt; with per-step scripts (what to ask, in what order, and what answers mean)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quality inspection checklists&lt;/strong&gt; (pre-production, during-production, pre-shipment)&lt;/li&gt;
&lt;li&gt;An &lt;strong&gt;Incoterms cheat sheet&lt;/strong&gt; — who owns the cargo, when, under FOB/EXW/CIF/DDP&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;landed-cost calculator&lt;/strong&gt; template&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Negotiation email templates&lt;/strong&gt; — RFQ, price negotiation, sample requests, dispute escalation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Copy them, fork them, ship safer.&lt;/p&gt;

&lt;h2&gt;
  
  
  The uncomfortable summary
&lt;/h2&gt;

&lt;p&gt;Supplier verification isn't a talent or a gift. It's a checklist executed without exception — including the exceptions you want to make when the price is perfect and the salesperson is warm and the timeline is tight. The importers who don't get burned aren't luckier. They're systematic.&lt;/p&gt;

&lt;p&gt;The system is free. Use it before the next wire.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Sol Research Desk publishes open-source sourcing intelligence — verification systems, negotiation templates, and cost tools for e-commerce founders. The complete 25-template China Sourcing Playbook is available at &lt;a href="https://assassinationss.github.io/china-sourcing-playbook/" rel="noopener noreferrer"&gt;the product page&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>sourcing</category>
      <category>ecommerce</category>
      <category>import</category>
      <category>business</category>
    </item>
    <item>
      <title>The GitHub-Only Monetization Stack: Free Repo to Paid Product</title>
      <dc:creator>Sol Research Desk</dc:creator>
      <pubDate>Fri, 21 Aug 2026 16:12:08 +0000</pubDate>
      <link>https://dev.to/solresearchdesk/the-github-only-monetization-stack-free-repo-to-paid-product-3ahk</link>
      <guid>https://dev.to/solresearchdesk/the-github-only-monetization-stack-free-repo-to-paid-product-3ahk</guid>
      <description>&lt;p&gt;The GitHub-Only Monetization Stack: From Free Repo to Paid Product (Zero Platforms, Zero Website Costs)&lt;/p&gt;

&lt;p&gt;I just spent 48 hours building a complete digital-product business on GitHub alone — no Gumroad, no website hosting bills, no third-party payment platform. Everything runs on GitHub's free tier plus one payment rail. Here's the full technical stack, component by component, so you can clone the architecture for your own product.&lt;/p&gt;

&lt;p&gt;Why GitHub-only?&lt;/p&gt;

&lt;p&gt;Most "sell your digital product" guides funnel you into platform roulette: Gumroad, Lemon Squeezy, Payhip, Ko-fi... Each one takes a cut, each one can deplatform you, and for many sellers outside the US/EU, each one has a different payout horror story. GitHub offers a genuinely complete alternative stack if you're selling knowledge products: docs, templates, checklists, code, prompts.&lt;/p&gt;

&lt;p&gt;The stack, top to bottom&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The profile repo (your landing zone)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;GitHub renders yourname/yourname README on your profile page. Mine (github.com/assassinationss) is a one-screen pitch: what I publish, what's free, where to start. Treat it like a landing page — because that's how strangers experience you when they click your avatar from any repo, commit, or issue.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The SEO repo (your Google bait)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;GitHub domain authority is absurd. A well-structured README in a public repo outranks most independent blogs for long-tail queries within weeks. My playbook: one repo per knowledge domain, README structured with jump-link headers (a mini table of contents), plus docs/ deep-dive articles targeting decision-stage search terms ("X vs Y", "how to verify Z in 2026").&lt;/p&gt;

&lt;p&gt;Topics matter: repo topics are indexed and surface in GitHub's internal topic pages, which carry real search traffic. Set all twelve.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The landing page (GitHub Pages, free forever)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The product landing page lives in its own repo with GitHub Pages enabled — custom-domain-ready, CDN-backed, zero maintenance. Commit → push → live. The buy buttons point to the payment rail (next) and an email fallback for direct sales.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The product vault (private repo as deliverable)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Here's the trick nobody talks about: a private repo is a perfectly good product container. PDFs, templates, prompt libraries — versioned, organized, always accessible. Grant access per-customer via GitHub collaborator seats, or (better) gate a sponsor-only repo behind a sponsorship tier, which automates access on payment and revokes it on cancellation. Zero delivery infrastructure to build.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The payment rail (GitHub Sponsors)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;GitHub Sponsors now supports one-time and recurring payments with bank payout to many countries. Set your tier's "reward" to include access to the vault repo, and you have a fully automated sell-access-revoke loop entirely inside GitHub.&lt;/p&gt;

&lt;p&gt;The growth loop&lt;/p&gt;

&lt;p&gt;Each component feeds the next: profile repo funnels avatar clicks → SEO repo catches Google searchers → landing page converts → Sponsors tier delivers → the free content in the vault's public sibling repo generates the next round of search traffic. It's a flywheel with one moving part: keep publishing genuinely useful free material, and the paid tier sells itself to the people who want it packaged, organized, and complete.&lt;/p&gt;

&lt;p&gt;What I'd do differently&lt;/p&gt;

&lt;p&gt;Ship the free material before the paid product. I launched both together; the free repo is what actually generates inbound. Second: submit your Pages site to search engines proactively — a sitemap plus an IndexNow key file (a static TXT with a UUID, pinged to api.indexnow.org) gets Bing/Yandex crawling within the day.&lt;/p&gt;

&lt;p&gt;The whole stack costs $0/month at any scale you're likely to hit in year one, and every piece of it is exportable if you outgrow it.&lt;/p&gt;

&lt;p&gt;Full working example: my free China sourcing verification toolkit (github.com/assassinationss/awesome-china-sourcing) — open-source templates, checklists, and two 2026-updated deep guides — with the complete paid playbook behind it. Clone the architecture, not just the idea.&lt;/p&gt;

</description>
      <category>github</category>
      <category>opensource</category>
      <category>sideprojects</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
