Update about Shipping Restrictions (July '26)

(UPDATED July 2026)

Nothing changes at checkout, and there’s nothing you need to do to stay protected. Our LGL Shipping Validation app still automatically blocks orders that can’t legally ship to a given state — and it’s now more accurate, because we’ve moved restrictions to a per-variant system (different sizes can ship from different growers with different rules). This all happens on our side.

What’s actually changing: Historically we published these restrictions as product tags on your products (tags that look like rs_CA, rs_TX, etc.). Those tags are now legacy — the app no longer reads them. The live data lives on each product variant in a metafield called lgl.restricted_states.

Why we’re writing: If your storefront theme uses those rs_XX product tags to display shipping-restriction info on your product pages, that display will gradually become less accurate (the tags are product-wide; the real restrictions are now per-variant), and we plan to stop maintaining the rs_XX tags after [DATE — ~2026-10-31].

What we need from you — by [DATE — ~2026-09-15]:

  • If you’re not doing anything custom with rs_XX tags (most retailers): no action needed. You can ignore the rest of this email.

  • If your theme does use rs_XX tags for display: reply and let us know. We’ll help you switch to the per-variant metafield (lgl.restricted_states) so your product pages stay accurate, or find another approach that works for you.

  • Not sure? Just reply and we’ll check with you.

(For your developer, if relevant: restrictions are now on the variant metafield lgl.restricted_states — a list of 2-letter state codes the variant cannot ship to, including AK/HI on all products. The rs_XX product tags are the legacy product-level union of those values.)

To be clear: your checkout protection is automatic and unaffected throughout — customers still cannot complete an order to a restricted state.