An order changed after checkout: preserve the original sale and the revision

Save the original order lines and the confirmed revision before asking the accountant to correct sales. An order edit can change quantities, discounts, delivery charges or the amount still due. A current order screen shows the result, but it may not explain which change arrived after an earlier accounting import. Record the original order identifier, revision time, affected lines and employee who approved the change.

Shopify explains that an edit made after the original order date can appear as a separate order in certain reports even though no new order was created. It also warns that some connected apps do not recognize edits. Treat the report presentation and the connector's posting behavior as separate questions. A second row does not, by itself, establish a second customer purchase.

Start with the revised amount the customer owes under the agreed order. Compare it with captured payments and completed refunds, keeping pending attempts visible separately. Editing an order total does not prove that additional money was collected or that an owed refund was delivered. Give the customer service team one agreed balance so it does not send a payment request while finance is arranging a credit.

For a hypothetical example, an order originally totals $180 and the customer has paid $180. A supported revision raises the total to $205. The additional amount to collect is $25. If the customer pays that amount, a connector should not treat the full revised $205 as an additional sale on top of the original $180. Tax and revenue classifications still follow the business's approved accounting policy.

Check discounts and shipping individually. The change may affect a promotional threshold or the cost of sending the goods. Retain the customer's accepted price and the final calculation instead of silently adjusting the original document until it happens to match cash.

Ask the warehouse which version it received and whether picking has begun. Record the acknowledgment against the revision. If an item was removed from the order but remains on a packing instruction, the goods can leave without a corresponding customer obligation. If an item was added but never reached the warehouse, the revised payment can be correct while the delivery is incomplete.

Keep the item identifier stable through the investigation. Product titles can change, and two variants may share similar names. Compare the order line, SKU, quantity and fulfillment reference. Where an app cannot process the revision automatically, use the documented exception procedure and record who updated the warehouse instruction. Avoid an informal message that disappears when a shift ends.

Inspect the connector's original posting, revision posting and any payment or refund entry for the same order. Decide whether the integration updates a document, posts a difference or creates a replacement. Use its supported correction method so the next sync does not recreate a manual adjustment. Save both the source export and the resulting ledger references.

Close the exception when the customer balance, revised fulfillment and ledger agree. If edits recur, maintain a small review population of orders changed after their first export, with extra attention to changes across a reporting cutoff. The reviewer should be able to explain the amount added or removed and the period in which the correction was recorded without reconstructing the customer's conversation.