slug: shopmonkey provider: Shopmonkey generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology 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: 3 edges: - tag: Customers spec_file: shopmonkey-customers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.85 evidence: 'POST /customer "Create a new customer record"; PUT /customer/{id} "Update customer information"; POST /customer/search-by-email; schemas: Customer, CustomerInput' reason: CRUD, search and contact-detail maintenance over customer master records, with links to their vehicles and orders. This is customer data management within CRM. - tag: Invoices & Payments spec_file: shopmonkey-invoices-payments-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.75 evidence: GET /order_shared/{publicId}/signed_invoice/latest "Get the latest signed invoice"; POST /integration/payment/manual/charge "Record a payment manually"; POST /integration/payment/manual/refund "Create one Manual Refund" reason: Customer invoice issuance/retrieval plus recording of customer payments and refunds against orders — accounts receivable style customer invoicing and cash application. - tag: Employees spec_file: shopmonkey-employees-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: POST /user/{id}/password "Change user password"; PUT /user/{userId}/role "Assign the User Type/role"; GET /user/logged-in "Retrieve currently authenticated user details" reason: Although tagged Employees, the operations manage application user accounts, passwords and role assignment — identity and access management, not HR employee lifecycle. Homograph avoided; some residual chance the vendor treats these records as HR staff data.