Publishing a price list: XML and CSV, every day

What gets published

Every day, right after the price snapshot, the whole catalogue is exported to the chosen formats at a permanent address. The dated file stays as an archive and an undated file always points at the newest list.

https://your-store.com/cjenik/
https://your-store.com/cjenik/cjenik.csv
https://your-store.com/cjenik/cjenik-2026-09-21.csv
https://your-store.com/cjenik/index.json

Three formats, the same content

CSV is semicolon separated, the notation Croatian ERPs and localised Excel produce. Numbers use a decimal point and no thousands separator.

XML carries one element per product; JSON adds a product count at the end so a truncated file is obvious.

Archive and JSON index

index.json lists every available day and address per format, plus the store name, export date, product count and column list.

Retention is a setting, ninety days by default.

Why it is served through PHP

A file in uploads is public on both Apache and nginx, while an .htaccess rule only applies to Apache. Serving through WordPress honours the visibility setting on any web server and keeps the headers correct.

Large catalogues

The export runs in batches, writing to a temporary file and renaming only once the whole catalogue is in. Anyone fetching mid-export gets yesterday's complete list rather than today's half one.

Customising the content

Each row passes through a filter before it is written, so values can be changed from a theme or your own plugin.

add_filter( 'klikoteka_cjenik_red', function ( $red, $product ) {
	$red['kategorija'] = strtoupper( $red['kategorija'] );
	return $red;
}, 10, 2 );

Export columns