slug: parcellab
provider: parcelLab
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: 4
edges:
- tag: Promise
  spec_file: parcellab-promise-api-openapi.yml
  capability_id: BC-2510.30
  capability_id_l1: BC-2510
  capability_name: ETA Prediction Management
  confidence: 0.85
  evidence: GET /v4/promise/prediction/predict/  predictDelivery  Predict Delivery Date; schema PromisePrediction
  reason: Operation computes a predicted delivery date, which is exactly ETA Prediction Management.
- tag: Surveys
  spec_file: parcellab-surveys-api-openapi.yml
  capability_id: BC-430.50
  capability_id_l1: BC-430
  capability_name: Customer Feedback Management
  confidence: 0.85
  evidence: POST /v4/survey/survey/{id}/answer/  submitSurveyAnswer; GET getSurveyAnswer
  reason: Publishing surveys to customers and collecting answers is voice-of-customer/feedback collection.
- tag: Events
  spec_file: parcellab-events-api-openapi.yml
  capability_id: BC-2510.10
  capability_id_l1: BC-2510
  capability_name: Event Capture and Status Management
  confidence: 0.7
  evidence: POST /v4/track/events/  sendShopEvent  Send Shop or Warehouse Event; schema ShopEvent
  reason: Single operation ingests shop/warehouse events into the post-purchase tracking platform, i.e.
    event capture feeding shipment status resolution. Mapped to Event Capture and Status Management; moderate
    confidence as the event payload is generic.
- tag: Orders
  spec_file: parcellab-orders-api-openapi.yml
  capability_id: BC-2510.20
  capability_id_l1: BC-2510
  capability_name: Shipment Tracking Management
  confidence: 0.7
  evidence: PUT /v4/track/orders/ upsertOrder; GET /v4/track/orders/info/ getOrderInfo 'Get Order Status';
    schemas Tracking, Checkpoint
  reason: Orders are pushed under the /track/ namespace with Tracking and Checkpoint schemas and a 'Get
    Order Status' read, so the surface serves shipment/order status resolution for tracking pages rather
    than order capture or fulfilment orchestration.