The automated Extra Costs import expects correct data. Check your rows before they go into the file. For a single edit or deletion, use the Kickbite UI instead of the import.
Google Sheets
A Google Sheets import replaces the whole Extra Costs history.
GCS / BigQuery
A GCS or BigQuery import updates Extra Costs only for the date range currently in your file, per market, and only for automated rows.
If you change a date or amount, the next run updates that row. It does not create a duplicate.
If you delete a row that still sits inside the file’s date range, the next run removes it. You do not need to delete it by hand.
If a row falls outside the file’s current date range (for example the range shrinks from 1993–2028 to 2003–2026), it stays. Tell Kickbite support so we can delete it.
Manual rows in the Kickbite UI
Rows you add manually in the Kickbite UI are never touched by the import.
When dashboards refresh
Dashboards refresh Extra Costs for the last 2 months on the daily run. Changes to older dates need a reprocess — ask Kickbite support.