Foodprint · Platform admins
Platform Foodprint (admin view)
Master-admin view of the platform foodprint — every revenue order across the platform, bucketed by country, region, postcode-area community and merchant. Used internally for partnerships, press conversations, and prioritising onboarding effort by region.
Where to find it
Admin sidebar → Commerce → Foodprint. Direct link: /admin/foodprint.
How it differs from the public page
The public page at /foodprint shows the same headline numbers plus country, region and community breakdowns — anonymised. The admin view adds the merchant leaderboard the public page deliberately hides (top 20 producers by kept-local £, each row deep-linking into /admin/merchants/[id]), and goes deeper on communities (top 20 vs the public top 10).
Use the public page for outward-facing comms; use the admin page when you need to know which stalls and parishes are driving impact.
Data freshness
The admin page is force-dynamic — every load reads the live database. The public page is ISR-cached for 10 minutes so we do not hammer the DB on public traffic. If you publish a change you want to see live, refresh the admin page; the public page will catch up within ten minutes.
Methodology
All four foodprint surfaces (customer, merchant, admin, public) call into apps/web/lib/foodprint.ts and use the same FoodprintMetrics shape. If you want to tune the constants — kept-local pence per £, supermarket food-miles baseline, CO₂ saved per £ — they are documented at the top of that file and the numbers ripple through every surface on the next page load.