Skipping

Gro supports two kinds of skipping, so customers can adjust a single order without changing their subscription going forward.

Type	What it does	Future orders
Skip an item	Leaves one product off the next order only	Unaffected, the item returns automatically
Skip an order	Moves the whole next order forward by a week or two	Unaffected, the schedule resumes after

Skipping a single item

Skipping an item takes one product off the next order only. The item stays on the subscription the whole time, tagged “Skipped for next order”, and comes back automatically once that order has shipped. Nothing else on the subscription changes.

This is useful when a customer is well stocked on one thing but still wants everything else, without pausing or editing their whole subscription.

How it works:

The item is shown on the subscription with a clear “Skipped for next order” tag, so it is never lost from view.
When the next order is charged, that item is left off and the customer is not billed for it.
After the order ships, the item is added straight back for the following order.

Good to know:

At least one item must remain. A customer cannot skip every product on an order. They will be told why if they try.
Box items cannot be skipped individually. Items that are part of a build-a-box are managed through the box, not skipped one by one.
While an item is skipped from the current order, it cannot be edited or removed until that order has shipped.

Turn it on under Settings > Subscriptions > Portal with the Allow skip item toggle. It is off by default.

Skipping an entire order

Skipping an order moves the customer’s next billing and delivery forward, by one or two weeks, then resumes the normal schedule. The order is not charged and nothing ships for that cycle.

This is the right choice when a customer wants a break this time around but is happy to continue as normal afterwards.

Turn it on under Settings > Subscriptions > Portal with the Allow skip toggle.

Where skipping happens

Customer portal — customers can skip items and orders themselves, when you have enabled the matching toggle.
Dashboard — your team can skip an item or an order on a customer’s behalf at any time, regardless of the portal toggles.

Skipping in your emails and flows

Every skip is available to your marketing tools, so you can react to it and always show the right order contents.

Events

Event	When it fires	Use it for
Subscription line skipped (`subscription_line_skipped`)	A customer or your team skips a single item from the next order	A “we have left that out this time” confirmation, or a win-back for the skipped product
Subscription skipped (`subscription_skipped`)	A customer skips a whole order	A “see you next time” note, or a nudge to bring the order forward
Subscription payment reminder (`subscription_payment_reminder`)	A reminder is sent before billing	The pre-billing email that lists what is coming and the amount

The line skipped event carries the item that was skipped in its top-level properties: product_title, variant_title, quantity, price, who did it (skipped_by), and any reason given.

The fields that matter for skips

Every subscription event includes the full order, plus a few fields that already account for skips so you never have to do the maths yourself.

Field	What it holds
`next_charge_total`	The amount the next order will actually charge, with skipped items removed and one-off items added. Use this in any email that shows a price.
`skipped_items_total`	The value of the items skipped from the next order.
`total`	The normal recurring total. It ignores skips and one-offs, so do not use it for the next order.
`lines`	Every item on the subscription.
`lines[].is_skipping_next_order`	`true` when that item is skipped from the next order, `false` when it is coming. Present on the lines of every event.

Because is_skipping_next_order sits on each line of every event, you can split “what is coming” from “what was skipped” in a payment reminder, an order confirmation, or any other message, without a separate feed of skipped items.

Using these events in Klaviyo

When your account is connected to Klaviyo, Gro sends each of these events to Klaviyo as a custom metric. The metric name matches the readable name above (for example Subscription Line Skipped or Subscription Payment Reminder), and the full payload arrives as event properties you can reference in a flow.

1. Trigger a flow. Create a flow and choose the metric as its trigger, for example Subscription Line Skipped to follow up on a skipped product, or Subscription Payment Reminder for the pre-billing email.

2. Show the real amount. Use next_charge_total, not total:

Your next order totals {{ event.next_charge_total }} {{ event.currency }}.

3. List only the items that are coming. Loop the lines and hide anything skipped:

{% for line in event.lines %}
  {% if not line.is_skipping_next_order %}
    {{ line.product_title }} x{{ line.quantity }} ({{ line.price }} {{ event.currency }})
  {% endif %}
{% endfor %}

4. Optionally show what was skipped, so the customer knows it will be back next time:

{% for line in event.lines %}
  {% if line.is_skipping_next_order %}
    Skipped this order: {{ line.product_title }} (returns automatically next time)
  {% endif %}
{% endfor %}

5. On the line skipped event, you can reference the skipped item directly from the top level:

{{ event.product_title }} was left off your next order.
{% if event.reason %}You told us: {{ event.reason }}.{% endif %}

Rescheduling for moving an order to a specific date rather than skipping it.
Flow Builder for building automated emails on these events inside Gro.