Order modification across channels

How do we apply one order modification policy across the store, the website and the phone, so the result is the same in every channel and written to the order management system?

Run one modification process behind every channel. Whether the customer asks in a store, on the website, in the app, by chat, by phone or through an AI assistant, Callvu identifies the customer and prefills the order with its live status across channels (an online order being picked up in store, a store purchase shipped to home, a split order), classifies the request (a change, an exchange, a partial cancellation, a pickup-to-delivery switch, a store return of an online order) against the one policy with its cutoffs and exceptions, applies the result by rule where the policy allows with the price difference taken or refunded on a secure screen, routes a request outside the policy, above the channel's authority or on a flagged order to the order desk in the Decision Desk, and writes the modification to the order management system, the system of record, so the store, the warehouse and the website show the same order.

In scopeComplex: multi-party handoffsCallvu moves: classify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The store changed the order the website had refused to change, and the warehouse shipped the original anyway.

Today, without Callvu

Omnichannel retail promises one customer and one order, and delivers three systems with three policies: the store's point of sale, the website's order tool, the contact center's console. A customer who buys online and picks up in store, or buys in store and ships to home, asks for a change in whichever channel is nearest; the channel applies its own rules and writes to its own system; the other channels learn later or never. The customer experiences the retailer as inconsistent and the warehouse as uninformed.

The order is one record in the order management system with a live status that spans the channels; the policy is one set of rules with cutoffs by fulfillment stage and exceptions by product and order type; the authority is one matrix by channel and amount. A modification is the same classification and the same write whether a store associate, a web form or an agent starts it. The consumer protection laws require the disclosed policy to be the one applied, everywhere.

One policy behind every channel is what the customer was promised and what the regulator expects.

How it runs

From the requestto the system of record.

A customer requests an order modification in a store, on the website, in the app, by chat, by phone or through an AI assistant. Callvu identifies them and opens the request on the one order record.

Customer: Requests the change in any channel and confirms the result on a secure screen or the store's device.
Store associate or agent: Starts the request in their channel and sees the same record and the same answer.
Order desk: Decides requests outside the policy or the channel's authority in the Decision Desk.
Callvu: Prefills the cross-channel status, classifies against the one policy, applies by rule, routes and writes.

Prefill the cross-channel order
The order record with every line, its origin channel, its fulfillment path (ship from warehouse, ship from store, pick up in store, delivered) and its live status per line, the payment and any store credit, and the customer's history are prefilled from the order management system; the request is captured in the channel it arrives in with the same fields.
Classify against the one policy
The request (a line change, an exchange, a partial or full cancellation, a switch from pickup to delivery or the reverse, a store return of an online order, an address change) is classified against the one policy: the cutoff for the line's fulfillment path and stage, the product and order type exceptions, the price difference and its method, the channel's authority for the amount; the answer is the same in every channel because the policy is the same.
Decide
A request within the policy and the channel's authority is applied by rule with the customer's confirmation (on their phone, on the store's device, or on the website) and the price difference taken or refunded on a secure screen; a request outside the policy, above the channel's authority, on a flagged order or on a split order with conflicting statuses goes to the order desk in the Decision Desk with the live record and only the allowed outcomes (apply, apply with the difference, intercept at a cost, convert to a return, or decline with the reason).
Write back
The modification is written to the order management system, the system of record, once, and the store's point of sale, the warehouse's queue, the website's order view and the carrier are updated from it; the customer receives one confirmation regardless of the channel, and the channel's record shows the same result.

Where it ends: The request got the same answer in whichever channel it arrived, applied against the live cross-channel status and the one policy, decided by the order desk where it fell outside, and written once to the order management system that every channel reads. The Decision Trace shows the status, the classification and any decision; the Audit Trace shows the request's channel, the confirmation 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.

Regulations

FTC: The FTC Act Section 5 prohibits deceptive practices, and the FTC's Mail, Internet or Telephone Order Merchandise Rule governs shipment promises and refunds on cancellation for remote orders; a modification or cancellation policy applied differently by channel from the one disclosed, or a refund promised in one channel and not honored in another, is the practice these address; the one policy and the one record keep the promise consistent.
State consumer protection: The state consumer protection acts and the state return and refund disclosure laws require the policy to be disclosed before purchase and applied as disclosed, with the same terms for the same purchase regardless of where the customer asks; a store refusing what the website allows (or the reverse) for an identical order is inconsistent with the disclosed terms.
Payment and tax rules on modified orders (the card network rules on partial captures and refunds; the sales tax rules on the destination and the exchange): A price difference is captured or refunded as a partial transaction referencing the original, an exchange follows the network's rules, and the tax is recomputed for the modified lines and the fulfillment destination; the write applies them once for every channel.

Company policies

One policy, one order record and one authority matrix behind every channel; no channel has its own rules.
The live cross-channel status decides the cutoffs; the store sees what the warehouse is doing.
Exceptions are decided by the order desk with the live record, never by the channel.
The order management system is the system of record, written once and read by every channel.

Controls

Cross-channel order and status prefill.
One-policy classification with cutoffs and exceptions.
Channel authority matrix.
Rule-based application with secure price adjustment.
Decision Desk for exceptions.
Single order management write with channel updates.

Clocks and deadlines

Cutoffs by fulfillment path: The stage at which each change stops for the line's path (warehouse, store, pickup), checked live.
Refund: To the original method within the policy's period and the rule's seven working days for a cancelled remote order.
Pickup window: The store pickup hold period, with the switch to delivery or the cancellation decided before it ends.

Documents and checks

The cross-channel order with its live statuses
The request with its channel
The classification and the authority check
The confirmation and any price adjustment
Any decision and the order management record

In the Decision Trace

The status per line and the cutoffs.
The classification and the authority.
Any decision and the person.

In the Audit Trace

The request with channel and time.
The confirmation and the adjustment.
The write and the channel updates.

The handoff

Between the front doorand the back office.

The front door

A store, the website, the app, chat, phone or an AI assistant; the customer confirms on their phone, the store's device or the site.

The back office

The order desk decides only exceptions; the warehouse, the stores and the website read one record.

The Decision Desk

A request outside the policy, above the channel's authority, on a flagged order or on a split order with conflicting statuses goes to the order desk in the Decision Desk with the live record and only apply, apply with the difference, intercept at a cost, convert to a return, or decline with reason.

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 be started by the customer's server, a webhook from any system, a phone menu that texts the caller a link (Visual IVR), the Callvu AI chat, an outside AI agent over MCP, a campaign spreadsheet, a public link or an inbound email.

CAP-01 · Self-asserted · verified 2026-11-02

Callvu reads what the CRM, core or EHR already knows and prefills, so the customer only answers what is missing.

HND-03 · 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.

Will the store and the website give the same answer?

Yes. The request is classified against the one policy on the one order record with its live cross-channel status, and the answer is the same whichever channel starts it.

Can a store change an order the warehouse is shipping?

Only within the cutoff for that line's fulfillment path, checked live; past it, the order desk can decide an intercept at a cost or convert the request to a return.

Where is the change recorded?

Once, in the order management system, which the store's point of sale, the warehouse, the website and the carrier are updated from.

Related processes

Order changes and cancellations Returns and refunds Delivery address change after shipment Price adjustment and price match Compared with the alternatives Try it in the sandbox All travel and ecommerce 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.