Skip to main content
Question

Acumatica Export Stock Item to Shopify error on weight_unit: 'lbs' is not a valid unit of measurement


I’m really new to Acumatica and the documentation is very sparse. 

 

I’m trying to export stock items to Shopify and facing this random error. Even if I haven’t mapped the weight_unit field. 

 

I’ve scoured the forums and the web and came up dry. I followed all of the instructions in the guide and it still isn’t working. 

6 replies

KarthikGajendran
Acumatica Moderator
Forum|alt.badge.img+3

@adambauer  We got to see your error message and the entity mappings. Acumatica connector does not send the UOM info to Shopify. So not sure how you are getting this error. Could you please create a case with Acumatica Support? 


PorchlightZach
Varsity III
Forum|alt.badge.img

I’m working on setting up the Shopify connector on a local Acumatica instance and I ran into this same issue.  My instance has data based on a production instance of Acumatica where every stock item has its Weight UOM as LBS.  The problem the OP encountered is related to Shopify expecting the weight_unit to be “lb” for pounds and not LBS.  It cannot have the S and it must be lower case.

To prevent this error from showing up, I first went into CS203100 and added LB to the Units of Measure with a conversion to and from LBS with a 1.0x multiplier.  I also setup a standard LB/LB from/to configuration.

On the single stock item I was trying to sync, I changed the weight UOM from LBS to LB and everything worked as expected.   

Given that we have a lot of stock items already setup for LBS, I wanted to find a way to deal with this without having to go modify every stock item’s configuration.  Here is how I accomplished a proof of concept that I think should work unless you use some other stock item unit of measure that contains an S.

In Entities I configured the Stock Item export with an export mapping on External Object: Product → Product Variants, External Field: Weight Unit to use the following ERP field from Stock item: 

=LCase(Replace([StockItem.WeightUOM], 'S', '')) 

This handles both the uppercase LBS and LB weight UOM in Acumatica.  It is kind of important to know that if your weight UOM is LB and you do not define an export map for that field, the system appears to automatically lower case the UOM value when exporting.  However, if you define an export mapping by hand, it does not modify the value, so the LCase function becomes necessary.

 


simonliang91
Acumatica Employee
Forum|alt.badge.img+1
  • Acumatica Employee
  • 79 replies
  • March 12, 2024

@PorchlightZach, you are right. Shopify doesn’t support “lbs” value, it only accept the following valid values in lower case: gkgoz, and lb. So if the value in the weight UOM is not the above values, it may cause the error.  


Forum|alt.badge.img
  • Varsity I
  • 42 replies
  • April 4, 2025

Hello ​@simonliang91 ​@KarthikGajendran ,

I believe this issue was resolved in 24R1 and 24R2, as we did not encounter it then. However, with the same data and configuration, we are now facing it again in the latest version, 25R1.

Here’s the actual error:

 We have temporarily applied a fix by adding an export external mapping to substitute ‘LB’ with ‘lb.’ However, it would be better if we could reapply the original fixes, if any exist.

Thank you!


simonliang91
Acumatica Employee
Forum|alt.badge.img+1
  • Acumatica Employee
  • 79 replies
  • April 4, 2025

@jib87 , the issue is because Shopify specifies the weight unit in GraphQL API, it only accepts the value in one of “KILOGRAMS, GRAMS, POUNDS, OUNCES”, and we have an internal conversion between

G → GRAMS

KG → KILOGRAMS

POUND → POUNDS

OZ → OUNCES

So if the unit is in the above list, it will not be an issue, base on your feedback, we will create a ticket to add the conversion for “LB → POUNDS” as well.


KarthikGajendran
Acumatica Moderator
Forum|alt.badge.img+3

@simonliang91 Lets add both LB and LBS to POUNDS. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings