slug: shop-ware
provider: Shop-Ware
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: 7
edges:
- tag: Customers
  spec_file: shop-ware-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.85
  evidence: POST /api/v1/tenants/{tenant_id}/customers "Create a customer"; PUT "Update a specific customer"
  reason: Full CRUD over customer records in the shop management system — customer master data maintenance.
- tag: Inventory
  spec_file: shop-ware-inventory-api-openapi.yml
  capability_id: BC-530
  capability_id_l1: BC-530
  capability_name: Inventory Management
  confidence: 0.78
  evidence: GET /api/v1/tenants/{tenant_id}/inventories/active_ros_parts_net_value "Get active RO inventory
    net value for parts assigned to active work orders"
  reason: Operations read and update parts inventory records and inventory valuation for a repair shop
    — stock/inventory management. Evidence does not single out a specific sub-capability (stock levels
    vs replenishment vs accuracy), so L1 only.
- tag: Contacts
  spec_file: shop-ware-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.75
  evidence: GET /api/v1/tenants/{tenant_id}/customers/{customer_id}/contacts "Get a list of customer's
    contacts"; POST "Create new contact for customer"
  reason: CRUD over contact records nested under a customer — maintenance of customer master/contact data,
    i.e. Customer Data Management.
- tag: Staff Members
  spec_file: shop-ware-staff-members-api-openapi.yml
  capability_id: BC-300.70
  capability_id_l1: BC-300
  capability_name: HR Operations Management
  confidence: 0.72
  evidence: 'POST /api/v1/tenants/{tenant_id}/staffs "Create a new staff member"; vendor: "staff time
    clocks and pay rates"'
  reason: CRUD over staff member records plus staff notification is employee-record keeping / HR service
    delivery for the shop, i.e. HR Operations rather than any automotive-specific capability.
- tag: Pay Rates
  spec_file: shop-ware-pay-rates-api-openapi.yml
  capability_id: BC-300.30
  capability_id_l1: BC-300
  capability_name: Compensation & Benefits Management
  confidence: 0.7
  evidence: 'POST /api/v1/tenants/{tenant_id}/pay_rates — "Create a new pay rates"; vendor: "staff time
    clocks and pay rates"'
  reason: Vendor description explicitly ties pay rates to staff, so CRUD over pay rates is employee compensation
    administration. Residual risk that these are labour billing rates charged to customers, hence 0.7.
- tag: Shift clocks
  spec_file: shop-ware-shift-clocks-api-openapi.yml
  capability_id: BC-300.70
  capability_id_l1: BC-300
  capability_name: HR Operations Management
  confidence: 0.7
  evidence: GET /api/v1/tenants/{tenant_id}/time_clocks — "Get shift clocks"
  reason: Staff time-clock/shift records, matching the vendor's "staff time clocks" — time and attendance
    data supporting HR/payroll operations. Single read-only operation, so 0.7.
- tag: Staff shift clocks
  spec_file: shop-ware-staff-shift-clocks-api-openapi.yml
  capability_id: BC-300.70
  capability_id_l1: BC-300
  capability_name: HR Operations Management
  confidence: 0.7
  evidence: GET /api/v1/tenants/{tenant_id}/staffs/{staff_id}/time_clocks "Get shift clocks for staff"
  reason: Time-clock / shift records per employee are time-and-attendance data feeding payroll administration,
    which sits under HR Operations Management.