Comments
We also need to be able to modify segments used in other segment our journeys as we sometimes need to modify some requirements or criteria of segmentation. The inability to do so forces us to stop all journeys and segments using this segment to be able to modify it, which is a major painpoint.
This is indeed a great idea. We just had a call with MS Support explaining that we really need the notifications voor PQU's back. We now have to frequently check if there has been a change to the schedule; what we need is a notification some (5) days in advance so our end customer can prepare for the PQU to be installed.
We have a company that trades with multiple currencies. We experience that Shopify cannot handle currencies, as there is no currency code on Shopordre and amounts are transferred in accounting currency. This happens despite the fact that we use customer templates that define the currency code based on the country code. We experience that the code for creating a sales order in BC uses the currency code from the shop order, which is blank and therefore uses LV.If we code that the currency code should be retrieved from the customer and used on the sales order. Then the currency code on totals is shown correctly, but amounts are still inserted in LV when they are transferred from Shopordre. It would be my opinion that many of the challenges we experience could be solved by: That the Currency code, amount in Total and VAT amount were shown in the currency in which the customer had purchased the item. Information that must be stated in the Order Confirmation to the customer.The same company also has a US tenant that also uses Shopify. Here we do not experience similar problems, but here Avalara is also used at the same time.