Globax Intelligence
Globax 资讯
聚合平台政策、出海运营、海外推广和 AI 工具趋势，把外部资讯沉淀为可执行的选题、指南与工具线索。
5第 5 页继续浏览统一资讯流中的历史内容。
Feed
全部资讯
采集新闻和站内文章统一按最新时间排列。
SH跨境电商采集The `orderCreate` mutation now supports multiple tracking numbers for each fulfillmentWe’ve added a trackingNumbers field to OrderCreateFulfillmentInput , so you can attach multiple tracking numbers to a fulfillment when importing orders. If you use the orderCreate mutation to import orders that ship in more than one package, you no longer need to update the fulfillment after creation to add additional tracking numbers. Instead, you can include all tracking numbers upfront when you create the order. Use the trackingNumbers field to pass an array of tracking number strings, for example: trackingNumbers: ["1Z999AA10123456784", "1Z999AA10123456785"] The trackingCompany value you provide applies to every tracking number in the array. This behavior is consistent with how FulfillmentTrackingInput already works on the fulfillmentCreate mutation. If you provide both the singular trackingNumber and the plural trackingNumbers , the singular value takes precedence. In that case, the value of trackingNumber is used and trackingNumbers is ignored. This ensures that your existing integrations continue to work without any changes. This field is available starting in API version 2026-10 . Learn more orderCreate mutation reference OrderCreateFulfillmentInput Manage fulfillments原文Shopify Changelog2026-08-03SH跨境电商采集Updated Built for Shopify requirements for Fulfillment services appsWe've updated three Built for Shopify requirements for Fulfillment services apps . The updated thresholds better reflect how fulfillment operations run in practice, making Built for Shopify achievable for more high-quality fulfillment apps. No action is required. What changed 5.8.2 Complete fulfillment orders : adjusted the required completion rate for assigned fulfillment orders. 5.8.6 Respond to fulfillment requests : extended the response window and adjusted the required response rate. 5.8.7 Respond to cancellation requests : extended the response window. How these criteria are measured is otherwise unchanged. The requirements page linked above lists the current thresholds. Who's affected Apps in the Fulfillment services category, such as third-party logistics and warehousing apps, that hold or are working toward Built for Shopify status. Apps in other categories aren't affected, and no other Built for Shopify requirements have changed. What to do No action is required. Built for Shopify status is evaluated automatically against these criteria. If your fulfillment app previously fell short of these requirements, you may now qualify. Related docs Build for fulfillment services Built for Shopify overview原文Shopify Changelog2026-08-01SH跨境电商采集Hydrogen developer preview update: July 30, 2026The Hydrogen developer preview adds new capabilities to the toolkit and extends the ways developers can build Shopify storefronts: Vue bindings: Build your storefront in Vue with the same Hydrogen APIs you know from React, through the new @shopify/hydrogen/vue entrypoint. GraphQL TypeScript tooling: Query autocomplete and type checking for both Shopify APIs now ship with the package. Analytics and consent through ShopifyScripts: Storefront analytics and consent management now set up with the rest of your Shopify scripts, including support for Shopify's privacy banner. Shopify Inbox support: Shoppers can chat with your store's AI agent and get handed off to your staff, right from your Hydrogen storefront. Suspense cart reads in React: The cart can stream in after the page renders, so your app shell stays fast and cacheable. To get started, visit the Hydrogen developer preview documentation . For a detailed breakdown of this release, read the full release notes .原文Shopify Changelog2026-07-31SH跨境电商采集New purchaseType and recurringCycleLimit fields in the discounts API for discount UI extensionsYou can now configure purchaseType and recurringCycleLimit for app discounts directly from discount UI extensions using the discounts plugin. Previously, these fields were only accessible through the GraphQL Admin API. App developers building discount UI extensions had no way to let merchants control whether a discount applies to one-time purchases, subscriptions, or both, or how many subscription billing cycles a discount should apply to. The following fields are now available through the discounts plugin: purchaseType : control whether the discount applies to one-time purchases, subscriptions, or both recurringCycleLimit : set the number of billing cycles a subscription discount applies to (such as, a value of 4 applies the discount on the first 4 orders, then stops). A value of 0 means unlimited. These fields work with both DiscountCodeApp and DiscountAutomaticApp discount types, and the values are enforced by purchase type filtering at checkout. No action is required. To start using these fields, update your discount UI extension to include them in your discounts plugin configuration. For more details, see the API documentation for DiscountAutomaticAppInput .原文Shopify Changelog2026-06-17SH跨境电商采集Flow action extensions now support relative paths for endpoint URLsYou can now use relative paths for endpoint URLs in your Flow action extension configuration . The runtime_url , validation_url , config_page_url , and config_page_preview_url properties accept either an absolute HTTPS URL, such as https://example.com/api/flow/actions/place-bid , or a relative path that starts with a single / , such as /api/flow/actions/place-bid . When you use a relative path, Shopify CLI resolves it against your development tunnel URL while shopify app dev is running, and against your app’s application_url after you deploy. This means you no longer need to update your runtime_url each time your development tunnel URL changes, making it easier to point Flow actions at routes hosted by your own app. Use an absolute HTTPS URL when your endpoint is hosted on a different domain or service than your app, or when you want Flow to call the same URL in every environment. Protocol-relative URLs (such as //example.com/api/execute ) aren’t supported, and your app configuration must include an HTTPS application_url before you deploy with relative paths. For more details, see the Flow action configuration reference and Create a Flow action .原文Shopify Changelog2026-06-18SH跨境电商采集Storefront MCP cart tools are being deprecated in favour of UCP Cart MCPWhat's changing The cart tools on the Storefront MCP server are being deprecated in favour of the UCP-conforming Cart MCP tools: get_cart and update_cart on https://{shop}.myshopify.com/api/mcp are deprecated. Cart MCP implements the UCP cart capability ( dev.ucp.shopping.cart , version 2026-04-08 ) and exposes the following tools at the https://{shop-domain}/api/ucp/mcp endpoint: create_cart : Create a new cart with line items and optional buyer context. get_cart : Retrieve the current state of a cart. update_cart : Replace the cart's contents. cancel_cart : Cancel a cart. The deprecated tools will be maintained until August 31, 2026, but all documentation will refer to the Cart MCP tools. What you should do If you're building with the Storefront MCP cart tools: Migrate get_cart and update_cart calls to the Cart MCP tools, and update endpoints to use https://{shop-domain}/api/ucp/mcp . Include a meta object carrying ucp-agent.profile in every request, and a meta["idempotency-key"] (UUID) for cancel_cart . Note that update_cart uses PUT semantics: each request replaces the cart's full state, so send the complete line_items array on every update rather than patching individual fields. Consult the updated request and response schemas for all cart tools and update your app to match. See the documentation for Cart MCP ( https://shopify.dev/docs/agents/carts-and-checkout/cart-mcp ) for more details.原文Shopify Changelog2026-06-24SH跨境电商采集`DraftOrderDiscountNotAppliedWarning.priceRule` removed in GraphQL Admin API 2026-10Starting with GraphQL Admin API version 2026-10 , the deprecated priceRule field on the DraftOrderDiscountNotAppliedWarning object is removed. This is a breaking change for apps that query priceRule on DraftOrderDiscountNotAppliedWarning , which is returned in draft order discount warnings from mutations such as draftOrderCalculate , draftOrderCreate , and draftOrderUpdate . If your app selects priceRule in these responses, you must update those queries before upgrading to 2026-10 . The warning already exposes the relevant discount data directly, so you no longer need the legacy priceRule object. Use the following fields instead: discountTitle — the title of the discount that couldn’t be applied. Use this instead of priceRule { title } . discountCode — the code of the discount that couldn’t be applied. Use this instead of priceRule { discountCodes { nodes { code } } } . Update any query that reads priceRule from this warning to select discountTitle and discountCode instead. Before: ... on DraftOrderDiscountNotAppliedWarning { priceRule { title discountCodes(first: 1) { nodes { code } } } } After: ... on DraftOrderDiscountNotAppliedWarning { discountTitle discountCode } DraftOrderDiscountNotAppliedWarning was the only place where the legacy PriceRule object was reachable from the public GraphQL Admin API. As a result, removing priceRule also removes the PriceRule object and its related types from the public schema in 2026-10 and later. Older supported API versions continue to expose priceRule on DraftOrderDiscountNotAppliedWarning until those versions reach end of life. Learn more about the DraftOrderDiscountNotAppliedWarning object.原文Shopify Changelog2026-06-23SH跨境电商采集Removal of ITEM_NOT_STOCKED_AT_LOCATION errorThe ITEM_NOT_STOCKED_AT_LOCATION error will be removed from InventoryAdjustQuantities , InventoryMoveQuantities , InventorySetOnHandQuantities , and InventorySetQuantitiesUserErrorCode as of API version 2026-10. Following the changes described here , inventory quantities can now be adjusted at any location. As a result, the condition that previously triggered ITEM_NOT_STOCKED_AT_LOCATION can no longer occur, and this error is no longer emitted. This update removes an obsolete error code. If your app currently handles ITEM_NOT_STOCKED_AT_LOCATION , you can safely remove any logic that depends on this specific error.原文Shopify Changelog2026-06-19
站内文章eBay跨境电商全面解析：搜索排名、曝光逻辑、店铺增长策略一次讲透eBay跨境电商全面解析：搜索排名、曝光逻辑、店铺增长策略一次讲透 的 Globax 出海运营摘要。1Globax 编辑部2025-12-12
站内文章Etsy平台深度解析：小众产品如何在全球爆红？从搜索排名到产品设计，一篇读懂EtsyEtsy平台深度解析：小众产品如何在全球爆红？从搜索排名到产品设计，一篇读懂Etsy 的 Globax 出海运营摘要。0Globax 编辑部2025-12-12
站内文章Facebook运营干货：跨境卖家必备的广告、社群与内容三大增长方法Facebook运营干货：跨境卖家必备的广告、社群与内容三大增长方法 的 Globax 出海运营摘要。1Globax 编辑部2025-12-11站内文章LinkedIn运营干货：B2B高质量获客与专业品牌打造的核心方法LinkedIn运营干货：B2B高质量获客与专业品牌打造的核心方法 的 Globax 出海运营摘要。1Globax 编辑部2025-12-11站内文章Amazon运营干货：选品、流量与转化三大核心，跨境卖家必看的实战指南Amazon运营干货：选品、流量与转化三大核心，跨境卖家必看的实战指南 的 Globax 出海运营摘要。282Globax 编辑部2025-12-11站内文章Shopee跨境电商：从0到1的系统化运营干货（最新实战指南）Shopee跨境电商：从0到1的系统化运营干货（最新实战指南） 的 Globax 出海运营摘要。0Globax 编辑部2025-12-11站内文章Google推广干货：跨境卖家必懂的流量获取与转化技巧Google推广干货：跨境卖家必懂的流量获取与转化技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章Instagram运营干货：跨境卖家的曝光、涨粉与转化技巧Instagram运营干货：跨境卖家的曝光、涨粉与转化技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章TikTok运营干货：跨境卖家快速起号与上热门技巧TikTok运营干货：跨境卖家快速起号与上热门技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章Twitter（X）实战干货：低成本获取精准流量的运营技巧Twitter（X）实战干货：低成本获取精准流量的运营技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章跨境电商运营干货：高效管理多账号与自动化操作技巧跨境电商运营干货：高效管理多账号与自动化操作技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-09站内文章海外社媒引流干货：跨境电商账号曝光与互动提升技巧海外社媒引流干货：跨境电商账号曝光与互动提升技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-09
站内文章eBay跨境电商全面解析：搜索排名、曝光逻辑、店铺增长策略一次讲透eBay跨境电商全面解析：搜索排名、曝光逻辑、店铺增长策略一次讲透 的 Globax 出海运营摘要。1Globax 编辑部2025-12-12站内文章Etsy平台深度解析：小众产品如何在全球爆红？从搜索排名到产品设计，一篇读懂EtsyEtsy平台深度解析：小众产品如何在全球爆红？从搜索排名到产品设计，一篇读懂Etsy 的 Globax 出海运营摘要。0Globax 编辑部2025-12-12站内文章Facebook运营干货：跨境卖家必备的广告、社群与内容三大增长方法Facebook运营干货：跨境卖家必备的广告、社群与内容三大增长方法 的 Globax 出海运营摘要。1Globax 编辑部2025-12-11站内文章LinkedIn运营干货：B2B高质量获客与专业品牌打造的核心方法LinkedIn运营干货：B2B高质量获客与专业品牌打造的核心方法 的 Globax 出海运营摘要。1Globax 编辑部2025-12-11站内文章Amazon运营干货：选品、流量与转化三大核心，跨境卖家必看的实战指南Amazon运营干货：选品、流量与转化三大核心，跨境卖家必看的实战指南 的 Globax 出海运营摘要。282Globax 编辑部2025-12-11站内文章Shopee跨境电商：从0到1的系统化运营干货（最新实战指南）Shopee跨境电商：从0到1的系统化运营干货（最新实战指南） 的 Globax 出海运营摘要。0Globax 编辑部2025-12-11站内文章Google推广干货：跨境卖家必懂的流量获取与转化技巧Google推广干货：跨境卖家必懂的流量获取与转化技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章Instagram运营干货：跨境卖家的曝光、涨粉与转化技巧Instagram运营干货：跨境卖家的曝光、涨粉与转化技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章TikTok运营干货：跨境卖家快速起号与上热门技巧TikTok运营干货：跨境卖家快速起号与上热门技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章Twitter（X）实战干货：低成本获取精准流量的运营技巧Twitter（X）实战干货：低成本获取精准流量的运营技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-10站内文章跨境电商运营干货：高效管理多账号与自动化操作技巧跨境电商运营干货：高效管理多账号与自动化操作技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-09站内文章海外社媒引流干货：跨境电商账号曝光与互动提升技巧海外社媒引流干货：跨境电商账号曝光与互动提升技巧 的 Globax 出海运营摘要。0Globax 编辑部2025-12-09