PickerPro icon

PickerPro

Automate your e-commerce operations by integrating PickerPro with n8n. Manage sales, inventory, warehouses, and orders from multiple marketplaces in a single workflow

Overview

This node integrates with the PickerPro platform to automate e-commerce operations such as managing sales, inventory, warehouses, and orders across multiple marketplaces. Specifically, the "Get Stocks by Zone" operation retrieves inventory stock information for a specified zone within a warehouse. This is useful for businesses that need real-time visibility into stock levels segmented by physical zones in their warehouses, enabling better inventory management and order fulfillment.

Practical examples:

  • A warehouse manager wants to check current stock availability in a specific zone before processing an order.
  • An automated workflow updates inventory dashboards with zone-level stock data.
  • Integration with other systems to trigger replenishment when stock in a zone falls below a threshold.

Properties

Name Meaning
Warehouse ID The unique identifier of the warehouse where the zone is located. Required for this operation.
Zone ID The unique identifier of the zone within the warehouse for which to retrieve stock data. Required for this operation.

Output

The node outputs a JSON object containing an inventory field. This field holds the stock information for the specified zone in the warehouse. The exact structure of the inventory data depends on the PickerPro API response but generally includes details about product quantities and availability within that zone.

Example output structure:

{
  "inventory": {
    // stock details per product/item in the specified zone
  }
}

The node does not output binary data.

Dependencies

  • Requires an active PickerPro API key credential and an organization ID configured in n8n credentials.
  • Relies on PickerPro's external API endpoints to fetch warehouse, zone, stock, and integration data.
  • No additional environment variables are needed beyond the API authentication setup.

Troubleshooting

  • Missing API Key or Organization ID: The node will throw an error if these credentials are not set up properly. Ensure both are provided in the node’s credential configuration.
  • Invalid Warehouse or Zone IDs: If the provided IDs do not exist or are incorrect, the API may return errors or empty results. Verify the IDs before running the node.
  • Operation Not Supported Error: Occurs if an unsupported operation value is passed. Confirm the operation name matches one of the supported options.
  • Network or API Errors: Connectivity issues or PickerPro service downtime can cause failures. Check network access and PickerPro service status.

Links and References

  • PickerPro Official Website (for general platform info)
  • PickerPro API documentation (not publicly linked here; refer to your PickerPro account resources)

Discussion