Expected ship date (ETA)

How to communicate the expected ship date for preorder items to your customers.

Available on Growth and Scale plans.

Two places to set an ETA

Campaign-level default

Settings → Preorder ships in (days).

When set, every new mixed-cart order gets split_at + N days stamped onto its preorder half at creation time. The date shows up in:

• The customer notification email (for example, Expected to ship by August 15, 2026).

• The Splits row in your dashboard.

• Default: blank (no ETA shown to customers).

• Range: 1 to 365 days.

Use this when your campaign has a single expected ship date. Example: Fall24 preorders all ship by end of August.

Per-split override

On the Splits page, every row has an inline date input under the ETA column. Type a new date and click Save. The change:

• Updates the date in any future customer emails for that split.
• Triggers an immediate delay notice to the customer (if you change a date on a non-dispatched split). See Delay & cancel.

Constraint: the date can be up to 365 days in the future. Past dates are allowed by design. If you realize a campaign has slipped past its original date, set an honest past-due ETA so the dashboard surfaces it properly.

Use this to refine the campaign default for an individual customer or batch, or to communicate slippage promptly.

How the date renders

In the customer email, the date is formatted in US-English long form:

Expected to ship by August 15, 2026

The timezone is UTC. We don't show a time component to the customer; it's a calendar date.

When the date is null

If no ETA is set (no campaign default and no per-split override), the customer email shows:

We'll ship these the moment stock arrives.

The split still happens; only the date line is omitted.

The 30-day mark

If a preorder is open for more than 30 days without a confirmed ship date AND without a customer cancel request on file, the FTC 30-day sweeper fires an automatic delay notice. See Delay & cancel for the full FTC story.