Overview
Customer records from iPaaS.com can be synchronized into Clover using a manual sync method and an outbound webhook. This mapping supports the synchronization of customer data from iPaaS into Clover via the Customer API.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: The sync is triggered manually or when a customer record is updated in iPaaS.
ID Format: When manually syncing, the correct iPaaS CustomerID must be entered (e.g., Customer John Doe with ID 10001 must be entered as 10001).
Conflicting Mappings: This mapping applies only to Customer records. Ensure no other mappings target the same Clover entity to prevent data from being overwritten.
Supported Child Collections
The integration supports the synchronization of the parent customer and its related child collections:
M2 Customer Address From iPaaS: Maps primary, billing, and shipping addresses.
System Caveats
iPaaS Caveats
Required fields such as FirstName, LastName, and EmailAddress should be valid to ensure clean records in Clover.
The dynamic formula for EmailAddress ensures only a valid or fallback email is sent.
Clover Caveats
Clover requires a valid email format if an email is provided.
BusinessName (Company) is optional but will override Clover’s business name field if supplied.
Address fields may not sync if values are blank or fail validation rules.
Setup Requirements
iPaaS Configuration
CustomerID: Unique identifier in iPaaS.
EmailAddress: Must be valid.
FirstName/LastName: Required fields.
Clover Configuration
CustomerID: Maps to iPaaS Customer ID.
Ensure default billing/shipping address flags are correctly applied.
Authentication & Security
Clover2 MerchantId: Used to access the iPaaS API for fetching data.
Clover2 API Key: Used to access the iPaaS API for fetching data.
Integration Flow
Retrieve Data: iPaaS identifies customer records that need to be synced with Clover.
Prepare Fields: Apply field mappings and dynamic transformations.
Map Customer Data: Map FirstName, LastName, EmailAddress, and BusinessName to Clover.
Map Address Data: Push address fields through the child Address collection.
Sync to Clover: Create new or update existing Clover customer records.
Mappings
Customer (Parent)
Mapping Type | Source Field (iPaaS) | Destination Field (Clover) | Description |
Dynamic Formula |
| Uses the customer’s email if available; otherwise, defaults to guest@customerdomain.com. | |
Field | FirstName | FirstName |
|
Field | LastName | LastName |
|
Field | Company | BusinessName |
|
Clover Customer Address From iPaaS (Child)
Mapping Type | Source Field (iPaaS) | Destination Field (Clover) | Description |
Field | Address1 | Address1 |
|
Field | Address2 | Address2 |
|
Field | Address3 | Address3 |
|
Field | City | City |
|
Field | Region | State |
|
Field | PostalCode | Zip |
|
Dynamic Formula |
| Country | Returns the country code if available; otherwise, defaults to "US". |
Field | PhoneNumber | PhoneNumber |
|
Error Handling
Missing Required Name Fields
FirstName or LastName is empty.
Description: Clover requires name fields for customer creation.
Resolution: Populate missing fields in iPaaS.
Address Field Validation Failure
Address fields contain invalid or unsupported characters.
Description: Clover may ignore or reject certain address structures.
Resolution: Ensure address data is clean and follows expected formats.
Invalid Region/State
Region not recognized by Clover.
Description: Clover accepts only predefined state/region values.
Resolution: Map Region values to a valid state code supported by Clover.
Validation Rules & Testing
Validation Rules
FirstName, LastName, and EmailAddress must contain valid values.
BusinessName must be mapped correctly if provided.
Region/state and country codes must align with Clover's accepted formats.
Address fields cannot exceed Clover’s character limits.
Test Scenarios
New Customer Push: Create a new customer in iPaaS and validate creation in Clover.
Update Customer: Modify email, name, or company in iPaaS, then confirm the updates in Clover.
Address Sync: Validate that address changes from iPaaS reflect correctly in Clover.
Invalid Email Simulation: Set an invalid email in iPaaS and confirm Clover rejects or handles the update correctly.
Additional Notes
The dynamic email formula ensures Clover receives a valid email structure when possible.