slug: just-eat provider: Just Eat generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Transportation & Logistics min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 10 edges: - tag: Order Delivery API spec_file: just-eat-order-delivery-api-api-openapi.yml capability_id: BC-2420.40 capability_id_l1: BC-2420 capability_name: Last-Mile Delivery Operations Management confidence: 0.85 evidence: PUT /orders/{orderId}/deliverystate/driverassigned "Update order with driver assigned details"; .../delivered; .../onitsway; PUT /orders/deliverystate/driverlocation "Update current driver locations (bulk upload)"; GET /delivery/estimate reason: Operations track driver assignment, driver position, arrival at restaurant and at the delivery address, and final delivered state for a food order — final-leg delivery execution with routing and delivery confirmation. - tag: Order Delivery Webhooks spec_file: just-eat-order-delivery-webhooks-api-openapi.yml capability_id: BC-2420.40 capability_id_l1: BC-2420 capability_name: Last-Mile Delivery Operations Management confidence: 0.78 evidence: PUT /driver-assigned-to-delivery; PUT /driver-at-delivery-address; PUT /driver-has-delivered-order "Driver has delivered order"; PUT /order-is-ready-for-pickup reason: Event callbacks report last-mile delivery milestones (driver assigned, en route, at address, delivered) for orders; the substance is last-mile delivery operations even though the mechanism is webhooks. - tag: ConsumerQueries spec_file: just-eat-consumerqueries-api-openapi.yml capability_id: BC-430.20 capability_id_l1: BC-430 capability_name: Complaints & Issue Management confidence: 0.75 evidence: POST /orders/{tenant}/{orderId}/consumerqueries/lateordercompensation/restaurantresponse Update late order compensation request with Restaurant response reason: Captures restaurant responses/resolutions to consumer late-order complaints and compensation requests — complaint capture and resolution. - tag: Delivery Pools API spec_file: just-eat-delivery-pools-api-api-openapi.yml capability_id: BC-520.50 capability_id_l1: BC-520 capability_name: Logistics Operations Management confidence: 0.75 evidence: POST /delivery/pools Create a new delivery pool; PUT /delivery/pools/{deliveryPoolId}/hours Set the delivery pools daily start and end times reason: Configures last-mile delivery pools, their operating hours, pickup availability and assigned restaurants — transport/delivery network operations management. recovered_from: vertical-agriculture-food-production-edges.json - tag: Restaurant Claims spec_file: just-eat-restaurant-claims-api-openapi.yml capability_id: BC-430.20 capability_id_l1: BC-430 capability_name: Complaints & Issue Management confidence: 0.72 evidence: GET /restaurants/{tenant}/{restaurantId}/customerclaims "Get claims"; POST .../customerclaims/{id}/restaurantresponse "Submit a restaurant response for the claim"; schemas OrderClaim, ClaimResolution, Justification reason: Handles customer claims raised against orders, the restaurant's response and justification, and claim resolution — customer complaint capture and resolution workflow, not cargo liability claims. - tag: Attempted Delivery API spec_file: just-eat-attempted-delivery-api-api-openapi.yml capability_id: BC-2420.40 capability_id_l1: BC-2420 capability_name: Last-Mile Delivery Operations Management confidence: 0.7 evidence: POST /{tenant}/orders/{orderId}/queries/attempteddelivery/resolution/redeliverorder Request Redelivery of the Order reason: Handles a failed final-leg delivery attempt and requests redelivery — last-mile delivery execution/exception handling for food orders. Some overlap with visibility exception management. - tag: Consumer Queries Webhooks spec_file: just-eat-consumer-queries-webhooks-api-openapi.yml capability_id: BC-430.20 capability_id_l1: BC-430 capability_name: Complaints & Issue Management confidence: 0.7 evidence: POST /late-order-compensation-query late order compensation query, restaurant response required reason: Pushes consumer late-order and compensation queries to restaurants for response — customer complaint/issue intake and resolution routing. - tag: Consumers spec_file: just-eat-consumers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.7 evidence: POST /consumers/{tenant} Create consumer; GET /consumers/{tenant}/me/communication-preferences reason: Creates and retrieves consumer records and manages their marketing/communication channel subscriptions — customer master data plus consent preferences. Communication-preference operations could also lean to marketing, so not maximal confidence. recovered_from: vertical-agriculture-food-production-edges.json - tag: Order API spec_file: just-eat-order-api-api-openapi.yml capability_id: BC-520.40 capability_id_l1: BC-520 capability_name: Order Fulfilment Management confidence: 0.7 evidence: 'POST /orders Create order (schemas: order-request-v2, fulfilment-v2, payment-v2, items-v2)' reason: Creates a customer food order with items, fulfilment and payment details — order capture and fulfilment orchestration. recovered_from: vertical-agriculture-food-production-edges.json - tag: Order Acceptance API spec_file: just-eat-order-acceptance-api-api-openapi.yml capability_id: BC-520.40 capability_id_l1: BC-520 capability_name: Order Fulfilment Management confidence: 0.7 evidence: PUT /orders/{orderId}/accept "Accept order"; PUT /orders/{orderId}/reject; POST /orders/{orderId}/complete; PUT /orders/{orderId}/duedate "Update order ETA"; POST /orders/{orderId}/readyforcollection reason: Operations drive the order lifecycle at the merchant — accept, reject, cancel, complete, promise a new ETA, mark ready for collection. That is order promising and fulfilment orchestration, not payments or delivery execution.