OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to manage warehouse-related operations, specifically focusing on product stock movements within warehouses. The "Movement" operation under the "Warehouse" resource allows users to send data about product movements, such as transfers or adjustments, to the OZON system.

Typical use cases include:

  • Automating inventory movement updates between different warehouse locations.
  • Recording stock adjustments due to internal transfers or corrections.
  • Synchronizing warehouse stock movements from external systems into OZON.

For example, a user can provide details of products moved from one warehouse to another, and this node will submit that information to OZON's API to keep inventory records accurate.

Properties

Name Meaning
Payload (JSON) Optional JSON payload string. If provided, it will be merged with the auto-generated payload for the movement request. This allows customization or extension of the default data sent to OZON.

Output

The node outputs a single JSON object containing the response from the OZON API after submitting the product movement data. The structure depends on the API response but generally includes confirmation of the movement operation, status codes, and any relevant messages or identifiers returned by OZON.

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 API endpoints, with support for sandbox or production environments based on configuration.
  • Network access to OZON's API endpoints is necessary.
  • The node handles retries automatically for transient errors like rate limits or server errors.

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 before running the node.
  • API Errors: Errors returned by the OZON API (e.g., authentication failures, invalid parameters) will be surfaced with their messages. Verify API credentials and payload correctness.
  • Rate Limiting: The node implements retry logic for HTTP 429 responses. If requests continue to fail due to rate limits, consider reducing request frequency or increasing retry intervals.
  • Timeouts: Network timeouts may occur; ensure stable internet connectivity and that the API endpoint is reachable.

Links and References

Discussion