Adcell feed for Shopify

Adcell's spec PDF quotes the technical structure in one breath: encoding UTF-8 or ISO-8859-15, column separator semicolon, text separator double apostrophe, line separator a line break, first line the column labels. With a semicolon as the separator, any text containing one must be quoted. The exporter quotes when needed, so a stray semicolon in a description never breaks a row.

The column names themselves are free: Adcell evaluates the columns of your file and standardises the data, and anything beyond the spec's list is appended as an info column publishers can read. The template's snake_case headers in the PDF's own order are a clean starting point, not a required spelling. Feedflock renders the file on a stable public URL and regenerates it as often as every hour.

The spec PDF documents the registration itself: in your Adcell account, under My campaigns → Advertising material → Create new → CSV. A CSV that carries full product URLs is registered with the @0@ placeholder in the Link field, and Adcell wraps its tracking around the deeplink. Extra parameters are appended to the placeholder. That is why the deeplink column stays plain: no utm, no tracking, nothing to maintain when campaigns change.

What the PDF does not say is whether Adcell re-fetches the file on a schedule. Second-hand documentation has the merchant pasting the feed URL into the Adcell account and Adcell updating the file about every 24 hours. The PDF names a dedicated CSV contact: the cadence is one question to them, and Feedflock's hourly regeneration means every fetch reads current prices and stock either way.

The gross price goes out as a bare number with the currency in its own column. The PDF recognises dot and comma decimals, thousands grouping and even the 123,- form, and the template emits the simplest one: 123.45. One currency per row is the rule: if you sell in several currencies, each gets its own data row. EUR is assumed when the currency column is empty; the template sends the code anyway.

Two details deserve care. price_strike is starred mandatory in the PDF even though it is a reference price. The template maps it from your compare-at price and leaves it empty when the product is not on sale, because an always-filled strike price invents a permanent discount. And identification is a trio, not a field: EAN and/or AAN and/or HAN, at least one per product. The template fills EAN from the Shopify barcode and AAN from the SKU, and checks the rule at generation.

Two mandatory columns come with no vocabulary at all: availability and delivery_time. The template's defaults are honest ones: availability as 1 or 0 derived from Shopify's stock (a worded variant is one mapping away if Adcell's mapper asks), and delivery time as free text like "2-4 working days" that you set, because an invented lead time is a promise only you can make. Shipping is a mandatory bare number in the feed's currency, deliberately unmapped by default: writing 0 would tell every publisher the catalog ships free.

Four more columns are gated on German regulations, marked with a double star in the PDF. Products under the Basic Price Regulation (Grundpreisverordnung) must carry content, base_price and base_price_unit: the content as an integer and a unit with a space between them, "750 ml" or "50 kg", because without the space the data cannot be processed. Products under the Energy Efficiency Classes Regulation carry energy_efficiency_class. All four are in the template, ready when your assortment needs them.