OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to manage orders in the Fulfillment by Seller (FBBS) system. Specifically, the Order (FBBS) - Cancel operation allows users to cancel one or more orders programmatically.

Typical use cases include:

  • Automatically cancelling orders that meet certain criteria (e.g., payment issues, stock unavailability).
  • Integrating order cancellation into larger workflows for inventory and order management.
  • Handling bulk cancellations efficiently by sending multiple cancellation requests in one execution.

For example, a seller could use this node to cancel all orders flagged as fraudulent or to automate cancellations when items are out of stock.

Properties

Name Meaning
Payload (JSON) Optional JSON payload string. If provided, it will be merged with the auto-generated payload. This allows adding or overriding fields in the cancellation request sent to OZON API.

Output

The node outputs a JSON object containing the response from the OZON API after attempting to cancel the specified orders. The structure typically includes details about the success or failure of each cancellation request.

Example output JSON structure (simplified):

{
  "result": [
    {
      "posting_number": "123456789",
      "status": "cancelled",
      "message": "Order cancelled successfully"
    },
    ...
  ]
}

No binary data 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, either production or sandbox based on configuration.
  • Network access to https://api-seller.ozon.ru or sandbox URL is required.
  • Supports configurable retry logic for handling rate limits and transient server errors.

Troubleshooting

  • Invalid JSON in Payload: If the optional Payload (JSON) field 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), invalid order identifiers, or exceeding rate limits.
  • Rate Limiting: The node automatically retries requests on HTTP 429 responses with exponential backoff. Persistent rate limit errors may require reducing request frequency or contacting OZON support.
  • Empty Input Data: If no input data is provided or the expected fields (like order cancellation info) are missing, the node may fail or return empty results. Verify input data correctness.

Links and References

Discussion