Summary
This mapping collection brings the customer categories maintained in NCR Counterpoint into iPaaS.com. It carries the category's code and its readable description.
ID Format
Manual Sync id: the Counterpoint customer category code — this collection reads inbound from Counterpoint, so the id entered on the Manual Sync page is the category's Counterpoint-side code, not an iPaaS.com value.
External ID saved after transfer: once a category has been transferred, iPaaS.com records the Counterpoint customer category code as the external ID on a dedicated platform-managed external-ID record. That record — not any field on the category record itself — is the primary match that routes a subsequent transfer of the same category to an update rather than adding it a second time. The Name mapping also writes the Counterpoint category code onto the iPaaS.com category, which gives subscribers visibility of the category in both systems and serves as a fallback collision key where no external-ID record exists yet. Remapping Name to a different source is supported but disables that fallback link for any pre-existing iPaaS.com categories.
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. No mapping filter is applied.
Trigger Events: see Transfer Methods in the collection description; automatic transfers require the relevant Outbound/Inbound Data Flow subscriptions to be enabled.
System Caveats
NCR Counterpoint Caveats
Descriptions arrive populated and short: Counterpoint holds the category description as text of up to 30 characters and requires it to be populated, so a description always arrives and is never longer than 30 characters. Subscribers replacing this mapping with a formula are not held to that limit by iPaaS.com, but should keep results short enough to stay readable alongside descriptions that came straight from Counterpoint.
Integration Flow
No records are transferred as prerequisites for this collection. The records it references are expected to exist already.
The record is sent to iPaaS.com, where subsequent transfers are routed by the external ID recorded on transfer.
Mappings
Add/Update NCR Counterpoint Customer Category TO iPaaS.com
Mapping Type | Source Field (NCR Counterpoint) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. IPaaS.com rejects the customer category without it. |
Field |
| Description | Optional. . |
Name — Field
Source: CATEG_COD · Destination: Name
This is a required field — iPaaS.com rejects the customer category without it. The customer category code as maintained in NCR Counterpoint, carried across unchanged and used as the category's name in iPaaS.com.
This is the short code subscribers or their MiSP see against the category in Counterpoint, not its readable label — the label travels on Description. Counterpoint always supplies it, because it is the category's key.
Customer categories classify customers for pricing and reporting; they are separate from the ecommerce categories that classify products, which the Add/Update NCR Counterpoint Ecommerce Category TO iPaaS.com collection handles.
Description — Field
Source: DESCR · Destination: Description
This is an optional field. The customer category's readable description as maintained in NCR Counterpoint, carried across unchanged. It is the label subscribers recognize where Name carries only the code.
Counterpoint stores this as text of up to 30 characters and requires it to be populated, so a description always arrives and is never longer than 30 characters. Subscribers replacing this mapping with a formula are not held to that limit by iPaaS.com, but should keep results short enough to stay readable alongside descriptions that came straight from Counterpoint.
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.
Testing & Validation
Replace every placeholder value called out above with one from the target Counterpoint installation, and confirm each exists in Counterpoint.
Transfer a single record through Manual Sync and confirm it appears in Counterpoint as expected.
Confirm any child records transferred with the parent.
Enable the relevant triggers and confirm a new record transfers automatically, and that a change updates the same Counterpoint record 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.
Related Documents
NCR Counterpoint Connections and Settings: the credentials and subscription settings that connect iPaaS.com to Counterpoint.
NCR Counterpoint Installation Instructions: installing CPHive and CPWebhooks on the Counterpoint server.
NCR Counterpoint Known Limitations: what the integration does not do, and the values to replace before go-live.
NCR Counterpoint Error Messages: the errors a transfer can raise, what causes them, and how to resolve them.
NCR Counterpoint API Endpoints: the CPHive endpoints the integration calls.