# alibaba1688_pair_sku (https://sellersheetai.com/docs/mcp-api/tools/alibaba1688_pair_sku)

> Pair one local SKU with one 1688 variant, so an order of that SKU buys that variant; then preview an order with alibaba1688_preview_order.

Access: **WRITE** · toolset alibaba1688 · family null

Gate: approve — interactive: show the change (1688's preview first where one exists), wait for an explicit approve; autopilot: only when the seller's own words asked for this change; otherwise ask.

## Call it

MCP tool call:

```json
{
  "name": "alibaba1688_pair_sku",
  "arguments": {
    "account": "<account>",
    "sku": "<sku>",
    "item_id": "<item_id>"
  }
}
```

Tool API (early access — contact us):

```bash
curl -X POST https://api.sellersheetai.com/api/v1/tools/alibaba1688_pair_sku \
  -H "Authorization: Bearer $SELLERSHEET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"account":"<account>","sku":"<sku>","item_id":"<item_id>"}'
```

## Arguments

| Name | Type | Required | Description |
|---|---|---|---|
| `account` | string | yes | the 1688 account ref (its 1688 login name) — one of get_user_context's alibaba1688 account_refs, verbatim. |
| `sku` | string | yes | the local SKU code, exactly as the workspace's Products list has it. |
| `item_id` | string | yes | the variant's item_id (from alibaba1688_list_pairings or alibaba1688_list_offer_variants). |
| `units_per_sku` | integer |  | how many 1688 units make ONE of the local SKU (a 2-pack bought as singles is 2); an order multiplies its quantity by it. |
| `make_default` | boolean |  | true makes this the pairing an order of the SKU uses. A SKU's first pairing is its default anyway. |
| `replace` | boolean |  | true replaces the pairing the SKU already has with the SAME supplier. Without it such a pairing is refused, naming both variants: show both to the seller and ask before passing true. |

## Result

- `data.item` — the stored variant with its pairing — item_id, offer_id, spec_id, subject, supplier_login_id, sku {sku_id, sku, name}, units_per_sku, is_default.

## Gotchas

- One variant per (SKU, supplier); a SKU may have pairings with several suppliers, one of them the default.
- One variant may serve several SKUs: pairing a SKU with a variant another SKU holds ADDS a row for it (data.item has a new item_id), and the other SKU keeps its pairing. To move a pairing to another SKU, unpair it first.