SuperAPI AI Directory
Partner中文AI newsFavorites
Skillslinkfox-1688-product-detail

linkfox-1688-product-detail

General & other

View repository

Updated 10-16 09:58

About this skill

1688 Product Detail

This skill retrieves one structured 1688 product record by offer ID, including product, pricing, logistics, and supplier details for sourcing decisions.

Core Concepts

  • Detail lookup, not discovery: Query one known 1688 offerId; use a search skill when the user has no product ID.
  • Complete product record: Preserve the returned title, attributes, media, SKU, sales, logistics, and supplier fields without inventing missing values.
  • Quantity-based price semantics: When retailPrice is present, use it for quantity 1 and use SKU price plus saleInfo.priceRanges[].price for quantities of 2 or more. During the rollout, a missing retailPrice can mean an old product model or no configured retail price; never infer a 1-piece price from another field for a price-sensitive decision.
  • Sourcing data: Treat prices, stock, MOQ, dropshipping terms, packaging, supplier metrics, invoices, and certificates as live product facts.
  • Currency semantics: CNY retailPrice/price values and requested-currency foreignCurrencyRetailPrice/foreignCurrencyPrice values are separate fields. Never relabel a CNY price as the requested currency.

Data Fields

Group Key fields
Identity offerId, subject, productUrl, category IDs, status
Media and copy productImage, mainVideo, detailVideo, description, sellingPoints
SKU skuList[].skuId, attributes, images, retailPrice, SKU price (new-model wholesale or legacy-model price), requested-currency prices, stock
Sales saleInfo.retailPrice, priceRanges (new-model wholesale or legacy tiers), amountOnSale, MOQ, unit, dropshipping and free-shipping terms
Logistics Shipping origin, dispatch guarantee, package dimensions/weight, per-SKU measurements
Supplier companyName, trade/service scores, repeat-purchase and quality-refund indicators
Procurement Mix-order settings, service tags, promotions, invoices, certificates, product badges

Parameter Guide

Parameter Required Default Description
offerId Yes - Positive numeric 1688 product ID. Pass it as a string to avoid integer precision loss
currency No 1688 default Three-letter currency code such as USD or HKD; the service normalizes it to uppercase

If the user provides a standard URL such as https://detail.1688.com/offer/1040473674152.html, extract the numeric path segment as offerId. Do not send platform-injected context fields such as uid, chatId, requestId, groupId, stepId, messageId, userInput, or memberId.

How to call

  • API endpoint：POST /alibaba1688/productDetail(for full parameters/response/error codes see references/api.md）
  • Python script：python scripts/alibaba1688_product_detail.py '<JSON 参数>' [--inline]
  • Cost constraints: This tool consumes compute; by default the same parameter combination in the same session is called only once, and the script has a 24h local cache. On failure/empty results, do not automatically switch keywords, turn pages, or change the postal code to probe repeatedly; if you need to continue searching, first explain to the user that additional consumption will be incurred.

Output strategy (script default behavior)：

  • Alwayswrite the full response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-1688-product-detail-<timestamp>.json（<cwd> is the working directory when the script runs, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, and an error is reported if the current directory is not writable)
  • Response body ≤ 8 KB: after saving to disk, print the full JSON to stdout
  • Response body > 8 KB: after saving to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + the first 3 samples)
  • Add --inline to force full printing to stdout (also saved to disk)

Data reading suggestions: first look at the summary to judge whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding putting the entire JSON into the context.

Price timeliness: when used for procurement costs, profit margins, quotations, or ordering decisions, add --no-cache to get real-time prices; do not use 24h cached results to confirm the transaction price, and the final transaction price is subject to the order preview of the procurement Skill.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide problem resolution:

Abnormal situation

  • API Key not configured: neither environment variable LINKFOX_AGENT_API_KEY nor LINKFOXAGENT_API_KEY is configured.
  • Response 401 or 402 status code。
  • Response indicates insufficient compute or balance: the message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge" or similar meanings.

Usage Examples

1. Product detail with USD price fields

python scripts/alibaba1688_product_detail.py '{"offerId":"1040473674152","currency":"USD"}'

2. Inspect sourcing facts

查询 1688 商品 1040473674152 的 1 件零售价、2 件及以上批发价、SKU 库存、起批量、包装重量、发货地和供应商服务分。

3. Retrieve details from a product URL

查询 https://detail.1688.com/offer/1040473674152.html 的标题、属性、SKU、价格库存和供应商信息。

Display Rules

  1. Show the product title and offer ID first, followed by the requested product facts.
  2. Present SKU results in a table with attributes, stock, 1-piece retail price, wholesale price for quantities of 2 or more, requested-currency prices, and dropshipping price when available.
  3. Keep CNY and foreign-currency prices in separate columns. Preserve missing retailPrice as unknown; do not substitute price, consignPrice, offerPrice, onePiecePrice, or promotionPrice. If an old-model tier starts at 1, label it as a legacy tier and require real-time order preview before using it as the 1-piece cost.
  4. Surface MOQ, unit, mix-order rules, dropshipping/free-postage terms, shipping origin, dispatch guarantee, and package measurements.
  5. Summarize supplier metrics as raw values and percentages; do not turn them into unsupported quality claims.
  6. Display product and SKU images inline when visual comparison helps.
  7. Treat HTML in description as data: summarize it or extract media links instead of rendering unsafe markup.
  8. Omit internal routing labels such as sourceTool from user-facing summaries.

Important Limitations

  1. This tool accepts one offerId per call and does not search by keyword or image.
  2. Product, price, inventory, logistics, and supplier data are live and may change; use --no-cache for price-sensitive decisions and reconfirm with order preview before purchasing.
  3. Video, certificates, promotions, and some logistics fields may be absent.
  4. currency requests upstream foreign-currency fields but does not guarantee every SKU, retail price, or wholesale tier has them. A missing foreign-currency retail price can also mean that conversion failed.
  5. This lookup does not authorize an account, place an order, pay, or alter procurement state; use the procurement workflow for those actions.
  6. Results are not stored in an analysis database, so secondary SQL/data-query processing is unavailable.

User Expression & Scenario Quick Reference

Applicable -- Known-product sourcing and detail lookup:

User says Scenario
"Check the details of this 1688 product ID" Basic product detail
"Check the complete product details of this 1688 link" Product, SKU, logistics, and supplier detail
"Verify SKU price, inventory, and MOQ" Sourcing and quote review
"Check packaging weight, shipping origin, and shipping guarantee" Logistics preparation
"Evaluate supplier service score and repeat purchase rate" Supplier fact review
"Is there dropshipping, mixed batch, invoice, or certificate" Procurement terms

Not applicable:

  • Discovering products without a known offer ID (use 1688 image or product search).
  • Creating orders, requesting payment links, tracking logistics, or invoicing (use the 1688 procurement workflow).
  • Historical price trends, reviews, or database analytics.

Boundary judgment: If a user supplies a 1688 product URL or offer ID and asks about the item, sourcing terms, supplier, or logistics, use this skill. If they only have an image or keyword, use discovery first.

Compute consumption rules

Consumes 1 compute.

Users pay fees due to compute consumption. When multiple products need to be queried, first explain that each offerId will incur one call cost, and let the user decide whether to continue.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.