Summary
This mapping collection brings customers from NCR Counterpoint into iPaaS.com. A customer that iPaaS.com does not yet hold is created; one it already holds is updated. The collection carries the customer's Counterpoint customer number, their name, their email address, the free-text comment recorded against them, and their category assignment.
The collection also serves the integration's customer-as-company feature. While the Customer-as-company Field and Customer-as-company Field Value settings are set, a Counterpoint customer that carries the subscriber's company marker transfers as a company through Add/Update NCR Counterpoint Company TO iPaaS.com instead of through this collection, and that company's first and second contacts are transferred through this collection as iPaaS.com customers of their own (see Company Contacts below). Customer-as-company is for new customers: switching an existing customer to a company in place, by setting the marker on a customer that has already transferred, is not supported, because its iPaaS.com customer record stops receiving its changes.
ID Format
Manual Sync id: the Counterpoint customer number — this collection reads inbound from Counterpoint, so the id entered on the Manual Sync page is the customer's Counterpoint-side number, not an iPaaS.com value. Do not enter the number of a customer that carries the customer-as-company marker: this collection's Manual Sync is not redirected, and a company not yet in iPaaS.com is created as an ordinary customer, which leaves it switched to a company in place once it transfers as one. Use the Manual Sync of Add/Update NCR Counterpoint Company TO iPaaS.com instead.
External ID saved after transfer: once a customer has been transferred, iPaaS.com records the Counterpoint customer number as the external ID on a dedicated platform-managed external-ID record. That record — not any field on the customer record itself — is the primary match that routes subsequent transfers of the same customer to the existing iPaaS.com customer rather than adding a second one. The CustomerNumber mapping also writes the Counterpoint customer number onto the iPaaS.com customer, which gives subscribers visibility of the customer in both systems and serves as a fallback collision key where no external-ID record exists yet.
Company contacts: a contact transferred by the customer-as-company feature is identified by the company's customer number followed by :CONTCT_1 or :CONTCT_2, for example 1001:CONTCT_1. There is no Counterpoint customer with that number, so a contact cannot be entered in a Manual Sync of this collection; it is transferred with its company.
Deleted Record Support
This family does not itself carry deletions. Where a separate Delete collection exists for this entity it handles removals from Counterpoint to iPaaS.com; otherwise a removal in Counterpoint is not propagated. See NCR Counterpoint Known Limitations.
Mapping Collection Status
Status: Enabled. The mapping filter narrows which customers are processed rather than blocking them all.
Trigger Events: see Transfer Methods in the collection description; automatic transfers require the relevant Outbound/Inbound Data Flow subscriptions to be enabled.
Duplicate or Conflicting Mappings
Add/Update NCR Counterpoint Company TO iPaaS.com: reads the same Counterpoint customers. For a change reported by CPWebhooks, the integration runs one of the two collections for each customer: the Company collection when the customer matches the customer-as-company settings, and this collection otherwise. Scheduled polls are separate: this collection's poll skips customers that match the settings, and they transfer only through a poll scheduled on the Company collection.
Important: choose a customer-as-company marker that no existing customer carries: an existing customer that carries it is switched to a company in place on its next change, which is not supported.
Supported Child Collections
Add/Update NCR Counterpoint Customer Billing Address TO iPaaS.com: carries the address held directly on the Counterpoint customer record as the customer's billing address, as part of the customer's transfer.
Add/Update NCR Counterpoint Customer Ship-To Address TO iPaaS.com: carries the customer's default ship-to address, as part of the customer's transfer. The address transfers with a change reported by CPWebhooks, but not with a Manual Sync or a scheduled poll, which do not read a customer's ship-to addresses.
Company Contacts
When a customer transfers as a company, the integration first transfers the company's contacts through this collection, one iPaaS.com customer for each of the Contact 1 and Contact 2 fields that holds a name. Each contact:
is identified by the company's customer number followed by :CONTCT_1 or :CONTCT_2;
takes its first and last name from its own contact name, as described under FirstName and LastName below;
has no company name of its own: it belongs to its iPaaS.com company through the company's relationship records;
gets Email 1 (Contact 1) or Email 2 (Contact 2) with a CONTCT_1: or CONTCT_2: prefix; a Contact 2 with no Email 2 gets Email 1;
gets the company's billing address through Add/Update NCR Counterpoint Customer Billing Address TO iPaaS.com, and no ship-to addresses.
The prefix keeps a contact's address apart from the ordinary customers', so a contact is never linked to an ordinary customer with the same address; an ordinary customer is kept apart from a contact only while the contact keeps its prefix, so a storefront that sends customer changes back to iPaaS.com must keep it. The prefix does not separate companies: two companies with the same Email 1, or with none, give their contacts the same address, and the second company's contact is matched to the first company's contact record instead of getting its own, or its transfer fails with CRPT-BIZL-1002 where that link cannot be made. It is kept in iPaaS.com by design. Adobe Commerce/Magento 2 version 1.4.10 or later removes it when it writes the contact; earlier versions send the prefixed address, which Adobe Commerce rejects as invalid.
A contact that cannot be transferred stops its company's transfer, with the contact's error in Dashboard / Integration Monitoring / Error Logs. A contact that this collection's mapping filter holds back is skipped instead, and so is its relationship to the company, unless it is designated the company's Super User, in which case the company's transfer stops with CRPT-BIZL-1008.
System Caveats
iPaaS.com Caveats
Confirm your customer data satisfies the name rule before enabling: because iPaaS.com rejects a customer with no first name, no last name, and no company, and because a company name is sent only for customers Counterpoint marks as a business, any customer marked as a person and holding a blank name in Counterpoint is rejected. Subscribers or their MiSP should check their Counterpoint data for person-type customers with blank names before enabling this collection, and correct them in Counterpoint or narrow this collection's filter to exclude them.
Confirm every selected customer has an email address before enabling: the email address is required and Counterpoint does not enforce one, so a customer without one is rejected. This is worth checking against the set of customers the filter actually admits, not against the customer base as a whole.
Duplicate prevention depends on the email address: before a customer iPaaS.com has not seen before is created, the integration looks for an existing iPaaS.com customer with the same email address, ignoring differences in capitalization, and links the Counterpoint customer number to that customer instead of creating a second copy. This is what keeps a shopper entered separately in each system from becoming two customers. Where that link cannot be created the transfer fails rather than proceeding and creating the duplicate, and the error surfaces at Dashboard / Integration Monitoring / Error Logs.
Categories must be transferred before customers to arrive assigned: a customer's category is resolved by looking up a category already transferred into iPaaS.com. Subscribers or their MiSP who want customers to arrive categorized must run Add/Update NCR Counterpoint Customer Category TO iPaaS.com before this collection. This collection does not transfer the category as a prerequisite, and no later update backfills the assignment — a customer transferred before its category exists stays uncategorized until it is transferred again.
This collection is not run as a prerequisite of other transfers, except for a company's contacts: other collections that link a record to a customer resolve the link by looking up a customer already transferred into iPaaS.com. They do not pull the customer across. Subscribers who want those links made should ensure customers are transferring before the records that reference them. The one exception is the customer-as-company feature: a company's transfer first transfers its contacts through this collection (see Company Contacts above).
Integration Flow
Customers that transfer as companies are routed to the Company collection. While both customer-as-company settings are set, a change reported by CPWebhooks for a customer that carries the company marker runs Add/Update NCR Counterpoint Company TO iPaaS.com instead of this collection. Where customers are polled on a schedule, this collection's poll skips such customers; they transfer only through a poll scheduled on the Company collection (see NCR Counterpoint to iPaaS.com Company Mapping Documentation). This collection's mapping filter also holds back a customer whose customer number already has an iPaaS.com company.
An existing iPaaS.com customer is matched and linked first. Before the customer is sent, the integration checks for an iPaaS.com customer with the same email address and links to it rather than creating a duplicate. This is a lookup-and-link step, not a transfer; if a match is found but the link cannot be created, the transfer reports an error.
The record is sent to iPaaS.com, where subsequent transfers are routed by the external ID recorded on transfer.
Child records transfer as part of the same transfer — the collections listed under Supported Child Collections above.
A company's contacts follow the same steps: when a company transfers, each contact that holds a name is transferred through this collection first, as an iPaaS.com customer, before the company itself is written. See Company Contacts above.
Mappings
Add/Update NCR Counterpoint Customer TO iPaaS.com
Mapping Filter
// Only e-commerce customers transfer.
if (IS_ECOMM_CUST != "Y") { return false; }
// Customer-as-company: a Counterpoint customer that transfers to iPaaS.com as a company is never also sent as a customer. A
// plain-id transfer (a resync) is not routed to the company, so without this it would create a second customer carrying the
// company's email address. Company contacts, and every customer while the Customer-as-company presets are blank, pass as before.
if (Convert.ToString(CUST_NO).Contains(":CONTCT_")) { return true; }
if (string.IsNullOrWhiteSpace(GetSubscriptionSettingValue("Customer-as-company Field")) || string.IsNullOrWhiteSpace(GetSubscriptionSettingValue("Customer-as-company Field Value"))) { return true; }
return string.IsNullOrEmpty(Convert.ToString(await GetSpaceportIdAsync(CUST_NO, "Company", SpaceportSystemId)));
Filter Description.
Only customers flagged in NCR Counterpoint as e-commerce customers are transferred. Counterpoint holds that flag as a single character, permits only Y or N, and defaults it to N — so a customer transfers only once someone has deliberately set the flag to Y. Subscribers or their MiSP who want every customer transferred, rather than only the e-commerce ones, can widen the first line of this filter, and should read the iPaaS.com Caveats above before doing so, because a wider filter admits customers that may not satisfy them.
The rest of the filter serves the customer-as-company feature. Its customer-as-company lines always let a company's contacts through, but a contact must still pass the first line. So a Manual Sync or scheduled poll of a company that is not an e-commerce customer transfers it without its contacts, or stops it with CRPT-BIZL-1008 where a contact is designated Super User; as installed, CPWebhooks does not report such a company at all. While either customer-as-company setting is blank, every e-commerce customer passes. While both are set, a customer whose customer number already has an iPaaS.com company is not sent: a Manual Sync or a resync of such a customer through this collection is not redirected to the company, and without this line it would create a second iPaaS.com customer carrying the company's email address. Keep these lines in place whenever the customer-as-company settings are in use.
Mapping Type | Source Field (NCR Counterpoint) | Destination Field (iPaaS.com) | Description |
Field |
| CustomerNumber | Required. IPaaS.com rejects the customer without it. |
Dynamic Formula |
| FirstName | See detail. This is a conditionally required field. |
Dynamic Formula |
| LastName | See detail. This is a conditionally required field. |
Dynamic Formula |
| Company | See detail. This is a conditionally required field. |
Field |
| EmailAddress | Required. IPaaS.com rejects the customer without it, and on a newly created customer the address must be unique. |
Field |
| Comment | Optional. . |
Dynamic Formula |
| Categories | Optional. . |
CustomerNumber — Field
Source: CUST_NO · Destination: CustomerNumber
This is a required field — iPaaS.com rejects the customer without it. The customer number as assigned in NCR Counterpoint. Counterpoint stores this as text of up to 15 characters and always populates it, so a value always arrives. This is the value subscribers or their MiSP use to identify the customer in both systems. iPaaS.com also saves the Counterpoint customer number as the external ID on the customer record, which is the primary match for subsequent updates to the same customer. For a company's contact, which the customer-as-company feature transfers through this collection, the value is the company's customer number followed by :CONTCT_1 or :CONTCT_2, and there is no Counterpoint customer with that number.
FirstName — Dynamic Formula
Source:
// A company contact's record carries the company's first/last name; take the contact's own name (NAM) instead.
if (!Convert.ToString(CUST_NO).Contains(":CONTCT_")) { return FST_NAM; }
var contactName = Convert.ToString(NAM).Trim();
var cut = contactName.LastIndexOf(" ");
return cut > 0 ? contactName.Substring(0, cut).Trim() : contactName;
Destination: FirstName
This is a conditionally required field. iPaaS.com requires at least one of FirstName, LastName, or Company to be supplied and rejects the customer when all three are empty. For an ordinary customer, the formula sends the customer's first name as recorded in NCR Counterpoint, which Counterpoint stores as text of up to 15 characters and permits to be empty. Because Company in this collection is populated only for business-type customers, FirstName and LastName are what satisfy the requirement for person-type customers — a person-type customer with no first or last name in Counterpoint has nothing to satisfy the rule and is rejected. Subscribers or their MiSP whose Counterpoint data includes person-type customers with blank names should confirm this before enabling the collection.
For a company's contact, which the customer-as-company feature transfers through this collection with a customer number ending :CONTCT_1 or :CONTCT_2, the record Counterpoint provides carries the company's own first and last name, so the formula takes the contact's name from the Contact 1 or Contact 2 field instead: everything before the last space is the first name, and a one-word name is used as both the first and the last name.
LastName — Dynamic Formula
Source:
// A company contact's record carries the company's first/last name; take the contact's own name (NAM) instead.
if (!Convert.ToString(CUST_NO).Contains(":CONTCT_")) { return LST_NAM; }
var contactName = Convert.ToString(NAM).Trim();
var cut = contactName.LastIndexOf(" ");
return cut > 0 ? contactName.Substring(cut + 1).Trim() : contactName;
Destination: LastName
This is a conditionally required field. iPaaS.com requires at least one of FirstName, LastName, or Company to be supplied and rejects the customer when all three are empty. For an ordinary customer, the formula sends the customer's last name as recorded in NCR Counterpoint, which Counterpoint stores as text of up to 25 characters and permits to be empty. For a company's contact, it sends the last word of the contact's name from the Contact 1 or Contact 2 field, or the whole name when it is one word. See the FirstName note in this collection for how the three fields interact.
Company — Dynamic Formula
Source:
// A company contact belongs to its iPaaS.com company through the relationship records; its own name is not a company.
return Convert.ToString(CUST_NO).Contains(":CONTCT_") ? null : (CUST_NAM_TYP == "B" ? NAM : null);
Destination: Company
This is a conditionally required field. iPaaS.com requires at least one of FirstName, LastName, or Company to be supplied and rejects the customer when all three are empty. NCR Counterpoint records every customer under a single name field together with a name-type flag that marks the customer as either a business or a person. This formula reads that flag: when it is B, the customer is a business and the Counterpoint name is sent as the company name; for any other value the formula produces no company name, because for a person the Counterpoint name is simply the first and last name already carried by the FirstName and LastName mappings. Counterpoint permits only B or P for the name type, defaults it to B, and always requires a name — so business customers always arrive with a company name of up to 40 characters, and person customers always arrive with none. A company's contact never gets a company name here: it belongs to its iPaaS.com company through the company's relationship records, not through this field.
EmailAddress — Field
Source: EMAIL_ADRS_1 · Destination: EmailAddress
This is a required field — iPaaS.com rejects the customer without it, and on a newly created customer the address must be unique. The customer's primary email address in NCR Counterpoint. Counterpoint stores this as text of up to 50 characters and permits it to be empty, so a Counterpoint customer with no email address is rejected. Subscribers or their MiSP should confirm that every customer selected by this collection's filter carries an email address before enabling the collection.
Before a customer that iPaaS.com has not seen before is created, the integration checks iPaaS.com for an existing customer with the same email address, ignoring differences in capitalization. When one is found, the integration links the Counterpoint customer number to that existing iPaaS.com customer rather than creating a second copy, which is what keeps a customer entered separately in each system from becoming a duplicate. If that link cannot be created, the transfer fails with the message "Unable to dynamically link to existing iPaaS customer using email address. This may result in duplicate customer records." rather than proceeding and creating the duplicate.
For a company's contact, the address is the company's Email 1 (Contact 1) or Email 2 (Contact 2) with a CONTCT_1: or CONTCT_2: prefix; a Contact 2 with no Email 2 gets Email 1. The prefix keeps a contact's address apart from the ordinary customers', so the check described above never links a contact to an ordinary customer with the same address. It does not separate companies: two companies with the same Email 1, or with none, give their contacts the same address, and the check matches the second company's contact to the first company's contact record, or fails with CRPT-BIZL-1002 where that link cannot be made. It is kept in iPaaS.com by design. Adobe Commerce/Magento 2 version 1.4.10 or later removes it when it writes the contact; earlier versions send the prefixed address, which Adobe Commerce rejects as invalid.
Comment — Field
Source: COMMNT · Destination: Comment
This is an optional field. The free-text comment recorded against the customer in NCR Counterpoint, carried across unchanged for reference. iPaaS.com accepts the customer without it, and customers with no comment in Counterpoint transfer with this field empty.
Categories — Dynamic Formula
Source: return await ConvertCustomerCategoriesToiPaaSIdListAsync(CATEG_COD); · Destination: Categories
This is an optional field. Assigns the customer to its category in iPaaS.com. iPaaS.com identifies a category by its own internal id and accepts only ids that already exist, so the Counterpoint category code cannot be sent directly. The formula takes the category code from the customer record and looks up the matching category already transferred into iPaaS.com, returning its id. When no matching category is found — because the category has not been transferred yet, or the customer carries no category code — the formula produces no category and the customer transfers without one. It does not fail the transfer, and it does not transfer the category on its own.
The category is matched on the Counterpoint category code, which is what Add/Update NCR Counterpoint Customer Category TO iPaaS.com writes as the category name and external ID. Subscribers or their MiSP who want customers to arrive categorized MUST run that collection before this one; otherwise customers transfer uncategorized and stay that way until they are transferred again.
Where more than one category is supplied, iPaaS.com requires that the same category not be listed twice.
Add/Update NCR Counterpoint Customer Billing Address TO iPaaS.com
Parent: Add/Update NCR Counterpoint Customer TO iPaaS.com.
The collection also carries the billing address of each company contact that the customer-as-company feature transfers through the parent collection. A contact's billing address is its company's: the same Counterpoint address, name and Phone 1 as the company's own billing address.
Mapping Filter
SourceTypeName == "ParentOnly"
Filter Description.
The filter admits only the address derived from the customer record itself — the billing address — and excludes the customer's ship-to records, which are handled by Add/Update NCR Counterpoint Customer Ship-To Address TO iPaaS.com. Every mapping in this collection reads from the parent customer accordingly. Subscribers should leave this filter in place: without it, this collection and the ship-to collection would both process the same records.
Mapping Type | Source Field (NCR Counterpoint) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| FirstName | Optional. . |
Dynamic Formula |
| LastName | Optional. . |
Dynamic Formula |
| Address1 | Recommended. . |
Dynamic Formula |
| Address2 | Optional. . |
Dynamic Formula |
| Address3 | Optional. . |
Dynamic Formula |
| City | Recommended. . |
Dynamic Formula |
| Region | Recommended. . |
Dynamic Formula |
| Country | Recommended. . |
Dynamic Formula |
| PostalCode | Recommended. . |
Dynamic Formula |
| PhoneNumber | Recommended. . |
Static |
| IsPrimaryBilling | Optional. . |
FirstName — Dynamic Formula
Source: Parent.FST_NAM · Destination: FirstName
This is an optional field. The first name from the parent customer record in NCR Counterpoint, reused as the billing contact's first name because Counterpoint does not hold a separate name against the billing address. Counterpoint stores this as text of up to 15 characters and permits it to be empty, in which case the address transfers without a first name. For a company's contact, this is the first name on the company's own customer record, not the contact's.
LastName — Dynamic Formula
Source: Parent.LST_NAM · Destination: LastName
This is an optional field. The last name from the parent customer record in NCR Counterpoint, reused as the billing contact's last name for the same reason as FirstName above. Counterpoint stores this as text of up to 25 characters and permits it to be empty. For a company's contact, this is the last name on the company's own customer record, not the contact's.
Address1 — Dynamic Formula
Source: Parent.ADRS_1 · Destination: Address1
This is a recommended field. iPaaS.com accepts the address without it, but the first address line is what makes the address usable for billing and correspondence, so it should be mapped for any meaningful customer sync. The first line of the billing address held on the customer record in NCR Counterpoint. Counterpoint stores this as text of up to 40 characters and permits it to be empty, so customers entered without an address transfer with an empty address record attached.
Address2 — Dynamic Formula
Source: Parent.ADRS_2 · Destination: Address2
This is an optional field. The second line of the billing address, used in NCR Counterpoint for suite, unit, or similar detail. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.
Address3 — Dynamic Formula
Source: Parent.ADRS_3 · Destination: Address3
This is an optional field. The third line of the billing address. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.
City — Dynamic Formula
Source: Parent.CITY · Destination: City
This is a recommended field. iPaaS.com accepts the address without it, but a billing address without a city is not deliverable, so it should be mapped for any meaningful customer sync. The city from the billing address on the customer record. Counterpoint stores this as text of up to 20 characters and permits it to be empty.
Region — Dynamic Formula
Source: Parent.STATE · Destination: Region
This is a recommended field. iPaaS.com accepts the address without it, but the region is generally needed for tax and shipping purposes downstream, so it should be mapped for any meaningful customer sync. The state or province from the billing address on the customer record. Counterpoint stores this as text of up to 10 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a fixed list of state or province codes on this field.
Country — Dynamic Formula
Source: Coalesce(Parent.CNTRY,"United States") · Destination: Country
This is a recommended field. iPaaS.com accepts the address without a country, but many storefronts and shipping systems that read customer data from iPaaS.com require one, which is why this mapping supplies a fallback rather than passing the field through. The country from the billing address on the customer record. Counterpoint stores this as text of up to 20 characters and permits it to be empty; when it is empty, the formula produces United States instead. The fallback applies per address, so customers who do have a country recorded keep their own value.
Subscribers or their MiSP whose customers are predominantly outside the United States should replace the fallback with the country appropriate to their business, because the fallback is applied silently and an address that reaches iPaaS.com with the wrong country carries no indication that it was defaulted.
PostalCode — Dynamic Formula
Source: Parent.ZIP_COD · Destination: PostalCode
This is a recommended field. iPaaS.com accepts the address without it, but the postal code is generally needed for tax and shipping purposes downstream, so it should be mapped for any meaningful customer sync. The postal or ZIP code from the billing address on the customer record. Counterpoint stores this as text of up to 15 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a postal code format on this field.
PhoneNumber — Dynamic Formula
Source: Parent.PHONE_1 · Destination: PhoneNumber
This is a recommended field. iPaaS.com accepts the address without it, but storefronts that read customer data from iPaaS.com, such as Adobe Commerce/Magento 2, can require a telephone number on every address, so it should be mapped for any meaningful customer sync. The customer's Phone 1 from NCR Counterpoint, sent as the telephone number on the billing address, because Counterpoint holds no telephone number against the billing address itself. Counterpoint stores this as text of up to 25 characters and permits it to be empty, in which case the address transfers without a telephone number. For a company's contact, this is the company's Phone 1, because a contact's billing address is the company's.
IsPrimaryBilling — Static
Source: true · Destination: IsPrimaryBilling
This is an optional field. Marks the address as the customer's primary billing address in iPaaS.com. The value is fixed rather than read from NCR Counterpoint because the collection's filter already restricts it to the one billing address held on the customer record — Counterpoint has no second billing address to compete with it, so every address this collection produces is the primary one. Subscribers or their MiSP should leave this set; clearing it leaves the customer with no address marked for billing, which downstream systems reading iPaaS.com may rely on.
Add/Update NCR Counterpoint Customer Ship-To Address TO iPaaS.com
Parent: Add/Update NCR Counterpoint Customer TO iPaaS.com.
Mapping Filter
SourceTypeName != "ParentOnly" && SHIP_ADRS_ID == "(DEFAULT)"
Filter Description.
The first half excludes the address derived from the customer record, which is handled by Add/Update NCR Counterpoint Customer Billing Address TO iPaaS.com, leaving only genuine ship-to records. The second half narrows those to the one whose ship-to identifier is (DEFAULT), which is the identifier Counterpoint assigns to a customer's default ship-to address. Subscribers or their MiSP who need every ship-to address to reach iPaaS.com should widen the second half of the filter, and should read NCR Counterpoint Known Limitations before doing so.
Mapping Type | Source Field (NCR Counterpoint) | Destination Field (iPaaS.com) | Description |
Field |
| FirstName | Optional. . |
Field |
| LastName | Optional. . |
Field |
| Address1 | Recommended. . |
Field |
| Address2 | Optional. . |
Field |
| Address3 | Optional. . |
Field |
| City | Recommended. . |
Field |
| Region | Recommended. . |
Field |
| PostalCode | Recommended. . |
Dynamic Formula |
| Company | Optional. . |
Dynamic Formula |
| IsPrimaryShipping | Optional. . |
Dynamic Formula |
| Country | Recommended. . |
FirstName — Field
Source: FST_NAM · Destination: FirstName
This is an optional field. The first name of the contact recorded against this ship-to address in NCR Counterpoint. Unlike the billing address, a ship-to row carries its own name, so this is not the customer's name unless someone entered the same value. Counterpoint stores this as text of up to 15 characters and permits it to be empty.
LastName — Field
Source: LST_NAM · Destination: LastName
This is an optional field. The last name of the contact recorded against this ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 25 characters and permits it to be empty.
Address1 — Field
Source: ADRS_1 · Destination: Address1
This is a recommended field. iPaaS.com accepts the address without it, but the first address line is what makes the address usable for shipping, so it should be mapped for any meaningful customer sync. The first line of the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 40 characters and permits it to be empty.
Address2 — Field
Source: ADRS_2 · Destination: Address2
This is an optional field. The second line of the ship-to address, used in NCR Counterpoint for suite, unit, or similar detail. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.
Address3 — Field
Source: ADRS_3 · Destination: Address3
This is an optional field. The third line of the ship-to address. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.
City — Field
Source: CITY · Destination: City
This is a recommended field. iPaaS.com accepts the address without it, but a ship-to address without a city is not deliverable, so it should be mapped for any meaningful customer sync. The city from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 20 characters and permits it to be empty.
Region — Field
Source: STATE · Destination: Region
This is a recommended field. iPaaS.com accepts the address without it, but the region is generally needed for tax and shipping purposes downstream, so it should be mapped for any meaningful customer sync. The state or province from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 10 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a fixed list of state or province codes on this field.
PostalCode — Field
Source: ZIP_COD · Destination: PostalCode
This is a recommended field. iPaaS.com accepts the address without it, but the postal code is generally needed for shipping and rate calculation downstream, so it should be mapped for any meaningful customer sync. The postal or ZIP code from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 15 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a postal code format on this field.
Company — Dynamic Formula
Source: (SHIP_NAM_TYP == "B" ? NAM : null) · Destination: Company
This is an optional field. NCR Counterpoint records a ship-to address under a single name field together with a name-type flag that marks it as either a business or a person. This formula reads that flag: when it is B, the address belongs to a business and the Counterpoint name is sent as the company name; for any other value the formula produces no company name, because for a person the Counterpoint name is simply the first and last name already carried by the FirstName and LastName mappings. Counterpoint permits only B or P for the name type, defaults it to B, and always requires a name — so business ship-to addresses always arrive with a company name of up to 40 characters, and person ship-to addresses always arrive with none.
IsPrimaryShipping — Dynamic Formula
Source: (SHIP_ADRS_ID == "(DEFAULT)" ? true : false) · Destination: IsPrimaryShipping
This is an optional field. Marks the address as the customer's primary shipping address in iPaaS.com. The formula sets the flag when the Counterpoint ship-to address id is (DEFAULT), which is the id Counterpoint assigns to a customer's default ship-to address.
As shipped, this collection's filter already admits only the (DEFAULT) row, so the formula's condition is always met and every address this collection produces is flagged as primary. The formula matters only once that filter is widened: subscribers or their MiSP who change the filter to bring across a customer's additional ship-to addresses will find the formula already distinguishing the default address from the rest, so only one address per customer is flagged as primary. Replacing the formula with a fixed value while transferring more than one ship-to address per customer would flag all of them as primary.
Country — Dynamic Formula
Source: Coalesce(CNTRY,"United States") · Destination: Country
This is a recommended field. iPaaS.com accepts the address without a country, but many storefronts and shipping systems that read customer data from iPaaS.com require one, which is why this mapping supplies a fallback rather than passing the field through. The country from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 20 characters and permits it to be empty; when it is empty, the formula produces United States instead. The fallback applies per address, so ship-to addresses that do have a country recorded keep their own value.
Subscribers or their MiSP whose customers are predominantly outside the United States should replace the fallback with the country appropriate to their business, because the fallback is applied silently and an address that reaches iPaaS.com with the wrong country carries no indication that it was defaulted.
Error Handling
Errors raised while transferring these records surface at Dashboard / Integration Monitoring / Error Logs. The specific messages, their causes and their resolutions are documented in NCR Counterpoint Error Messages. A record stopped by an error is not retried automatically; it must be resolved manually. An error raised for a company's contact is recorded against the contact, whose customer number ends :CONTCT_1 or :CONTCT_2, and stops the company's transfer.
Testing & Validation
Confirm that the customers this collection's filter selects satisfy the iPaaS.com Caveats above: each needs a name and an email address.
Transfer a single customer through Manual Sync and confirm it appears in iPaaS.com as expected.
Confirm the customer's billing address transferred with it. The default ship-to address does not transfer with a Manual Sync or a scheduled poll; it transfers with a change reported by CPWebhooks (step 4).
Enable the relevant triggers and confirm a new customer transfers automatically with its default ship-to address, and that a change updates the same iPaaS.com customer rather than creating a second one.
Attempt a transfer with a missing required field and confirm the expected error appears at Dashboard / Integration Monitoring / Error Logs.
Where the customer-as-company feature is in use, transfer a new company through the Manual Sync of Add/Update NCR Counterpoint Company TO iPaaS.com, and confirm that each contact holding a name appears in iPaaS.com as a customer whose customer number ends :CONTCT_1 or :CONTCT_2, with the prefixed email address and the company's billing address.
Related Documents
Related Mapping Documentation