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

> Rename a shipment (write, synchronous).

Access: **WRITE** · toolset amazon_sp · family sp.fulfillmentInbound_2024-03-20

Amazon SP-API · updateShipmentName · PUT /inbound/fba/2024-03-20/inboundPlans/{inboundPlanId}/shipments/{shipmentId}/name Gate: approve — interactive: show the change (Amazon'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": "fbaInbound_updateShipmentName",
  "arguments": {
    "store": "myStore-US",
    "plan_id": "<plan_id>",
    "shipment_id": "<shipment_id>",
    "name": "<name>"
  }
}
```

Tool API (early access — contact us):

```bash
curl -X POST https://api.sellersheetai.com/api/v1/tools/fbaInbound_updateShipmentName \
  -H "Authorization: Bearer $SELLERSHEET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"store":"myStore-US","plan_id":"<plan_id>","shipment_id":"<shipment_id>","name":"<name>"}'
```

## Arguments

| Name | Type | Required | Description |
|---|---|---|---|
| `store` | string | yes | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. |
| `plan_id` | string | yes | the inboundPlanId (from fbaInbound_createInboundPlan or fbaInbound_listInboundPlans). |
| `shipment_id` | string | yes | the shipmentId (from the placement option's shipmentIds in fbaInbound_listPlacementOptions, or fbaInbound_getInboundPlan once a placement is confirmed). |
| `name` | string | yes | new shipment name (maxLength 100). |

## Result

- `data.updated` — true — Amazon applied the name synchronously; nothing to poll.