Order exception notices
See what changed, who needs to know, and what still needs checking.
Give OrderLilt the order and fulfilment events for one storefront cut-off. It classifies delays, holds, address, stock, cancellation, and refund exceptions, suppresses obsolete shipping language, and returns an unsent notice bundle for seller review.
Sign in and you go straight back to the OrderLilt conversation. Work happens in chat. This page never asks for your card details or email address.
RUBBER STAMPS ON THE DESKEvery candidate gets one stamp. Only draftable rows carry unsent customer wording.
01 / BRING THE BATCH
The desk starts from order and fulfilment events you supply.
Ecommerce sellers who need delayed, blocked, address, payment, stock, and delivery exceptions summarized for notification, without pretending to resolve cases or mutate marketplace records.
- 01
A batch of storefront order records with source event ids and observed times
- 02
Exception events such as carrier delay, cancellation, payment hold, or delivery failure
- 03
Channel, locale, review owner, and any prior candidate keys
02 / THE PACKING LINE
Turn order exceptions into calm, seller-ready notices.
Delay, cancel, payment, and delivery events arrive together, so a seller either sends an obsolete shipping update or invents wording that the records do not support.
- KEYKey the candidate
Each supplied candidate is keyed by storefront, order, exception, and source revision.
- HOLDStamp the disposition
Cancellation or refund suppresses obsolete payment, stock, and delay notices.
- KEEPLeave it unsent
Conflicting facts stay held. A repeated candidate key is duplicate. Nothing is sent.
WHAT LEAVES THE DESK
The bundle is a review pack, not a sent message.
A notice bundle with triggering evidence, affected order, channel, and unsent wording
Disposition counts for draftable, held, suppressed, and duplicate
Held rows that name the seller decision instead of guessing
CONTROLLED DELAY SLIP
SO-100 stayed draftable. The wording named hub SIN, not a promise.
Catalog evidence from the produce-notice-bundle eval: order SO-100, exception carrier-delay, channel email, owner Lee. Counts draftable 1 / held 1 / duplicate 1. Held order SO-200 stays with Sam. This is not a live store notification.
- order
- SO-100
- channel
- evidence
- Carrier scan: in transit, delayed at hub SIN
- counts
- draftable 1 / held 1 / duplicate 1
A SELLER STILL HOLDS SEND
OrderLilt drafts the notice. The seller still sends it.
For ecommerce sellers who need delayed, blocked, address, payment, stock, and delivery exceptions summarized for notification, without pretending to resolve cases or mutate marketplace records.
It does not
- Live store, carrier, or payment monitoring
- Sending the draft, issuing a refund, or editing an address
Before acting
- The candidate does not monitor live stores, carriers, payment providers, or notification channels.
- Drafts are not sent, and delivery, acknowledgement, or resolution is not guaranteed.
- Refunds, cancellations, address changes, stock corrections, and customer promises remain with an authorized seller.
BEFORE YOU BRING A BATCH
Questions
Does it send the customer message?
No. Draftable rows include unsent wording. Sending, refunds, cancellations, and address edits stay with the seller.
What happens if the order is cancelled after a delay event?
The delay candidate is suppressed so the obsolete shipping language is not used. The cancellation candidate stays draftable.
What if payment-hold and paid both appear?
The candidate is held with both source records listed. The script does not claim that a retry succeeded.
STARTER / MONTHLY
Starter
Billing appears inside the signed-in workspace. Card payment runs through Stripe Checkout.
US$19 per month
This landing page never captures card or email details.
Continue to workspace billing