Commerce Layer
Commerce Layer provides transactional commerce and analytics APIs for managing orders, inventory, pricing, customers, fulfillment, and related ecommerce operations.
Verdict
Common use cases
- Pull order details during live support chats
- Calculate monthly revenue by market or currency
- Look up SKU stock before quoting lead times
- Create customer records from signup webhooks
- Audit order status across fulfillment stages
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
Setup guide
- 11. Open your Switchy workspace and navigate to Settings → Integrations → Commerce Layer. 2. Click 'Connect Commerce Layer' to start the OAuth flow in a new browser tab. 3. Log in to your Commerce Layer organization and authorize Switchy to read orders, customers, SKUs, and metrics, plus write customer records. 4. After redirect, confirm the connection appears active in Switchy's integration list. 5. Create or open a Project where you want Commerce Layer data. 6. Type '@Commerce Layer list the last 10 orders' and send; if the MCP returns order IDs and statuses, the connection works. 7. To invoke other tools, @mention Commerce Layer and describe the task—'get order abc123', 'create customer for jane@example.com', or 'show revenue metric for last month'.
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.
How Switchy teams use it
Starter prompts
Recent Order Summary
@Commerce Layer list the last 10 orders and show their status, customer email, and total. Format as a table.
Revenue This Month
@Commerce Layer get the order metric for total revenue this month in USD. Include order count and average order value.
Customer Lookup by Email
@Commerce Layer find the customer with email support-case@example.com and return their ID and any external reference.
SKU Availability Check
@Commerce Layer list SKUs containing 'wireless-charger' and show code, name, and inventory level.
Order Detail Deep Dive
@Commerce Layer get order ORD-12345 with line items, shipment status, and customer details. Summarize any issues.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@commercelayer show me all orders placed in the last 7 days with status 'pending' so I can follow up on payment issues
Found 14 pending orders from the past week. The list includes order #CL-8472 (€245.00, placed 2 days ago), #CL-8461 (€89.50, 4 days ago), and 12 others. Each entry shows the order ID, total amount, customer email, and placement timestamp. You can retrieve full details for any order by ID to see line items, shipping address, and payment method.
This example uses LIST_ORDERS with date and status filters. The MCP returns paginated results (default 25 per page), so large result sets require multiple calls. OAuth scope must include read access to orders. Response shape depends on your Commerce Layer market configuration.
@commercelayer create a new customer with email support-test@example.com and external reference 'zendesk-12345' for our support ticket sync
Customer created successfully with ID cust_AbC123XyZ. The record is now live in your Commerce Layer organization with email support-test@example.com and external_reference 'zendesk-12345'. You can retrieve this customer by ID or search by email. Note: duplicate emails are allowed in Commerce Layer unless your org enforces uniqueness via validation rules.
This write operation demonstrates CREATE_CUSTOMER. The external_reference field is useful for linking Commerce Layer records to your CRM or ticketing system. This action is reversible with DELETE_CUSTOMER, but deletion is permanent and cannot be undone. Requires OAuth write scope for customers.
@commercelayer calculate total revenue for orders marked 'placed' in March 2025 across all markets, then break it down by currency
Total placed-order revenue in March 2025: €142,890.00 equivalent across 3 currencies. Breakdown: EUR €98,200.00 (68.7%), USD $38,450.00 (~€35,120.00, 24.6%), GBP £7,890.00 (~€9,570.00, 6.7%). This uses the GET_ORDER_METRIC tool with date and status filters. Currency conversion to EUR uses Commerce Layer's configured exchange rates at order placement time.
This synthesis example pairs the Metrics API with AI reasoning to produce a financial summary. Metrics are computed server-side and respect your org's market/currency setup. Rate limits apply to the Metrics API (check your plan). The AI interprets raw metric output into a narrative breakdown, which is approximate for multi-currency totals.
Use-case deep-dives
When Commerce Layer MCP beats manual dashboard hunting
A 3-person support team fields 20-30 Intercom tickets a day asking "where's my order?" Without this MCP, each agent tabs out to the Commerce Layer dashboard, searches by email, clicks through to the order, then copies the tracking number back into Intercom. With the MCP, the agent asks Switchy "get order for customer@example.com" and the AI calls LIST_CUSTOMERS by email, pulls the most recent order via GET_ORDER with shipment context, and surfaces the tracking link in 4 seconds. The trade-off: if your support flow requires editing orders or issuing refunds, you still need dashboard access—this MCP is read-heavy with only customer-create and customer-delete as write operations. If 80% of your tickets are status checks, this MCP cuts your median handle time in half.
Fast KPI pulls for small e-commerce ops teams
A solo founder running a Shopify-plus-Commerce-Layer store wants Monday morning revenue by market without building a BI stack. The GET_ORDER_METRIC tool lets Switchy answer "total orders last week in EUR market" or "average order value this month, shipped status only" by calling the Metrics API with date and filter parameters. The MCP returns the number in 2 seconds; the founder pastes it into a Notion dashboard or Slack thread. The boundary: if you need cohort analysis, LTV curves, or joins across customer segments, the single-metric-per-call design gets tedious—at that scale, export to a warehouse. But for a team under 10 people tracking 5-8 KPIs weekly, this MCP is faster than logging into Commerce Layer's analytics every Monday.
When LIST_SKUS helps ops catch missing SKUs before launch
A 6-person product team at a DTC brand uploads 40 new SKUs to Commerce Layer before a seasonal drop. The ops lead wants to confirm every SKU from the Google Sheet made it into the live catalog without clicking through 40 dashboard pages. She asks Switchy "list all SKUs with code starting FALL24" and the MCP pages through LIST_SKUS, returning name and ID for each match. She spots 3 missing codes in 90 seconds and flags them for re-upload. The limit: this MCP has no bulk-create or bulk-update tool, so if the sync failed because of a batch-import error, you're back in the dashboard to fix it. If your launch checklist is mostly verification and the occasional one-off customer-create for VIP early access, this MCP saves 15 minutes per launch.
Frequently asked
What does the Commerce Layer MCP let me do in Switchy?
It connects your Commerce Layer catalog and order data to Switchy's AI workspace. You can query customers by email, pull order details, list SKUs for product lookup, and compute order metrics like revenue or conversion rate — all without leaving your chat. It's built for ops teams who need fast answers from their commerce backend.
Which OAuth scopes does Commerce Layer MCP request?
The MCP uses OAuth2 to authenticate with your Commerce Layer organization. You'll grant read access to customers, orders, and SKUs, plus write access to create or delete customer records. The exact scope list depends on your Commerce Layer plan; admin or integration-manager roles typically approve the connection during setup.
Can it update existing orders or change inventory levels?
No. The MCP reads order and SKU data and writes only to the customer resource — creating or deleting records. It won't modify order statuses, adjust stock counts, or trigger fulfillment workflows. For those operations, use Commerce Layer's dashboard or a dedicated automation tool like Zapier.
How is this different from querying Commerce Layer's API directly?
The MCP wraps ten common queries into plain-English prompts, so your team skips writing cURL commands or remembering endpoint paths. You ask "show me orders over $500 this week" and get structured results instantly. It's faster for ad-hoc questions but less flexible than a full API client for custom integrations.
Who on my team should connect the Commerce Layer MCP?
Whoever manages your Commerce Layer organization and can approve OAuth apps — typically your head of ops or technical co-founder. Once connected, any Switchy workspace member can query orders and customers. The delete-customer tool requires explicit confirmation, so accidental deletions are harder even if junior team members have access.