{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/commerce.order-lookup/",
    "json": "https://www.anchorterminal.com/niches/commerce.order-lookup/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/commerce.order-lookup/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/commerce.order-lookup/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 10 | 9 | 20 | 13 | 7 |\n\n## What counts as done\n\nThe order's line items, status, fulfilment and customer address returned, or the status change written and read back, with the store's policy text quoted where asked.\n\nMeasured, for our own tests: returned in one or two calls.\n\nHow agents ask for it: where is my order; what did order 1042 contain; mark these orders fulfilled; answer this customer's returns question\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Adobe Commerce (Magento) (Adobe Inc.)**: GET /V1/orders/{id} returns items, addresses and status with fields= trimming to what the agent needs, and REST actions write status changes that read back the same way.\n- **commercetools (commercetools GmbH)**: read_orders returns orders with line items and addresses, fields can be filtered per server, and update_orders writes state changes that return the versioned order for readback.\n- **Ecwid by Lightspeed (Ecwid, Inc.)**: Get order returns items, payment and fulfilment status, shipping person and extra fields, trimmed with responseFields, and Update order writes the fulfilment status for a read-back.\n- **Fabric (Commerce Fabric, Inc.)**: The Orders API reads an order by number with ship-to addresses and payments, and update-status and cancel actions write status, with check-cancel-eligibility before a change.\n- **Saleor API + MCP (Saleor Commerce sp. z o.o.)**: run_query returns an order's lines, fulfilments and addresses in one GraphQL call, and fulfilling or cancelling runs through run_high_impact_mutation with Full access, returning the object for readback.\n- **Shopware (shopware AG)**: shopware-entity-search and entity-read return an order with its associations, and shopware-order-state changes order, transaction and delivery state in one call after a dry-run preview.\n- **Snipcart API + MCP (Snipcart inc.)**: get_order returns items, customer, billing and shipping addresses and payment details, and update_order sets status or tracking and returns the updated order.\n- **Spree Commerce (Vendo Connect Inc)**: get_resource reads an order and action tools such as orders_cancel, orders_complete and fulfillments_fulfill write status, each write asking the client to confirm.\n- **Swell (Swell Commerce Corp.)**: get_record fetches an order by number, update_order changes notes, hold and shipping details, and create_shipment records fulfilment, with access set per area.\n- **Vendure (Elevantiq GmbH)**: Admin get_order returns customer, addresses, payments, refunds and fulfilments, and update_order_state and create_fulfillment write status after a confirmation round-trip.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Agentzon (Merit Systems Inc (agentzon.co terms); Merit Systems, Inc. (merit.systems terms))**: GET /api/orders/{id} with the order token returns items, payment status and totals, but no fulfilment or shipping address, and a paid status does not mean shipped. Policies are on /returns.\n- **BigCommerce API + MCP (Commerce.com US, Inc.)**: Management MCP get_orders returns status, totals and line items on request but never shopper names or addresses, which only the REST Orders API holds, so the address takes extra REST calls under a separate API account.\n- **Commerce Layer API + MCP (Commerce Layer, Inc.)**: The Core MCP reads and writes orders with schema discovery and preflight validation, but its tool list is not on the page, so field coverage per tool was not confirmed.\n- **Elastic Path API + MCP (Elastic Path Software Inc.)**: The Composable Commerce MCP queries and manages orders, but it authenticates with a client_credentials pair that has full CRUD on the store, and order field coverage per tool was not read.\n- **Medusa API + MCP (MedusaJS, Inc.)**: read_admin_api fetches any admin order route with full fields, but the MCP is read-only and Cloud-only, so a status change needs the Admin API with its own key.\n- **Shopify API + MCP (Shopify Inc.)**: get_order returns line items, fulfilment and shipping address, but only for orders placed through the agent. The policies tool agents used for returns questions was sunset and replaced with a different response shape.\n- **Square (Block, Inc.)**: Orders are in the API, but an open issue says order line items cannot be retrieved through the MCP connector because array and path parameters are dropped.\n- **Wix Stores and eCommerce API (Wix.com Ltd.)**: The eCommerce Orders API holds orders and order webhooks, reached through CallWixSiteAPI with no read-only mode; order field coverage was not read this run.\n- **WooCommerce API + MCP (WooCommerce, Inc.)**: REST orders hold every field and MCP abilities update status, but an open issue shows order abilities return no customer name, address, country or shipping method.\n\n- not this job: doola MCP (doola): Status tools cover the user's own companies, not commerce orders.\n\n## What stops agents finishing\n\n- agent tools return fewer order fields than the REST API\n- array or path parameters dropped by the MCP wrapper\n- connector OAuth fails for the agent's client\n\n## Around it\n\nBefore: support.ticket-in, chat.user-request. After: support.reply, email.send.\n\n## Where this comes from\n\nWeight 13 of 100 in Commerce \u0026 checkout: 7 of 49 accounts (Square, WooCommerce and commercetools issues, Shopify forum)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/commerce.order-lookup.json, or the MCP tool get_use_case with id commerce.order-lookup. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Look up an order and act on it",
        "url": ""
      }
    ],
    "description": "Look up an order and act on it: 10 companies fully do it, 9 with a limit, 20 carry the tag. Every listing in Commerce \u0026 checkout with the reason and a source.",
    "facts": null,
    "h1": "Look up an order and act on it",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/commerce.order-lookup/",
    "published": "",
    "section": "agents",
    "title": "Look up an order and act on it: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/commerce.order-lookup/"
  },
  "tokens": {
    "markdown": 1650,
    "slim": 380
  },
  "version": 1
}
