Neuro
9 days ago

V1.34.2.1 Update (11.04.2025)

New Features: 
  • BigCommerce – Dynamic Bundling Setting Added:
    A new setting, "Use Dynamic Bundling," was added to handle bundle SKUs more effectively. When enabled, the system removes the parent bundle SKU during order import and replaces it with its child SKUs, distributing pricing and quantities accordingly to improve stock and customs documentation accuracy.
Adjustments:
  • Shopify – "Get Authorised Orders" Setting Added:
    Allows the import of authorised (but unpaid) orders to support inventory reservation for pending payments.
  • Shopify – Fulfilment Sync:
    Resolved an issue causing fulfilment sync failures due to item count mismatches.
  • Account Creation Fix:
    Fixed a bug related to account creation errors, improving platform onboarding.
  • Rule Engine – Replace Order Item Action Fix:
    Corrected an issue where the rule action to replace order items wasn’t functioning as expected.
  • Rule Engine Execution Chain Fix:
    Ensured rules execute based on priority order, so sequential rules function properly within a single workflow.
  • Order Created Trigger Fix:
    The trigger now fires only after all order details, including items and addresses, have been fully imported.
  • Fulfilment Status Recovery:
    Logic added to detect and reset fulfilments stuck in “in progress” status.
  • Shopify – Product Customs Info Setting Fix:
    Corrected an issue where setting download_product_customs_information via API was not being saved properly.
  • JD Plugin – Push Order Job Error Handling:
    Enhanced validation error messages for better clarity when push order jobs fail.
  • Stock Update Logic Adjustment for Amazon:
    Resolved an issue where failed stock updates were not retried, even when product quantity was unchanged.
  • Show Channel Products Endpoint Fix :
    Fixed the API endpoint for viewing channel products, which was previously failing for some users.
  • Mirakl – Confirmation Order Import Fix:
    Orders previously marked as “already confirmed” were incorrectly stuck in the confirmation flow. We now treat them as regular orders to prevent confirmation errors.