This guide provides an operating framework, not legal, financial, safety, medical, licensing, or regulatory advice. Adapt it to your business and local requirements.
Define the system of record
For customers, menu, prices, employees, orders, payments, inventory, and financial categories, state which system owns the data and where changes should begin.
Trace timing and failure behavior
Ask whether updates are immediate or batched, what retries automatically, how duplicates are prevented, and who is alerted when synchronization stops.
Clarify support boundaries
Determine which vendor owns first response, what evidence each side requires, and how issues are escalated. “Supported integration” does not always mean one team accepts end-to-end responsibility.
Review access and security
Use individual accounts, minimum permissions, multi-factor authentication, and a process for removing former staff or vendors. Avoid sharing owner-level credentials to complete routine setup.
Plan for disconnection
Document how to pause, replace, or remove the integration and retrieve needed data. Test whether daily operations can continue safely when the connection is unavailable.