platform-listing

---
name: platform-listing
description: Turns your current Deliveroo, Uber Eats and Just Eat listings, your food hygiene rating and your dish photographs and descriptions into a listing built from what each platform actually publishes about being seen and being picked: the food hygiene rating position stated correctly for where you trade, a photo audit run against each platform's own published photo rules, a menu description and claims review that survives a substantiation and availability check, a ranking factor checklist read from each platform's own performance pages, and a dated action sheet. Use when you are choosing photos, rewriting dish descriptions, deciding whether to fix your hygiene rating first, or trying to work out why the listing next door gets picked over yours.
---

# A listing built from what the platforms actually publish about being picked, not from a blog's guess

You give this your current listing on every platform you sell through, your food hygiene rating and the country you trade in, your dish photographs, your menu descriptions and any claim words in them, and the evidence behind those claims. You get back the hygiene rating position written correctly for where you trade, a photo audit checked against each platform's own published rules, a description and claims review, a ranking factor checklist naming only what each platform has published about how it ranks listings, and a dated action sheet. It will not tell you how many extra orders a better photo brings. No published figure exists for a single independent UK listing's own uplift, and the "25 percent more orders" line attributed to Deliveroo in marketing blogs could not be traced to anything Deliveroo itself publishes, so it is not repeated here.

## What it does

1. **Settle the food hygiene rating position for where you actually trade, because the rule is not what most owners assume.** GOV.UK guidance, updated 30 June 2026, states for England that premises display is something a business "can" do, not something it must do, and that online display is something the FSA merely "encourage[s]". The FSA's own 2024 display audit, published 12 June 2025, confirms it: "In England the scheme is voluntary, and businesses are encouraged to display their ratings." Wales and Northern Ireland differ in law: a business in either is "legally required to display your rating in a visible place at or near each customer entrance". Wales adds a second, specific duty: since 28 November 2016, a takeaway with "a takeaway leaflet or menu" showing food, a price and a way to order "without visiting the premises" must carry a bilingual statement directing customers to the ratings website. Whether that reaches an app listing is not spelled out in the announcement, so record it as a question for a Welsh environmental health officer, not a settled yes. Write down the country you trade in, what the law there requires, and your current rating with its date.

2. **Read what the platforms have committed to on hygiene, because it can gate your listing even where the law does not.** On 18 October 2022 the FSA announced a Food Safety Charter with Deliveroo, Uber Eats and Just Eat, under which they committed to "make sure businesses selling food through their platforms are registered with their Local Authority" and that those businesses "meet a minimum standard under the Food Hygiene Rating Scheme (FHRS)". This is a voluntary industry commitment, not a statute, and the FSA's post names no single figure across all three. Read your own platform's current published standard rather than a number from a news article. Deliveroo's own partner terms go further: inside the Marketer section governing paid promotion, "FSA rating (UK only)" is one of five monthly performance metrics, and a rating of "3, PASS (Scotland), Awaiting Inspection, Exempt" places you in the "GREY" band, suspending Marketer access until every metric clears. A hygiene rating problem is not only a hygiene problem on Deliveroo. It is a promotion problem.

3. **Read the ranking mechanics each platform has actually published, and stop there.** Uber Eats' Success Score FAQ names four pillars: "operational excellence", "menu markup", "menu details" (the "percentage of menu items with photos and/or descriptions"), and "ratings". A higher score brings "enhanced visibility opportunities in newly created carousels on the app, recognition with badges highlighting success stores, and discounts on tools to grow on the app, such as Ads credits." Deliveroo's Marketer thresholds work in reverse, penalising rejection rate, wait time and restaurant rating alongside the FSA rating. Neither platform publishes the weighting between inputs. Build the checklist from the named inputs only, and record "not published" against anything a platform has not said, rather than filling the gap from a blog ranking for the search term.

4. **Audit every photo against the platform's own published photo rules, one platform at a time, because the rules differ.** Deliveroo's Help Centre states specifics: JPEG, "Up to 8MB", a menu item image at least "1200 px wide, 675 px high", a hero image at least "1920 x 1080 pixels", and one restriction stated without qualification: "AI-generated images are not permitted on Deliveroo. Please only upload authentic images of the food or products you sell." It lists rejection reasons too: a "cluttered background", a "blurry image", "poor colour saturation", a visible person, "obvious signs of image editing", "poor lighting", or a text overlay. Uber Eats publishes no technical specification at all, only best practice: natural light, an overhead angle for plates, cutting items open to "show what's inside", and shooting food "while it's hot". Its one hard test matters more than any resolution figure: the photo must be "a true representation of the dish", checked through Menu Maker. Run every current photo against the rules that specific platform has published, not the other one's rules.

5. **Check the photo against what is actually served, not what plating once produced for the camera.** Regulation (EU) 1169/2011 Article 7, as it applies in the UK, states food information "shall not be misleading, particularly... as to the characteristics of the food and, in particular, as to its nature, identity, properties, composition... method of manufacture or production", and paragraph 4 extends this "to advertising" and to "the presentation of foods, in particular their shape, appearance or packaging". A listing photo is presentation. If the portion, garnish or container photographed is not what leaves the kitchen today, the photo is what is wrong. Where a recipe or supplier has changed since, that is also the trigger the allergen-on-delivery skill uses to reopen its matrix, so treat a photo refresh and an allergen recheck as one job.

6. **Write the menu itself to the quality clause the platform already holds you to.** Deliveroo's partner terms state it directly: your menu, "including each menu item image and description", "must: Be clear, accurate, complete and error-free." The clause explains why a gap does not stay empty: Deliveroo "may assist you in completing your menu by supplementing the information you provide about your menu items with information, including product images, from our data sources, or by enhancing images including through the use of AI tools." Leave a dish undescribed and you may be handing it to a system that has never tasted it. Write every course, name and description yourself, before the platform does it for you.

7. **Strike or evidence every claim word, the same test the menu leaving the kitchen already has to pass.** CAP Code rule 3.7 sets the duty: "Before distributing or submitting a marketing communication for publication, marketers must hold documentary evidence to prove claims that consumers are likely to regard as objective and that are capable of objective substantiation." "Award winning", "halal certified", "wood fired" and "locally sourced" each need a dated document, exactly as on a printed menu. Rule 3.28 covers the dish that is not there: marketing quoting a price "must disclose if the marketer has any reasonable grounds for believing that it will not be possible to supply the advertised (or an equivalent) product at the advertised price within a reasonable period and in reasonable quantities." A listing is marketing that runs every hour the app is open, so this rule applies every one of them.

8. **Treat a dish you cannot fulfil as a ranking problem, not only a compliance one.** A dish left live when the kitchen cannot make it becomes a rejected order the moment it is chosen, and rejection rate is one of Deliveroo's own Marketer thresholds from step 2. The fix costs nothing: mark it unavailable the moment it runs out, and reinstate it the moment it does not. An owner protecting the look of a full menu by leaving a sold out dish live pays twice, once under CAP 3.28 and once through a metric that can suspend their own promotion.

9. **Hand the audited facts to Codex so nothing gets typed twice.** Every judgement is already made: the country you trade in, your current rating, which claims you can evidence, and which dishes are actually in stock. Run:

   ```
   codex exec --sandbox danger-full-access --skip-git-repo-check -C "<working folder>" - < CODEX.md
   ```

   Claude hands over the hygiene rating facts, the photo audit against each platform's own rules, the descriptions with flagged claims and evidence, the availability status of every dish, and the ranking factor checklist built only from what each platform has published. Codex returns the hygiene position file, the photo and menu review tables, the checklist and a gaps file. Codex writes no dish description and invents no ranking weighting.

10. **Produce the one page listing sheet, dated against today's standing, not the day the listing was built.** One page per platform: the current FHRS rating and the date it was checked, whether display is a legal duty in your country, whether the platform's own minimum standard is met, the count of photos failing that platform's own rules, the count of unresolved claim words, and the dishes live but out of stock. Put the date every fact was checked in the footer. A sheet built once and never reopened is how a rating drops two grades, photos age out and a sold out dish sits live for a fortnight unnoticed, while the platform's own metrics quietly move you down the page.

## Then it checks

1. The hygiene rating position names the country of trading, the current rating and its date, whether premises display is a legal duty there, whether online display is a legal duty there, and whether the platform's own minimum standard is currently met, each traced to a named, dated source.
2. Every photo on every platform has been checked against that specific platform's own published photo rules, and any AI generated or stock image is flagged rather than left unmarked, since at least one platform forbids it outright.
3. Every claim word in every dish description capable of being checked is either backed by a dated evidence document or rewritten to a plain, unfalsifiable description.
4. Every dish currently unable to be fulfilled is marked unavailable on the live listing, not left orderable on the strength of an update that has not happened yet.
5. The ranking factor checklist names, for every factor listed, the platform's own published page or clause it came from, and contains no invented weighting, algorithm description or "how ranking really works" claim.
6. No photo uplift percentage, order conversion figure or "typical" ranking benchmark appears anywhere in the file that was not read, dated and quoted directly from a source actually opened.

Any check fails: name it, redo that step once. Failed twice: say what is wrong and stop.

## Rules
- Public information only.
- Never invent a fact, a number or a quote.
- Anything sent in someone's name says whose name it is.
- Never state a photo uplift percentage, an order conversion rate or a "typical" ranking benchmark for a single independent UK listing. No such figure has been published by any platform for an individual venue, and the one that circulates, a claimed "up to 25 percent more orders" attributed to Deliveroo, could not be traced to anything Deliveroo itself publishes, so it is not written into any file this skill produces. An owner chasing a borrowed figure will judge a genuinely improved listing against a number nobody can stand behind.
- Never state whether hygiene rating display is legally required from memory. Name the country, quote the source, and give the date checked; the position differs between England, Wales and Northern Ireland and the assumption that a 2022 rule made it universal is wrong.
- Never present a platform's published ranking factor as the whole algorithm. A platform names the inputs it chooses to name; none has published the weighting, and a checklist implying otherwise is inventing a fact.
- Never let a listing photograph outlive the recipe, portion or supplier it once showed. Where the packaging-spec or allergen-on-delivery skill has recorded a change behind a dish, the photo review is reopened for that dish at the same time.
- Never leave a dish that cannot currently be made sitting live to protect the look of a full menu. It breaks CAP 3.28 and, on at least one platform, a metric that can suspend your own promotion.
- This output is a working document prepared for the owner to check against their own current listings, and for their environmental health officer on the hygiene rating position and their solicitor on their own signed platform agreement. It applies published platform rules and published law to a draft listing. It is not legal advice, it is not a ranking guarantee and it is not a food hygiene rating verification.

## Built from
- Food Standards Agency and GOV.UK, "Food Hygiene Rating Scheme (FHRS): guidance for businesses", https://www.gov.uk/government/publications/food-hygiene-rating-scheme-fhrs-guidance-for-businesses/food-hygiene-rating-scheme-fhrs-guidance-for-businesses, last updated 30 June 2026, read 23 September 2026: the voluntary England position, the mandatory Wales and Northern Ireland premises position, and the online display wording in step 1.
- Food Standards Agency, "Food Hygiene Rating Scheme Audit of Display and Business Survey: 2024", https://science.food.gov.uk/article/138241-food-hygiene-rating-scheme-audit-of-display-and-business-survey-2024, published 12 June 2025, read 23 September 2026: confirmation that England remains voluntary in step 1.
- Food Standards Agency, "Emily Miles' stakeholder update: Safer takeaways and the power of online platforms", https://food.blog.gov.uk/2022/10/18/emily-miles-stakeholder-update-safer-takeaways-and-the-power-of-online-platforms/, published 18 October 2022, read 23 September 2026: the Aggregators Food Safety Charter commitments in step 2.
- The Caterer, "Renewed call to make 'scores on the doors' mandatory in England", https://www.thecaterer.com/news/food-hygiene-rating-display-england-fsa, published 19 April 2022, read 23 September 2026: confirmation that mandatory display, including online, remained a proposal awaiting ministers in step 1.
- Welsh Government, "Rules requiring takeaways to promote food hygiene ratings on leaflets, come into force", https://www.gov.wales/rules-requiring-takeaways-promote-food-hygiene-ratings-leaflets-come-force-0, dated 28 November 2016, read 23 September 2026: the bilingual statement duty for Welsh takeaway ordering materials in step 1.
- Deliveroo, "Deliveroo Partners Terms and Conditions", https://merchants.deliveroo.com/en-GB/legal/terms, page states last updated 14 January 2021 with later dated sections, read 23 September 2026: the Marketer performance thresholds including the FSA rating band in step 2, and the menu quality and AI enhancement clause in step 6.
- Uber, "Success Score FAQ", Uber Help, https://help.uber.com/merchants-and-restaurants/article/success-score-faq?nodeId=5d51959c-bc59-45d8-a582-03ceff05b38f, no date shown on the page, read 23 September 2026: the four Success Score pillars and the visibility rewards in step 3.
- Deliveroo, "How to upload your own photos in Menu Manager", Help Centre, https://help.deliveroo.com/en/articles/3295699-how-to-upload-your-own-photos-in-menu-manager, page states updated within the last month, read 23 September 2026: the technical photo specification and the AI image ban in step 4.
- Uber Eats, "Restaurant menu photography guidelines", https://merchants.ubereats.com/gb/en/restaurant-submitted-photos/, no date shown on the page, read 23 September 2026: the best practice photo guidance and the "true representation" test in step 4.
- Regulation (EU) No 1169/2011 on the provision of food information to consumers, Article 7, as it applies in the UK, https://www.legislation.gov.uk/eur/2011/1169/article/7, read 23 September 2026: the fair information test applied to listing photographs and presentation in step 5.
- Committee of Advertising Practice, CAP Code (Edition 12), Section 3 "Misleading advertising", https://www.asa.org.uk/type/non_broadcast/code_section/03.html, no publication date shown on the page, read 23 September 2026: rule 3.7 on substantiation in step 7 and rule 3.28 on availability in steps 7 and 8.

# platform-listing

## You are given
The country of trading for one UK hospitality business, its current food hygiene rating and the date that rating was checked, and the owner's statement of whether the business is signed up to each platform's own published minimum hygiene standard. The current listing on each platform the business sells through, with every dish, its course, its price and its description exactly as published. For every dish photograph currently live, the platform it sits on, the image source, and the owner's check of that image against the specific technical and content rules that platform has published. For every claim word or phrase in a description that a reasonable customer could check, the claim type and the evidence document behind it where one exists, named and dated. The current availability status of every dish. The ranking or visibility factors each platform has published about itself, copied by the owner from that platform's own page, with the source named. All judgement calls, including which claims are true, which photographs to use, which dishes are in stock and whether the hygiene rating position is accurate, have already been made by the owner and are supplied to you.

## Produce
Write into a `./platform-listing-output/` folder:

1. `fhrs-position.md` recording, on separate lines and nothing else: the country of trading as supplied; the current FHRS rating and the date it was checked; whether premises display is a legal duty in that country, stated as `legally required` or `not legally required`, with the source named; whether online or app display is a legal duty in that country, stated the same way, with the source named; whether the platform's own minimum standard is currently met for each platform supplied, stated as `met`, `not met` or `not stated`; and a closing line naming every source used. No conclusion is drawn without a named source line above it.
2. `photo-audit.csv` with these columns in this order: `dish_ref`, `platform`, `dish_name_verbatim`, `image_source`, `meets_platform_technical_spec`, `spec_document_checked_against`, `matches_current_recipe`, `last_photographed_date`, `flag`. `dish_ref` is D001 upward. `platform` is exactly one of `deliveroo`, `uber_eats`, `just_eat`, `own_website`. `image_source` is exactly one of `owner photograph`, `platform supplied`, `ai generated`, `stock image`, `not stated`. `meets_platform_technical_spec` and `matches_current_recipe` are `yes`, `no` or `not stated`. `flag` is exactly one of `none`, `ai image on a platform that forbids it`, `stale recipe`, `no document supplied`, and is set to `ai image on a platform that forbids it` wherever `image_source` is `ai generated` and `platform` is `deliveroo`.
3. `menu-listing-review.csv` with columns: `dish_ref`, `platform`, `course`, `dish_name_verbatim`, `description_verbatim`, `price_gbp`, `availability_status`, `last_updated_date`. `availability_status` is exactly one of `in stock`, `out of stock`, `seasonal, currently unavailable`. Any row where `availability_status` is not `in stock` and the dish is still marked live by the owner is listed in `gaps.md`.
4. `claims-substantiation.csv` with columns: `dish_ref`, `platform`, `word_or_phrase_verbatim`, `claim_type`, `evidence_document_supplied`, `evidence_file_name`, `evidence_date`, `substantiated`. `claim_type` is exactly one of `provenance`, `method of production`, `certification`, `award or accolade`, `superlative`, `freshness`, `plain description`. `substantiated` is `yes` or `no`. Rows marked `plain description` need no evidence and are recorded as `substantiated` `yes` automatically.
5. `ranking-factor-checklist.csv` with columns: `platform`, `factor_name_verbatim`, `source_document`, `owner_current_status`, `meets_requirement`, `action_needed`. `meets_requirement` is exactly one of `yes`, `no`, `not stated`. Every row must carry a `source_document` copied from what the owner supplied; a row with no source is moved to `gaps.md` instead of being written here.
6. `gaps.md` a numbered list of: every dish photograph with no supplied technical spec check; every AI generated or stock image on a platform whose own rules were supplied as forbidding it; every dish marked live while its `availability_status` is not `in stock`; every claim word with no evidence document; every ranking factor claimed with no named source document; and any figure the owner supplied without a date.

## Rules
- Codex checks, sorts, counts and records. It never decides whether a claim is true, never chooses a photograph, never sets a dish's availability, and never decides whether the hygiene rating position is accurate. Those were supplied.
- Never estimate a missing fact. A photo with no supplied spec check has `meets_platform_technical_spec` set to `not stated` and a line in `gaps.md`. A claim with no evidence document has `substantiated` set to `no` and a line in `gaps.md`, never `yes` on the strength of the words alone.
- Never write a photo uplift percentage, an order conversion rate, a ranking weighting or any industry benchmark into any file. No such figure is to be recorded, whether or not the owner supplied one; a supplied benchmark figure is instead listed in `gaps.md` as unverified.
- Never carry a hygiene rating, a photo check or an availability status forward from an earlier date. Each file uses only what was supplied for this run; an older figure may be recorded in a separate column for comparison and never used in a conclusion.
- Never mark a ranking factor as met without a named source document behind it, and never invent a ranking factor that was not supplied by the owner from a platform's own published page.
- Use British English, GBP written as `GBP` or the pound sign, and DD Month YYYY dates. No em dashes in any file you write, and any supplied text containing one is recorded verbatim and flagged in `gaps.md`.
- Every dish name, description, claim phrase and source document reference is copied exactly as supplied, including its punctuation and capitalisation.
- Every file ends with this line: this is a working document prepared for the owner to check against their own current listings, and for their environmental health officer on the hygiene rating position and their solicitor on their own signed platform agreement. It applies supplied facts to a draft listing review and is not legal advice, a ranking guarantee or a food hygiene rating verification.

## Return
The absolute path of every file written, the row count of each CSV, the FHRS rating and the legal display position recorded in `fhrs-position.md` stated in full with its sources, the count of photographs flagged `ai image on a platform that forbids it`, the count of dishes marked live while not `in stock`, the count of claim words with `substantiated` set to `no` and the dishes they sit on, the count of ranking factor rows with `meets_requirement` set to `no`, and the `gaps.md` item count.