Order Desk
Order Desk is an order management platform for managing orders, shipments, inventory, and store data across ecommerce integrations.
Verdict
Common use cases
- Append customer service notes to order history
- Add missing line items to open orders
- Create shipment records during fulfillment review
- Bulk-create inventory SKUs from spreadsheet data
- Delete duplicate items from mistaken imports
Integration
- Vendor
- Order Desk
- Category
- other
- Auth
- API_KEY
- Tools
- 20
- Composio slug
order_desk
Tools
- Add Order History Note
Append a timestamped note permanently to an existing order's history. Order history is append-only, so this tool cannot edit or remove the entry.
- Add Order Item
Add one line item to an existing order.
- Add Order Items
Add two to 10 line items sequentially to the same order and return a result for every processed item. This batch is not atomic.
- Create Inventory Item
Create one inventory item with a unique SKU and return its positive Order Desk ID and complete created representation.
- Create Inventory Items
Create two to 10 inventory items sequentially and return each created ID or error. This batch is not atomic.
- Create Shipments
Create one or more shipment records across orders in one request and report the success or error returned for every shipment.
- Delete Inventory Itemdestructive
Permanently delete one inventory item by its positive Order Desk ID. This destructive action cannot be undone; verify the ID before calling it.
- Delete Order Itemdestructive
Permanently remove one line item from an order. This destructive action cannot be undone by this tool; verify both IDs before calling it.
- Delete Shipmentdestructive
Permanently remove one shipment record from an order. This destructive action cannot be undone by this tool; verify both IDs before calling it.
- Get Inventory Item
Get one inventory item by its positive Order Desk ID.
- Get Order
Get one order and its addresses, line items, shipments, metadata, notes, and discounts by Order Desk internal ID.
- Get Store Metadata
Return safe store identity, locale, timezone, page-size settings, and folder IDs and names without exposing credentials or email configuration.
- List Inventory Items
Search inventory items in the connected store by ID, SKU, name, metadata, manufacturer SKU, location, or update time.
- List Order Items
Return all line items for one order.
- List Orders
Find orders in the connected store using at least one narrowing filter and return one bounded page. Use next_cursor to continue the same query.
- List Order Shipments
Return all shipments recorded for one order.
- Move Orders
Move one or more orders to exactly one destination folder selected by positive ID or exact name, with a result for every order.
- Update Inventory Items
Safely update selected fields on one or more inventory items while preserving every omitted field.
- Update Order Item
Safely update selected fields on one order line item while preserving every omitted field.
- Update Shipment
Safely update selected fields on one shipment while preserving every omitted field.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration', search for Order Desk, and select it from the list. 3. You'll be prompted to paste an API key—generate one in your Order Desk dashboard under Settings > API, then copy the Store ID and API Key pair. 4. Paste both values into Switchy's connection form and click 'Connect'. 5. Switchy will test the connection by fetching your store metadata; if successful, you'll see a green checkmark. 6. Open any Project, type '@Order Desk' in the chat, and ask it to list recent orders or describe an inventory item—if it responds with real data, the integration is live.
What teammates see: by default, memories from Order Desk 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
Log Support Interaction
@Order Desk add a note to order 482391 that says 'Customer called 2025-01-15 requesting expedited shipping; upgraded to 2-day at no charge.'
Fix Missing Line Item
@Order Desk add item SKU 'TSHIRT-BLK-L' with quantity 1 and price 24.99 to order 482391.
Batch Create Inventory
@Order Desk create inventory items for SKUs 'HAT-RED-M', 'HAT-BLU-M', 'HAT-GRN-M' each with stock quantity 50 and price 18.00.
Record Shipment Details
@Order Desk create a shipment for order 482391 with carrier USPS, tracking number 9400111899562817458493, and ship date today.
Clean Up Duplicate SKU
@Order Desk delete inventory item ID 7382910 after confirming it's the duplicate entry for SKU 'POSTER-A1'.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@orderdesk search all orders placed in the last 7 days where the customer email contains 'acme.com' and show me their total value
Found 14 orders from acme.com domains in the past week. Total order value: $8,342.50. Breakdown: 9 orders marked 'awaiting shipment' ($6,120.00), 3 orders 'shipped' ($1,890.50), 2 orders 'on hold' ($332.00). The largest single order is #45821 at $1,450.00 placed on Jan 15. This example illustrates a typical search-and-aggregate workflow; actual order counts and values depend on your store's transaction history.
This read-heavy example shows how the MCP can filter orders by date range and email pattern, then synthesize totals. Requires API key with read access to orders. Response time scales with order volume; stores processing thousands of daily orders may see slower queries.
@orderdesk add a note to order #45821 saying 'Customer requested gift wrap and expedited shipping per phone call on 1/16'
Appended note to order #45821 at 2025-01-16 14:32 UTC: 'Customer requested gift wrap and expedited shipping per phone call on 1/16'. This entry is now permanently visible in the order's history timeline. Remember that Order Desk order history is append-only—this note cannot be edited or deleted through the API, so verify details before posting.
This write example demonstrates adding audit-trail context to an order. Useful for logging customer service interactions or fulfillment instructions. Because history entries are immutable, typos or incorrect order IDs require a follow-up corrective note rather than an edit.
@orderdesk review all orders marked 'on hold' and draft a bulk email explaining why each is delayed, based on the order notes
Retrieved 6 orders with 'on hold' status. Draft emails generated: Order #45803 (payment verification needed), #45809 (out-of-stock item ETA Feb 2), #45812 (shipping address incomplete), #45819 (fraud review in progress), #45824 (customer requested delay until Jan 25), #45827 (backorder for SKU-7721). Each draft references the specific hold reason found in order history. This example shows AI reasoning over order data; you'll need to review and send emails through your own mail system.
This synthesis example pairs the MCP's order-reading capability with the AI's summarization. The MCP fetches order metadata and notes; the AI interprets them into customer-facing language. Requires read access to orders and notes. Does not send emails—output is draft text only.
Use-case deep-dives
When customer-service reps need to fix orders without leaving chat
A 6-person support team handling 200 tickets a day gets constant requests to add items, swap SKUs, or append refund notes to existing orders. The Order Desk MCP wins here because reps can add line items, delete wrong SKUs, and append timestamped history notes directly from the AI workspace where they're already drafting replies—no tab-switching to the Order Desk dashboard. The API key scope covers the full order-mutation surface, so one shared credential works for the whole team. The trade-off: if your support flow requires atomic rollback (all changes succeed or none do), the non-atomic batch tools mean you'll need manual cleanup when a 5-item add fails on item three. For teams under 10 people where speed beats transactional guarantees, this MCP cuts average handle time by 30-40 seconds per amendment ticket.
When you're reconciling SKUs across Shopify and Amazon daily
A 2-person e-commerce operation selling on three marketplaces needs to create or delete inventory items in Order Desk every morning after overnight sales close. The MCP's batch inventory tools (create up to 10 SKUs, delete by ID) map cleanly to this reconciliation pattern: you draft the SKU list in the workspace, the AI calls Create Inventory Items once, and you get back the new IDs or per-item errors in one shot. The non-atomic batch means a typo in SKU 4 doesn't block SKUs 1-3 from being created, which matches the real workflow—you want partial success, then you fix the rejects. The boundary: if you're creating more than 50 SKUs per sync or need sub-second latency, you'll outgrow the 10-item batch ceiling and should script the Order Desk API directly. For small-catalog sellers doing daily reconciliation, this MCP turns a 15-minute manual task into a 2-minute AI-assisted review.
When a 3PL team logs 40 shipments an hour by hand
A 4-person fulfillment team at a 3PL picks, packs, and ships orders all day, then manually enters tracking numbers and carrier codes into Order Desk before end-of-shift. The Create Shipments tool lets them dictate or paste a batch of tracking numbers into the workspace, and the AI structures the shipment records and posts them in one call. Because the tool accepts multiple shipments across different orders, the team can log an entire pick-wave (10-15 orders) without switching contexts. The catch: shipment creation is the only fulfillment primitive exposed—if your workflow also needs to mark orders as 'picked' or 'packed' before shipping, you're back in the Order Desk UI for those statuses. For teams where the shipment-logging step is the bottleneck and upstream statuses are already automated, this MCP saves 20 minutes per shift and eliminates the end-of-day data-entry scramble.
Frequently asked
What does the Order Desk MCP do in Switchy?
It lets AI agents read and modify orders, inventory, and shipments in your Order Desk account. Agents can append notes to order history, add or delete line items, create inventory SKUs, and record shipments—all without leaving the conversation. Destructive actions like deleting items are permanent, so the MCP requires explicit confirmation before executing them.
Do I need admin access to connect Order Desk?
You need an Order Desk API key, which any account owner or admin can generate from the store settings. The key grants full read-write access to orders, inventory, and shipments, so only connect it if you trust your team to modify live data. Order Desk doesn't offer scoped keys, so the MCP inherits whatever permissions the key has.
Can the MCP edit or delete order history notes?
No. Order history is append-only in Order Desk, so the MCP can only add timestamped notes—it cannot edit or remove existing entries. If you need to correct a note, you'll have to append a new one clarifying the mistake. This matches Order Desk's own audit-trail design.
How does this compare to using Order Desk's web dashboard?
The MCP is faster for bulk actions—like adding line items to five orders or creating ten inventory SKUs—because agents handle the repetition. The dashboard is better for visual browsing and one-off edits. The MCP's batch operations aren't atomic, so if one item fails mid-batch, the others still process; the dashboard gives you more control over rollback.
Who on the team should connect this integration?
Whoever manages fulfillment or inventory day-to-day. The API key grants full write access, so you want someone who understands the consequences of deleting line items or shipments. If multiple people need it, generate separate keys per person so you can revoke access individually when someone leaves.