Reduced prices (durchgestrichene Preise)
A shop may announce a price reduction by showing the former, higher price struck through next to the current price. The platform detects reductions automatically: it records every item's price once a day and compares the current price with the recorded one. The shop operator decides in the admin settings whether the feature is on and how big a reduction must be (minimum percentage and/or minimum amount) and for how many days it is announced.
As an API client you do not have to compute anything. You get the result as one field per item.
Note: There is also a different reduce (or increase) price tag in carts, that indicates price changes of an item that is already in a cart for a while. Different feature.
The field: Item.lastPrice
Available in the Item response type from version 22 on (position 35), returned by /api/items20 and later, /api/item1, /api/assortment13 and the item lists embedded in /api/order27 and later.
| Value | Meaning |
|---|---|
lastPrice > 0 |
Announce a reduction: lastPrice is the former price, price the current one. lastPrice is always higher than price. |
lastPrice == 0 |
Nothing to announce. Either the feature is off, the price did not fall, the reduction is below the operator's thresholds, or the announcement period is over. |
Points that are easy to miss:
- The value is already filtered. Thresholds and the announcement duration are applied server side, so if the field is > 0 the operator wants it shown. Do not add your own rules on top, and do not try to derive reductions by polling prices yourself.
- It is per unit, in the same unit and currency as
price. If you show a reference price (Grundpreis), you may derive the former reference price the same way you derive the current one. - It is informational only. Order totals, discounts and bulk prices are calculated from
price.lastPricenever enters an order. - It can depend on the selected delivery date. Items may carry a price change for a future period (see delivery date selection). If the customer looks at a delivery day where the lower, future price applies, the current price becomes the struck price. Reload the items after the delivery date changes, exactly as you do for the price itself.
- It changes once a day. Caching item data for the session is fine; a daily refresh is enough for this field.
Display
The standard shop renders the former price struck through, in red, in front of or above the current price, in item lists as well as on item detail pages. Keep the two prices visually distinct so that the customer cannot mistake the struck price for the price to pay.
Do not confuse three different "lower price" mechanisms, which can all appear on the same item:
| Mechanism | Field(s) | What the customer sees in the standard shop |
|---|---|---|
| Reduced price (this skill) | lastPrice |
former price struck through |
| Customer discount | maxDiscount, the customer's discount |
list price struck through, discounted price shown |
| Bulk price | bulkPrice, bulkAmount, bulkPriceReference |
"Staffelpreis ab …" offer, badge in the cart |
Legal notes (Germany / EU)
Announcing a price reduction is regulated (Preisangabenverordnung §11, based on the EU Omnibus directive). Whenever you show a reduction you must also state the lowest price the item had within the last 30 days before the reduction. The platform records this lowest price per item and the standard shop labels the struck price with "Kleinster Preis seit 30 Tagen" (lowest price of the last 30 days).
- Put the same or an equivalent wording next to the struck price. A tooltip on a footnote marker is the minimum; a visible text is better.
- Do not invent your own strike-through prices (e.g. from a manufacturer's recommended price) under the same look. Mixed semantics are a common reason for warnings (Abmahnung).
- The API does not yet return the 30-day lowest price as a separate value. The shop operator can review it in the admin area (Status → Preissenkung), where items whose price was even lower within the last 30 days are highlighted. If you need the value in your client, ask for it.
Price changes on positions already in the cart are a different topic: the standard shop shows a
"Preissenkung!" or "Preiserhöhung" badge when a stored position's price differs from the current item
price. You can implement the same by comparing the position price in the order with
the current Item.price.
Checklist for the shop operator
These are not API calls, but a client implementer should know them, because an empty lastPrice is usually
one of these:
- The feature is switched on in the shop settings ("durchgestrichene Preise": Automatik).
- Thresholds (minimum % and minimum amount) and the announcement duration are set.
- The admin overview Status → Preissenkung shows which items are currently announced and why.
Ideas
- A "Reduziert" / "Angebote" listing: filter the item set client side for
lastPrice > 0and render it as its own page or carousel. - Show the saving as a badge:
-((lastPrice - price) / lastPrice * 100)rounded, e.g. "-15 %". - Combine with sale-off: items that are both reduced and limited in stock make a good "last chance" teaser.
- Mention reduced items in a newsletter or push message; the daily change makes a morning digest a natural fit (see message series).
Related
- Item details — the other informational fields of an item
- Sale-off — limited stock, a different kind of offer
- Delivery date selection — why item data depends on the chosen delivery day