Zendrop

Use this to list or search catalog categories. Returns category id, name, parent id, and product count. Pass the returned id as the category_id filter in get_catalog_products to browse products by category. Read-only.

get_catalog_categories

Check the status of an async fulfillment operation. Poll this after calling fulfill_order to track progress. Terminal states are completed and failed.

get_order_fulfillment_operation

Get full details for a single import-list product — Zendrop linking status, store sync status, and variant mappings. Use the import_list_id returned by get_my_products (for imported or in_store items) as the import_list_id. Read-only.

get_my_product

Poll the status of an async product import operation started by `import_my_product`. Returns the current status (pending, processing, completed, failed) and the store product ID once the import completes. Read-only.

get_my_product_import_operation

Returns current inventory levels per variant for a linked product. Requires a plan with inventory_read permission. Read-only.

get_my_product_inventory

List all products for a store — import list entries and store products — filterable by status (imported, in_store, unlinked). Use get_stores to find the store_id. Use the returned import_list_id as import_list_id in get_my_product for imported/in_store items. Read-only.

get_my_products

Retrieve full details of a single order: line items with tracking numbers and fulfillment type (regular Zendrop / print-on-demand / Amazon), partial shipping address (country, city, ZIP), fulfillment status, issue messages, and actual shipping & product costs for fulfilled orders. Look the order up either by its internal order ID (from get_orders) or by the customer-facing order number the customer quotes (e.g. #1004) - no get_orders call is needed first. Read-only.

get_order

Check the status of an async cancellation operation. Poll this after calling cancel_order to track progress. Terminal states are completed and failed

get_order_cancellation_operation

Use this to see order counts by fulfillment status for a store. Requires a store ID; defaults to the last 30 days if no date range is provided. Returns counts for unfulfilled, processing, shipped, delivered, external, and canceled orders, plus an active issues count. Prefer this over `get_orders_performance` for operational questions about order volume or backlogs. Read-only.

get_orders_breakdown

Use this to fetch full details for a single product by ID. Returns name, description, pricing, all images, categories, supplier details (name, country, type), product-level stock, and a per-variant breakdown carrying SKU, size/colour, price, weight and packaging dimensions. The variant breakdown is paginated (default 100 per call, max 200): check `variants_total` and `variants_has_more`, and request further pages with `variants_page` before treating the list as complete. Answer stock questions only from the returned values — never estimate or infer. Weight units are recorded per variant and are not normalised, and dimensions carry no unit at all, so quote both verbatim and never convert, sum, or compare them across variants or products. Prefer this over `get_catalog_products` when a product ID is already known. Read-only.

get_catalog_product

Use this to fetch details and fulfillment settings for a specific store by ID. Returns name, URL, platform, connection status, and settings including auto-fulfillment, daily fulfillment, and tracking page configuration. Prefer this over `get_stores` when the store ID is already known. Read-only.

get_store

Use this to get a financial summary for a store over a date range. Requires a store ID and a date range. Returns gross revenue, profit, costs, refunds, discounts, units sold, top products, and a daily revenue chart. Optionally filter by country. Prefer this over `get_orders_breakdown` for revenue and business performance questions. Read-only.

get_orders_performance

Returns the shipment tracking history for a given tracking number — all events on record, sorted oldest to newest, plus a direct tracking page URL to share with the merchant. Use when the merchant asks where a shipment is or wants tracking details. Get the tracking number from the tracking_number field on a get_order line item. Returns an empty events array (not an error) if no updates have been received yet. Read-only.

get_tracking_events

Use this to browse currently popular products without a search query. Returns a ranked list with name, pricing, images, supplier details (name, country, type), and live stock status — up to 20 per page. Call `get_catalog_product` for per-variant weight, packaging dimensions, SKU and stock. Read-only.

get_catalog_trending_products

Condensed performance snapshot for a store: fulfilled orders count, gross revenue, gross profit, and units sold. Default window is the last 7 days; any date range is accepted. Returns zeros when no matching orders exist in the period (never an error). Requires a store ID. Prefer this over `get_orders_performance` when you only need the 4 headline metrics without deltas, breakdowns, or top products. Read-only.

get_weekly_performance

Push a product from the import list to the connected store. The operation is asynchronous — use `get_my_product_import_operation` to poll the result. If the product is already importing or imported, the current status is returned without re-dispatching.

import_my_product

Link an unlinked store product to a Zendrop catalog product using a two-step confirmation flow. First call (no confirmation_token) returns a preview and a short-lived token. Second call (with confirmation_token) executes the link. Use get_my_products with status=unlinked to find store_product_id values.

link_my_product

List order issues (fulfillment problems or disputes) for a merchant store. Filter by type, status, date range, or order number. Returns paginated results with AI-refined messages, replies, and file attachments. Issues requiring merchant action are sorted first; inspect the requires_action field in each result. Use get_order_issue for full type-specific details of a single issue.

get_order_issues

Search and filter a merchant's orders. Supports filtering by status, date range, shipping country, keyword and fulfillment issues. Returns a paginated list with basic order info. Use get_order for full details of a specific order. Read-only.

get_orders

Use this to list stores. For regular users, returns only their own connected stores. For admins, returns all active stores across all merchants (paginated). Returns store IDs, names, URLs, platforms, and connection statuses. Use this first to discover store IDs before calling store-specific or order tools. Read-only.

get_stores

Get full details for a single order issue. Call after get_order_issues to drill into a specific result. Pass the `id` field from get_order_issues as issue_id — not the supplier's `issue_id` field, which is a different identifier. Returns all standard issue fields plus type-specific context (address, affected SKUs, missing item map, return tracking) when the issue type populates them; these fields are null otherwise.

get_order_issue

Use this to search or browse products when no product ID is known. Supports keyword, category, price, supplier, and ships-from country filters with pagination (up to 60 per page). Returns matching products with name, pricing, images, supplier details (name, country, type), and live stock status. Use `ships_from: "US"` when the merchant asks for US suppliers or faster US delivery. Call `get_catalog_product` for per-variant stock, weight, packaging dimensions and SKU. Prefer `get_catalog_product` when a product ID is already available. Read-only.

get_catalog_products

Update the shipping address for an unfulfilled order. Call with confirmed=false to preview which fields will be updated. Call again with confirmed=true within 5 minutes to apply the update.

update_order_address

Update fulfillment mode and tracking settings for a store (two-step). First call without confirmation_token returns a preview of proposed changes. Pass the returned confirmation_token in the second call to apply the update. Requires stores:write scope.

update_store_settings