OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to manage orders, products, warehouses, and reports. Specifically for the Order (FBBS) - Print Labels operation, it allows users to request printing of package labels for fulfillment by OZON sellers. This is useful in scenarios where sellers need to generate shipping labels for their orders to streamline the dispatch process.

Practical examples include:

  • Automatically generating shipping labels for multiple orders after confirming shipments.
  • Integrating label printing into an automated order fulfillment workflow.
  • Merging custom JSON payloads with the default request to customize label printing parameters.

Properties

Name Meaning
Payload (JSON) Optional JSON payload string. If provided, it will be parsed and merged with the auto-generated payload sent to OZON API when printing labels. Useful for adding or overriding request parameters.

Output

The node outputs a JSON object containing the response from the OZON API's print labels endpoint. The structure typically includes information about the generated labels, such as URLs or identifiers for the printable label files.

Example output JSON structure (simplified):

{
  "result": {
    "labels": [
      {
        "posting_number": "123456789",
        "label_url": "https://..."
      }
    ]
  },
  "success": true,
  "error": null
}

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 connectivity to https://api-seller.ozon.ru or sandbox URL if configured.
  • Optional configuration for maximum retry attempts on failed requests.

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 parameters.
  • Timeouts and Retries: The node implements retries for transient errors like HTTP 429 or 5xx responses. If requests consistently fail, verify network connectivity and API service status.
  • Missing Posting Numbers: The operation requires posting numbers from input items. Ensure that each input item has a valid posting_number field in its JSON.

Links and References

Discussion