Add support for Chinese LCSC (szlcsc.com)

[Ainndy]

As discussed in PR #1194, while the international LCSC is great, many users in the Chinese market rely on szlcsc.com. I would like to request a dedicated provider for the Chinese version of LCSC.

[swdee]

Can you provide a few examples of the raw scanned barcode data and URL's/Links of those parts on szlcsc?

It looks like a search by LCSC part number c138033 can be done with https://so.szlcsc.com/global.html?k=%%part_number%%. However the search result has many source vendors parts and pricing. To load the specific LCSC part would require parsing that page to pull out the item number https://item.szlcsc.com/149349.html.

[Ainndy]

Can you provide a few examples of the raw scanned barcode data and URL's/Links of those parts on szlcsc?

It looks like a search by LCSC part number c138033 can be done with https://so.szlcsc.com/global.html?k=%%part_number%%. However the search result has many source vendors parts and pricing. To load the specific LCSC part would require parsing that page to pull out the item number https://item.szlcsc.com/149349.html.

I have scanned a real QR code from a recent szlcsc.com package! Here is the raw data:

{pc:C6119790,pm:CGA0402X5R224K250GT,qty:100,mc:,cc:1,pdi:200616857,hp:null}

Actual Web URL: https://item.szlcsc.com/7062496.html

[swdee]

I have scanned a real QR code from a recent szlcsc.com package! Here is the raw data:

{pc:C6119790,pm:CGA0402X5R224K250GT,qty:100,mc:,cc:1,pdi:200616857,hp:null}

Actual Web URL: https://item.szlcsc.com/7062496.html

That barcode is mostly the same as the LCSC one, the most important part is the field pc:C6119790. You can actually paste that barcode in to the Scanner and it will detect it as an LCSC part.

When creating a part it does correctly load the part details.

So from the example barcode you have provided it does in fact work. Do you have any barcodes from szlcsc that don't work?

[Ainndy]

I have scanned a real QR code from a recent szlcsc.com package! Here is the raw data:
{pc:C6119790,pm:CGA0402X5R224K250GT,qty:100,mc:,cc:1,pdi:200616857,hp:null}
Actual Web URL: https://item.szlcsc.com/7062496.html

That barcode is mostly the same as the LCSC one, the most important part is the field pc:C6119790. You can actually paste that barcode in to the Scanner and it will detect it as an LCSC part.

When creating a part it does correctly load the part details. So from the example barcode you have provided it does in fact work. Do you have any barcodes from szlcsc that don't work?

"You are absolutely right. The barcode format is compatible, and the scanner correctly identifies the pc:C6119790 field. My scan works with the current LCSC provider because the Part Number (C-number) is universal across both sites."

"However, the main issue is the data source. Currently, it pulls information from the international site (lcsc.com), which provides descriptions in English and prices in USD. For users in the Chinese market, we specifically need the data from szlcsc.com for several Descriptions and parameters in Chinese are much more helpful for local users."

"I noticed that szlcsc.com uses a different endpoint/URL structure compared to lcsc.com, which seems to be the main challenge for implementation. Since the barcodes are identical, would it be possible to add an option to choose the 'Data Origin' (International vs. Chinese) for the LCSC provider?"

[swdee]

Since the barcodes are identical, would it be possible to add an option to choose the 'Data Origin' (International vs. Chinese) for the LCSC provider?"

Yes, that is probably a good way to handle this. Under System Settings, Info Provider, add a Data Origin to the LCSC provider.

[jbtronics]

Yes, that is probably a good way to handle this. Under System Settings, Info Provider, add a Data Origin to the LCSC provider.

I agree. In the end its also the same data, just with different language and currency.

And I would hope that large parts of the LCSC logic can be reused.

[Ainndy]

Since the barcodes are identical, would it be possible to add an option to choose the 'Data Origin' (International vs. Chinese) for the LCSC provider?"

Yes, that is probably a good way to handle this. Under System Settings, Info Provider, add a Data Origin to the LCSC provider.

One more thing I noticed: The QR code raw data clearly contains the field qty:100. However, when I scan the code, this quantity doesn't seem to be automatically filled into the 'amount' or 'stock' field.

Is this a limitation of the current scanner implementation, or can we make the LCSC provider parse the qty value to facilitate faster stock intake? It would be a huge time-saver if scanning the bag could automatically suggest the quantity to be added to the inventory.

[swdee]

Is this a limitation of the current scanner implementation, or can we make the LCSC provider parse the qty value to facilitate faster stock intake?

Yes, this is a current limitation of the scanner. Another user commented about adding this feature here.

One of the issues about using the Quantity field from the barcode is how that will work as the quantity is associated with the storage location, which requires manual selection. In terms of process, how do you see that working?

One process idea could be;

• Scan the barcode of an existing Storage Location which sets the Location to use.
• Then scan the barcode of the Part to create. This reads in the Quantity field and makes use of the scanned Storage Location.

[jbtronics]

Part-DB 2.9.0 implements the ideas of @MayNiklas.
When scanning an LCSC, digikey or mouser barcode, Part-DB will create an part lot, with the order number as description, the quantity and the label content as user barcode, so that scanning the label will redirect to the specific partlot directly.

[Ainndy]

Part-DB 2.9.0 implements the ideas of @MayNiklas. When scanning an LCSC, digikey or mouser barcode, Part-DB will create an part lot, with the order number as description, the quantity and the label content as user barcode, so that scanning the label will redirect to the specific partlot directly.

Increment Mode: If the part already exists in that location, scanning the barcode should ideally increment the current stock by the qty value.

[liuyang0690]

我扫描了一个真实的二维码，来自最近的 szlcsc.com 包裹！以下是原始数据：实际网页网址：https://item.szlcsc.com/7062496.html`{pc:C6119790,pm:CGA0402X5R224K250GT,qty:100,mc:,cc:1,pdi:200616857,hp:null}`

那个条形码和LCSC的条形码基本相同，最重要的是字段。你其实可以把条形码粘贴到扫描仪上，它会检测它是LCSC零件。pc:C6119790
创建零件时，它确实会正确加载零件细节。所以从你举的条形码示例来看，它确实是能用的。你有没有SZLCSC的条形码不能用？

“你说得完全正确。条码格式兼容，扫描仪能正确识别 pc：C6119790 字段。我的扫描结果适用于当前的LCSC提供者，因为零件编号（C编号）在两个地点都是通用的。”

“不过，主要问题是数据来源。目前，它从国际网站（lcsc.com）获取信息，网站提供英文描述和美元价格。对于中国市场用户，我们特别需要 szlcsc.com 数据，若干描述和中文参数对本地用户更有帮助。”

“我注意到 szlcsc.com 使用的端点/URL结构与 lcsc.com 不同，这似乎是实现上的主要挑战。既然条形码相同，是否可以添加选择LCSC提供商'数据来源'（国际与中国）的选项？”

Firstly, LCSC and SZLCSC have adopted different path structures on the product detail pages. Currently, the URL of SZLCSC is difficult to access directly through tags because the product number starting with "C" and the internal product ID cannot be matched. I have temporarily solved this problem through regular expressions. It is necessary to manually obtain the product detail page ID through the product number starting with "C", and then automatically extract the Chinese page elements after input.

[liuyang0690]

我扫描了一个真实的二维码，来自最近的 szlcsc.com 包裹！以下是原始数据：实际网页网址：https://item.szlcsc.com/7062496.html`{pc:C6119790,pm:CGA0402X5R224K250GT,qty:100,mc:,cc:1,pdi:200616857,hp:null}`

那个条形码和LCSC的条形码基本相同，最重要的是字段。你其实可以把条形码粘贴到扫描仪上，它会检测它是LCSC零件。pc:C6119790
创建零件时，它确实会正确加载零件细节。所以从你举的条形码示例来看，它确实是能用的。你有没有SZLCSC的条形码不能用？

“你说得完全正确。条码格式兼容，扫描仪能正确识别 pc：C6119790 字段。我的扫描结果适用于当前的LCSC提供者，因为零件编号（C编号）在两个地点都是通用的。”

“不过，主要问题在于数据来源。目前，它从国际网站（lcsc.com）获取信息，该网站提供英文描述和美元价格。对于中国市场的用户，我们特别需要 szlcsc.com 的数据，中文描述和参数对本地用户更有帮助。”

“我注意到 szlcsc.com 使用了与 lcsc.com 不同的端点/URL结构，这似乎是实施上的主要挑战。既然条码相同，是否可以为LCSC提供商添加选择'数据来源'（国际与中国）的选项？”

In the short term, it is unlikely that SZLCSC will open an API similar to that of LCSC, as JLC already provides a domestic inventory management system with comparable functions, which is part of its product promotion strategy.

[swdee]

Firstly, LCSC and SZLCSC have adopted different path structures on the product detail pages. Currently, the URL of SZLCSC is difficult to access directly through tags because the product number starting with "C" and the internal product ID cannot be matched. I have temporarily solved this problem through regular expressions. It is necessary to manually obtain the product detail page ID through the product number starting with "C", and then automatically extract the Chinese page elements after input.

I have taken a look and its actually easier than this, data extraction can be achieved with the following steps;

1. Given the product code c138033 we perform a search using URL https://so.szlcsc.com/global.html?k=%%product_code%.

2. In the returned HTML it has JSON data we can extract;

{
  "@context": "http://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "item": {
        "@type": "Product",
        "name": "RC0402FR-071ML",
        "image": "https://alimg.szlcsc.com/upload/public/product/breviary/20230110/08BE2CE85F7626B90ACD952AE0F6F271.jpg",
        "description": "特性：无卤环氧树脂。符合RoHS标准。无铅端接产品符合RoHS要求。RoHS豁免电极、电阻元件和玻璃中含有的铅玻璃。减少对环境有害的废物。高组件和设备可靠性。应用：所有通用应用",
        "brand": {
          "@type": "Brand",
          "name": "YAGEO(国巨)"
        },
        "offers": {
          "@type": "Offer",
          "url": "https://item.szlcsc.com/149349.html",
          "priceCurrency": "CNY",
          "price": 0.0047,
          "availability": "http://schema.org/InStock"
        }
      }
    }
  ],
  "numberOfItems": "1",
  "name": "c138033搜索结果",
  "description": "立创商城-专业的电子元器件现货采购平台,为您提供c138033的价格，库存，数据手册，参数等信息，采购c138033上立创商城。"
}

3. From the JSON we can parse out the Offer: url key to get the product page https://item.szlcsc.com/149349.html.

4. From the product page HTML we can extra the JSON data.

{
  "@context": "http://schema.org",
  "@type": "Product",
  "name": "YAGEO(国巨) RC0402FR-071ML",
  "sku": "C138033",
  "mpn": "RC0402FR-071ML",
  "brand": "YAGEO(国巨)",
  "description": "贴片电阻 RC0402FR-071ML由YAGEO(国巨)设计生产，立创商城现货销售，正品保证，参考价格￥0.0025，封装为0402。商城还提供RC0402FR-071ML专业规格书、详细参数、引脚图、PCB焊盘图，典型应用图，Datasheet数据手册等资料查询和免费下载。",
  "image": [
    "https://alimg.szlcsc.com/upload/public/product/source/20230110/08BE2CE85F7626B90ACD952AE0F6F271.jpg",
    "https://alimg.szlcsc.com/upload/public/product/source/20230110/2E109E1D3559E8A319D97EBF1F5FABBF.jpg",
    "https://alimg.szlcsc.com/upload/public/product/source/20230110/668E5FBF2A80CF6C4D827E4711490D51.jpg"
  ],
  "offers": {
    "@type": "Offer",
    "url": "https://item.szlcsc.com/149349.html",
    "priceCurrency": "CNY",
    "price": 0.0025,
    "itemCondition": "http://schema.org/NewCondition",
    "availability": "http://schema.org/InStock",
    "inventoryLevel": 1009177,
    "seller": {
      "@type": "Organization",
      "name": "立创商城",
      "url": "https://www.szlcsc.com"
    }
  }
}

[liuyang0690]

首先，LCSC和SZLCSC在产品详情页采用了不同的路径结构。目前，SZLCSC 的网址难以通过标签直接访问，因为产品编号以“C”开头和内部产品 ID 无法匹配。我暂时通过正则表达式解决了这个问题。需要手动通过以“C”开头的产品编号获取产品详情页ID，然后在输入后自动提取中文页面元素。

我看过了，实际上比这更简单，数据提取可以通过以下步骤实现;

1. 给定产品代码，我们使用 URL 进行搜索。c138033``https://so.szlcsc.com/global.html?k=%%product_code%
2. 在返回的 HTML 中，它包含我们可以提取的 JSON 数据;

{
  "@context": "http://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "item": {
        "@type": "Product",
        "name": "RC0402FR-071ML",
        "image": "https://alimg.szlcsc.com/upload/public/product/breviary/20230110/08BE2CE85F7626B90ACD952AE0F6F271.jpg",
        "description": "特性：无卤环氧树脂。符合RoHS标准。无铅端接产品符合RoHS要求。RoHS豁免电极、电阻元件和玻璃中含有的铅玻璃。减少对环境有害的废物。高组件和设备可靠性。应用：所有通用应用",
        "brand": {
          "@type": "Brand",
          "name": "YAGEO(国巨)"
        },
        "offers": {
          "@type": "Offer",
          "url": "https://item.szlcsc.com/149349.html",
          "priceCurrency": "CNY",
          "price": 0.0047,
          "availability": "http://schema.org/InStock"
        }
      }
    }
  ],
  "numberOfItems": "1",
  "name": "c138033搜索结果",
  "description": "立创商城-专业的电子元器件现货采购平台,为您提供c138033的价格，库存，数据手册，参数等信息，采购c138033上立创商城。"
}

3. 从JSON中我们可以解析出密钥，得到产品页面。Offer: url``https://item.szlcsc.com/149349.html
4. 从产品页面的 HTML 中，我们可以添加 JSON 数据。

{
  "@context": "http://schema.org",
  "@type": "Product",
  "name": "YAGEO(国巨) RC0402FR-071ML",
  "sku": "C138033",
  "mpn": "RC0402FR-071ML",
  "brand": "YAGEO(国巨)",
  "description": "贴片电阻 RC0402FR-071ML由YAGEO(国巨)设计生产，立创商城现货销售，正品保证，参考价格￥0.0025，封装为0402。商城还提供RC0402FR-071ML专业规格书、详细参数、引脚图、PCB焊盘图，典型应用图，Datasheet数据手册等资料查询和免费下载。",
  "image": [
    "https://alimg.szlcsc.com/upload/public/product/source/20230110/08BE2CE85F7626B90ACD952AE0F6F271.jpg",
    "https://alimg.szlcsc.com/upload/public/product/source/20230110/2E109E1D3559E8A319D97EBF1F5FABBF.jpg",
    "https://alimg.szlcsc.com/upload/public/product/source/20230110/668E5FBF2A80CF6C4D827E4711490D51.jpg"
  ],
  "offers": {
    "@type": "Offer",
    "url": "https://item.szlcsc.com/149349.html",
    "priceCurrency": "CNY",
    "price": 0.0025,
    "itemCondition": "http://schema.org/NewCondition",
    "availability": "http://schema.org/InStock",
    "inventoryLevel": 1009177,
    "seller": {
      "@type": "Organization",
      "name": "立创商城",
      "url": "https://www.szlcsc.com"
    }
  }
}

That's a good approach. However, for electronic components like transistors and diodes, their parameters are also very important, and the current method cannot obtain these related parameters. I have an idea. Since the numbering starting with "C" seems to be consistent between LCSC and SZLCSC, we could integrate data from both sites using the method you provided. That is, get the brand, price, description, and price from SZLCSC, and get the other parameters from LCSC. This way, we could obtain relatively comprehensive Chinese component data, but it might be a bit of a roundabout way.