slug: aftership
provider: AfterShip
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: Estimated delivery date
  spec_file: aftership-estimated-delivery-date-api-openapi.yml
  capability_id: BC-2510.30
  capability_id_l1: BC-2510
  capability_name: ETA Prediction Management
  confidence: 0.95
  evidence: POST /estimated-delivery-date/predict  predict  Prediction for the Estimated Delivery Date
  reason: Operations do exactly ETA prediction — single and batch prediction of estimated delivery date,
    with Estimated_delivery_date_Request/Response schemas. No other reading fits.
- tag: Tracking
  spec_file: aftership-tracking-api-openapi.yml
  capability_id: BC-2510.20
  capability_id_l1: BC-2510
  capability_name: Shipment Tracking Management
  confidence: 0.92
  evidence: 'GET /trackings  get-trackings  Get trackings; POST /trackings/{id}/retrack  Retrack an expired
    tracking by ID; schemas: Tracking, Checkpoint'
  reason: Operations create and resolve shipment tracking records with carrier checkpoints, which is squarely
    shipment tracking/visibility for the vendor's post-purchase tracking product.
- tag: Labels
  spec_file: aftership-labels-api-openapi.yml
  capability_id: BC-520.50
  capability_id_l1: BC-520
  capability_name: Logistics Operations Management
  confidence: 0.8
  evidence: POST /labels post-labels 'Create a label'; schemas Label.v3, Parcel.v3, Customs.v3, Shipment.v3,
    Rate.v3
  reason: Shipping-label creation with parcel, customs and shipment payloads is carrier/transport execution
    — logistics operations.
  recovered_from: vertical-retail-consumer-goods-edges.json
- tag: Fulfillments
  spec_file: aftership-fulfillments-api-openapi.yml
  capability_id: BC-520.40
  capability_id_l1: BC-520
  capability_name: Order Fulfilment Management
  confidence: 0.75
  evidence: POST /fulfillments  create-fulfillment  Create a fulfillment; POST /fulfillments/{id}/update-status  Update
    fulfillment status; schemas Fulfillment.v1, Tracking.v1, Pickup_location.v1
  reason: Lifecycle of order fulfilments (create, retrieve, update, status change) with tracking, pickup
    location and weight — order fulfilment orchestration. Slight ambiguity versus outbound/dispatch capabilities
    keeps this below 0.8.
- tag: Manifests
  spec_file: aftership-manifests-api-openapi.yml
  capability_id: BC-520.50
  capability_id_l1: BC-520
  capability_name: Logistics Operations Management
  confidence: 0.75
  evidence: POST /manifests post-manifests 'Create a manifest'; schemas Manifest.v3, Files.v3
  reason: Carrier manifest creation (end-of-day handover document for shipments) is transport execution
    within logistics operations.
  recovered_from: vertical-retail-consumer-goods-edges.json
- tag: Pickups
  spec_file: aftership-pickups-api-openapi.yml
  capability_id: BC-520.50
  capability_id_l1: BC-520
  capability_name: Logistics Operations Management
  confidence: 0.75
  evidence: 'POST /pickups  post-pickups  Create a pickup; schemas: Pickup_parcel.v3, Address.v3, Dimension.v3'
  reason: Scheduling carrier parcel pickups with parcel dimensions and addresses is transport execution
    within logistics operations.
  recovered_from: sweep-20260829T005356Z-edges.json
- tag: Rates
  spec_file: aftership-rates-api-openapi.yml
  capability_id: BC-2520.50
  capability_id_l1: BC-2520
  capability_name: Rating Engine Operations Management
  confidence: 0.75
  evidence: POST /rates post-rates 'Calculate rates'; schemas Rate.v3, Rate_record.v3, Shipment.v3, Parcel.v3,
    Money.v3
  reason: Postmen rate-shopping endpoint that computes shipping charges for a given shipment/parcel across
    carriers. This is operation of a freight rating engine that calculates and validates charges, matching
    BC-2520.50.
- tag: Returns
  spec_file: aftership-returns-api-openapi.yml
  capability_id: BC-2460.50
  capability_id_l1: BC-2460
  capability_name: Returns and Reverse Operations Management
  confidence: 0.72
  evidence: POST /returns/{return_id}/approve 'Approve Return'; POST /returns/{return_id}/receive-items
    'Receive items by Return ID'; schemas Receiving, Restock, Refund, Exchange, Return_method
  reason: Full RMA lifecycle — create, approve, reject, resolve, receive items — with Receiving, Restock,
    Refund and Exchange schemas. This is the receipt, triage and disposition of returned goods, i.e. returns
    and reverse-logistics operations.
- tag: Cancel Labels
  spec_file: aftership-cancel-labels-api-openapi.yml
  capability_id: BC-520.50
  capability_id_l1: BC-520
  capability_name: Logistics Operations Management
  confidence: 0.7
  evidence: POST /cancel-labels  Cancel a label; Get the cancelled labels
  reason: Shipping-label lifecycle (cancellation of carrier labels) is transport/logistics execution within
    the supply chain.
  recovered_from: sweep-20260829T005356Z-edges.json
- tag: Cancel Pickups
  spec_file: aftership-cancel-pickups-api-openapi.yml
  capability_id: BC-520.50
  capability_id_l1: BC-520
  capability_name: Logistics Operations Management
  confidence: 0.7
  evidence: POST /cancel-pickups  Cancel a pickup; Get the cancelled pickups
  reason: Carrier pickup scheduling/cancellation is transport execution — logistics operations.
  recovered_from: sweep-20260829T005356Z-edges.json