These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Recipe Management System
- Integrations
Integrations
Agree how payment and fulfillment evidence reaches the kitchen record.
- Recipe Management System
- Payment provider
- Fulfillment source
- Identity
- Files
Systems to connect
- Payment provider. Bring provider issued authorization, capture, refund and void events with the provider event ID, reference, amount and occurrence time.
- Fulfillment source. Bring allocation, picking, shipping, delivery and return events with their external event ID, menu item, quantity and order reference.
- Identity. Link team members to the correct platform user and organization before assigning orders or review decisions.
- Files. Attach supporting service and decision evidence to the related order with the intended visibility.
How connections are governed
Decide which system is authoritative for a provider event or fulfillment acknowledgment. Reconcile incoming IDs, quantities and revisions with the local order before changing a guarded operation result. A repeated external event should resolve to its earlier evidence record. Review attachment visibility and the people permitted to investigate exceptions. Use implementation to stage these connections alongside the first service rehearsal.
Set up Recipe Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.