Composed salad and cold-dish assembly with delicate fresh produce
SSP's menus span salads, sushi/sashimi-style items and other composed cold dishes that require picking and placing delicate, easily-bruised produce - leaves, tomato slices, soft fruit, garnishes - and arranging them in a presentation-sensitive way. These ingredients are fragile, variable in size and shape, and slip or compress unpredictably, so handling them well is a feel-driven task: too much force bruises or shreds, too little drops the item. In SSP this would live in store or commissary prep where consistency and presentation matter for premium positioning. It is hard for a robot because each piece of produce is non-rigid and unique, and acceptable handling is defined by minimal contact damage rather than precise placement. There is no SSP-specific public signal that they intend to automate this with dexterous robots - it is inferred from their menu mix. We identified this through our own research; we have not confirmed the specifics with the customer directly. This page is our researched read — a starting point for that conversation.
What the task is
RESEARCHED · our reconstructionSSP's menus span salads, sushi/sashimi-style items and other composed cold dishes that require picking and placing delicate, easily-bruised produce - leaves, tomato slices, soft fruit, garnishes - and arranging them in a presentation-sensitive way. These ingredients are fragile, variable in size and shape, and slip or compress unpredictably, so handling them well is a feel-driven task: too much force bruises or shreds, too little drops the item. In SSP this would live in store or commissary prep where consistency and presentation matter for premium positioning. It is hard for a robot because each piece of produce is non-rigid and unique, and acceptable handling is defined by minimal contact damage rather than precise placement. There is no SSP-specific public signal that they intend to automate this with dexterous robots - it is inferred from their menu mix.
Is this the actual task and sequence? What are the real tolerances, cycle rate, and reject criteria, and which steps are today's manual bottleneck? Answering these is what turns this from a researched signal into a validated use case.