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) - Confirm Shipment operation, it confirms the shipment of one or more orders by sending their posting numbers to the OZON API.

Typical use cases include automating order fulfillment workflows where once an order is shipped, this node updates the order status in OZON's system to reflect that the shipment has been confirmed. This helps keep inventory and order statuses synchronized between your internal systems and OZON.

For example, after a warehouse ships items, you can pass the shipment details (posting numbers) to this node to confirm shipment on OZON automatically, avoiding manual updates.

Properties

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

Output

The node outputs a JSON object containing the response from the OZON API for the confirm shipment request. The structure typically includes information about the success or failure of confirming shipments for the specified postings.

Example output JSON structure (simplified):

{
  "result": {
    "posting_numbers": ["1234567890"],
    "status": "success",
    "message": "Shipment confirmed"
  }
}

No binary data is output by this node.

Dependencies

  • Requires an active connection to the OZON Seller API.
  • Needs credentials including a Client ID and API Key for authentication.
  • Supports optional configuration such as sandbox mode and base URL override.
  • Uses HTTP POST requests to the endpoint /v3/posting/fbs/ship for confirming shipments.
  • Handles retries on rate limiting or server errors with exponential backoff.

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: Errors returned by the OZON API (e.g., invalid posting numbers, authentication failures) will be surfaced with messages prefixed by "OZON error". Check the API key and client ID validity and ensure the posting numbers are correct.
  • Rate Limiting: The node implements retry logic for HTTP 429 responses. If you encounter repeated rate limit errors, consider reducing request frequency or increasing retry settings if configurable.
  • Timeouts: Network timeouts may occur; verify network connectivity and API availability.

Links and References

Discussion