As per celigo support, the meta field is not supported for orders. However, we need to find a way to achieve this, possibly through a prebuilt custom flow. The Customer's Order Reference/PO Number is crucial for the majority of our customers.
Currently, we can manually enter these into Sales Orders (SOs). However, once the flow in Phase 2 is automated, there will be no opportunity for manual entry, which would be inefficient anyway. For many of our customers, receiving a shipment without a PO# will result in rejection and/or delayed account payment. Please research further to find a solution for this.
We struggled with not having access to order metafields as well. We run into it with POs as well as Resident ID numbers for international shipments.
Is this for orders moving from Shopify to Netsuite?
Shopify does have a dedicated PO field that is accessible via REST meaning the Celigo connector has it available by default to push with your order. We have also used order notes or attributes for this, things that are both also available in the REST api. That way it is accessible in Celigo.
For things like resident id that are not directly available via REST, I run a flow in the Flow Shopify app that retrieves the resident id number via graphql and then adds it as an order attribute for me to get in Celigo.
Thank you for your response.
While Shopify does have a dedicated PO field accessible via REST, meaning the Celigo connector can push it with our order by default, we do not want the order number in the PO field. Instead, we want users to manually add the PO number through Shopify, which should then be sourced to a Shopify metafield. When creating an order, this metafield needs to be imported into the NetSuite sales order. Is there a way to achieve this?
We have a field in the cart by the order summary/checkout button that we added to the cart form. Labeled it PO for our customers to fill out if needed. This field adds the value to the cart as a cart attribute. Those are accesssible in Celigo to then map wherever necessary. So the customer is on the cart attribute for the order instead of a metafield and that makes it easily accessible via REST.