Restaurant orders turned into optimized delivery routes

Problem

Orders landed in the point-of-sale system, and routes were planned somewhere else. Someone had to move the details across by hand, which is slow at lunchtime and wrong often enough to matter.

Approach

We built the pipeline between the two: orders leave Toast over secure webhooks and arrive in Routific as delivery stops. The writes are idempotent, so a retried webhook or a duplicated event never creates a second stop, and jobs retry safely when a service is briefly unavailable.

Outcome

Dispatch works from routes that are already correct, and nobody re-types an address between two systems that were never meant to talk.

Stack

• TypeScript service with secure webhook endpoints
• Toast point-of-sale and Routific route optimization
• Idempotent upserts and retry-safe job handling