“Leak-proof” is not a useful buying conclusion until the test conditions are named. A soup container is a complete pack made from a base, lid, rim interface, food load and delivery carrier. Its performance can change with temperature, fill level, headspace, route vibration, tilt and the time between packing and eating.
Build a test around the actual order
Choose the highest-risk liquid menu item rather than plain water. Include the usual garnish, temperature at fill, target fill line, lid application method and handoff sequence. Photograph the sample before and after the route, and log the time at each stage so the results can be repeated.
Check these points in order
- Rim and lid identity: write down both product codes. A lid that appears to fit can still belong to a different bowl rim.
- Headspace: leave the same clearance that staff will leave during service. An overfilled bowl can make a good closure look poor.
- Closure feel: check the full perimeter, not only the front edge. Note the force required and whether the lid reopens after steam builds.
- Carrier interaction: test the assembled package in the bag, cup holder or stacked order position used by the courier.
- After-route condition: inspect leakage, condensation, softening, lid displacement and customer-opening experience.
Separate base performance from the lid claim
A bowl may be appropriate for a menu trial while a selected lid is not, or vice versa. Treat components separately for food-contact documentation, disposal instructions and product claims. Avoid representing a snap fit as a guaranteed seal unless a product-specific specification and test condition support that wording.
Turn the trial into a purchasing record
Once the sample works, preserve the exact bowl and lid references, drawing revision, fill target and carrier conditions in the approval file. If a supplier changes a component or you add a label, repeat the critical test instead of assuming the earlier result still applies.
See the 500 mL round bowl reference, compare bowl formats, and use the sourcing FAQ when preparing a request.