• Resolved bjm26

    (@bjm26)


    Good Afternoon

    We have recently installed Codisto LINQ since the ebay developed integration for Australia has been recently retired.

    Unfortunately we are having problems with the inventory synchronisation from ebay > LINQ > woocommerce. This is happening sporadically.

    Typical scenario:
    1. Sell an item that has an inventory of 1 in woo, LINQ and ebay. Payment received via paypal.
    2. Inventory correctly reduces on ebay and an order is sent to LINQ. LINQ inventory reduces to 0
    3. LINQ creates an order, and sends it to woo. Sales note in woo specifies the item inventory reduces from 1 > 0
    4. Check the woo commerce inventory. Inventory is still 1
    5. Subsequently, woo synchronises with LINQ, increasing inventory to 1 again.
    6. LINQ syncs to ebay, increasing inventory to 1

    This does not happen consistently. We have had 4 orders today, and this issue has only occurred for one order.

    Unfortunately we’re not sure where to start debugging. However LINQ has confirmed everything is working from their side.

    Does anybody have some suggestions about how to resolve / troubleshoot this issue?

    Thanks
    Brad

Viewing 10 replies - 1 through 10 (of 10 total)
  • Hi Brad,

    Luke from Codisto, can I just confirm that you are running on innodb and not myisam.

    Thread Starter bjm26

    (@bjm26)

    Hi Luke,

    I will get back to you on this within the day. Just out of the office at the moment.

    All – I have installed an Audit logger on the site and see the following event triggered (not sure what is triggering this) after LINQ reduces stock as a consequence of a sale:

    array(
    ClientIP => 103.18.109.170
    EditorLinkProduct => https://www.shopperholic.com.au/wp-admin/post.php?post=325&action=edit
    NewValue => 3
    ProductStatus => publish
    ProductTitle => NutriBullet RX 1700 – N171007M
    Severity => 4
    UserAgent => WordPress/5.0.3; https://www.shopperholic.com.au
    Username => Website Visitor
    )

    I have no idea what is triggering this. Could anybody shed some light on this?

    Thanks
    Brad

    • This reply was modified 5 years, 9 months ago by bjm26.

    Just FYI:

    103.18.109.170 comes from:

    Country: AU
    Registration Date: 2013-03-01
    Registrar: apnic
    Owner: NET1-AS-AP Net Virtue Pty Ltd, AU

    our traffic will be Owner: Amazon as that is where we are hosted.

    Thread Starter bjm26

    (@bjm26)

    Thanks Luke,

    In response to your initial question, majority of tables use innodb, however we note that some use myISAM.

    Regarding the log output, we’re aware that this is our domain address and we’re reasonably sure the issue is not due to LINQ, unless LINQ is somehow triggering an edit / update on the product after the initial inventory reduction.

    What we are unable to ascertain is why AFTER LINQ does what it is supposed to (i.e. reduce inventory by 1 when a woocommerce order is created), another process is somehow triggered (randomly, by the above user agent) to change the inventory in an invalid manner.

    Thanks
    Brad

    • This reply was modified 5 years, 9 months ago by bjm26.

    What I can tell you is that we try our very best to honour all hooks / filters / actions that the standard checkout flow does, so that third party extensions that deal with fulfilment / tax / post sales all fire and order processing isn’t any different for marketplace orders relative to standard web checkout orders.

    It is reasonably easy to look at what hooks / filters we fire by looking at what we do here: https://github.com/CodistoConnect/CodistoConnect-WooCommerce/blob/development/connect.php#L1207

    Any other plugin hooking those events is going to do ‘what it usually does’ and in general this is what you want.

    Finally, the usage of myISAM could be problematic, we explicitly lock tables to be serialized such that there is no ‘lost updates’ which innodb does correctly, myISAM on the other hand says .. ok.. locked! then doesn’t assure that things are isolated (like imagine we send a new order and an order update which ends up being processed at the same time, luck will determine the final state).

    (locking is here https://github.com/CodistoConnect/CodistoConnect-WooCommerce/blob/development/connect.php#L1219 – note https://stackoverflow.com/a/16453987 – myisam does not honour locks via transactions)

    Thread Starter bjm26

    (@bjm26)

    Hello
    Unfortunately this is beyond our understanding (we are a small business without an IT department).
    Can somebody from Codisto look into this in further detail for us? Previously the Codisto support representative had advised that it was not an issue with Codisto LINQ causing the incorrect inventory updates.
    Thanks
    Brad

    Unfortunately, as the issue is a wordpress environment issue, not a Codisto issue, we cannot provide wordpress troubleshooting.

    My advice is to work through converting all your tables to innodb, there is good tutorials on how to do that online. If that solves the problem all good.

    If the problem persists, contact our support channel with the list of extensions you are using so we can point out where the trouble may lie.

    Thread Starter bjm26

    (@bjm26)

    Thanks Luke

    All of the transactional tables appear to be innodb.

    We will go ahead and contact support.

    Thanks
    Brad

    Thread Starter bjm26

    (@bjm26)

    Hello
    We can confirm this is not a CODISTO issue.
    Could anybody shed some light on why this may be happening so randomly? Perhaps a caching issue?
    Thanks
    Brad

    Thread Starter bjm26

    (@bjm26)

    Issue is not related to LINQ. Marking as resolved and moving to general woocommerce issue.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Inventory Not Reducing Codisto LINQ’ is closed to new replies.