Questions, answered

Click Get started, then use Proto to configure Food Truck POS & Route Planner for your business. Pilot one active stop, a small menu and a shift that includes order acceptance, ticket review, preparation, service and exception reconciliation.

Order Taker accepts feasible menu and portion scope for a stop and serving time. Kitchen Lead submits the line ticket, and Shift Supervisor reviews its revision before release.

A recipe has a revision, effective date and approval state. The kitchen works from the approved revision for the released order scope. Review a later change separately.

Ingredients and order lines carry allergen declarations. Check them while accepting the order and before preparation.

The line keeps requested and served portions separately. Review the remaining scope before cancellation or compensation, and record waste separately.

Shift Supervisor records an independent decision on the submitted revision with a reason. Release uses that reviewed revision.

Finance Reviewer verifies the provider’s refund evidence, including its event ID, reference and amount, against the order. A request alone does not confirm the provider result.

Open the operation receipt from the Shift Operations exception queue. Compare its expected revision and linked effects with actual records before resolving it.

Keep each active destination as a route stop under the correct organization. Assign each order an owner and serving time, then review open work by stop.

Review the current pricing and scope imports, integrations and agent activity for the planned shift.