Commerce Layer
Commerce Layer provides transactional commerce and analytics APIs for managing orders, inventory, pricing, customers, fulfillment, and related ecommerce operations.
Integration
- Vendor
- Commerce Layer
- Category
- other
- Auth
- OAUTH2
- Tools
- 10
- Composio slug
commerce_layer
Tools
- Create Customer
Create one Commerce Layer customer from an email and optional external-reference metadata. Use a unique email or reference for automation. This mutation is cleanly undoable with DELETE_CUSTOMER using the returned customer ID.
- Delete Customerdestructive
Permanently delete one Commerce Layer customer by exact ID. This irreversible operation requires explicit confirmation and is intended only for confirmed cleanup or erasure, never bulk deletion. Never infer or enumerate customer IDs; call G
- Get Customer
Retrieve one customer by its Commerce Layer resource ID.
- Get Order
Retrieve one Commerce Layer order by ID, optionally including customer, line-item, shipment, or return context.
- Get Order Metric
Compute one common order KPI over optional date, market, currency, and status filters using the Commerce Layer Metrics API.
- List Customers
Return one page of customers, optionally filtered by an exact email address.
- List Orders
Return one page of orders, newest first by default, for operational review and follow-up by order ID.
- List SKUs
Return one page of catalog SKUs for product discovery and ID lookup.
- List Stock Items
Return one page of stock items with inventory quantities and SKU codes.
- Update Customer
Update selected attributes of one Commerce Layer customer. Only non-null fields supplied by the caller are changed. Inspect the customer first when rollback matters; restoring the captured values reverses this update.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Commerce Layer.
- Authorise through oauth2. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Commerce Layer tools in chat.
What teammates see: by default, memories from Commerce Layer are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.