The unique identifier for the brand (Deliveroo's integration team will provide this).

The unique identifier for the menu for the given "brand" context.

The POS system the merchant actually runs, applied to every site in site_ids - upload sites on different POS systems separately. Name the system behind the site, not yourself: your own name as a stand-in for a POS you cannot see tells us nothing we did not already know, and costs us the one thing this field is for. Leave it out rather than guess.

Optional free text, up to 128 characters rather than bytes; trimmed and NFC-normalised before storage. Over-length and other rejected values are reported rather than refused - see below - so the limit never fails an upload.

Rejecting the value never changes what happens to the menu itself: it is accepted or refused on its own merits, and the reason for the pos_name comes back in the non-fatal warnings array (too_long, empty, control_character, line_separator, zero_width_or_bidi, replacement_character). replacement_character means the request was mis-encoded, so check its encoding rather than the name. control_character, line_separator and zero_width_or_bidi all mean the value carried something invisible or line-breaking, usually from a copy-paste: send it as plain single-line text. On the v3 large-menu upload the same warning appears in details.warnings on GET /v3/brands/{brand_id}/jobs/{job_id}.

Three things we ask of you:

1. Treat it as a dynamic value: send a menu update when a site changes POS system, otherwise the value we hold goes stale.

2. If the name you are reporting is a white-labelled version of your own platform rather than an independent POS system, mark it with the suffix _WL - that exact token, at the end. It tells us the name is a rebadge of your platform rather than an independent POS, which we have no other way to know. We store the value verbatim, suffix included, and it counts toward the 128 characters.

3. Omitting the field leaves the stored value unchanged; an empty string is rejected rather than clearing it. Where two overlapping uploads disagree for the same site, the last write wins.