• Resolved ToPpS

    (@topps)


    Hi Guys,

    Hope you’re well.

    We have a number of products that are custom made (21 days). They are set up in WC as to “allow back orders”.

    I tried your snippet that you have provided (thank you for that) but it doesn’t seem to be working. https://webappick.com/docs/ctx-feed/faqs/how-to-add-an-availability-date-based-on-the-current-date-for-the-items-on-backorder/

    I suspect that the route cause would be the fact we enable “Track stock quantity for this product” rather than leaving it unticked (as per the provided guide). As we need to track inventory as the ERP will allocate the Bill of?Materials?(BOM) for the product when it enters production, would you by any chance have a revamped snippet to factor this in?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Shahed

    (@shahedbd71)

    Hello @topps,

      To achieve the expected output, please follow these steps:

      1. Enable the custom field “availability date” as shown here: screenshot.
      2. Activate the snippet using a code snippet plugin.
      3. Incorporate the “availability date” attribute in your feed: screenshot.

      After completing these steps, a date will be added to your feed for products with an on_backorder status, like this example product: screenshot.

      • This reply was modified 2 weeks ago by Shahed.
      • This reply was modified 2 weeks ago by Shahed.
      • This reply was modified 2 weeks ago by Shahed.
      • This reply was modified 2 weeks ago by Shahed.
      Thread Starter ToPpS

      (@topps)

      HI @shahedbd71

      Thank you for the reply.

      Points 1 through 3 were already in place.

      I think the site cache is the culprit at the moment as I see the feed in question isn’t updating. I’ve followed your guide on that https://webappick.com/docs/ctx-feed/faqs/how-to-solve-feed-configuration-not-updating-issue/

      Shahed

      (@shahedbd71)

      Hello,

      If the issue persists even after clearing the cache, it must be a site-specific issue. In this case, please reach out to us from here.

      Thread Starter ToPpS

      (@topps)

      I cloned the problematic feed and that seemed to fix the issue. The new version is working perfectly.

      Plugin Support mansary

      (@mansary)

      Hi?@topps

      We’re glad to hear the issue has been resolved! We’re marking this topic as resolved. Please feel free to start a new topic if you need further assistance.

      Best regards,

    Viewing 5 replies - 1 through 5 (of 5 total)
    • You must be logged in to reply to this topic.