slug: cuboh
provider: Cuboh
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Automotive & Mobility
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: 1
edges:
- tag: Orders
  spec_file: cuboh-orders-api-openapi.yml
  capability_id: BC-520.40
  capability_id_l1: BC-520
  capability_name: Order Fulfilment Management
  confidence: 0.7
  evidence: POST /api/v2/external-integration/order  Order Creation; POST /cuboh-connect-order/{order_id}/accept/  Accept
    Order; POST /cuboh-connect-order/{order_id}/complete/  Complete Order; POST /cuboh-connect-order/{order_id}/cancel/
  reason: Full order lifecycle — creation, acceptance, completion, cancellation, refund — for delivery/pickup
    orders routed to the restaurant POS. That is order capture and fulfilment orchestration; some ambiguity
    because refund/upcharge touch billing.