Push: Get Matched Product Logistics
get_push_shipping_recommendation[Import List Product]
[What it does] Reads publish-time logistics candidates for each exact Import List product and target-store pair. Product Core computes these candidates from both the product's logistics conditions and the target store's current logistics settings. Results apply only to their exact target and are not a general store shipping-method list, the supplier product's complete shipping catalog, or a supplier freight quote.
[When to use] Use only when actively preparing an exact publish_products_to_stores call, once for every product-store target in that request. Do not call it for standalone or exploratory shipping queries.
[When not to use] Do not use it to browse store or order logistics, publish or edit products, or estimate freight, landed cost, prices, or pricing formulas. For supplier-cost workflows, including requests to build pricing formulas, use list_supplier_product_shipping_methods_and_cost.
[How to use]
import_list_idsanddsers_store_idsexpand into a unique Cartesian product capped at 100 targets; copy IDs exactly fromlist_pre_publish_productsand the store-discovery Tool.If any requested target is missing, malformed, or hits an upstream error, the entire call fails instead of returning partial results.
Handle each result independently by its exact
import_item_idanddsers_store_id. Iflogisticsis non-empty, present only that target's candidates and ask whether the user wants to specify one. Selecting a candidate is optional; never choose for the user unless they already specified the exactservice_idfor that target.If the user chooses a candidate, copy its exact
service_idonly to the matchingpublish_products_to_storesitems[].stores[].shipping_method_idwith the sameimport_item_idanddsers_store_id. Do not reuse a selection for another product-store target or derive it fromcompany_nameor another source.If the user declines, does not choose one, or asks to use the default logistics, omit only that target's
shipping_method_id. An empty logistics array is a successful and complete result for that pair; it does not mean the supplier product itself has no shipping methods or freight quote. Do not search the web, call another Tool or API to replace the result, infer a carrier, or manufacture a shipping method. Continue publishing that target with its default logistics.amountbelongs only to that publish candidate and is not a general supplier freight quote. It is a decimal string in major currency units, not a float. [Side effects] None; read-only and changes no product or store logistics settings. [Confirmation] Not required. [Follow-up] Return to the currentpublish_products_to_storesworkflow; never reuse these results for another target or workflow.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"import_list_ids": "<import_list_ids>",
"dsers_store_ids": "<dsers_store_ids>"
},
"name": "get_push_shipping_recommendation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dsers_store_ids | Yes | One or more dsers_store_id values returned by list_stores. Combined with every import_list_ids value; the unique matrix may contain at most 100 targets. Paste JSON example: ["1999323491106619392"]. | |
| import_list_ids | Yes | One or more import_item_id values returned by list_pre_publish_products or get_pre_publish_product. Combined with every store_ids value; the unique matrix may contain at most 100 targets. Paste JSON example: ["2085934367682592768"]. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Matched publish-logistics candidates for every requested import-item/store target, in request matrix order | |
| toolcall_response_at | Yes | UTC timestamp when the Tool response was returned, formatted as RFC3339. |