Backorder and preorder delay consent
How do we notify customers when an item cannot ship on time, capture their consent to the delay or their cancellation, and update the order under the Mail Order Rule?
Make the delay notice a screen with a choice and a clock. When an item cannot ship by the promised date (a backorder, a preorder slip, a supplier delay), Callvu classifies the affected orders (the promised date, the new estimated date or none, the item and the quantity, the payment status, the delay count on the order), sends each customer the notice the rule requires (the delay, the revised date or the statement that none is known, the right to cancel for a prompt refund, how to consent or cancel) with a secure screen to choose, applies the rule's defaults where the customer does not respond (consent deemed for a first delay with a definite date within the rule's period, cancellation deemed otherwise), routes an order the rule does not cover cleanly (a partial shipment, a second delay, a bundle) to the order desk in the Decision Desk, and writes the consent, the new date or the cancellation and the refund to the order management system, the system of record.
In scopeSimpleCallvu moves: classify, write back
Last updated November 7, 2026.
The problem today
The backorder email said 'we'll let you know', and the regulator's letter said the rule requires more than that.
Items run late: a preorder's date slips, a supplier misses, a bestseller sells out. The retailer sends a vague email, or nothing, and keeps the payment. The rule is specific about what the customer is owed when the promised shipment date is missed: a notice with the revised date, the right to cancel for a prompt refund, and a clear way to do either, with defaults the rule sets when the customer is silent. The retailer that gets it wrong faces the regulator and the chargebacks.
The delay is data: the orders with the item, the promised dates, the new estimate from the supplier, the payment status, how many delays this order has had. The notice is a form with required content; the response is a choice on a screen; the defaults are rules with clocks. The order management system must reflect the consent, the new date or the cancellation and the refund, order by order.
A delay handled as the rule describes keeps the order and the customer; a vague email loses both.
How it runs
From the requestto the system of record.
An item's availability changes so orders cannot ship by their promised dates (a supplier notice, an inventory event, a preorder date change). Callvu classifies the affected orders and opens a consent case per order.
- Customer
- Receives the notice and consents to the delay, cancels, or lets the default apply, on a secure screen.
- Order desk
- Decides orders the rule does not cover cleanly in the Decision Desk.
- Merchandising or the supplier
- Supplies the new estimated date or confirms none is known.
- Callvu
- Classifies, sends the notice, captures the choice, applies the defaults, routes and writes.
Classify the affected orders
Every open order with the item is identified from the order management system with its promised shipment date, the quantity, whether other lines can ship now (a partial shipment), the payment status (charged or authorized), and the number of prior delay notices; the new estimated date from merchandising or the supplier, or the statement that none is known, is attached; each order is classified under the rule: a first delay with a definite revised date within the rule's period, a first delay with a longer or indefinite date, or a second or later delay.
Send the notice with a choice
Each customer receives the notice the rule requires (the item, the delay, the revised date or that none can be given, the right to cancel for a prompt refund, and how to consent or cancel) with a link to a secure screen to consent to the new date, cancel the line or the order, or for a partial shipment to ship what is available now; the screen states the default the rule applies if they do not respond and by when.
Apply the defaults and decide
A response is applied as chosen; where the customer does not respond, the rule's default applies on the clock: for a first delay with a definite date within the rule's period, silence is consent; for a longer, indefinite or later delay, silence is cancellation with the refund; an order the rule does not cover cleanly (a bundle where one component is delayed, a customized item, a second delay with a disputed consent, a payment that cannot be refunded to the original method) goes to the order desk in the Decision Desk with the order and only the allowed outcomes (ship partially, hold with consent, cancel with refund, or substitute with the customer's agreement).
Write back
The consent with the new promised date, the partial shipment, or the cancellation with the refund issued to the original method within the rule's period is written to the order management system, the system of record, against each order with the notice and the response (or the default) and their times, the customer receives the confirmation, and the new promised date becomes the next clock for the same process.
Where it ends: Every affected order received the rule's notice with a real choice, the response or the default was applied on the clock, and the order management system holds the consent, the new date or the cancellation and the refund with the evidence. The Decision Trace shows the classification and the default applied; the Audit Trace shows the notice, the response and the write with time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The notice by email and text with a link to the choice screen; the app shows the same choice.
The back office
The order desk decides only edge cases; merchandising supplies the dates; finance sees refunds posted on the rule's clock.
The Decision Desk
- A bundle with a delayed component, a customized item, a disputed consent on a second delay or a payment that cannot be refunded to the original method goes to the order desk in the Decision Desk with the order and only ship partially, hold with consent, cancel with refund, or substitute with agreement.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
A process can run a timer that tracks a regulatory clock, such as a response or disclosure deadline, and act when it runs out.
CAP-13 · Self-asserted · verified 2026-11-02
Automatic and agent-sent reminders go out until a screen is submitted.
CAP-11 · Self-asserted · verified 2026-11-02
Every run produces a Decision Trace (why each AI action was allowed) and every workflow execution an Audit Trace (the chronological governance record).
ENF-03 · Self-asserted · verified 2026-11-02
Questions
What buyers ask next,answered plainly.
What must the delay notice say?
The item and the delay, the revised shipment date or that none can be given, the right to cancel for a prompt refund, and how to consent or cancel, with the default stated.
What if the customer does not answer?
For a first delay with a definite date within thirty days, silence counts as consent; for a longer, indefinite or later delay, silence counts as cancellation with the refund, applied on the clock.
How fast is the refund on cancellation?
Within seven working days, or one billing cycle for a credit card, to the original payment method.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.