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
- On November 19, the unstable references for Order Routing Location Rule and Fulfillment Constraints both listed cartLine and cost.
- The 2027-01 release candidate and 2026-10 stable references for both APIs omitted these deliverable-line fields.
- Multiple bundle components can share one cart line, and that parent can be absent after an order edit.
- For a component cost, read the deliverable line’s own cost and select the amount and currency fields your rule needs.
Check the version and target when the query fails validation
Shopify’s November 13 Functions changelog describes a deliverable-line cost and a link to the corresponding cart line. The input path is cart.deliverableLines. On November 19, the unstable API references for Order Routing Location Rule and Fulfillment Constraints listed cartLine and cost there. The 2027-01 and 2026-10 references for both APIs omitted the same fields.
If your editor reports Cannot query field, check the API version and target in shopify.extension.toml. Run shopify app function schema from the Function directory and inspect the generated schema.graphql. The CLI uses the Function API type and version in the TOML file. Use the extension’s actual schema to determine which fields its query can request.
Handle cartLine: null after a query succeeds
When a bundle occupies one entry in cart.lines, each component can be a separate deliverable line pointing to the same parent. Check that cartLine exists before reading a parent ID or attribute. After an order edit, the complete bundle may no longer be in the cart, and a remaining deliverable line can have cartLine: null.
For example, a rule might read an attribute from the parent. If the link is absent, follow the rule’s fallback and record that the condition requiring a parent was skipped. Let the deliverable-line quantity or cost follow its own logic. Avoid guessing a parent by matching the SKU or product title.
Choose the component cost or the full bundle cost
For rules that depend on a component’s cost, read cost on the deliverable line. For a rule covering the whole bundle, read the cart line cost when cartLine is present. Reusing the entire bundle cost for every component can inflate the result when they share a parent.
For example, for a per-unit component rule, request amount and currencyCode under the deliverable line’s cost.amountPerQuantity. That amount is decimal and represents one unit. If the rule needs a line total, choose the corresponding total field and account for quantity, discount treatment, and currency explicitly.
Verify three input shapes
In a development shop or an authorized Function fixture, check a regular item, several bundle components sharing a cart line, and a deliverable line with cartLine set to null after an order edit. Check that the input query validates against the schema, then verify the result both with and without the parent.
Save a small redacted input and expected result, including the API version, target, component costs, and currency used by the rule. On later version upgrades, you can use it to distinguish field availability, null handling, and changes in how you calculate the amount.
Sources
Frequently Asked Questions
Why are these fields missing in the 2027-01 release candidate schema?
When checked, both Function references listed them in unstable. Confirm the exact target and API version, then check the generated schema.
Can I still use other deliverable-line data when cartLine is null?
A null cartLine means the parent cart line can be absent. Handle other requested fields supported by the current schema according to their own types and meanings.
Do several components with the same cartLine.id indicate duplicate data?
Components can share a parent when the bundle occupies one cart line. Process component values separately so deduplication by parent ID does not drop valid components.