Get a Demo Get Started

Seller Order Updates

Get Started

Ship this workflow

Pick how you want to build it.

Try it in the dashboard Fastest Go to Workflows → New Workflow → Use sample workflow in your workspace, and select this workflow. Try it
Build with the SuprSend Agent Try the agent
Build with SuprSend MCP Set up MCP

When to use this workflow

    Sellers miss new orders and ship late. An order sitting unseen blows the delivery promise.

    The ship-by deadline arrives with no warning. Without a heads-up, the seller scrambles or misses it.

    A missed deadline is caught only when the buyer complains. No breach alert means the team finds out last.

    A "new order" alert with no detail makes the seller dig. Without the items and the deadline, they have to open the dashboard to act.

How it works

1

New order placed

When an order is placed (ORDER_PLACED), the seller is alerted right away.

TriggerMulti-Channel
2

Ship-by reminder before the deadline

12 hours before the ship-by deadline, a reminder goes out if the order is not yet shipped.

Wait UntilMulti-Channel
3

SLA breach alert if missed

If the deadline passes unshipped, an SLA breach alert fires.

Wait UntilMulti-Channel
4

Shipping or cancelling ends it

Shipping or cancelling the order (ORDER_SHIPPED, ORDER_CANCELLED) stops the reminders.

Wait UntilExit

Best practices

    Put the order details and ship-by time in the first alert

    Items, address, and the deadline up front let the seller act without opening the dashboard. A bare "new order" alert just sends them digging.

    Send the reminder with enough time to actually ship

    Twelve hours before is the default. Set it to your fulfilment time so the seller can still pack and dispatch, not a reminder that lands too late to matter.

    Escalate a missed deadline beyond the seller

    A breach the seller already ignored needs another set of eyes. Add an Invoke Workflow step to alert their manager or ops so a slipped order does not go quiet.

Common mistakes to avoid

    Using one ship-by window for every order

    A stock item and a made-to-order one need different deadlines. Set the ship-by per order so the reminder fits what the seller actually has to do.

    Sending the breach alert where no one is watching

    A breach in a shared inbox is missed until a buyer complains. Route it to a channel the seller checks now, which is why the breach adds SMS.

    Sending a new-order alert the seller cannot act on

    An alert that only informs makes the seller switch tabs to do anything. Let them accept the order or print a label from the message itself.

What users receive

The actual notifications this workflow sends, on each channel.

Order Received

Email
Order Received — Email
In-app inbox
Order Received — In-app inbox
Android push
Order Received — Android push

What good looks like

Primary signal On-time

More orders ship on time

More orders go out before the deadline when the seller is alerted, reminded, and flagged on a breach, compared with an order list they have to watch.

Fatigue signal Noise

Sellers tune out the alerts

When sellers mute order alerts, every order is pinging them the same way, with no difference between a routine order and a real breach.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

At the new order, 12 hours before the ship-by deadline (timed by a Wait Until), and again on a breach if the deadline is missed.

Shipping or cancelling the order stops them at the Wait Until; once it ships, the ship-by reminder and breach alert no longer fire.

Email, in-app inbox, and push for the order alert and reminder, with SMS added on a breach so it cuts through.

No, this is seller-facing. Buyer-side updates like packed and shipped are handled by the Buyer Order Updates workflow.

Fire ORDER_PLACED with a near ship_by_date, then ORDER_SHIPPED with the same order_id to check the stop, or let the deadline pass for the breach alert. Use the Test button, the SuprSend Agent, or the API, CLI, or MCP.

Ship Seller Order Updates in under 5 minutes.

Try directly in SuprSend

Fastest

Sign up and test the workflow directly in the dashboard.

Get Started

Build with the SuprSend Agent

Copy the prompt, paste it into the Agent in your SuprSend dashboard, and the workflow gets built for you.

Try the agent

Build it with SuprSend MCP

Set up SuprSend MCP in Claude Code, Cursor or Windsurf, copy the prompt, and the workflow builds itself in your workspace.

Set up MCP