Issue syncing after selling a variable product version

  • Tom

    (@tomvos66)


    4 months ago

    After selling a version of a variable product via de Zettle POS environment, somehow communication between Zettle and Woocommerce seems to fail and product / variant mapping is deleted.

    After this, all variants of the product disappear from Zettle and in Woocommerce show up with status:

    PayPal Zettle Status column entry in Product overview:

    Not synced
    <small>Not syncable</small>
    <small>- Not purchasable</small>
    <small>- No variation attributes</small>

    In Woocommerce and website, all product Variants still show up as expected.

    A zettle-pos-integration log file is available showing all events.

    Hope you can help figuring out what goes wrong here and come up with a quick solution (as current issue renders the POS solution useless).

    Thanks in advance.

    Kind regards,
    Tom Vos

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Krystian

    (@inpsydekrystian)

    Hello @tomvos66

    This issue is already being handled on our private support board, so let’s continue the conversation there to ensure we keep everything organized. We’ll do our best to resolve this for you as quickly as possible.

    Kind Regards,

    Krystian

    Thread Starter Tom

    (@tomvos66)

    Unfortunately today it happened again (first time using Zettle again after reporting the issue).

    Looking through the log file, the issue starts appearing after the first variable product was sold via the Zettle app. Any simple product sold before that did not result in any issue.In the log-file under Woocommerce status, the following line appears:

    “Stock management at variation level is not supported from PayPal Zettle. ID:6075”

    After that, more and more syncing errors pop up for any product sold or even edited in the Products list in Woocommerce.

    The test I did earlier (with a specially created variable product) did not result in this error, so I really do not understand what is going on.

    Replied to the last email I got on the support ticket, but not sure if that is still active.

    Updated it here so other users with potential similar issues might respond as well.

    Hope you or anyone else can come with a solution for us and solve this permanantly.

    Kind regards,

    Tom Vos

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