This mapping collection brings items from NCR Counterpoint into iPaaS.com as products. It carries the item's number and its short and long descriptions, its weight, how it is taxed, a single convenience barcode, its category assignments, whether it is a physical or virtual product, whether it is available, whether stock is counted for the item as a whole or per variant, and its standard and current selling prices. It also records whether the item is a kit parent and what the item most recently cost.

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 Filter

Filter Description.

Only items that NCR Counterpoint flags as ecommerce items are transferred. An item whose ecommerce flag holds anything other than Y is skipped, and because the eleven child collections are dispatched by this one, none of them contributes anything for a skipped item either — no variants, stock, units, barcodes, options, or substitute items arrive by this route. The standalone inventory collections reach the same iPaaS.com stock records by a separate route, but as shipped their Counterpoint-side webhook subscriptions carry their own filter limiting them to ecommerce items too, so a non-ecommerce item's stock does not arrive by that route either. Subscribers or their MiSP who find products missing from iPaaS.com should check this flag on the item in Counterpoint first. Subscribers who want their whole item catalogue in iPaaS.com rather than only their ecommerce items should review this filter before enabling the collection.

Source: ITEM_NO.toString().TrimEnd() · Destination: Sku

This is a required field — iPaaS.com rejects the product without it. The Counterpoint item number, with any trailing spaces removed. Counterpoint stores the item number as text of up to 20 characters and always populates it, so this mapping always produces a value. This is the identifier subscribers or their MiSP use to recognise the product in both systems.

The trailing-space trim matters beyond appearance. The child collections build their own keys from this same item number — the variant SKU format in Add NCR Counterpoint Product Variant TO iPaaS.com is derived from it, and the unit and barcode collections look records up by it. Subscribers who replace this mapping with a different format should expect to revisit those collections as well.

Source: DESCR · Destination: Name

This is a required field — iPaaS.com rejects the product without it. The item's short description in NCR Counterpoint, used as the product name. Counterpoint stores this as text of up to 30 characters and always supplies a value, so a name 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 short names remain easier to read alongside names that came straight from Counterpoint. Where a longer, richer name is wanted, the item's long description is available and is already mapped to Description.

Source: LONG_DESCR · Destination: Description

This is an optional field. The item's long description in NCR Counterpoint, carried across unchanged. Items saved without a long description transfer with this field empty; iPaaS.com accepts the product either way. This is the field to use for storefront copy, since Name is limited to the item's 30-character short description.

Source: WEIGHT · Destination: Weight

This is an optional field. The item's weight as recorded in NCR Counterpoint, carried across unchanged. iPaaS.com does not attach a unit of measure to this number, so it means whatever the subscriber's Counterpoint installation records it in — a value of 5 is not inherently pounds or kilograms. Subscribers relying on weight for shipping calculations should confirm that the receiving system reads it in the same unit Counterpoint stores it in. Items with no weight recorded transfer with the field empty.

Variants do not carry their own weight in this integration — Add NCR Counterpoint Product Variant TO iPaaS.com reads this same item-level value for every variant.

Source: IS_TXBL == "N" ? "None" : TAX_CATEG_COD · Destination: TaxClass

This is an optional field. Records how the product is taxed. When the Counterpoint item is flagged as not taxable, the mapping produces None; otherwise it produces the item's Counterpoint tax category code as-is.

The iPaaS.com endpoint does not restrict this field to a fixed list of values, so whatever tax category codes exist in the subscriber's Counterpoint installation arrive unchanged. Because the codes are the subscriber's own, a receiving system that expects its own tax-class names will need those codes either renamed in Counterpoint or translated somewhere downstream. A taxable item with no tax category code recorded transfers with this field empty rather than as None — only the not-taxable flag produces None.

Source:

Destination: Barcode

This is an optional field. Finds a single barcode to record against the product. The formula searches the subscriber's Counterpoint barcode records for one that belongs to this item, is registered against the stocking unit, carries the barcode type UPC, and is not tied to any specific grid dimension. If such a barcode exists it is used; if none does, the product transfers with no barcode and the transfer still succeeds.

Three points follow from how narrowly that search is defined. Barcodes of any type other than UPC are not considered. Barcodes registered against an alternate unit rather than the stocking unit are not considered here — those are carried by the alternate unit collections instead. And grid-specific barcodes are excluded: a barcode that identifies one particular colour or size does not identify the product as a whole, so those belong to Add/Update NCR Counterpoint Product Variant Barcode TO iPaaS.com.

This is deliberately a single convenience value, not the subscriber's full barcode list. Add/Update NCR Counterpoint Product Barcode TO iPaaS.com carries every barcode on the item as its own record, and is the mapping to rely on where a product genuinely has more than one.

Source: return await ConvertCategoriesToSpaceportIdsAsync(Categories); · Destination: Categories

This is an optional field. Assigns the product to its categories in iPaaS.com. The formula reads the item's ecommerce category assignments from NCR Counterpoint and converts each one to the matching iPaaS.com category.

Only the ecommerce categories are read. Counterpoint's other category structures are not included, so an item organised solely by those arrives with no category assignments.

The iPaaS.com endpoint requires each category referenced here to be one that already exists in iPaaS.com, and the same category must not be assigned twice. The formula honours that by including only those Counterpoint categories it can match to an existing iPaaS.com category. A category the subscriber has not yet transferred is left out silently — the product still transfers, and it is simply not assigned to that category. This is the most common reason for a product arriving with fewer categories than expected, and it resolves itself once categories are transferring: subscribers or their MiSP should have the product category collection running before this one, since this mapping does not pull a missing category across on its own.

Removing a category assignment later is not handled by this mapping. iPaaS.com treats an update through this collection as adding the categories listed, so a category dropped in Counterpoint is not automatically unassigned in iPaaS.com.

Source: Lookup Translation — **CP Product ITEM_TYP To iPaaS** · Destination: Type

This is a required field — iPaaS.com rejects the product without it. Allowed values: Physical and Virtual. Records whether the product is something the subscriber ships or something they do not, by translating the Counterpoint item type.

Because Type is required, an item whose Counterpoint item type has no row in this table produces no value and is rejected rather than transferred without one. The three rows above cover the item types this table was built for; subscribers whose Counterpoint installation uses any further item type should add a row for it before enabling this collection, and should confirm the set against their own installation rather than assuming these three are exhaustive. Each row's result must remain either Physical or Virtual — a custom value causes the transfer to fail.

Source: Lookup Translation — **CP Product STAT To iPaaS** · Destination: Status

This is a required field — iPaaS.com rejects the product without it. Allowed values: Preorder, Active, Disabled, and Discontinued. Records whether the product is available, by translating the Counterpoint item status.

Two of the four values iPaaS.com accepts are never produced by this table as shipped. Preorder has no Counterpoint equivalent to translate from. Discontinued is not used even though Counterpoint has a discontinued status — the D row deliberately reports it as Disabled, which stops the product being sold rather than merely labelling it. Subscribers who want a discontinued Counterpoint item to arrive as Discontinued can change that row's result, but should confirm first that the receiving system treats Discontinued as unavailable, since the two values can behave differently downstream.

Because Status is required, an item whose Counterpoint status has no row here produces no value and is rejected rather than transferred without one. Each row's result must remain one of the four allowed values.

Source: Lookup Translation — **CP Product TRK_METH To iPaaS** · Destination: TrackingMethod

This is a required field — iPaaS.com rejects the product without it. Allowed values: Product and Variant. Records whether stock is counted for the product as a whole or separately for each variant, by translating the Counterpoint tracking method.

This mapping decides the shape of the whole transfer, so it deserves more care than its two values suggest. iPaaS.com allows variants only where the tracking method is Variant; where it is Product, variants are not accepted in the request at all. Only Counterpoint grid items translate to Variant, which is what makes the child collections behave: for a grid item, Add NCR Counterpoint Product Variant TO iPaaS.com and its own children carry each grid cell, and for every other item they contribute nothing.

Note that serial-numbered items are reported as Product, not Variant — Counterpoint tracks their stock at item level and the serial numbers themselves travel separately, on Add/Update NCR Counterpoint Product Inventory TO iPaaS.com.

Because TrackingMethod is required, an item whose Counterpoint tracking method has no row here produces no value and is rejected rather than transferred without one. Each row's result must remain either Product or Variant. Subscribers should not repoint a grid item away from Variant to flatten it, as the variant collections would then send variants that iPaaS.com does not accept for a product-tracked product.

Source: CoalesceToDecimal(REG_PRC,PRC_1) · Destination: DefaultPrice

This is a required field — iPaaS.com rejects the product without it. The product's standard selling price. The formula uses the Counterpoint item's regular price, falling back to its price-1 where no regular price is recorded.

SalePrice in this collection uses the same two prices in the opposite order, so on an item that records both, DefaultPrice reports the regular price and SalePrice reports price-1. On an item that records only one of them, both fields report that same value and the product arrives with no effective discount.

Because the field is required, subscribers should confirm that at least one of the two prices is populated on every item that passes this collection's filter. An item with neither recorded produces no value and is rejected.

Source: CoalesceToDecimal(PRC_1,REG_PRC) · Destination: SalePrice

This is an optional field. The product's current selling price. The formula uses the Counterpoint item's price-1, falling back to its regular price where no price-1 is recorded — the reverse of DefaultPrice in this collection.

Counterpoint supports several price levels, and only price-1 is read here. Subscribers whose storefront pricing lives on a different price level should repoint this mapping at that level rather than relying on price-1.

Note that this mapping reports price-1 as the sale price whether or not the item is actually on sale. Where price-1 is simply the everyday price, DefaultPrice and SalePrice arrive equal, which correctly represents no discount.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Mapping Filter

Filter Description.

A unit record is produced only for an item that actually defines alternate unit 1. An item that does not is skipped, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

This is the only thing that distinguishes this collection from the other four alternate unit collections, each of which applies the same test to its own slot. Subscribers or their MiSP editing this filter should keep it pointed at slot 1: repointing it at another slot would leave that slot carried twice and slot 1 not carried at all.

Source: Parent.ALT_1_UNIT · Destination: Name

This is a required field — iPaaS.com rejects the unit without it. The name of the item's alternate unit 1 in NCR Counterpoint — something like Case, Box, or Dozen — carried across unchanged.

NCR Counterpoint gives every item a stocking unit and up to five alternate units, numbered 1 to 5. This collection carries alternate unit 1 specifically, and each of the five has its own collection alongside it. The collection's filter means it contributes nothing for an item that has no alternate unit 1 defined, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

The same unit name must not appear twice on one product. Counterpoint does not prevent a subscriber defining the same unit name in two alternate slots on the same item, so where that has happened the second one to transfer is rejected. Subscribers or their MiSP seeing unit records rejected as duplicates should check their items for a unit name repeated across slots.

Unit names are also the link the barcode collections rely on: Add/Update NCR Counterpoint Product Barcode TO iPaaS.com reports each barcode's unit by name, and iPaaS.com requires that name to be a valid unit for the product. A unit that fails to transfer here therefore takes its barcodes with it.

Source: ConvertToDouble(ConvertToDecimal(Parent.ALT_1_NUMER) / ConvertToDecimal(Parent.ALT_1_DENOM)) · Destination: Conversion

This is a recommended field. iPaaS.com accepts the unit without it, but a unit with no conversion factor cannot be related to the stocking unit, so it should be mapped for any meaningful unit sync. Records how many stocking units make up one of this alternate unit.

NCR Counterpoint expresses the relationship as a fraction, and the formula divides the numerator by the denominator to produce a single number. A case of twelve is stored as 12 over 1 and arrives as 12.

A properly configured alternate unit in NCR Counterpoint records both parts of that fraction. Where the denominator is missing or zero the division has no meaningful result, so subscribers or their MiSP should confirm the alternate unit's setup on the item rather than expecting this mapping to compensate for it.

The result is used by MSRP, DefaultPrice, and SalePrice in this collection when a price has to be computed rather than read, so a wrong conversion factor produces wrong prices as well as a wrong quantity.

Source: (CoalesceToInt(Parent.ALT_1_REG_PRC,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_1_NUMER) / ConvertToDecimal(Parent.ALT_1_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_1_REG_PRC)) · Destination: MSRP

This is an optional field. The manufacturer's suggested price for one of this alternate unit.

The formula prefers the regular price recorded against alternate unit 1 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00.

Two aspects of this deserve attention before subscribers rely on the value. The computed fallback is based on the item's price-1 rather than its regular price, even though the value being produced is the alternate unit's regular price — so on an item where the two differ, a computed MSRP is derived from the sale price rather than the list price. And the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit regular price of less than one currency unit can be treated as though it were not set at all, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_1_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_1_NUMER) / ConvertToDecimal(Parent.ALT_1_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_1_PRC_1)) · Destination: DefaultPrice

This is an optional field. The standard selling price for one of this alternate unit.

The formula prefers the price-1 recorded against alternate unit 1 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00. The computed fallback assumes no discount for buying the larger unit; subscribers who price a case below twelve singles must record that price against the alternate unit in Counterpoint rather than expecting the calculation to find it.

As with MSRP, the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit price of less than one currency unit can be treated as though it were not set, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_1_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_1_NUMER) / ConvertToDecimal(Parent.ALT_1_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_1_PRC_1)) · Destination: SalePrice

This is an optional field. The current selling price for one of this alternate unit.

This mapping performs exactly the same calculation as DefaultPrice in this collection, reading the same alternate-unit price-1 and falling back to the same computed figure. Alternate units therefore always arrive with their default price and sale price equal, which represents no discount. The pattern the parent collection uses for the item itself — where DefaultPrice reads the regular price and SalePrice reads price-1 — is not repeated here, because Counterpoint holds a single price-1 per alternate unit slot and the unit's regular price is already read by MSRP.

Subscribers or their MiSP who want alternate units to carry a genuine discount need a second price for this mapping to read; repointing it at the alternate unit's regular price would report that price as the sale price rather than producing a discount.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Mapping Filter

Filter Description.

A unit record is produced only for an item that actually defines alternate unit 2. An item that does not is skipped, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

This is the only thing that distinguishes this collection from the other four alternate unit collections, each of which applies the same test to its own slot. Subscribers or their MiSP editing this filter should keep it pointed at slot 2: repointing it at another slot would leave that slot carried twice and slot 2 not carried at all.

Source: Parent.ALT_2_UNIT · Destination: Name

This is a required field — iPaaS.com rejects the unit without it. The name of the item's alternate unit 2 in NCR Counterpoint — something like Case, Box, or Dozen — carried across unchanged.

NCR Counterpoint gives every item a stocking unit and up to five alternate units, numbered 1 to 5. This collection carries alternate unit 2 specifically, and each of the five has its own collection alongside it. The collection's filter means it contributes nothing for an item that has no alternate unit 2 defined, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

The same unit name must not appear twice on one product. Counterpoint does not prevent a subscriber defining the same unit name in two alternate slots on the same item, so where that has happened the second one to transfer is rejected. Subscribers or their MiSP seeing unit records rejected as duplicates should check their items for a unit name repeated across slots.

Unit names are also the link the barcode collections rely on: Add/Update NCR Counterpoint Product Barcode TO iPaaS.com reports each barcode's unit by name, and iPaaS.com requires that name to be a valid unit for the product. A unit that fails to transfer here therefore takes its barcodes with it.

Source: ConvertToDouble(ConvertToDecimal(Parent.ALT_2_NUMER) / ConvertToDecimal(Parent.ALT_2_DENOM)) · Destination: Conversion

This is a recommended field. iPaaS.com accepts the unit without it, but a unit with no conversion factor cannot be related to the stocking unit, so it should be mapped for any meaningful unit sync. Records how many stocking units make up one of this alternate unit.

NCR Counterpoint expresses the relationship as a fraction, and the formula divides the numerator by the denominator to produce a single number. A case of twelve is stored as 12 over 1 and arrives as 12.

A properly configured alternate unit in NCR Counterpoint records both parts of that fraction. Where the denominator is missing or zero the division has no meaningful result, so subscribers or their MiSP should confirm the alternate unit's setup on the item rather than expecting this mapping to compensate for it.

The result is used by MSRP, DefaultPrice, and SalePrice in this collection when a price has to be computed rather than read, so a wrong conversion factor produces wrong prices as well as a wrong quantity.

Source: (CoalesceToInt(Parent.ALT_2_REG_PRC,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_2_NUMER) / ConvertToDecimal(Parent.ALT_2_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_2_REG_PRC)) · Destination: MSRP

This is an optional field. The manufacturer's suggested price for one of this alternate unit.

The formula prefers the regular price recorded against alternate unit 2 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00.

Two aspects of this deserve attention before subscribers rely on the value. The computed fallback is based on the item's price-1 rather than its regular price, even though the value being produced is the alternate unit's regular price — so on an item where the two differ, a computed MSRP is derived from the sale price rather than the list price. And the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit regular price of less than one currency unit can be treated as though it were not set at all, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_2_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_2_NUMER) / ConvertToDecimal(Parent.ALT_2_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_2_PRC_1)) · Destination: DefaultPrice

This is an optional field. The standard selling price for one of this alternate unit.

The formula prefers the price-1 recorded against alternate unit 2 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00. The computed fallback assumes no discount for buying the larger unit; subscribers who price a case below twelve singles must record that price against the alternate unit in Counterpoint rather than expecting the calculation to find it.

As with MSRP, the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit price of less than one currency unit can be treated as though it were not set, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_2_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_2_NUMER) / ConvertToDecimal(Parent.ALT_2_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_2_PRC_1)) · Destination: SalePrice

This is an optional field. The current selling price for one of this alternate unit.

This mapping performs exactly the same calculation as DefaultPrice in this collection, reading the same alternate-unit price-1 and falling back to the same computed figure. Alternate units therefore always arrive with their default price and sale price equal, which represents no discount. The pattern the parent collection uses for the item itself — where DefaultPrice reads the regular price and SalePrice reads price-1 — is not repeated here, because Counterpoint holds a single price-1 per alternate unit slot and the unit's regular price is already read by MSRP.

Subscribers or their MiSP who want alternate units to carry a genuine discount need a second price for this mapping to read; repointing it at the alternate unit's regular price would report that price as the sale price rather than producing a discount.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Mapping Filter

Filter Description.

A unit record is produced only for an item that actually defines alternate unit 3. An item that does not is skipped, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

This is the only thing that distinguishes this collection from the other four alternate unit collections, each of which applies the same test to its own slot. Subscribers or their MiSP editing this filter should keep it pointed at slot 3: repointing it at another slot would leave that slot carried twice and slot 3 not carried at all.

Source: Parent.ALT_3_UNIT · Destination: Name

This is a required field — iPaaS.com rejects the unit without it. The name of the item's alternate unit 3 in NCR Counterpoint — something like Case, Box, or Dozen — carried across unchanged.

NCR Counterpoint gives every item a stocking unit and up to five alternate units, numbered 1 to 5. This collection carries alternate unit 3 specifically, and each of the five has its own collection alongside it. The collection's filter means it contributes nothing for an item that has no alternate unit 3 defined, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

The same unit name must not appear twice on one product. Counterpoint does not prevent a subscriber defining the same unit name in two alternate slots on the same item, so where that has happened the second one to transfer is rejected. Subscribers or their MiSP seeing unit records rejected as duplicates should check their items for a unit name repeated across slots.

Unit names are also the link the barcode collections rely on: Add/Update NCR Counterpoint Product Barcode TO iPaaS.com reports each barcode's unit by name, and iPaaS.com requires that name to be a valid unit for the product. A unit that fails to transfer here therefore takes its barcodes with it.

Source: ConvertToDouble(ConvertToDecimal(Parent.ALT_3_NUMER) / ConvertToDecimal(Parent.ALT_3_DENOM)) · Destination: Conversion

This is a recommended field. iPaaS.com accepts the unit without it, but a unit with no conversion factor cannot be related to the stocking unit, so it should be mapped for any meaningful unit sync. Records how many stocking units make up one of this alternate unit.

NCR Counterpoint expresses the relationship as a fraction, and the formula divides the numerator by the denominator to produce a single number. A case of twelve is stored as 12 over 1 and arrives as 12.

A properly configured alternate unit in NCR Counterpoint records both parts of that fraction. Where the denominator is missing or zero the division has no meaningful result, so subscribers or their MiSP should confirm the alternate unit's setup on the item rather than expecting this mapping to compensate for it.

The result is used by MSRP, DefaultPrice, and SalePrice in this collection when a price has to be computed rather than read, so a wrong conversion factor produces wrong prices as well as a wrong quantity.

Source: (CoalesceToInt(Parent.ALT_3_REG_PRC,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_3_NUMER) / ConvertToDecimal(Parent.ALT_3_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_3_REG_PRC)) · Destination: MSRP

This is an optional field. The manufacturer's suggested price for one of this alternate unit.

The formula prefers the regular price recorded against alternate unit 3 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00.

Two aspects of this deserve attention before subscribers rely on the value. The computed fallback is based on the item's price-1 rather than its regular price, even though the value being produced is the alternate unit's regular price — so on an item where the two differ, a computed MSRP is derived from the sale price rather than the list price. And the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit regular price of less than one currency unit can be treated as though it were not set at all, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_3_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_3_NUMER) / ConvertToDecimal(Parent.ALT_3_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_3_PRC_1)) · Destination: DefaultPrice

This is an optional field. The standard selling price for one of this alternate unit.

The formula prefers the price-1 recorded against alternate unit 3 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00. The computed fallback assumes no discount for buying the larger unit; subscribers who price a case below twelve singles must record that price against the alternate unit in Counterpoint rather than expecting the calculation to find it.

As with MSRP, the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit price of less than one currency unit can be treated as though it were not set, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_3_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_3_NUMER) / ConvertToDecimal(Parent.ALT_3_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_3_PRC_1)) · Destination: SalePrice

This is an optional field. The current selling price for one of this alternate unit.

This mapping performs exactly the same calculation as DefaultPrice in this collection, reading the same alternate-unit price-1 and falling back to the same computed figure. Alternate units therefore always arrive with their default price and sale price equal, which represents no discount. The pattern the parent collection uses for the item itself — where DefaultPrice reads the regular price and SalePrice reads price-1 — is not repeated here, because Counterpoint holds a single price-1 per alternate unit slot and the unit's regular price is already read by MSRP.

Subscribers or their MiSP who want alternate units to carry a genuine discount need a second price for this mapping to read; repointing it at the alternate unit's regular price would report that price as the sale price rather than producing a discount.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Mapping Filter

Filter Description.

A unit record is produced only for an item that actually defines alternate unit 4. An item that does not is skipped, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

This is the only thing that distinguishes this collection from the other four alternate unit collections, each of which applies the same test to its own slot. Subscribers or their MiSP editing this filter should keep it pointed at slot 4: repointing it at another slot would leave that slot carried twice and slot 4 not carried at all.

Source: Parent.ALT_4_UNIT · Destination: Name

This is a required field — iPaaS.com rejects the unit without it. The name of the item's alternate unit 4 in NCR Counterpoint — something like Case, Box, or Dozen — carried across unchanged.

NCR Counterpoint gives every item a stocking unit and up to five alternate units, numbered 1 to 5. This collection carries alternate unit 4 specifically, and each of the five has its own collection alongside it. The collection's filter means it contributes nothing for an item that has no alternate unit 4 defined, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

The same unit name must not appear twice on one product. Counterpoint does not prevent a subscriber defining the same unit name in two alternate slots on the same item, so where that has happened the second one to transfer is rejected. Subscribers or their MiSP seeing unit records rejected as duplicates should check their items for a unit name repeated across slots.

Unit names are also the link the barcode collections rely on: Add/Update NCR Counterpoint Product Barcode TO iPaaS.com reports each barcode's unit by name, and iPaaS.com requires that name to be a valid unit for the product. A unit that fails to transfer here therefore takes its barcodes with it.

Source: ConvertToDouble(ConvertToDecimal(Parent.ALT_4_NUMER) / ConvertToDecimal(Parent.ALT_4_DENOM)) · Destination: Conversion

This is a recommended field. iPaaS.com accepts the unit without it, but a unit with no conversion factor cannot be related to the stocking unit, so it should be mapped for any meaningful unit sync. Records how many stocking units make up one of this alternate unit.

NCR Counterpoint expresses the relationship as a fraction, and the formula divides the numerator by the denominator to produce a single number. A case of twelve is stored as 12 over 1 and arrives as 12.

A properly configured alternate unit in NCR Counterpoint records both parts of that fraction. Where the denominator is missing or zero the division has no meaningful result, so subscribers or their MiSP should confirm the alternate unit's setup on the item rather than expecting this mapping to compensate for it.

The result is used by MSRP, DefaultPrice, and SalePrice in this collection when a price has to be computed rather than read, so a wrong conversion factor produces wrong prices as well as a wrong quantity.

Source: (CoalesceToInt(Parent.ALT_4_REG_PRC,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_4_NUMER) / ConvertToDecimal(Parent.ALT_4_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_4_REG_PRC)) · Destination: MSRP

This is an optional field. The manufacturer's suggested price for one of this alternate unit.

The formula prefers the regular price recorded against alternate unit 4 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00.

Two aspects of this deserve attention before subscribers rely on the value. The computed fallback is based on the item's price-1 rather than its regular price, even though the value being produced is the alternate unit's regular price — so on an item where the two differ, a computed MSRP is derived from the sale price rather than the list price. And the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit regular price of less than one currency unit can be treated as though it were not set at all, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_4_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_4_NUMER) / ConvertToDecimal(Parent.ALT_4_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_4_PRC_1)) · Destination: DefaultPrice

This is an optional field. The standard selling price for one of this alternate unit.

The formula prefers the price-1 recorded against alternate unit 4 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00. The computed fallback assumes no discount for buying the larger unit; subscribers who price a case below twelve singles must record that price against the alternate unit in Counterpoint rather than expecting the calculation to find it.

As with MSRP, the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit price of less than one currency unit can be treated as though it were not set, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_4_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_4_NUMER) / ConvertToDecimal(Parent.ALT_4_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_4_PRC_1)) · Destination: SalePrice

This is an optional field. The current selling price for one of this alternate unit.

This mapping performs exactly the same calculation as DefaultPrice in this collection, reading the same alternate-unit price-1 and falling back to the same computed figure. Alternate units therefore always arrive with their default price and sale price equal, which represents no discount. The pattern the parent collection uses for the item itself — where DefaultPrice reads the regular price and SalePrice reads price-1 — is not repeated here, because Counterpoint holds a single price-1 per alternate unit slot and the unit's regular price is already read by MSRP.

Subscribers or their MiSP who want alternate units to carry a genuine discount need a second price for this mapping to read; repointing it at the alternate unit's regular price would report that price as the sale price rather than producing a discount.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Mapping Filter

Filter Description.

A unit record is produced only for an item that actually defines alternate unit 5. An item that does not is skipped, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

This is the only thing that distinguishes this collection from the other four alternate unit collections, each of which applies the same test to its own slot. Subscribers or their MiSP editing this filter should keep it pointed at slot 5: repointing it at another slot would leave that slot carried twice and slot 5 not carried at all.

Source: Parent.ALT_5_UNIT · Destination: Name

This is a required field — iPaaS.com rejects the unit without it. The name of the item's alternate unit 5 in NCR Counterpoint — something like Case, Box, or Dozen — carried across unchanged.

NCR Counterpoint gives every item a stocking unit and up to five alternate units, numbered 1 to 5. This collection carries alternate unit 5 specifically, and each of the five has its own collection alongside it. The collection's filter means it contributes nothing for an item that has no alternate unit 5 defined, so items using fewer than five alternate units produce fewer unit records rather than empty ones.

The same unit name must not appear twice on one product. Counterpoint does not prevent a subscriber defining the same unit name in two alternate slots on the same item, so where that has happened the second one to transfer is rejected. Subscribers or their MiSP seeing unit records rejected as duplicates should check their items for a unit name repeated across slots.

Unit names are also the link the barcode collections rely on: Add/Update NCR Counterpoint Product Barcode TO iPaaS.com reports each barcode's unit by name, and iPaaS.com requires that name to be a valid unit for the product. A unit that fails to transfer here therefore takes its barcodes with it.

Source: ConvertToDouble(ConvertToDecimal(Parent.ALT_5_NUMER) / ConvertToDecimal(Parent.ALT_5_DENOM)) · Destination: Conversion

This is a recommended field. iPaaS.com accepts the unit without it, but a unit with no conversion factor cannot be related to the stocking unit, so it should be mapped for any meaningful unit sync. Records how many stocking units make up one of this alternate unit.

NCR Counterpoint expresses the relationship as a fraction, and the formula divides the numerator by the denominator to produce a single number. A case of twelve is stored as 12 over 1 and arrives as 12.

A properly configured alternate unit in NCR Counterpoint records both parts of that fraction. Where the denominator is missing or zero the division has no meaningful result, so subscribers or their MiSP should confirm the alternate unit's setup on the item rather than expecting this mapping to compensate for it.

The result is used by MSRP, DefaultPrice, and SalePrice in this collection when a price has to be computed rather than read, so a wrong conversion factor produces wrong prices as well as a wrong quantity.

Source: (CoalesceToInt(Parent.ALT_5_REG_PRC,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_5_NUMER) / ConvertToDecimal(Parent.ALT_5_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_5_REG_PRC)) · Destination: MSRP

This is an optional field. The manufacturer's suggested price for one of this alternate unit.

The formula prefers the regular price recorded against alternate unit 5 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00.

Two aspects of this deserve attention before subscribers rely on the value. The computed fallback is based on the item's price-1 rather than its regular price, even though the value being produced is the alternate unit's regular price — so on an item where the two differ, a computed MSRP is derived from the sale price rather than the list price. And the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit regular price of less than one currency unit can be treated as though it were not set at all, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_5_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_5_NUMER) / ConvertToDecimal(Parent.ALT_5_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_5_PRC_1)) · Destination: DefaultPrice

This is an optional field. The standard selling price for one of this alternate unit.

The formula prefers the price-1 recorded against alternate unit 5 on the item. Where no such price is set, it computes one instead: it multiplies the unit's conversion factor by the item's price-1 and rounds the result to two decimal places — so a case of twelve on an item priced at 2.50 produces 30.00. The computed fallback assumes no discount for buying the larger unit; subscribers who price a case below twelve singles must record that price against the alternate unit in Counterpoint rather than expecting the calculation to find it.

As with MSRP, the test for whether a price is set converts it to a whole number before comparing it to zero, so an alternate-unit price of less than one currency unit can be treated as though it were not set, and the computed price used in preference to it. Subscribers or their MiSP whose alternate units are priced below one currency unit should validate the results in a staging environment before relying on them in production.

Source: (CoalesceToInt(Parent.ALT_5_PRC_1,0) <= 0 ? Round(ConvertToDouble(((ConvertToDecimal(Parent.ALT_5_NUMER) / ConvertToDecimal(Parent.ALT_5_DENOM))* ConvertToDecimal(Parent.PRC_1))),2) : ConvertToDouble(Parent.ALT_5_PRC_1)) · Destination: SalePrice

This is an optional field. The current selling price for one of this alternate unit.

This mapping performs exactly the same calculation as DefaultPrice in this collection, reading the same alternate-unit price-1 and falling back to the same computed figure. Alternate units therefore always arrive with their default price and sale price equal, which represents no discount. The pattern the parent collection uses for the item itself — where DefaultPrice reads the regular price and SalePrice reads price-1 — is not repeated here, because Counterpoint holds a single price-1 per alternate unit slot and the unit's regular price is already read by MSRP.

Subscribers or their MiSP who want alternate units to carry a genuine discount need a second price for this mapping to read; repointing it at the alternate unit's regular price would report that price as the sale price rather than producing a discount.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Mapping Filter

Filter Description.

Only barcodes that are not tied to a specific grid dimension are transferred. NCR Counterpoint marks an unused grid dimension with an asterisk, and this filter passes a barcode only where its first grid dimension carries that marker — that is, where the barcode identifies the item as a whole rather than one particular colour or size.

Grid-specific barcodes are excluded here and carried instead by Add/Update NCR Counterpoint Product Variant Barcode TO iPaaS.com, whose filter is the exact inverse of this one. Between the two collections, every barcode on the item is transferred exactly once. Subscribers or their MiSP editing either filter should edit both, or the two will begin to overlap or to leave barcodes behind.

Source:

Destination: Unit

This is an optional field, but where it is supplied iPaaS.com requires it to be a valid unit name for the product — not a unit id, and not a name the product does not have. Reports which of the item's units this barcode identifies.

NCR Counterpoint records the unit against a barcode as a number rather than a name, and the formula converts it by reading the matching unit name from the parent item: 0 gives the stocking unit, and 1 through 5 give the corresponding alternate unit. A value of an exclamation mark means no particular unit, and produces an empty value.

Because the endpoint validates the name against the product's units, this mapping depends on the unit collections having transferred successfully — Add NCR Counterpoint Product Stocking Unit TO iPaaS.com and the five alternate unit collections between them supply the names this mapping produces. A barcode naming a unit that did not transfer is rejected. Subscribers or their MiSP should have the unit collections running before enabling this one.

The conversion covers the stocking unit, the five alternate units, and the no-unit marker. A Counterpoint unit value outside that set produces no value at all rather than an empty one, so subscribers whose installation records unit values beyond those should validate this mapping's behavior in a staging environment before relying on it in production.

Source: return await GetSpaceportIdAsync(BARCOD_ID, "Alternate Id Type", SpaceportSystemId); · Destination: AlternateIdTypeId

This is a required field — iPaaS.com rejects the barcode without it, and the value must be an alternate id type that already exists in iPaaS.com. Records what kind of identifier this is. The formula takes the Counterpoint barcode type and looks up the matching alternate id type in iPaaS.com.

This is the mapping in this collection with a hard prerequisite. Because the endpoint requires a valid type, an iPaaS.com alternate id type matching each Counterpoint barcode type in use MUST exist before the first transfer — the formula does not create one. Where no match is found the mapping produces no value and the barcode is rejected. Subscribers or their MiSP should EITHER (a) transfer their Counterpoint barcode types into iPaaS.com before enabling this collection, OR (b) create the matching alternate id types in iPaaS.com by hand — one MUST be done at install time.

Note that this collection carries barcodes of every type the subscriber uses, not only UPC. That is a deliberate difference from the Barcode convenience mappings on the product and unit collections, which look only for a UPC: those answer "what is this product's barcode", where this collection answers "what identifiers does this product have". The consequence is that every barcode type in the subscriber's installation needs a matching alternate id type, not just UPC.

Source: BARCOD · Destination: AlternateId

This is a required field — iPaaS.com rejects the barcode without it. The barcode itself, as recorded in NCR Counterpoint and carried across unchanged.

iPaaS.com does not allow the same barcode to appear twice on a product, nor the same combination of alternate id type and unit to appear twice. The second constraint is the one subscribers meet in practice: it means a product may carry only one barcode of a given type per unit, so an item with two UPC barcodes both registered against the stocking unit has one of them rejected. Where that occurs, the item's barcode setup in Counterpoint is the place to resolve it.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Source: AVG_COST · Destination: Cost

This is an optional field. NCR Counterpoint's rolling average cost for this item at this location, carried across unchanged.

Average cost moves as stock is received at different prices, so this is a point-in-time figure — it reflects the cost when the transfer ran, not a live value, and it is refreshed on the next transfer of the item. It is held per location, so the same item can arrive with different costs at different locations, which is expected rather than a fault.

This is a different figure from the Parent Last Cost custom field on Add/Update NCR Counterpoint Product TO iPaaS.com, which reports the price on the most recent receipt rather than a rolling average and is not held per location. Subscribers reporting on margin should be deliberate about which of the two they use.

Source: QTY_AVAIL · Destination: QtyAvailable

This is an optional field, but it is the figure a storefront normally uses to decide what can be sold, so it should be mapped for any meaningful inventory sync. The quantity of this item available to sell at this location, as NCR Counterpoint calculates it.

Available quantity is generally lower than QtyOnHand, because Counterpoint reduces it by stock already committed to orders. The gap between the two is normal and is the point of carrying both. This is a point-in-time figure — it reflects the moment the transfer ran, and sales made after that are not reflected until the item transfers again.

Source: QTY_ON_HND · Destination: QtyOnHand

This is an optional field. The physical quantity of this item at this location, as counted in NCR Counterpoint.

This is stock on the shelf, including any already committed to orders — which is why it is usually higher than QtyAvailable. It is the right figure for stock-on-hand reporting and the wrong one for deciding what a storefront may sell. Like QtyAvailable, it is a point-in-time figure refreshed on the next transfer of the item.

Source: return await LocationIdFromNameAsync(LOC_ID); · Destination: LocationId

This is a required field — iPaaS.com rejects the inventory record without it, and the value must be a location that already exists in iPaaS.com. Records which location this stock sits at. The formula takes the Counterpoint location id and looks up the matching iPaaS.com location by name.

This is the one mapping in this collection with a hard prerequisite. Because the endpoint requires a valid location, an iPaaS.com location whose name matches the Counterpoint location id MUST exist before the first transfer — the formula does not create one. Where no match is found the mapping produces no value and the inventory record is rejected. Subscribers or their MiSP should EITHER (a) transfer their Counterpoint locations into iPaaS.com before enabling this collection, OR (b) create the matching locations in iPaaS.com by hand — one MUST be done at install time.

The match is by name, so an iPaaS.com location renamed after setup stops matching and its inventory begins to fail. iPaaS.com also rejects the same location appearing twice on one product, which Counterpoint's one-record-per-location structure naturally satisfies.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Source: GRID_ENT_ORDER · Destination: Order

This is an optional field. The position this option occupies among the product's options, taken from the order the grid dimensions are entered in within NCR Counterpoint.

Mapping it keeps the options presenting in the order the subscriber already sees in Counterpoint — colour before size, if that is how the grid was set up — rather than in an arbitrary one. Options transferred without an order are still accepted by iPaaS.com; only their presentation order is left undefined.

Source: GRID_DIM_TAG · Destination: OptionName

This is a required field — iPaaS.com rejects the option without it. The name of the grid dimension as labelled in NCR Counterpoint — typically something like Colour or Size — carried across unchanged.

The same option name must not appear twice on one product, which Counterpoint's grid structure naturally satisfies as each dimension is distinct. A grid dimension left unlabelled in Counterpoint produces no value and the option is rejected, so subscribers or their MiSP should confirm every grid dimension in use carries a label before enabling this collection.

This collection describes what options exist on the product; Add/Update NCR Counterpoint Product Option Value TO iPaaS.com carries the values each option can take. The Options mapping on Add NCR Counterpoint Product Variant TO iPaaS.com separately records which of those values a given variant carries, and it reads the same Counterpoint grid labels — so a dimension renamed in Counterpoint changes both.

Parent: Add/Update NCR Counterpoint Product Option TO iPaaS.com.

Source: DIM_UPR · Destination: Value

This is a required field — iPaaS.com rejects the option value without it. One of the values the parent option can take — Blue, or Large — as recorded against the grid dimension in NCR Counterpoint.

Counterpoint holds these values in upper case, and they transfer unchanged, so they arrive upper case in iPaaS.com. Subscribers whose storefront displays them directly should expect that and handle any presentation casing downstream rather than by editing this mapping, because the same upper-case values are what the Options mapping on Add NCR Counterpoint Product Variant TO iPaaS.com records against each variant. Changing the casing here alone would leave a variant's option value no longer matching the option value defined for the product.

The same value must not appear twice within one option, which Counterpoint's grid structure naturally satisfies.

Source: DIM_SEQ_NO · Destination: Order

This is an optional field. The position this value occupies within its option, taken from the sequence recorded against the grid dimension value in NCR Counterpoint.

Mapping it keeps values presenting in the subscriber's intended order — Small, Medium, Large rather than alphabetically — which matters most for sizes, where alphabetical order is actively misleading. Values transferred without an order are still accepted by iPaaS.com; only their presentation order is left undefined.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Mapping Filter

Filter Description.

A substitute relationship is transferred only where the substitute product has already been transferred into iPaaS.com. The filter takes the Counterpoint substitute item number, looks for a matching product in iPaaS.com, and passes the record only if one is found.

This is what makes the collection safe to enable rather than a source of failures. iPaaS.com requires the related product to be one that already exists, and the filter enforces that up front: a substitute item the subscriber has not yet transferred is skipped silently rather than rejected. The relationship is simply not created, and the parent product transfers normally.

Source: GetSpaceportId(SUBST_ITEM_NO, "Product", SpaceportSystemId) · Destination: RelatedId

This is a required field — iPaaS.com rejects the relationship without it, and the value must identify a product that already exists in iPaaS.com. Records which product is the substitute. The formula takes the Counterpoint substitute item number and looks up the matching product in iPaaS.com.

This is the same lookup the collection's filter performs, which is what keeps the two consistent: by the time this mapping runs, the filter has already established that the substitute exists, so the lookup succeeds. The mapping does not transfer the substitute product as a prerequisite — it only finds one already there.

The relationship is recorded against products rather than variants. Counterpoint holds substitutions at item level, so a grid item's substitute applies to the item as a whole and not to any particular colour or size.

iPaaS.com does not allow the same combination of related product and relationship type to appear twice on one product, which Counterpoint's structure naturally satisfies as an item lists a given substitute once.

Source: Static value —Replacement` · Destination: RelatedType

This is a required field — iPaaS.com rejects the relationship without it. Allowed values: Replacement, Similar Item, and Related Product. Records what kind of relationship this is.

Every record from this collection is marked Replacement, which is the value that matches what NCR Counterpoint means by a substitute item: something to sell in place of the original when the original is unavailable. This is a genuine constant rather than a value awaiting configuration, and it correctly describes every record this collection produces.

Subscribers or their MiSP whose storefront distinguishes between a true replacement and a merely similar or complementary product should be aware that Counterpoint's substitute list does not carry that distinction, so this collection cannot infer it — every substitute arrives as a Replacement. Where a finer distinction is wanted, it has to come from somewhere other than the Counterpoint substitute list. Any replacement for this static value must remain one of the three allowed values; a custom relationship type causes the transfer to fail.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Source:

Destination: Barcode

This is an optional field. Finds a single barcode to record against this variant. The formula searches the subscriber's Counterpoint barcode records for one belonging to the parent item that is registered against the stocking unit, carries the barcode type UPC, and matches this variant's exact grid dimensions. If such a barcode exists it is used; if none does, the variant transfers with no barcode and the transfer still succeeds.

The match on grid dimensions is what separates this from the parent product's barcode: this mapping wants the barcode for this particular colour and size, where the parent wants the one that identifies the item as a whole. Barcodes of any type other than UPC, and barcodes registered against an alternate unit, are not considered.

This is a single convenience value rather than the variant's full barcode list. Add/Update NCR Counterpoint Product Variant Barcode TO iPaaS.com carries every grid-specific barcode as its own record, and is the mapping to rely on where a variant genuinely has more than one.

Source: CoalesceToDecimal(Parent.REG_PRC,Parent.PRC_1) · Destination: DefaultPrice

This is an optional field. The variant's standard selling price. The formula reads the parent item's regular price, falling back to the parent's price-1 where no regular price is recorded — the same calculation the parent collection performs for its own DefaultPrice.

This is the item's price, not the variant's price. Every variant of an item therefore arrives at the same price, and any grid-cell price the subscriber holds in Counterpoint is not read. Where variants genuinely differ in price — a larger size costing more, for instance — this mapping does not reflect that, and subscribers or their MiSP should repoint it at the price level their installation uses for grid pricing before relying on variant prices downstream.

Source: CoalesceToDecimal(Parent.PRC_1,Parent.REG_PRC) · Destination: SalePrice

This is an optional field. The variant's current selling price. The formula reads the parent item's price-1, falling back to the parent's regular price where no price-1 is recorded — the reverse of DefaultPrice in this collection.

As with DefaultPrice, this is the item's price and not the variant's. All variants of an item arrive at the same sale price, and grid-cell pricing held in Counterpoint is not read. The same caution applies: subscribers whose variants differ in price should repoint this mapping at the price level their installation uses for grid pricing.

Source: (Parent.ITEM_NO + "|" + DIM_1_UPR + (DIM_2_UPR == "*" ? "" : "|" + DIM_2_UPR) + (DIM_3_UPR == "*" ? "" : "|" + DIM_3_UPR)).TrimEnd() · Destination: Sku

This is a required field — iPaaS.com rejects the variant without it, and it must not match the parent product's SKU. Builds the variant's identifier from the parent item number followed by each of the variant's grid dimensions, separated by a bar.

Counterpoint marks an unused grid dimension with an asterisk, and the formula omits those rather than passing them through, so a variant using one dimension produces a two-part SKU and a variant using all three produces a four-part SKU. Because the parent item number is always followed by at least the first dimension, the result never collides with the parent's own SKU.

This format is not merely cosmetic. Other mappings in this family reconstruct the same string to match records back to variants, so changing the format here breaks those matches — the per-variant barcode custom fields on the unit collections are built this way, and so is the recognition of variant records elsewhere. Subscribers or their MiSP should treat this mapping as structural and leave the format alone unless they are prepared to revisit the collections that depend on it.

Source: Parent.WEIGHT · Destination: Weight

This is an optional field. The variant's weight, read from the parent item's weight in NCR Counterpoint.

This is the item's weight, not the variant's — every variant of an item arrives at the same weight. Where variants genuinely differ in weight, this mapping does not reflect that, and subscribers relying on weight for shipping should confirm the difference is immaterial or repoint the mapping at a source that carries it. As on the parent, iPaaS.com attaches no unit of measure to the number.

Source: BuildC5GridOptions(DIM_1_UPR, DIM_2_UPR, DIM_3_UPR, Parent) · Destination: Options

This is an optional field, though a variant with no options is difficult to tell apart from its siblings, so it should be mapped for any meaningful variant sync. Records which grid values this variant represents — the colour, size, or other dimensions that distinguish it.

The formula produces one option per grid dimension the variant actually uses. For each, it takes the dimension's name from the parent item's grid setup, the value from the variant itself, and an order from the parent's grid entry sequence so the options present in the same order the subscriber sees in Counterpoint. Dimensions marked unused are skipped, and a variant using none at all produces no options.

Where each option's value is required by iPaaS.com, the option name is not, so a grid dimension left unnamed in Counterpoint still produces a usable option. The same option name must not appear twice on a variant, which Counterpoint's grid structure naturally satisfies as each dimension is distinct.

This collection also has a sibling pair — Add/Update NCR Counterpoint Product Option TO iPaaS.com and Add/Update NCR Counterpoint Product Option Value TO iPaaS.com — which carry the product's option definitions and their possible values. Those describe what options exist on the product; this mapping records which of those values a given variant carries.

Parent: Add NCR Counterpoint Product Variant TO iPaaS.com.

Mapping Filter

Filter Description.

Only barcodes that are tied to a specific grid dimension are transferred. NCR Counterpoint marks an unused grid dimension with an asterisk, and this filter passes a barcode only where its first grid dimension carries something other than that marker — that is, where the barcode identifies one particular colour or size rather than the item as a whole.

Barcodes that are not grid-specific are excluded here and carried instead by Add/Update NCR Counterpoint Product Barcode TO iPaaS.com, whose filter is the exact inverse of this one. Between the two collections, every barcode on the item is transferred exactly once. Subscribers or their MiSP editing either filter should edit both, or the two will begin to overlap or to leave barcodes behind.

Source:

Destination: Unit

This is an optional field, but where it is supplied iPaaS.com requires it to be a valid unit name for the product — not a unit id, and not a name the product does not have. Reports which of the item's units this variant barcode identifies.

NCR Counterpoint records the unit against a barcode as a number rather than a name, and the formula converts it by reading the matching unit name from the item. Because this collection sits one level deeper than its product-level counterpart — its records belong to a variant, whose own parent is the product — the formula reaches up two levels to find the item that holds the unit names. The conversion is otherwise the same: 0 gives the stocking unit, and 1 through 5 give the corresponding alternate unit. A value of an exclamation mark means no particular unit, and produces an empty value.

Because the endpoint validates the name against the product's units, this mapping depends on the unit collections having transferred successfully — Add NCR Counterpoint Product Stocking Unit TO iPaaS.com and the five alternate unit collections between them supply the names this mapping produces. A barcode naming a unit that did not transfer is rejected. Subscribers or their MiSP should have the unit collections running before enabling this one.

The conversion covers the stocking unit, the five alternate units, and the no-unit marker. A Counterpoint unit value outside that set produces no value at all rather than an empty one, so subscribers whose installation records unit values beyond those should validate this mapping's behavior in a staging environment before relying on it in production.

Source: return await GetSpaceportIdAsync(BARCOD_ID, "Alternate Id Type", SpaceportSystemId); · Destination: AlternateIdTypeId

This is a required field — iPaaS.com rejects the barcode without it, and the value must be an alternate id type that already exists in iPaaS.com. Records what kind of identifier this is. The formula takes the Counterpoint barcode type and looks up the matching alternate id type in iPaaS.com.

This is the mapping in this collection with a hard prerequisite. Because the endpoint requires a valid type, an iPaaS.com alternate id type matching each Counterpoint barcode type in use MUST exist before the first transfer — the formula does not create one. Where no match is found the mapping produces no value and the barcode is rejected. Subscribers or their MiSP should EITHER (a) transfer their Counterpoint barcode types into iPaaS.com before enabling this collection, OR (b) create the matching alternate id types in iPaaS.com by hand — one MUST be done at install time.

This is the same lookup Add/Update NCR Counterpoint Product Barcode TO iPaaS.com performs, so alternate id types prepared for that collection serve this one too. As there, every barcode type in the subscriber's installation is carried, not only UPC.

Source: BARCOD · Destination: AlternateId

This is a required field — iPaaS.com rejects the barcode without it. The barcode itself, as recorded in NCR Counterpoint and carried across unchanged.

iPaaS.com does not allow the same barcode to appear twice, nor the same combination of alternate id type and unit to appear twice on one variant. The second constraint means a variant may carry only one barcode of a given type per unit. The first has a wider reach on grid items than subscribers sometimes expect: where the same barcode has been recorded against two different grid cells of the same item, one of the two is rejected. Where that occurs, the item's barcode setup in Counterpoint is the place to resolve it.

Parent: Add NCR Counterpoint Product Variant TO iPaaS.com.

Source: QTY_ON_HND · Destination: QtyOnHand

This is an optional field. The physical quantity of this variant at this location, as counted in NCR Counterpoint.

This is stock on the shelf for this specific grid cell, including any already committed to orders — which is why it is usually higher than QtyAvailable. It is the right figure for stock-on-hand reporting and the wrong one for deciding what a storefront may sell. It is a point-in-time figure, refreshed on the next transfer of the variant.

Source: QTY_AVAIL · Destination: QtyAvailable

This is an optional field, but it is the figure a storefront normally uses to decide what can be sold, so it should be mapped for any meaningful inventory sync. The quantity of this variant available to sell at this location, as NCR Counterpoint calculates it.

Available quantity is generally lower than QtyOnHand, because Counterpoint reduces it by stock already committed to orders. This is a point-in-time figure — sales made after the transfer ran are not reflected until the variant transfers again.

Source: AverageCostFromSettings(Parent.Inventory) · Destination: Cost

This is an optional field. The cost of this variant, taken from NCR Counterpoint's rolling average cost.

This mapping does not behave the way the collection's other three do, and the difference is worth understanding before relying on the value. The other mappings read this variant's own record at this location. This one instead reads the parent item's inventory and returns the average cost at the single stocking location configured for the integration.

Two things follow. The cost is the item's, not the variant's — every variant of an item reports the same figure, and a grid cell whose true cost differs is not reflected. And the cost is that of the configured stocking location, not of the location this inventory record is for — so a variant stocked at several locations reports the same cost at all of them, regardless of what that stock actually cost at each.

Where the parent item holds no inventory record at the configured stocking location, the mapping produces no value and the variant inventory record transfers without a cost. iPaaS.com accepts it either way.

Subscribers or their MiSP who need per-location or per-variant costing should not use this mapping as shipped. The equivalent mapping on Add/Update NCR Counterpoint Product Inventory TO iPaaS.com reads the average cost of the record actually being transferred, and so does vary by location.

Source: return await LocationIdFromNameAsync(LOC_ID); · Destination: LocationId

This is a required field — iPaaS.com rejects the variant inventory record without it, and the value must be a location that already exists in iPaaS.com. Records which location this stock sits at. The formula takes the Counterpoint location id and looks up the matching iPaaS.com location by name.

This is the one mapping in this collection with a hard prerequisite. Because the endpoint requires a valid location, an iPaaS.com location whose name matches the Counterpoint location id MUST exist before the first transfer — the formula does not create one. Where no match is found the mapping produces no value and the variant inventory record is rejected. Subscribers or their MiSP should EITHER (a) transfer their Counterpoint locations into iPaaS.com before enabling this collection, OR (b) create the matching locations in iPaaS.com by hand — one MUST be done at install time.

The match is by name, so an iPaaS.com location renamed after setup stops matching and its inventory begins to fail. This is the same lookup Add/Update NCR Counterpoint Product Inventory TO iPaaS.com performs, so locations prepared for that collection serve this one too.

Parent: Add/Update NCR Counterpoint Product TO iPaaS.com.

Source: Static value —1` · Destination: Conversion

This is a recommended field. iPaaS.com accepts the unit without it, but a unit with no conversion factor cannot be related to the stocking unit, so it should be mapped for any meaningful unit sync. Records how many stocking units make up one of this unit.

The value is fixed at 1, and correctly so: this collection carries the stocking unit itself, and one stocking unit is by definition one stocking unit. This is a genuine constant rather than a value awaiting configuration, and subscribers should leave it alone. Every other unit's conversion is expressed relative to this one — the alternate unit collections each compute theirs as a fraction of the stocking unit.

Source: Parent.STK_UNIT · Destination: Name

This is a required field — iPaaS.com rejects the unit without it. The name of the item's stocking unit in NCR Counterpoint — something like Each, Ft, or Lb — carried across unchanged.

The stocking unit is the unit an item's stock is counted in, and Counterpoint gives every item exactly one. Unlike the alternate unit collections, this one has no filter and so contributes a unit record for every item that reaches it.

The same unit name must not appear twice on one product. Counterpoint does not prevent a subscriber naming an alternate unit the same as the stocking unit on the same item, so where that has happened one of the two is rejected as a duplicate.

Unit names are also the link the barcode collections rely on: Add/Update NCR Counterpoint Product Barcode TO iPaaS.com reports each barcode's unit by name, and iPaaS.com requires that name to be a valid unit for the product. Because most barcodes are registered against the stocking unit, a failure here has a wider reach than a failure on any single alternate unit.

Source: Parent.REG_PRC · Destination: MSRP

This is an optional field. The manufacturer's suggested price for one stocking unit, read from the item's regular price in NCR Counterpoint and carried across unchanged.

No calculation is involved, because a stocking unit needs no conversion — the item's price is already the price of one stocking unit. This is the same regular price the parent collection reads for its own DefaultPrice mapping. Items with no regular price recorded transfer with this field empty.

Source: Parent.PRC_1 · Destination: DefaultPrice

This is an optional field. The standard selling price for one stocking unit, read from the item's price-1 in NCR Counterpoint and carried across unchanged.

Note that this reads price-1, whereas the DefaultPrice mapping on Add/Update NCR Counterpoint Product TO iPaaS.com prefers the item's regular price and falls back to price-1. On an item where the two prices differ, the product's default price and its stocking unit's default price therefore report different figures — the product reports the regular price and the unit reports price-1. Subscribers or their MiSP whose downstream systems read prices from unit records rather than from the product should be aware of that difference, and should confirm which of the two their storefront actually uses.

Unlike the alternate unit collections, this mapping does not fall back to a computed price: an item with no price-1 recorded transfers with this field empty rather than deriving one.

Source: Parent.PRC_1 · Destination: SalePrice

This is an optional field. The current selling price for one stocking unit, read from the item's price-1 in NCR Counterpoint and carried across unchanged.

This mapping reads exactly the same price as DefaultPrice in this collection, so the stocking unit always arrives with its default price and sale price equal, which represents no discount. Where a subscriber wants the unit to carry a discount, the two mappings must read different prices — MSRP already reads the item's regular price, so the pattern the parent collection uses, in which the regular price is the standard price and price-1 the selling price, is the natural one to follow.

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.

These and other runtime behaviors are documented in NCR Counterpoint Known Limitations.