Summary
This mapping collection brings barcode types from NCR Counterpoint into iPaaS.com. A barcode type is the category a barcode belongs to — the kind of identifier it is, rather than the barcode value itself. It carries two things: the barcode type's identifier as maintained in Counterpoint, which becomes the type's name in iPaaS.com, and its readable description.
ID Format
Manual Sync id: the Counterpoint barcode type identifier — this collection reads inbound from Counterpoint, so the id entered on the Manual Sync page is the type's Counterpoint-side identifier, not an iPaaS.com value.
External ID saved after transfer: once a barcode type has been transferred, iPaaS.com records its Counterpoint identifier as the external ID on a dedicated platform-managed external-ID record. That record — not any field on the barcode type record itself — is the primary match that routes a subsequent transfer of the same type to an update rather than adding it a second time. The Name mapping also writes the Counterpoint identifier onto the iPaaS.com barcode type, which gives subscribers visibility of the type 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 barcode types.
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
A description is always present and is always short: Counterpoint stores the barcode type's 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 or their MiSP replacing the Description 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.
iPaaS.com Caveats
Barcode types must be in place before products transfer: a barcode arriving with a product is classified against a type that already exists in iPaaS.com. This collection is not run as a prerequisite of a product transfer, and products are not transferred as a prerequisite of this collection — the two are sequenced by subscribers or their MiSP, not by the integration.
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 Product Barcode Type TO iPaaS.com
Mapping Type | Source Field (NCR Counterpoint) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. IPaaS.com rejects the barcode type without it. |
Field |
| Description | Optional. . |
Name — Field
Source: BARCOD_ID · Destination: Name
This is a required field — iPaaS.com rejects the barcode type without it. The barcode type identifier as maintained in NCR Counterpoint, carried across unchanged and used as the barcode type's name in iPaaS.com.
A barcode type is the category a barcode belongs to — the kind of identifier it is, rather than the barcode value itself. Counterpoint always supplies this value, because it is the barcode type's key.
This collection transfers the types only. The barcode values that reference them travel with their products, as part of a full product transfer, rather than through this collection. Because a barcode's type must already exist in iPaaS.com for the barcode to be classified against it, barcode types should transfer before products.
Description — Field
Source: DESCR · Destination: Description
This is an optional field. The barcode type's readable description as maintained in NCR Counterpoint, carried across unchanged. It is the label subscribers or their MiSP recognize where Name carries only the identifier.
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.
Additional Notes
Changes in Counterpoint do not transfer on their own until the trigger is installed: at the time this documentation was written, the barcode type trigger subscriptions are not created by default, so until that Counterpoint-side installation step has been carried out and the subscriptions enabled a barcode type that is added, renamed, or re-described in NCR Counterpoint does not appear or change in iPaaS.com until a Manual Sync is run for it. Subscribers or their MiSP who maintain barcode types regularly should either carry out that step or plan for the on-demand sync.
These and other runtime behaviors are documented in NCR Counterpoint Known Limitations.
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.