My COGS are changing and I don't want to it change older orders?

If your supplier changes prices, you may want to use the new costs for newer orders while keeping the saved costs for older orders. The Database COGS setting lets supported calculations use the costs saved with each order instead of recalculating them from today's product-cost inputs.

Turn this setting on before changing your cost inputs. Enabling it afterward does not reconstruct the old prices if those saved costs have already been overwritten.

Example: new supplier prices from September 12

Suppose the old product cost was $10.00 and the new cost is $12.00 from September 12. You want orders before September 12 to keep their saved costs, and orders from September 12 onward to use the updated inputs.

1. Select your store. Check a few earlier orders on Edit Orders to confirm their saved costs are correct.
2. Enable the saved-cost setup. Check that product COGS are included in analytics, using Include in Analytics on Manual COGS where shown. Open Other COGS Settings, enable Database COGS, and save your settings. If earlier saved values are missing or incorrect, resolve those before relying on them to preserve history.
3. Update the cost method you actually use. This may be Manual COGS, a country rule, or a country-and-quantity rule. Updating a Manual COGS value will not replace a different rule that takes priority. If automatic Shopify cost-per-item syncing is enabled, keep the Shopify costs consistent with your intended inputs.
4. Identify the affected orders. In Shopify or Order Breakdown, identify the starting and ending Shopify order numbers for the orders you want to recalculate. Check dates using your store's timezone.
5. Recalculate only that order range. Open Update Saved/Calculated COGS & Custom Order Expense by Order Range. Enter the numeric starting and ending order numbers, then choose Update and wait for completion.
6. Check both sides of the change. Review an order before September 12 and orders inside the updated range, then refresh the dashboard for those periods.

The range is inclusive. Entering 1200 to 1250 includes both order 1200 and order 1250, as well as matching orders between them. Use the numeric Shopify order numbers, without a display prefix or #.

This tool selects orders by number, not by date or product. Verify that the chosen range represents the orders you intend to update. If it does not, use Edit Orders, the per-order CSV upload, or ask support for help selecting the appropriate orders.

What does recalculation change?

The order-range tool recalculates saved COGS and applicable Custom Order Expense using the current cost inputs. It is not limited to the one product whose price you just changed. Review any other cost rules that could affect orders in that range before running it.

Orders with protected manual cost overrides may retain those values. If a value remains unchanged, check its saved cost and override setup before assuming the recalculation failed.

What Database COGS does not freeze

Database COGS preserves the saved order-cost basis used by supported calculations. It does not freeze every financial number. Currency conversion, tax treatment, refund/edit settings, supplier integrations and separately calculated fees can still affect reports.

This workflow is for changing the product-cost inputs used to calculate saved order costs. For costs supplied by an integration, check that integration's own syncing and cost-selection settings instead of assuming a Manual COGS change will replace its charges.

See How does Database COGS Sync work? for the general setting explanation. If you already changed costs and are unsure which historical values remain saved, contact support before recalculating a broad range.