Problem Statement / Use Case: As a data and finance team, we rely on Fivetran to replicate Shopify data into our data warehouse to automate our financial reporting. However, we are currently unable to reconcile daily Gross Sales and Net Sales in our warehouse with the native Shopify Analytics Dashboard due to how historical Order Edits are handled by the Fivetran connector.

Current Behavior: When a customer service agent or a post-purchase upsell app edits an order (e.g., adding a new line item, swapping a variant, or applying a discount) days or months after the original checkout, Shopify's internal financial ledger records that new revenue on the date the edit occurred.

Currently, Fivetran handles this by overwriting the existing rows in the ORDER and ORDER_LINE tables. Because the ORDER_LINE table lacks its own creation timestamp, and the ORDER table relies on the original checkout created_at timestamp, this new revenue is retroactively attributed to the original order date in our data warehouse. This creates a "Cohort" view rather than a "Ledger" view, making daily financial reconciliation against Shopify's UI impossible.

Desired Behavior / Proposed Solution: Please add support for Shopify's Order Edit API / orders/edited webhooks.

Specifically, we are requesting new tables in the schema (e.g., ORDER_EDIT and ORDER_EDIT_LINE_ITEM) that log the exact details of the edit, including the created_at timestamp of the edit itself, the items added/removed, and the delta in financial value.

Business Impact: Without these tables, our daily sales reports constantly drift from Shopify's dashboard. Finance teams spend hours investigating variances only to discover they were caused by historical order edits. Adding these tables would allow Fivetran customers to build mathematically perfect, ledger-based daily sales models that match Shopify Analytics down to the penny.