LEDGERS icon

LEDGERS

Interact with LEDGERS API
Join our community

Actions34

Overview

This node operation updates an existing product variant within a catalog in the LEDGERS system. It is useful for scenarios where you need to modify details of a specific variant of a product, such as changing its price, currency, SKU, status, or description without altering the entire catalog or product.

Practical examples include:

  • Updating the price or tax settings of a variant after a pricing change.
  • Changing the SKU or name of a variant to reflect new inventory codes.
  • Activating or deactivating a variant based on availability.
  • Adjusting currency or tax applicability for variants sold in different regions.

This operation streamlines managing product variants programmatically, especially when integrated into automated workflows for inventory or sales management.

Properties

Name Meaning
Catalog ID The unique identifier of the catalog containing the variant to update. Required to specify which catalog the variant belongs to.
Variant Name or ID Select the variant to update by choosing from a list of existing variants loaded dynamically or specifying the variant ID directly via expression.
Update Variant Fields A collection of fields to update for the selected variant:
- Currency The currency code for the variant's price. Options include standard ISO currency codes like USD, EUR, INR, etc.
- Non-Taxable Numeric value indicating the non-taxable amount for the variant.
- Price The price of the variant as a string.
- Price Type Specifies whether the price is inclusive or exclusive of tax. Options: "Inclusive of Tax", "Exclusive of Tax".
- SKU ID The stock keeping unit identifier for the variant.
- Status The active status of the variant. Options: "Active" (1), "Inactive" (0).
- Variant Description Text description of the variant.
- Variant Name The name of the variant.

Output

The node outputs JSON data representing the response from the API after attempting to update the variant. This typically includes confirmation of the update and the updated variant details. The exact structure depends on the API response but generally contains fields reflecting the updated variant properties.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential and user authentication credentials (email and password) for the LEDGERS API.
  • The node performs login requests to obtain an API token before making update calls.
  • The API URL endpoint must be configured correctly in the credentials.
  • Dynamic loading of variant options depends on successful API authentication and catalog data retrieval.

Troubleshooting

  • Authentication Failures: Errors related to failed login usually indicate incorrect API key, email, or password. Verify credentials and API URL configuration.
  • Empty Variant List: If no variants appear in the selection dropdown, ensure the specified Catalog ID is correct and that the catalog contains variants.
  • Invalid Input Data: Providing invalid currency codes, price formats, or status values may cause API errors. Use the provided options and correct data types.
  • API Response Errors: Network issues or API downtime can cause request failures. Check connectivity and API service status.
  • Continue On Fail: If enabled, the node will suppress some errors and continue execution; otherwise, errors will stop the workflow.

Links and References

Discussion