Identifying POS Orders in Shopify Connector Sales Order Mapping

Hi ​@jib87 ,

i never implement this for shopify POS, but with the Import Mapping this should be possible. You have to identify the POS Orders to handle them differently to the “web shop orders”. (this will help: https://stackoverflow.com/questions/18759745/shopify-api-is-there-a-way-to-determine-whether-or-not-an-order-came-from-shopi )

maybe some comments of this Question will help you to create the Mapping: 

​@jib87 , custom-mapping a customer is not a good idea. Neither for POS orders, nor for regular ones. There is a lot to cover in a short post on the forum, but a short answer is: utilize Acumatica POS connector as designed.

There’re rumors that in 25R1, we will be able to define a single customer for orders import (maybe, we will be able to define one customer for regular orders and another one for POS...). Until that is available, orders must be associated with individual customer records created as part of the order import process (which is really a 3-step process: import customer, import order, import payment).

Sorry, I would love to have a better answer for you.

Thank you ​@PatrickSchlenker90 for the response, but that doesn’t work for connector.

​@Yuri Karpenko , what you said make sense. It’s helpful to know about the potential enhancements coming in 25R1 regarding customer definitions. 

Thank you for sharing your solution with the community ​@jib87!

​@jib87 , won’t this force all you non-POS orders to use the ECOMCUST customer then?

​@Yuri Karpenko  - this was also my first thought. Maybe it make sense to create a custom field (bool) and map it?

Yes ​@Yuri Karpenko - you are correct, and this is what we need.

However, for others who are looking for a solution to map POS orders to a generic customer account, while leaving normal orders assigned to the appropriate customer, I haven’t found a way to do it yet thru native mapping. 

​@jib87 , got it. I wish I asked you if this was a problem for you :) We would have gotten to the solution 2 months ago. Sorry...