A tiffin service is a relationship built over many deliveries. Give customers supported self-service choices and keep your kitchen working from the resulting schedule.
Inside PlateOS: a customer meal-plan portal. Available actions depend on store settings.
HOW IT WORKS
From the request to the work behind it.
01
Make room for everyday changes
Set up your plans, meal items and delivery patterns. Customers can use the portal actions you enable, while staff handle exceptions and custom packages. Keep veg and non-veg choices, portions and one-day changes explicit in the plan and item data.
Meal plans and aliases
Customer change history
Store-specific portal controls
02
Carry the detail into preparation
Review date-specific prep counts, customer rows and packing labels before dispatch. Use delivery zones and routes to organise the handoff. OpSy and the shared inbox help your support team respond using the customer's context, with human takeover when needed.
Daily item and plan breakdowns
Delivery instructions and labels
Customer conversation context
BEFORE YOU START
A few useful answers.
Can customers skip a delivery?
Yes, where you enable the supported portal action. Your configured cutoff and eligibility rules still apply.