docs: clarify Shopify subscription signal update behavior

[lordhumunguz]

Summary

• document Shopify subscription classification signal precedence updates
• add explicit note about placeholder value subscription_id='1' behavior
• document ReCharge app id 294517 fallback behavior in troubleshooting docs

Updated pages

• data-transformations/order-segmentation/order-type
• help-center/core-concepts/data-definitions/subscription-flags
• help-center/faq/data-faqs/why-doesnt-recharge-match-sourcemedium
• help-center/faq/data-faqs/data-faqs-home

Summary by CodeRabbit

• Documentation
  • Updated subscription classification logic for Shopify orders to recognize expanded metadata signals.
  • Added guidance on potential reclassification of historical orders following Shopify signal updates (effective February 20, 2026).
  • Enhanced help center documentation with troubleshooting notes and FAQ entries regarding subscription signal changes.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation updates describing changes to Shopify order-line classification signals, including new signal precedence logic (explicit one-time signals win), expanded metadata key recognition, placeholder value guardrails, and expected user impact regarding order reclassification.

Changes

Cohort / File(s)	Summary
Core Signal Documentation data-transformations/order-segmentation/order-type.mdx	Replaces previous signal priority with new Shopify/order-line sequence: explicit one-time signal → explicit subscription signal → platform matches → legacy fallback → default one-time. Adds Shopify metadata update section with new subscriber metadata keys and explicit one-time key recognition. Introduces placeholder value guardrail (subscription_id = '1'). Extends subscription tag patterns with case-insensitive recognition. Adds ReCharge app id 294517 to post-cutover order-source list.
Help Center Concept Definition help-center/core-concepts/data-definitions/subscription-flags.mdx	Adds new "Shopify behavior update (February 20, 2026)" section documenting expanded line-item metadata signals, signal precedence rules, placeholder-only subscription_id handling, and post-cutover app id inclusion. Notes possible reclassification impact for existing users while clarifying field definitions remain unchanged.
FAQ Updates help-center/faq/data-faqs/data-faqs-home.mdx, help-center/faq/data-faqs/why-doesnt-recharge-match-sourcemedium.mdx	Adds FAQ bullet noting February 20, 2026 Shopify subscription signal update. Introduces troubleshooting subsection explaining classification changes post-update and single-line order fallback logic with ReCharge app id matching.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~18 minutes

Poem

🐰 A rabbit's whisker-twitch of delight!
New signals shine in Shopify's light,
One-time wins first, subscriptions take flight,
Metadata expands, no schemas in sight—
Documentation hops to set things right! 📚✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: documentation clarifications about Shopify subscription signal update behavior. It is concise, specific, and directly reflects the content across all four updated documentation files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/shopify-sub-classification-doc-update

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (2)

data-transformations/order-segmentation/order-type.mdx (1)

33-58: Well-structured update section with clear user-facing expectations.

A couple of minor observations:

1. "Post-cutover" jargon (line 44): Same as in the ReCharge FAQ — consider using "after the February 20, 2026 update" for consistency and reader clarity.

2. Lines 56–57 nicely set user expectations about potential reclassification in both directions. Line 58 reassuring no schema change is a good touch.

Optional: minor wording adjustment on line 44

-- Added Shopify app-id fallback coverage for single-line orders:
-  - Includes ReCharge app id `294517` in the post-cutover order-source fallback list.
+- Added Shopify app-id fallback coverage for single-line orders:
+  - Includes ReCharge app id `294517` in the order-source fallback list (effective February 20, 2026).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@data-transformations/order-segmentation/order-type.mdx` around lines 33 - 58,
The phrase "post-cutover" in the Shopify update section is jargon; replace that
wording with "after the February 20, 2026 update" for clarity and consistency
with the ReCharge FAQ across the document (specifically update the phrase in the
sentence that references the order-source fallback list), leaving the rest of
the Shopify Metadata Update text (signal precedence, expectations, and schema
reassurance) unchanged.

help-center/faq/data-faqs/why-doesnt-recharge-match-sourcemedium.mdx (1)

47-53: Consider replacing "post-cutover" with a more reader-friendly phrase.

Line 53 uses "post-cutover Shopify data" which is internal jargon. Since this is a user-facing FAQ, a phrase like "after the February 20, 2026 update" would be more immediately clear to customers who may not know what "cutover" refers to.

Suggested change

-- In post-cutover Shopify data, single-line orders with `order_source_name = '294517'` can now classify as subscription via fallback logic.
+- After the February 20, 2026 update, single-line Shopify orders with `order_source_name = '294517'` can now classify as subscription via fallback logic.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@help-center/faq/data-faqs/why-doesnt-recharge-match-sourcemedium.mdx` around
lines 47 - 53, Replace the internal jargon "post-cutover Shopify data" in the
"Shopify metadata signal changes (for existing users)" section with a
user-friendly phrase such as "after the February 20, 2026 update" (or the actual
public-facing update date), updating the sentence "In post-cutover Shopify data,
single-line orders..." to read e.g. "In Shopify data after the February 20, 2026
update, single-line orders..." so customers immediately understand the timing;
make the same replacement for any other occurrences of "post-cutover" in this
FAQ section.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@data-transformations/order-segmentation/order-type.mdx`:
- Around line 33-58: The phrase "post-cutover" in the Shopify update section is
jargon; replace that wording with "after the February 20, 2026 update" for
clarity and consistency with the ReCharge FAQ across the document (specifically
update the phrase in the sentence that references the order-source fallback
list), leaving the rest of the Shopify Metadata Update text (signal precedence,
expectations, and schema reassurance) unchanged.

In `@help-center/faq/data-faqs/why-doesnt-recharge-match-sourcemedium.mdx`:
- Around line 47-53: Replace the internal jargon "post-cutover Shopify data" in
the "Shopify metadata signal changes (for existing users)" section with a
user-friendly phrase such as "after the February 20, 2026 update" (or the actual
public-facing update date), updating the sentence "In post-cutover Shopify data,
single-line orders..." to read e.g. "In Shopify data after the February 20, 2026
update, single-line orders..." so customers immediately understand the timing;
make the same replacement for any other occurrences of "post-cutover" in this
FAQ section.