Integrations and connections
Check the connection, not just the logo.
A useful integration has a clear direction, setup and owner. Review the exact work a connection needs to perform before relying on it during service.
See it with your restaurant in mindStripe: online payments through the restaurant’s account.
Account onboarding, enabled locations and checkout verification are part of payment readiness. Test the payment and refund journey with the configured methods. An integration in the product does not mean every restaurant account or wallet is already enabled.
Coexistence does not mean synchronisation.
Just Eat, Deliveroo and Uber Eats can be discussed as separate sales channels where available. GastroGrowth does not currently promise native order integrations for those marketplaces, a supplied courier network or universal POS compatibility.
Bring a workflow, and we can assess the fit.
Useful connection questions are specific.
Which system is the source?
Identify where menu, customer and order information originates and who is responsible for keeping it accurate.
What must move?
List the actual data and actions required. A menu import and an order connection are different jobs.
How will we test it?
Include a successful order, a change, a failure and recovery. Confirm the support boundary before launch.