# Batch Update SPU Status

This endpoint allows the bulk updating of product statuses using their SPU OpenItemCode.


App-level throttling: 


- The openItemCode field is mandatory with SPU entity-level uniqueness.

- This endpoint supports partial successful updates when processing multiple SPUs in a single request. However, if the entire request contains fundamental structural errors the system will reject the complete batch with a fail response.

- When the needLinkage parameter is set to 1, this endpoint facilitates the comprehensive synchronization of status changes not only for the specified SPUs but also for all associated ChoiceGroupSkus. This advanced functionality ensures cohesive inventory and product display management across related product options.

- Each request cannot exceed 200 SPUs.


Endpoint: POST /product/spustatus/batchupdatebycode
Version: v.1.0.0

## Request fields (application/json):

  - `shopId` (integer, required)
    Unique identifier of the Keeta store.
    Example: 12345

  - `spuOpenItemCodeList` (array, required)
    A list of SPU OpenItemCode
    Example: ["aCV","2code"]

  - `status` (integer, required)
    This field controls the visibility and availability of a SPU in the merchant storefront. Status = 0, this setting will immediately deactivate the specified SPU. Status = 1, this setting activates the SPU for public visibility and ordering.
    Example: 1

  - `needLinkage` (integer)
    This field determines whether the status change should propagate to related SKUs, with these behaviors: When needLinkage equals 0 the status update applies exclusively to the specified ChoiceGroupSku without affecting any related products. When needLinkage equals 1, the system will automatically identify and update all logically connected ChoiceGroupSkus based on existing mapping between ChoiceGroupSku names match SPU names
    Example: 1

## Response 200 fields (application/json):

  - `code` (integer, required)
    A numeric status identifier indicating the result of the interface call, used to determine whether the operation executed successfully.

  - `message` (string, required)
    Text description corresponding to the status code, explaining the operation result or error cause to users.
    Example: "Success"

  - `data` (array)
    Contains a list of OpenItemCodes for all SPUs whose statuses were successfully changed.

  - `errorList` (array)
    Failed SPUs list includes OpenItemCode and Error Message.

  - `errorList.id` (integer)
    Unique identifier for the SPU (Standard Product Unit), generated by Keeta's system

  - `errorList.name` (string)
    Display name of the SPU

  - `errorList.openItemCode` (string)
    Developer-provided external identifier that maintains a one-to-one mapping with Keeta's internal SPU ID. Refer to the "Menu Development Guide" for implementation details.
    Example: "VGsku-00035"

  - `errorList.errorPictureList` (array)
    Contains information about failed image binding attempts during batch operations, including error details

  - `errorList.errorPictureList.url` (string)
    Product image URLs
    Example: "https://img-ap-hongkong.mykeeta.net/sailorproduct/9c760595674b395e330cf94b0e5068b09999.jpg"

  - `errorList.errorPictureList.code` (integer)
    A numeric status identifier indicating the result of the interface call, used to determine whether the operation executed successfully.  indicates that .  indicates that .  can be viewed in the  field.