https://netsuiteprofessionals.com logo
Join Slack
Powered by
Does anyone know how the Shopify<->NetSuite ...
# integrations
c
Does anyone know how the Shopify<->NetSuite Celigo app handles different address fields? E.g. US address has different mandatory fields to Mexican address in NetSuite.
j
Hi Craig, With the prebuilt Shopify NetSuite Integration App you will have access to the mappings between Shopify Order and NetSuite Sales Order for each store. These can be field-to-field mapping or more customized to work with handlebar expressions (logic statements) and/or defaults. Here is a screenshot of the out-of-the-box fields, but you can certainly add other fields to the Sales Order mapping. Let me know if there are any additional questions or concerns!
c
@James Roth Are you suggesting that I need a different mapping for each country address field variation?
I guess there would be some superset of fields that you'd be able to make apply to all countries?
that sounds like a lot of mapping and lots of failed imports; in a high volume operation, that will be a massive pain.
j
Craig, I was showing the field mappings for the order Ship To Address. There are Customer Flows and an Order flows that would have separate mappings. Do you mind providing more information/details about your initial question, or perhaps the specific integration flow this pertains to?
c
Celigo have not made how their app works transparent so I will have to guess. I can see how the sales orders are mapped from SH into NS, I cannot see how new customers are entered. There is a customer flow/import but I don't see how it's triggered; I will have to assume some sort of hook on the sales order import
Mexican orders are throwing an error: missing street number (and other fields)
US orders are fine
I'm going to guess it's the SO delivery address that's breaking for the mexican orders
As soon as the country (Mexico) is mapped into NetSuite, the form updates to needing these fields which are not mapped in Celigo
If this were a US address, it would be fine.
I believe the same is happening every time the NetSuite address form updates when a non-US country is entered
I can add a street number mapping in Celigo, I have no idea if Shopify collects that data though, and even if it does, when other country specific field is going to break next?
So I'm looking for the overall design approach of how Shopify-Celigo-NetSuite should handle varying address formats which all have differing mandatory fields in NetSuite.
Interestingly, I can see older mexican orders in NetSuite so maybe this worked at one point? There have been no changes in the mappings in a very long time though.
j
Craig, have you submitted a support ticket on this yet? We would have to look at your mappings and your settings on the address entry form for Mexico to resolve this.
c
I have raised a ticket - I was crowdsourcing opinions from other users too as sometimes celigo come back with very tricky solutions
e.g. mapping every possible type of address.
Support also couldn't tell me how new customers get their record created in NS
it must be a hook - but you don't get visibility in the app.
It's all greyed out so you cant see what it does
j
Ok, let me check internally. Yes. There is a script in the Order flow to create the Customer Record, using the logic setup in the Customer Flow. Can you send a screenshot of the Custom Address Entry Form for Mexico?
Perhaps you can uncheck the mandatory boxes for those fields?
c
I dont' think it's a custom form in NS, it think it's there standard mexico one
It would be trivial to map to this format, I am hoping that is not the solution though.
Otherwise I might have to do many variations!
j
Hi, can you validate that you have the country code mapped in the Sales Order mappings?
c
We must have otherwise it wouldn’t be switching the form in NetSuite - I’ll check later though
j
It sounds like something may have changed on the NetSuite side. I would also check under Customization->Forms->Address Forms to see if anything has been changed recently. Especially since you said this was working at one point in time.
c
Would still be nice to know how the celigo Shopify app was deigned to handle different country addresses.
d
Have you tried adding a Mapping to hard code the “Shipping Address Form” for Mexico?
c
You mean creating a mapping for Mexico?
Sure I could do that
How many country variations are there?
My quick workaround is to mark the fields in NetSuite as non-mandatory then figure out a solution on the NetSuite side.
m
Craig, I have NEVER seen that address input format. We ship all over. I also just checked our instance and do not see that format populating for any country, including Mexico.
Is your form customized?
c
It is not, I thought this might be a 24.1 thing
I’ve since modified the form.
m
We are on 24.1
c
I’ll check
I’d like to know the best way of handling the mapping to those various formats though
I’d hate to have to do lots of conditionals based on country; but maybe that’s the answer?
m
I doubt Shopify even breaks up the address by street name/number?
In a custom integration with Celigo, you could add a pre-map function to break up the address to how you require (javascript), but I don't believe the Shopify app allows that ability as it is fairly locked down.
If you aren't familiar with shopify, you can goto the order transaction in shopify admin and add .json to the end of the url and it will give you the order json.
Shopify quite developer friendly.
c
I was thinking a suitescript given the paid for celigo flows are restricted RE: hooks etc
But it’s all down to whether Shopify is even collecting the correct fields
8 Views
Open in Slack
PreviousNext
Powered by