Summary
A NetSuite location can be captured into iPaaS.com as a location. The integration records the location name and description, captures the location's main address, and captures NetSuite-specific location attributes (location type, store-pickup flag, and store fulfillment memo) into NetSuite … custom fields. Locations are a reference record other collections depend on — inventory capture resolves the iPaaS.com location from the NetSuite location, so locations must be established here first.
ID Format
Manual Sync ID Format
Enter the NetSuite location's internal ID on the Manual Sync page.
External ID Format
iPaaS.com records the NetSuite location's internal ID as the external-ID link, so later transfers update the existing location rather than creating a duplicate. This link is what the product inventory collections resolve when capturing per-location inventory.
Deleted Record Support
There is a Delete NetSuite Location TO iPaaS.com collection that removes the linked iPaaS.com location when the NetSuite location is deleted (driven by the external-ID link), when the corresponding delete event is enabled.
Custom Field Support
NetSuite-specific location attributes are captured into iPaaS.com custom fields named NetSuite … (location type, store-pickup flag, store fulfillment memo). Add the matching iPaaS.com custom fields to retain them.
Mapping Collection Status
Status: Enabled (a single Add/Update collection).
Trigger Events: Create and Update. Locations are captured on demand from the Manual Sync page and on the location events enabled in Inbound Data Flows (see NetSuite Connections and Settings).
Duplicate or Conflicting Mappings
None. A single Add/Update collection captures locations, with the address child transferring alongside it.
Supported Child Collections
Add/Update NetSuite Location Address TO iPaaS.com — captures the location's main address. It transfers as part of the location; it is not synced on its own.
System Caveats
iPaaS.com Caveats
Locations are a prerequisite for inventory. The product and variant inventory collections resolve the iPaaS.com location from the NetSuite location, and skip inventory rows for locations that do not yet exist in iPaaS.com — capture locations before transferring inventory.
Location data type. This collection populates the iPaaS.com Location entity.
Only the main address is captured. NetSuite also holds a return address on a location; it is not captured.
The country name must match the iPaaS.com country list exactly. iPaaS.com validates the country against its own list of country names, and NetSuite does not always use the same name for the same country — NetSuite says United States where iPaaS.com says United States of America. The Country mapping converts the name rather than copying it, and the conversion it ships with is an example that must be extended — see Setup Requirements.
A location with no address still transfers. If the NetSuite location's main address is blank, the location is captured with an empty address rather than being rejected.
Setup Requirements
Sync locations first. Establish locations in iPaaS.com before running product inventory transfers (FROM or TO iPaaS).
NetSuite … custom fields: create the iPaaS.com custom fields for the location attributes you want to retain.
Inbound Data Flows + webhook scripts: enable the NetSuite location events for automatic capture.
Extend the Country conversion before go-live. The Country mapping on the address collection ships with an example conversion covering only United States, Bolivia, and Congo. A location in any other country is captured with an empty country and the transfer still succeeds, so nothing alerts you to the gap. Add a conversion for every country your locations use, and confirm each name against the country list in iPaaS.com.
Authentication
The integration authenticates to NetSuite using the connection configured for the integration; the webhook scripts that emit NetSuite events are documented in NetSuite Connections and Settings.
Integration Flow
A NetSuite location is captured — on demand (internal ID) or on location events when Inbound Data Flows and the webhook scripts are in place.
The integration creates or updates the iPaaS.com location with its name and description and captures the NetSuite location attributes into the NetSuite … custom fields.
In the same transfer, the location's main address is captured onto that iPaaS.com location. The address is linked to the location's NetSuite internal ID, so a later transfer updates the existing address rather than adding a second one.
Mappings
Add/Update NetSuite Location TO iPaaS.com
iPaaS.com data type: Location
Captures a NetSuite location into an iPaaS.com location.
Mapping Type | Source Field (NetSuite) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Name | Required. The location name — the NetSuite full (hierarchical) name when present, otherwise the simple name. |
Field | Name | Description | Optional. The location's simple name, stored as the description. |
Field | LocationType_RefName | NetSuite Location Type | Optional. The NetSuite location type (captured to a NetSuite … custom field). |
Field | AllowStorePickup | NetSuite Allow Store Pickup | Optional. Whether the location allows store pickup. |
Field | StoreFulfillmentMemo | NetSuite Store Fulfillment Memo | Optional. The store fulfillment memo. |
Add/Update NetSuite Location Address TO iPaaS.com
iPaaS.com data type: Location Address
Captures the main address of the NetSuite location onto the iPaaS.com location created or updated above. This collection transfers with its parent and is not synced on its own. No field on it is required — a location whose main address is blank in NetSuite is captured with an empty address.
Mapping Type | Source Field (NetSuite) | Destination Field (iPaaS.com) | Description |
Dynamic Formula | Main address, address line 1 | Address1 | Recommended. The first address line — the street address. |
Dynamic Formula | Main address, address line 2 | Address2 | Optional. The second address line (suite, unit, or floor). |
Dynamic Formula | Main address, address line 3 | Address3 | Optional. The third address line. |
Dynamic Formula | Main address, city | City | Recommended. The city. |
Dynamic Formula | Main address, state/province | Region | Recommended. The state or province, captured in the form NetSuite stores it (commonly a two-letter state code). |
Dynamic Formula | Main address, country name | Country | Recommended. Converted from the NetSuite country name to the iPaaS.com country name. The shipped conversion is an example — see the note below. |
Dynamic Formula | Main address, ZIP/postal code | PostalCode | Recommended. The ZIP or postal code. |
Dynamic Formula | Main address, phone number | PhoneNumber | Optional. The phone number recorded on the address. |
Country conversion — replace during implementation. iPaaS.com validates the country against its own list of country names, so the value has to match exactly. The mapping ships with an example conversion covering only these countries:
NetSuite country name | iPaaS.com country name |
United States | United States of America |
Bolivia | Bolivia (Plurinational State of) |
Congo | Congo, Democratic Republic of the |
A location in any other country is captured with an empty country, and the transfer still succeeds. Extend the Country mapping to cover every country your locations use, taking each name from the iPaaS.com Country Names section below. A name that is not on that list is rejected with "Country Name is not valid."
Recipient name is not captured. NetSuite records an addressee and an attention name on a location address; neither is captured into iPaaS.com.
iPaaS.com Country Names
The Country mapping on the location's address collection must supply a name from this list, spelled exactly as shown. A name that is not on the list is rejected with "Country Name is not valid.", and a country your conversion does not cover is captured as empty.
Use this list when extending the Country mapping: find the name NetSuite reports for the country, find the matching name below, and convert one to the other. Most names are identical in both systems and need no conversion — it is the differing ones (for example NetSuite's United States versus United States of America below) that the mapping has to handle.
Afghanistan | Germany | Norway |
Åland Islands | Ghana | Oman |
Albania | Gibraltar | Pakistan |
Algeria | Greece | Palau |
American Samoa | Greenland | Palestine, State of |
Andorra | Grenada | Panama |
Angola | Guadeloupe | Papua New Guinea |
Anguilla | Guam | Paraguay |
Antarctica | Guatemala | Peru |
Antigua and Barbuda | Guernsey | Philippines |
Argentina | Guinea | Pitcairn |
Armenia | Guinea-Bissau | Poland |
Aruba | Guyana | Portugal |
Australia | Haiti | Puerto Rico |
Austria | Heard Island and McDonald Islands | Qatar |
Azerbaijan | Holy See | Réunion |
Bahamas | Honduras | Romania |
Bahrain | Hong Kong | Russian Federation |
Bangladesh | Hungary | Rwanda |
Barbados | Iceland | Saint Barthélemy |
Belarus | India | Saint Helena, Ascension and Tristan da Cunha |
Belgium | Indonesia | Saint Kitts and Nevis |
Belize | Iran (Islamic Republic of) | Saint Lucia |
Benin | Iraq | Saint Martin (French part) |
Bermuda | Ireland | Saint Pierre and Miquelon |
Bhutan | Isle of Man | Saint Vincent and the Grenadines |
Bolivia (Plurinational State of) | Israel | Samoa |
Bonaire, Sint Eustatius and Saba | Italy | San Marino |
Bosnia and Herzegovina | Jamaica | Sao Tome and Principe |
Botswana | Japan | Saudi Arabia |
Bouvet Island | Jersey | Senegal |
Brazil | Jordan | Serbia |
British Indian Ocean Territory | Kazakhstan | Seychelles |
Brunei Darussalam | Kenya | Sierra Leone |
Bulgaria | Kiribati | Singapore |
Burkina Faso | Korea (Democratic People's Republic of) | Sint Maarten (Dutch part) |
Burundi | Korea, Republic of | Slovakia |
Cabo Verde | Kuwait | Slovenia |
Cambodia | Kyrgyzstan | Solomon Islands |
Cameroon | Lao People's Democratic Republic | Somalia |
Canada | Latvia | South Africa |
Cayman Islands | Lebanon | South Georgia and the South Sandwich Islands |
Central African Republic | Lesotho | South Sudan |
Chad | Liberia | Spain |
Chile | Libya | Sri Lanka |
China | Liechtenstein | Sudan |
Christmas Island | Lithuania | Suriname |
Cocos (Keeling) Islands | Luxembourg | Svalbard and Jan Mayen |
Colombia | Macao | Sweden |
Comoros | Madagascar | Switzerland |
Congo | Malawi | Syrian Arab Republic |
Congo, Democratic Republic of the | Malaysia | Taiwan, Province of China |
Cook Islands | Maldives | Tajikistan |
Costa Rica | Mali | Tanzania, United Republic of |
Côte d'Ivoire | Malta | Thailand |
Croatia | Marshall Islands | Timor-Leste |
Cuba | Martinique | Togo |
Curaçao | Mauritania | Tokelau |
Cyprus | Mauritius | Tonga |
Czechia | Mayotte | Trinidad and Tobago |
Denmark | Mexico | Tunisia |
Djibouti | Micronesia (Federated States of) | Türkiye |
Dominica | Moldova, Republic of | Turkmenistan |
Dominican Republic | Monaco | Turks and Caicos Islands |
Ecuador | Mongolia | Tuvalu |
Egypt | Montenegro | Uganda |
El Salvador | Montserrat | Ukraine |
Equatorial Guinea | Morocco | United Arab Emirates |
Eritrea | Mozambique | United Kingdom of Great Britain and Northern Ireland |
Estonia | Myanmar | United States Minor Outlying Islands |
Eswatini | Namibia | United States of America |
Ethiopia | Nauru | Uruguay |
Falkland Islands (Malvinas) | Nepal | Uzbekistan |
Faroe Islands | Netherlands, Kingdom of the | Vanuatu |
Fiji | New Caledonia | Venezuela (Bolivarian Republic of) |
Finland | New Zealand | Viet Nam |
France | Nicaragua | Virgin Islands (British) |
French Guiana | Niger | Virgin Islands (U.S.) |
French Polynesia | Nigeria | Wallis and Futuna |
French Southern Territories | Niue | Western Sahara |
Gabon | Norfolk Island | Yemen |
Gambia | North Macedonia | Zambia |
Georgia | Northern Mariana Islands | Zimbabwe |
Error Handling
Location not captured: if a location is not yet in iPaaS.com, dependent inventory rows are skipped. Resolution: sync the location, then re-run inventory.
Country is blank after a transfer: the location's country is not covered by the Country mapping's conversion. This does not raise an error. Resolution: add the country to the Country mapping, using the name exactly as it appears in iPaaS.com Country Names above, then re-sync the location.
"Country Name is not valid.": the Country mapping produced a name that is not on the iPaaS.com list — usually the NetSuite spelling passed through without conversion, or a typo in a conversion you added. Resolution: correct the mapping to return the name exactly as spelled in iPaaS.com Country Names above.
Testing & Validation
Test Scenarios
Capture a location. Manually sync a NetSuite location and confirm an iPaaS.com location with the name/description and the NetSuite … attributes.
Capture an address. Sync a NetSuite location that has a complete main address and confirm the iPaaS.com location's address carries the address lines, city, region, postal code, and phone number.
Confirm the country resolved. On that same location, confirm the country is populated and matches a name in the iPaaS.com country list. A blank country means the country is not covered by the Country mapping's conversion.
Capture a location with no address. Sync a NetSuite location whose main address is blank and confirm it transfers with an empty address rather than failing.
Re-sync a location. Sync the same location twice and confirm its address is updated in place rather than duplicated.
Inventory dependency. Confirm that after capturing a location, product inventory for that location is no longer skipped.
Validation Checklist
Locations referenced by inventory are established in iPaaS.com.
The NetSuite … location custom fields exist for the attributes you want to retain.
The Country mapping covers every country your locations use, and each converted name matches the iPaaS.com country list exactly.
Spot-check a captured location in iPaaS.com to confirm the country is populated — a blank country is the symptom of a missing conversion, and it is not reported as an error.
Additional Notes
The location external-ID link established here is what the inventory collections resolve; see NetSuite Inventory Product From iPaaS.com Mapping Documentation and the product-capture docs.
Known limitations are collected in NetSuite Known Limitations.