Field mapping
Map your custom fields to Elastly's canonical schema.
Every business models its catalog differently — especially in ERPs, where custom fields and record types are the norm. Field mapping is where you tell Elastly which of your fields correspond to the canonical product fields it reasons over.
The canonical fields
| Canonical field | Meaning |
|---|---|
sku | The unique identifier for the product. |
name | Human-readable product name. |
cost_cents | Unit cost, in integer cents. |
current_price_cents | Current selling price, in integer cents. |
gtin / mpn / brand | Optional identity and attribution fields. |
How mapping works
Each connector ships default mappings for its standard fields — for NetSuite, itemId → sku, displayName → name, averageCost → cost, and so on. When your account uses custom fields, override the mapping so the right source field lands on each canonical field.
Money is always normalized to integer cents on the way in (a dollars_to_cents transform handles providers that report decimals), because the engine never does floating-point math on money.