When integrators, MiSPs, and iPaaS.com staff talk about how data moves through the platform, they use two shared vocabularies: data domains (the families of data the platform manages) and Mapping Collection Types (the specific record types a mapping collection can move). This article defines both so everyone is speaking the same language.
Data Domains
iPaaS.com organizes its canonical data model into domains, each with a parent record type and related child records:
Products: products, variants, inventory, units, options, kits, categories, category sets, alternate IDs, related products, images, and bulk pricing.
Customers: customers, addresses, categories, customer companies, and relationships.
Transactions: transactions and their lines, addresses, taxes, payments, tracking, notes, and discounts, plus payment, gift cards, gift card activity, and shipping methods.
Employees: employees, addresses, timesheets, and timesheet entries.
Locations: locations, addresses, groups, group assignments, and relationships.
Messages: messages.
Mapping Collection Types
Every mapping collection targets exactly one Mapping Collection Type. It determines which fields are available for mapping and how parent/child relationships work. Child Mapping Collection Types (for example, Transaction Line) always belong to a parent collection (Transaction).
Domain | Mapping Collection Types (ID) |
Products | Product (1), Product Unit (2), Product Inventory (3), Product Variant (4), Product Variant Inventory (5), Product Category (6), Product Option (23), Product Option Value (24), Product Variant Option (25), Catalog Category Set (30), Kit (31), Kit Component (32), Alternate ID Type (33), Product Alternate ID (34), Product Variant Alternate ID (35), Product Category Assignment (36), Product Variant Category Assignment (37), Variant Kit (39), Variant Kit Component (40), Product Related Product (41), Variant Related Product (42), Category Set Category Assignment (56), Image (59), Image Assignment (60), Bulk Price (61), Bulk Price Assignment (62) |
Customers | Customer (8), Customer Category (16), Customer Address (17), Customer Company (49), Customer Company Address (50), Company Relationship (51), Customer Relationship (52), Customer Company Category (53), Customer Category Assignment (57), Company Category Assignment (58) |
Transactions | Transaction (9), Transaction Line (10), Transaction Address (11), Transaction Tax (12), Transaction Payment (13), Transaction Tracking Number (14), Transaction Note (15), Shipping Method (21), Payment Method (22), Transaction Discount (29), Transaction Line Discount (47), Gift Card (27), Gift Card Activity (28) |
Employees | Employee (43), Employee Address (44), Timesheet (45), Timesheet Entry (46) |
Locations | Location (7), Location Group (38), Location Address (54), Location Group Location Assignment (55), Location Relationship (63) |
Messages | Message (48) |
Why Mapping Collection Types Matter
Mapping collections: the MCT you choose controls the available source and destination fields and the valid directions.
Supported features: an integration declares which MCTs and directions it supports, which drives what you see in webhooks, manual sync, and mapping creation.
Custom fields: custom fields are defined per module, and the module list corresponds to these record types. See Custom Fields.
Troubleshooting: error log entries and events reference the record type being transferred, so knowing the MCT vocabulary makes logs much easier to read.