OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to update product stock information. Specifically, the Update Stock operation allows users to send stock quantity updates for products listed on the OZON marketplace. This is useful for sellers who want to keep their inventory synchronized between their internal systems and OZON, ensuring accurate stock levels are reflected online.

Typical use cases include:

  • Automatically adjusting stock quantities after sales or restocking events.
  • Synchronizing inventory from an ERP or warehouse management system to OZON.
  • Bulk updating stock levels for multiple products in one request.

Properties

Name Meaning
Payload (JSON) Optional JSON payload that will be merged with the auto-generated stock update data. This allows adding or overriding fields in the request body sent to OZON API.

Output

The node outputs a JSON object containing the response from the OZON API after attempting to update stock levels. The structure typically includes success indicators, error messages if any, and details about the updated stocks.

Example output JSON structure (simplified):

{
  "result": {
    "updated": [...],   // List of successfully updated stock items
    "errors": [...]     // Any errors encountered during update
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the OZON Seller API.
  • The node uses the official OZON Seller API endpoints.
  • Network access to https://api-seller.ozon.ru or sandbox URL if configured.
  • Optional configuration for maximum retry attempts and timeout settings.

Troubleshooting

  • Invalid JSON in Payload: If the optional Payload (JSON) property contains malformed JSON, the node will throw an error indicating invalid JSON. Ensure the JSON syntax is correct.
  • API Errors: The node surfaces errors returned by the OZON API, including HTTP status codes and messages. Common issues include authentication failures (check API keys), rate limiting (retry after delay), or invalid request data.
  • Timeouts and Retries: The node implements automatic retries for transient errors like HTTP 429 (rate limit) or 5xx server errors. If you experience repeated failures, verify network connectivity and API quota limits.
  • Mismatched Data Structure: The input data must conform to the expected format for stock updates as per OZON API documentation. Incorrect field names or missing required fields can cause errors.

Links and References

If you need help formatting the JSON payload or understanding the API response, refer to the official OZON API documentation linked above.

Discussion