Skip to content

Postcode markups for a SKU

Give a SKU its own markup for each destination postcode or range. Postcodes not in the table fall back to category, then global markup, and are flagged.

A postcode markup lets one SKU carry a different markup depending on where it goes, for example a lower markup to metro postcodes and a higher one to remote areas. It is set per SKU, on the Pricing page (/freight-pricing).

Postcode markups are on Growth and above. On Starter, any you set earlier keep working, but they cannot be changed.

A SKU markup or a postcode markup, never both

Each SKU uses one of three settings: a single SKU markup, a Postcode markup, or Free freight. Choosing a postcode markup replaces the SKU's single percentage. If you try to send both, Forensik refuses with "A SKU uses either a SKU markup or a postcode markup, never both".

Set up the table

  1. On the Pricing page, find the SKU and choose its pencil. You need the Master Admin role.
  2. Choose Postcode markup.
  3. In the Postcode table, enter a row for each postcode or range:
  • From: a 4-digit postcode, for example 3000.
  • To (optional): the end of the range, inclusive. Leave it blank for a single postcode.
  • Markup %: the markup on cost for that postcode or range.
  1. Choose Add postcode for more rows, up to 500.
  2. Set Effective from, or leave it blank for now, and choose Save new version.

Ranges may not overlap: each postcode can appear in one row only. A range that runs backwards, a postcode that is not 4 digits or two overlapping ranges are refused with the row that is wrong.

The Pricing page shows the first few ranges in the SKU's row. Hover over them to see the whole table.

Postcodes not in the table

When the destination postcode is not in the SKU's table, Forensik does not guess. It falls back to the SKU's category markup, or the global markup if the category has none. The price is flagged as a fallback so you can see where your table has gaps:

  • Which rule applies? shows a "Fallback" note naming the markup used;
  • Test a quote marks the line "no postcode row, fell back" under Show working.

If you see fallbacks to postcodes you sell to often, add them to the table.

Postcode markups and the CSV

The SKU markup CSV cannot carry a postcode table. A row with POSTCODE_MARKUP in the mode column keeps the SKU's existing table, as long as it already has one; otherwise the row is refused. Set up and change tables on the Pricing page. See Set your markup rules.

Was this helpful?