Understanding unit-level imports
Understand the benefits and setup requirements of importing unit-level restaurant data into Salesforce.

Updated over a week ago
With the Spring 2024 managed package 2.0 release, Restaurantology introduced functionality allowing Admins to batch import verified restaurant units tied to previously matched multi-unit Concepts. These units are created as child Accounts linked to their parent or sub-parent records, streamlining store-level data import into Salesforce without requiring spreadsheets, file prep, or manual cleanup.
Why this matters
Unit-level data enhances visibility and workflow for multiple teams:
- BDRs/AEs: Enables reps to add Contacts and log activity at the store level, and align outreach with time zone differences.
- Customer Success: Helps Implementation, Support, and CSM teams track usage or case activity at the unit level instead of tagging the parent Account.
- Finance: Connects Subscriptions to specific ZIP codes for improved NEXUS billing and unit-based reporting as store footprints evolve.
Context: Before unit import
Prior to this release, customers could only access unit-level insights using the Chrome extension. These details were visible but not exportable, and could only be reviewed on a case-by-case basis.
With the introduction of Restaurantology Business+ features, customers can now:
- Download all units associated with a specific Concept.
- Refresh unit data monthly to capture new store openings.
Getting started with Unit imports
Before downloading large volumes of records, we recommend reviewing the Unit import: Setup and permissions article. This ensures that your permissions, page layouts, and data mappings are properly configured before importing.