Status Row Block

The Status Row is a compact one-line trust strip for the product page, designed to sit right above the add to cart button:

● In stock · ● Free shipping · ● Delivered 1. Sep. – 3. Sep.

It answers the three questions customers have in the moment they click - availability, shipping, and when the order arrives - without taking up the vertical space of the full Shipping Checkpoints timeline. Add it via Product Section → Add block → Status Row and drag it where you want it (typically between the size chart and the Add block).

Points

Up to 3 points, each with:

• Text: What the point says. Leave empty to hide the point entirely (use 2 points if free shipping does not apply to your store).
• Dot color: The colored dot in front of the text.

Delivery date placeholder: Write [delivery_date] anywhere in a point text and it is replaced with the calculated delivery date range, e.g. "Delivered [delivery_date]" becomes "Delivered 1. Sep. – 3. Sep.".

Delivery date calculation

Identical to the Shipping Checkpoints block - if you use both, enter the same values so the dates never contradict each other:

• Processing time: Days until the order is ready to ship.
• Delivery time minimum / maximum: Days after ready - this forms the displayed range.
• Count workdays only: Skips weekends and German public holidays.
• Cutoff time / cutoff hour: Orders after the cutoff hour shift the date by one day. The date refreshes automatically when the cutoff passes.
• Date language: German or English.
• Date format: Six formats from "Mo. 5. Januar" to numeric "05.05.".

Layout

• Alignment: Left or center.
• Mobile layout: One line (wraps if needed) or stacked (each point on its own line).
• Text size desktop and mobile, dot size, gap between points, text color, block margins.

Honest use

Only state what is true: no fake stock scarcity, and only claim free shipping if it applies unconditionally. The calculated date is only as honest as the processing and delivery values you enter.

Layout per device

Desktop and mobile get their own alignment, because the same setting rarely works for both: what reads well spread across a wide column looks lost on a phone.

Alignment and Alignment (mobile) offer Left, Center and Spread out. Mobile defaults to Same as desktop.

Spread out pushes the points to the outer edges. With two points that means one left, one right — usually the better look for a pair, because a centred pair reads as one clump with a gap in the middle rather than as two separate statements.

Three points on a phone

One line (wraps) lets the third point drop under the first, where it lines up with nothing. That is the setting most likely to look broken on a narrow screen.

Two columns puts it at the start of its own row instead — tidy, and one line shorter than stacking all three.

Stacked puts each point on its own line. The clearest option, and the one that costs the most height right above the buy button.

With two points, One line is usually fine and none of this matters.

Per-device alignment and the two-column layout were added in August 2026. Existing blocks keep the behaviour they had: mobile follows desktop, and the layout stays on one line.

Dividers

The row sits between the variant options and the buy button, and without a border it can read as floating there rather than belonging anywhere. Line above and Line below fence it off; both are off by default. Three more settings appear once either line is on:

Setting	Range	Default
Line thickness	1-6px	1px
Line color	any colour	#e5e5e5
Space between line and content	4-40px	14px

All three apply to both lines, so the two can never drift apart. Keep the spacing tight: this row sits just above the buy button, and every pixel here pushes the button further down the screen.

A line above is the useful one. It separates the row from the options above, which is where the visual break belongs.

A line below is usually wrong. The row exists to support the buy button directly underneath it — "in stock, here by Thursday, then buy". A line in between cuts that connection and turns the row into a closing statement for the section above instead.

Use both only when the row sits somewhere unusual, for instance far from the button with other blocks in between.