noon_xborder_pricing_BatchUpsertProduct
Create or update the cross-border product record noon needs to ship a SKU cross-border (dimensions, weights, HS code) — when onboarding a new cross-border SKU, before its noon_xbor
destructivenoonnoon
der_pricing_BatchUpsertTransferPrice takes effect, or when its size, weight or HS code changes. noon API · XborderPricingService_BatchUpsertProduct · POST /xborder-pricing/v1/product/upsert Docs: https://noon-docs.noonpartners.dev/docs/api-reference/xborder-pricing/xborder-pricing-service-batch-upsert-product Gate: approve — interactive: show the change (noon'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
In an AI client (MCP)
{
"name": "noon_xborder_pricing_BatchUpsertProduct",
"arguments": {
"store": "myStore-US"
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/noon_xborder_pricing_BatchUpsertProduct \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US"}'Arguments
| Name | Type | Description |
|---|---|---|
storerequired | string | the noon account ref `<account>-<CC>` (name-country, e.g. 'myNoon-AE') — one of get_user_context's noon store_refs, verbatim. |
items | object[] | the rows to write (required), at most 1000 per call — partner_sku plus the fields to set: dimensions in cm (all three when given), vm_weight_cm (the volumetric weight, as noon's schema names it), actual_weight_kg in kg, hs_code (the Harmonized System customs code). Rows are sent as given. |
Result
Every tool answers {notification, data, human_action}; data carries:
data.items[]— partner_sku, status {status_code, message} — the per-row create/update result.
Body (noon schema): {items: [item]}, each item
partner_sku*: string
dimensions_cm: {length*, width*, height*}
vm_weight_cm: number
actual_weight_kg: number
hs_code: string