Custom enrichment mappings allow Admins to automate how Restaurantology data populates Salesforce Account fields, both during new Account creation and as part of ongoing monthly enrichment. These rules ensure consistency, save time, and extend the value of our verified data across your CRM.

Creating custom enrichment mappings

Admins can create and manage enrichment rules inside the Restaurantology App > Setup & Settings > Data Enrichment Settings. These rules apply to Concept- and Company-level records and run during:

• The creation of new Accounts (e.g., during unit import workflows).
• The enrichment of existing Accounts during monthly data syncs.

Each custom mapping is made up of six components:

1. Account field: The target field you wish to populate. Note that some fields (e.g., formulas or shadow fields with exact-match API names) may be restricted.
2. Value or field reference: Choose whether to input a static value or reference a field from the latest RestaurantologyLog (e.g., Target TAM, Tech Detections, Service Type).
3. Mapping mode:
   • No mapping (simple assignment)
   • Exact match
   • Contains
   • Starts with
   • Does not contain
4. Cast as: Specify the data type (String, Integer, Double, or Boolean).
5. Update option:
   • Complete if missing
   • Overwrite existing value

[!NOTE]
Restaurantology also supports enrichment mapping for unit-level records. Learn more in the unit import article →.

Examples of custom rules

1. Static Value → Assign a default Account Owner by inputting the Salesforce User ID.
2. Field Reference → Populate a custom POS Type picklist field when the latest RestaurantologyLog contains “Toast (POS).” Use contains-mode and cast as String.

Testing mappings for collisions and errors

To prevent sync errors, Restaurantology allows you to test enrichment rules before they go live.

1. Go to Data Enrichment Settings > Permissions and Shared Settings.
2. Use the Test Your Settings feature to simulate enrichment logic.
3. Address any errors caused by field validation, workflow automation, or third-party triggers.