Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- fulfillmentGroupsLocationRankingAdd applies one location ranking to multiple listed fulfillment groups, reducing repeated output. This capability is documented in the unstable version.
- The Order Routing Location Rule API remains a beta available by request to Shopify Plus merchants. Deploying a merchant’s own custom app and location rules also requires enrollment in the Partners program.
- Locations are prioritized by ascending rank values. Entry order in the rankings array does not set priority.
- When operations rank the same location in the same group, the later operation replaces its rank. Locations absent from that later operation retain their earlier ranks.
- Locations outside a group and unknown group handles are skipped. Inventory locations that no operation ranks are placed last.
Which merchants and API versions can use it?
Shopify’s November 5, 2026 developer changelog lists shared location rankings across fulfillment groups and links to the unstable Order Routing Location Rule Function API. Unstable is a development version that has not been stabilized; this documentation does not establish that the current stable version has the same fields.
The API documentation still labels it a beta available by request to Shopify Plus merchants. Merchants deploying their own custom apps and location rules must also be enrolled in the Partners program. A Plus subscription alone does not establish that an access request has been approved.
The capability documentation reviewed does not state a stable-release date, a complete country list or a separate price for this feature. Confirm the conditions for your shop, app and chosen version before integration; an omitted price is not a promise of free access.
What problem does a shared ranking solve?
A fulfillment group contains cart items that need to ship together. Returning a separate fulfillmentGroupLocationRankingAdd for each group repeats the same warehouse ranking. The official guide explains that this output grows with the number of groups and can exceed the Function output size limit.
The new fulfillmentGroupsLocationRankingAdd operation takes a fulfillmentGroupHandles list and one rankings list, applying that ranking to every listed group. Its result is equivalent to separate single-group operations, while the common ranking is sent only once.
Share a ranking when the ranking logic actually matches. If particular products or groups need different priorities, preserve those exceptions instead of merging business rules solely to shorten output. Shopify generates group and location handles; read them from the Function input.
How do rank values, skipped entries and omissions work?
The rank field supplies numeric priority, used in ascending order: 0 takes priority over 1. Moving entries within the rankings array does not change their existing rank values, so array position cannot substitute for the ranking field.
A shared ranking can include inventory locations from several groups. Shopify skips locations that do not belong to a particular group, and skips handles that match no fulfillment group in the current cart. A response without an error does not establish that every intended group or location participated.
A group’s inventory locations that no operation ranks go after ranked locations. Check both the actual output and valid input locations that no operation covers; omitting a location should not be mistaken for disabling it.
What survives a later per-group override?
Shopify applies operations in their returned order. If several operations rank the same location in the same fulfillment group, the later rank replaces the earlier value. Locations absent from the later operation keep their existing ranks; that operation does not automatically clear the group’s entire ranking.
Suppose two groups share Warehouse A at rank 0 and Store B at rank 1. If the second group needs the reverse priority, return a single-group operation after the shared operation and explicitly assign Store B rank 0 and Warehouse A rank 1. This is a hypothetical example of override behavior, not real merchant or warehouse data.
If you only change Store B to rank 0, Warehouse A retains its earlier 0, potentially creating a tie. To replace a group’s ranking completely, include all locations to be ranked for that group in the later single-group operation.
Check the actual sales surface before rollout
The official compatibility table lists support by surface. Order Edit in Admin is partially supported only for new items. POS is partially supported only when shipping to a customer. Partial Storefront support is limited to Buy with Prime.
Order Edit in Checkout, Pre-order and Try Before You Buy, and recurring subscription orders are listed as unsupported. Even if an app can return valid rankings, check compatibility for the actual order source; a normal checkout test does not establish support across all surfaces.
What should you validate before integration?
First confirm beta approval, the Plus and Partners conditions, and the API version actually used by the app. Preserve repeatable, isolated test inputs covering several groups with a shared ranking, different inventory locations, an unknown group handle and a group requiring an exception.
Next check output size, rank values, operation order, skipped locations, omissions and final priorities after overrides. Then inspect the effect of other locationRule outputs and the actual sales surface. A Function completing without an error is insufficient reason to expand its use.
Finally, use your authorized test workflow to check subsequent location selection and fulfillment status, retaining the version and results. These are validation recommendations: this article has not deployed a merchant app, called a shop API, handled real orders or established that any shop has migrated successfully.
Sources
Frequently Asked Questions
What is the Function run target?
The documentation reviewed lists cart.fulfillment-groups.location-rankings.generate.run. Also confirm the input and output schema for the selected API version; a shared target name does not establish identical fields across versions.
What happens when several locationRule functions return rankings?
The official guide says Shopify orders Function outputs by locationRule priority, then sorts locations using ranks from the first output. Ties are broken using ranks from the next output. When there are no ties, only the first output is considered.
Can a group handle be saved as permanent business configuration?
The documentation says Shopify generates group and location handles and the Function reads them from its current input. Example values should not replace the current call’s input. If you need persistent business identifiers, design that separately using the relevant API’s documented fields.