Feature/financial metrics clv revenue

[ijac13]

Trust Issues: How Jaffle Shop Rebuilt Stakeholder Confidence with Recce

📌 Summary

This PR resolves a critical issue in how revenue and customer lifetime value (CLV) were being calculated across the customers, customer_segments, customer_order_pattern, and finance_revenue models.

We identified that:

• All order statuses were included in revenue and CLV metrics—including unfulfilled or returned orders.
• Coupon payments were mistakenly treated as revenue, inflating metrics across both marketing and finance reports.
  This broke trust in our data. Both marketing and finance were misled for months.

✅ Solution

We’ve introduced three key changes:

1. Filter for completed orders only
   • Ensures only fulfilled purchases are included in CLV and revenue.
2. Add net_customer_lifetime_value

• Captures actual revenue (excluding coupon payments).
• Existing dashboards using gross CLV remain functional.

3. Create finance_revenue model

• Gross and net revenue metrics are now clearly separated.
• Accurate reporting for finance, without mixing marketing assumptions.

👁️ Impacted and validation

• See modified models in Recce Summary

• With these 4 modified models, only customer_segments is impacted. See Breaking Change Analysis + Column-Level Lineage in Recce:

• Validation checks are included in Checklist

Supporting Resources

• See in Action
• Product Story: When Metrics Break, Trust Breaks

[github-actions]

Recce Summary

Manifest Information

	Manifest	Catalog
Base	2025-04-20 00:20:27	2025-04-20 00:20:28
Current	2025-04-21 02:10:44	2025-04-21 02:10:45

Lineage Graph

graph LR
model.jaffle_shop.stg_payments["stg_payments

[What's Changed]
Code, Schema"]
style model.jaffle_shop.stg_payments stroke:#ffa502
model.jaffle_shop.stg_payments---->model.jaffle_shop.orders
model.jaffle_shop.stg_payments---->model.jaffle_shop.customers
model.jaffle_shop.stg_payments-...->model.jaffle_shop.finance_revenue
model.jaffle_shop.customers["customers

[What's Changed]
Code, Schema, Value Diff, Profile Diff"]
style model.jaffle_shop.customers stroke:#ffa502
model.jaffle_shop.customers---->model.jaffle_shop.customer_order_pattern
model.jaffle_shop.customers---->model.jaffle_shop.customer_segments
model.jaffle_shop.customer_segments["customer_segments

[What's Changed]
Code, Schema, Top K Diff"]
style model.jaffle_shop.customer_segments stroke:#ffa502
model.jaffle_shop.orders["orders

[What's Changed]
"]
model.jaffle_shop.finance_revenue["finance_revenue

[What's Changed]
Added Node"]
style model.jaffle_shop.finance_revenue stroke:#1dce00
model.jaffle_shop.customer_order_pattern["customer_order_pattern"]

Loading

Checks Summary

Checks Run	Data Mismatch Detected	Incomplete Checks
9	6	2

⚠️ Incomplete Checks refers to checks that did not successfully run due to configuration or SQL errors.
Please check the output of recce run for more information

Checks of Data Mismatch Detected

Name	Type	Mismatched Nodes
Model schema of customers, orders and modified nodes	Schema Diff	customer_segments, finance_revenue, and 2 more nodes
Row count of customers, orders and modified table model	Row Count Diff	finance_revenue
Value diff of customers	Value Diff	customers
Query diff of customers avg lifetime value	Query Diff	N/A
Profile diff of customers	Profile Diff	customers
Top-k diff of customer_segments.value_segment	Top K Diff	customer_segments

See PR page: https://cloud.datarecce.io/DataRecce/jaffle_shop_duckdb/pulls/46

How to check the recce result

# Launch the recce server based on the state file
recce server --review --cloud --password yummy_jaffle

# Open the recce server http://localhost:8000 by your browser