A row is blocked (skipped, shown first in the review with a Blocked tag) when any value does not resolve:

• Missing location_id and no default location for this page. - blank location on the all-locations upload.
• Retail location #N not found for this reseller. - wrong ID, not a retail location, or a location of another kitchen.
• Unreadable fulfillment_date "...". Use YYYY-MM-DD or MM/DD/YYYY. (YYYY/MM/DD and DD-MM-YYYY are also accepted). A blank date uses the page's date.
• No delivery date exists for YYYY-MM-DD. - the date is not a delivery date in your calendar.
• meal_id must be a number / Meal #N not found. / Meal #N does not belong to this reseller.
• portion_size_id must be a number / Portion Size #N is not valid for meal #M (valid: 0, 3, 5). A blank or negative portion means the default portion (0).
• quantity must be a whole number of 0 or more.

Duplicate rows for the same location + date + meal + portion are not errors: they are summed and shown as one line tagged merged with all source line numbers. Blocked rows never stop the good rows from applying, and they are saved with the upload so you can see them later on the upload's detail page.

In the current version, the Meal #N does not belong to this reseller message exists in the code but effectively never fires - your meal catalogue is not tagged to a single kitchen in the underlying data, so a meal ID that exists at all will normally pass this check regardless of which kitchen it's usually associated with.