logistics-tracking
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseInternational Logistics Tracking
国际物流追踪
Track packages across borders with carrier auto-detection and status explanation.
支持通过承运商自动识别和状态解释功能进行跨境包裹追踪。
When to Use
使用场景
- User asks "where is my package" or provides a tracking number
- User needs to check shipment status or delivery estimate
- User asks about customs clearance or logistics exceptions
- User needs to track multiple packages at once
- 用户询问“我的包裹在哪里”或提供运单编号时
- 用户需要查询货运状态或预计配送时间时
- 用户询问清关或物流异常相关问题时
- 用户需要同时追踪多个包裹时
MCP Server Setup
MCP 服务器配置
This skill works best with the companion MCP server. Add to your MCP config:
json
{
"mcpServers": {
"logistics-tracking": {
"command": "npx",
"args": ["-y", "@shopme/logistics-tracking-mcp"],
"env": {
"TRACK17_API_KEY": "your-17track-api-key"
}
}
}
}Get a free 17track API key at https://api.17track.net
该Skill搭配配套的MCP服务器使用效果最佳。将以下内容添加到你的MCP配置中:
json
{
"mcpServers": {
"logistics-tracking": {
"command": "npx",
"args": ["-y", "@shopme/logistics-tracking-mcp"],
"env": {
"TRACK17_API_KEY": "your-17track-api-key"
}
}
}
}Available Tools
可用工具
track_package
track_package
Query tracking info for a single package.
- Input: (required),
trackingNumber(optional),carrier(en/zh)language - Returns: status, current location, timeline of events
查询单个包裹的追踪信息。
- 输入:(必填)、
trackingNumber(可选)、carrier(en/zh)language - 返回:状态、当前位置、物流时间线
detect_carrier
detect_carrier
Identify the carrier from a tracking number's format.
- Input:
trackingNumber - Returns: carrier name, confidence level
通过运单编号格式识别承运商。
- 输入:
trackingNumber - 返回:承运商名称、置信度
batch_track
batch_track
Track up to 40 packages at once.
- Input: array,
trackingNumberslanguage - Returns: array of tracking results
最多可同时追踪40个包裹。
- 输入:数组、
trackingNumberslanguage - 返回:包裹追踪结果数组
explain_status
explain_status
Get a human-readable explanation of a tracking status code.
- Input: (e.g. InTransit, CustomsClearance)
statusCode - Returns: English and Chinese explanation with advice
获取追踪状态码的人性化解释。
- 输入:(例如:InTransit、CustomsClearance)
statusCode - 返回:中英文解释及建议
Tracking Number Format Guide
运单编号格式指南
| Pattern | Carrier | Example |
|---|---|---|
| China Post | LX123456789CN |
| China EMS | EA123456789CN |
| Yanwen | YT1234567890123456 |
| Cainiao | LP12345678901234 |
| SF Express | SF1234567890123 |
| UPS | 1ZABCDEF1234567890 |
| USPS | 9400111899223100012345 |
| DHL | 1234567890 |
| FedEx | 123456789012 |
| 格式 | 承运商 | 示例 |
|---|---|---|
| 中国邮政 | LX123456789CN |
| 中国邮政EMS | EA123456789CN |
| 燕文 | YT1234567890123456 |
| 菜鸟 | LP12345678901234 |
| 顺丰速运 | SF1234567890123 |
| UPS | 1ZABCDEF1234567890 |
| USPS | 9400111899223100012345 |
| DHL | 1234567890 |
| FedEx | 123456789012 |
Typical Delivery Times (International)
国际配送时效参考
| Route | Standard | Express |
|---|---|---|
| China to US | 15-30 days | 5-10 days |
| China to EU | 15-30 days | 5-10 days |
| China to SE Asia | 7-15 days | 3-7 days |
| China to Japan/Korea | 5-10 days | 3-5 days |
| 路线 | 标准配送 | 特快配送 |
|---|---|---|
| 中国到美国 | 15-30天 | 5-10天 |
| 中国到欧盟 | 15-30天 | 5-10天 |
| 中国到东南亚 | 7-15天 | 3-7天 |
| 中国到日本/韩国 | 5-10天 | 3-5天 |
Status Codes Explained
状态码解释
- InfoReceived: Carrier has the info but hasn't picked up the package (1-3 day wait)
- InTransit: Package is moving through the logistics network
- CustomsClearance: Going through customs (3-7 business days typical)
- OutForDelivery: Final delivery attempt today
- Delivered: Successfully delivered
- Exception: Problem occurred (customs hold, wrong address, failed delivery)
- Returned: Being sent back to origin
- InfoReceived: 承运商已获取包裹信息但尚未揽收(需等待1-3天)
- InTransit: 包裹正在物流网络中运输
- CustomsClearance: 包裹正在清关(通常需3-7个工作日)
- OutForDelivery: 今日将进行最终配送
- Delivered: 包裹已成功配送
- Exception: 出现问题(如清关滞留、地址错误、配送失败)
- Returned: 包裹正在退回发件方
Tips
小贴士
- If is not set, the server falls back to RTB56 (limited accuracy)
TRACK17_API_KEY - For best results, wait 24-48 hours after shipping before first query
- Query no more than once every 2 hours per tracking number to avoid rate limits
- Batch tracking is more efficient for multiple packages
- 若未设置,服务器将自动切换至RTB56(准确性有限)
TRACK17_API_KEY - 为获得最佳结果,建议在发货后24-48小时再进行首次查询
- 每个运单编号每2小时查询不要超过1次,避免触发频率限制
- 批量追踪对于多个包裹来说效率更高