Things To Consider Before Changing SOR To Woo

  • Resolved beogeek

    (@beogeek)


    4 years, 1 month ago

    So I wrote a detailed issue on Square and WooCommerce regarding the limitations of synching products with more than one attribute here called. Square best practice?

    Now due to that limitation with more than 1 attribute we’re thinking of switching woo to be the main source of record as we’re using multiple variations and swatches, additionally square is deleting all the other categories during every synch which is a pain!

    Now what I would like to know is what is the general way to handle this going forward? Is it as simple as going and changing the Square plugin setting and setting Woo as SOR? Do I need to do anything with the already existing products in square ie delete them or do I leave them there?? Any tips would be very much appreciated.

    Cheers
    Milos

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Aashik P – a11n

    (@aashik)

    Hello Milos,

    Just a heads up that you cannot sync products to Square even with WooCommerce as SOR if they have multiple attributes.

    As long as you’re aware of the limitations and sync options that come with setting either WooCommerce or Square as SOR, you’re right in that switching the SOR is only changing it manually at WooCommerce > Settings > Square > Settings

    If the SKU already matches that defined in the WooCommerce store, then you don’t have to delete them from your Square account.

    I’m not aware of a known issue with the change in SOR, but I’d still recommend reaching out to your web host and taking a complete backup of your store, just in case. Optionally, you can also export your Square items.

    Thread Starter beogeek

    (@beogeek)

    Hi Aashik,

    Yes, I am aware that even with Woo as SOR you still cannot sync everything to Square. I really don’t care at this point, I’m just wondering whether website support will be easier if I make Woo as SOR and use Square purely as the payment gateway.

    But, something comes to mind, if my client takes her shop on the road (which she does from time to time) then we will have the same problem with stock I assume as if Woo is SOR how will she process POS sales in person if not all stock is synced to Square due to the limitations regardless of if Woo or Square is SOR?

    Cheers

    Plugin Support Aashik P – a11n

    (@aashik)

    I’m just wondering whether website support will be easier if I make Woo as SOR and use Square purely as the payment gateway.

    If you’re intending to use Square just as a payment gateway, then you don’t need to set an SOR at all:

    nosync
    Link to image: https://d.pr/i/WNJq1P

    if my client takes her shop on the road (which she does from time to time) then we will have the same problem with stock I assume as if Woo is SOR how will she process POS sales in person if not all stock is synced to Square due to the limitations regardless of if Woo or Square is SOR?

    That’s a very valid point. If you’re selling through multiple channels (WooCommerce Store and POS), the Square is indeed the recommended SOR for the use case.

    That said, as you already know, syncing products with multiple attributes is not an option with our extension.

    At that point though, WooCommerce Square may not be the best way to continue with the product sync, and you may need to search for another extension that would suit the store needs, or go with custom coding.

    Thank you for your understanding.

    Plugin Support Aashik P – a11n

    (@aashik)

    Howdy!

    We haven’t heard back from you in a while, so I’m going to go ahead and mark this thread as resolved. If you have any other questions please start a new thread.

    Cheers!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Things To Consider Before Changing SOR To Woo’ is closed to new replies.