A repeated order ID isn't enough to decide which row to delete.
In this fictional example:
• Order 9001: one mug at $10, plus two teas at $10 each. Order total: $30.
• Order 9002: one book at $12. Order total: $12.
That's two orders, three line items and four units, with $42 in order totals. Deleting the tea row because 9001 appears twice loses a legitimate item. Copying the $30 order total onto both item rows and summing that column produces $72 instead of $42.
Keep the item-level view intact. Build a separate order summary with each verified order-level amount recorded once, and flag conflicting values for review.
Self-initiated, AI-assisted teaching sample with checked arithmetic. One currency; no shipping, discounts, taxes or refunds. These simplified rows are not an untouched Shopify export, and no live Shopify integration was tested.
I'm testing a $250 offline catalog/export preparation pilot: supplied mapping rules, a cleaned table, exceptions and reconciliation. If that fits a small agency task, message me here with a short non-sensitive description. Scope, data handling and timing would be agreed before starting.