Hey Folks, Couldn’t find much on this, so wanted to see if anyone had any thoughts:
In template item creation, under the “matrix item” tab, it is picking up the “last cost” and it seems to push this to Shopify as the product cost even though the item has a ‘current’ cost defined under the Stock Item:
These particular items have a “Current Cost” but not a “Last Cost”:
Do we happen to know why the Shopify Connector uses the Last Cost and not Current? Are we supposed to be updating the cost to “last cost” routinely?
Cheers,
k2
Page 1 / 1
Our company does not use current cost. The availability of this data depends on your company’s chosen cost calculation method. We primarily use the average cost field, but last cost is used by everyone, so I image that is why they chose that field.
Have you tried to manually change which field to map to Shopify in the entities screen?
Our company does not use current cost. The availability of this data depends on your company’s chosen cost calculation method. We primarily use the average cost field, but last cost is used by everyone, so I image that is why they chose that field.
Have you tried to manually change which field to map to Shopify in the entities screen?
interesting theory. I did look at the stock item entity mapping and there is no “Target” field for Cost, unless I’m missing something.
We use standard costing, is there a way to sync last cost and current cost?
I took a look at the json on the Shopify product page, and cost was not an available field to populate even though that field is available in the UI on the product screen. Apparently the cost field is updated through inventory processing rather than the product processing which is why we can’t edit the cost field in entities under stock items which is connected to product processing.
I suppose we could create a product request to allow us to edit that data transfer? This would allow us to map the cost field of our choosing back to Shopify.
I took a look at the json on the Shopify product page, and cost was not an available field to populate even though that field is available in the UI on the product screen. Apparently the cost field is updated through inventory processing rather than the product processing which is why we can’t edit the cost field in entities under stock items which is connected to product processing.
I suppose we could create a product request to allow us to edit that data transfer? This would allow us to map the cost field of our choosing back to Shopify.
Thanks for taking a look! We can also create Metafields and populate them, so I’ll look into seeing if we can use that avenue for an additional attribute...
Hi @K2a were you able to find a solution? Thank you!
I opened a ticket with ACU working through it now.
Any progress on this? We need to populate Shopify variant cost so the Ecomm team can run their reports.
Thanks!
Any progress on this? We need to populate Shopify variant cost so the Ecomm team can run their reports.
Thanks!
ACU has it as “Development in Progress”….
I was led to believe that it was not possible to push the cost to Shopify from Acumatica. Are we able to? Is there a how-to article someone can share or point me to the right screen/steps? Thanks!
@lawsont and @K2a , which Acumatica version are you using?
Shopify doesn’t have a cost field in Product or Product variant API, the cost field is in the InventoryItem API only. We don’t use InventoryItem API in product entity, so you cannot push the cost to Shopify currently.
But if you want to implement it through a customization package, it’s possible to do that in 2023r2, I will write a How-to article later to introduce the steps.
@simonliang91 We are on 23R1 planning to upgrade to R2 soon. I’d definitely be interested in that customization package and any steps you can provide. Thanks!
@simonliang91 We are on 23R1 planning to upgrade to R2 soon. I’d definitely be interested in that customization package and any steps you can provide. Thanks!
We are also 23R1, but we typically upgrade 1x per year to the R1...so 24R1 will be our next upgrade. Very interested in your your “how-to”!
Cheers
@simonliang91 Please tag me on this customization/How To post when you post it. Thanks!
@simonliang91 , @K2a , I think it is important to keep in mind that any of these 4 fields might be desirable as a source of data:
The first 2 are appropriate when STANDARD costing is used, while the bottom 2 are appropriate for Average, FIFO, and Specific costing methods.
So, @simonliang91 , if you’re thinking of exposing these values in the Entities screen, under the Product Availability object, it also makes sense to expose the costing method, so a formula could be built by a user as to which value to use, depending on the costing method for each inventory item.
In addition, it would be good to provide guidance on the non-stock items, since even though they are not part of the Product Availability sync, they also have a cost, and that cost can be complicated:
@Yuri Karpenko , the customization package will base on Product entity only, when you export the product item to Shopify, the cost info will be exported as well. In the Product Availability entity, we don’t fetch the cost info from ERP.
@K2a , @Yuri Karpenko , @michael73 , @brendan91 , @freddydelrio39 , @lawsont , I posted a “How To” article for export cost to Shopify.
@simonliang91 Thanks for sharing the Customization.
I take it from the whole conversation that the Cost for normal Items is not synced either and we would need to customize it?
This just seems like a huge miss from the native Product.