Foodics owns
Orders, items, payments, modifiers, taxes, store hours, staff clocks. Anything transactional. Habitu does not write to these, it reads them.
Habitu owns
Guest identity, consent, loyalty state (stamps, points, tier), campaign history, push tokens, attribution tags. Foodics does not see most of this, it sees the guest ID and any applied discount.
The integration
Foodics → Habitu: new orders stream in as they happen, tagged with guest ID when the guest was identified at payment. This drives Pulse, RFM, and campaign triggers.
Habitu → Foodics: applied discounts and stamp rewards push back at checkout so the ticket reflects the correct total. Menu sync runs nightly.