NCR Counterpoint to iPaaS.com Shipping Method Mapping Documentation

Summary

This mapping collection brings the shipping methods maintained in NCR Counterpoint into iPaaS.com. It carries the shipping method's ship-via code and its readable description — the carrier or service name subscribers recognize.

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

Vendor-only shipping methods are included: because this collection applies no filter on Counterpoint's customer/vendor distinction, shipping methods set up solely for vendor use reach iPaaS.com alongside those offered to customers. Subscribers or their MiSP who want only the customer-facing methods should add a mapping filter to this collection.

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 Shipping Method TO iPaaS.com

Mapping Type	Source Field (NCR Counterpoint)	Destination Field (iPaaS.com)	Description
Field	`SHIP_VIA_COD`	Name	Required. IPaaS.com rejects the shipping method without it.
Field	`DESCR`	Description	Optional. .

Name — Field

Source: SHIP_VIA_COD · Destination: Name

This is a required field — iPaaS.com rejects the shipping method without it. The ship-via code as maintained in NCR Counterpoint, carried across unchanged and used as the shipping method's name in iPaaS.com.

This is the short code subscribers or their MiSP see against the shipping method in Counterpoint, not its readable label — the label travels on Description. Counterpoint always supplies it, because it is the shipping method's key.

Description — Field

Source: DESCR · Destination: Description

This is an optional field. The shipping method's readable description as maintained in NCR Counterpoint — the carrier or service name subscribers recognize — carried across unchanged. It is the label subscribers see where Name carries only the code.

Counterpoint marks shipping methods as valid for customers, for vendors, or for both. This collection does not filter on that distinction, so vendor-only shipping methods transfer to iPaaS.com alongside the customer-facing ones. Subscribers who need only the customer-facing methods in iPaaS.com should add a mapping filter to this collection.

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.