Change requests without the email chaos

The text arrives at 9:47 p.m.: “Can we do the 96 instead?” By morning, sales thinks it means the wider sofa, purchasing thinks it means fabric 96, and the customer means the wider sofa in the other fabric. The number has traveled further than the meaning.

A change request needs one place to live, with the current choice, requested choice, decision, and revised agreement together. OrderPilot carries that conversation from the customer portal into staff review and back to the customer before the changed specification reaches the maker.

General information, not legal advice.

Make the request specific before saying yes

Pinning a change to an item or option removes the first ambiguity. The customer requests the different size on the sofa's size option, or another offered fabric on its upholstery option. Staff can see what is being replaced and what is proposed.

The portal offers customer-facing values from the product template and checks measurement requests against its allowed range. An off-menu idea belongs in a question for staff to investigate. The request is a proposal, not a direct instruction to the factory. That separation leaves room to price the change and establish whether it is still possible. Specifications matter beyond keeping the work tidy. In New Jersey, furniture that doesn't match the contract's size, style, color, or condition doesn't count as the required delivery under N.J.A.C. 13:45A-5.1(e). A recorded change helps establish what the agreement actually became.

The portal review guide explains the customer's tools. For the store, the first response is straightforward: acknowledge the exact request and explain who is checking it. Avoid a casual “done” while purchasing is still waiting for the maker.

Give every request a decision owner

The shared Inbox brings the request into a conversation with the order beside it. Staff see the current and proposed values, then accept, decline, or use Apply in quote as appropriate. The person responsible should settle both the specification and the consequences, even when a buyer or manager supplies part of the answer. Use this sequence as the shared working pattern:

Acceptance and completion are different events. Accepting a request means the store will work on the agreed change. The order record still needs to be updated, the customer needs the revised version, and any vendor commitment needs attention.

If the request arrived by phone, write the precise change into the order workflow and send the updated quote. Include a short recap of the call in the conversation. The customer's channel doesn't remove the need for an agreed specification. A friendly telephone call should leave a readable result for the colleague who wasn't there.

Handle unsigned and signed records differently

On an unsigned quote, a change request moves the quote to Changes Requested and signing waits while the open work is settled. Staff can review the request before the customer signs something that is already under discussion.

On a signed quote or placed order, a request doesn't move the order immediately. Staff acceptance starts the change work and moves the record to Changes Requested. Once the work is finished, Mark resolved or Done with changes supports returning it to its previous stage. Follow the record's actual available action rather than treating the request itself as completion. Only customer-facing changes invalidate the signature. A change to the furniture specification, price, or customer agreement needs the revised record reviewed and signed where required. An internal detail that doesn't change what the customer agreed to doesn't automatically require another signature. The earlier signed record remains available.

That keeps signing meaningful. Customers shouldn't be asked to approve routine internal housekeeping, and staff shouldn't rely on an old signature for a different sofa. The mid-production re-sign guide covers that agreement boundary in more detail.

Send a revision the customer can understand

The updated-quote email can explain what changed so the customer doesn't have to compare two long documents unaided. Name the affected piece, the old and new choices, and any price or timing consequence. Explain the changed total in the message that accompanies the attachment. Say an illustrative sofa order totals $3,000 and has $1,200 paid. An agreed wider frame adds $300. The revised total is $3,300, and the remaining balance becomes $2,100. The deposit is still $1,200 received; it doesn't become a different receipt because the order changed.

If a different choice lowers the total to $2,800 instead, that same paid amount leaves $1,600 outstanding. Where payments exceed the revised total, reconcile the excess and agree the refund or other lawful resolution. Don't erase a payment or create a second receipt to make the arithmetic look tidy.

Payment requests and customer pay links wait while blocking change requests are open or changes have been applied but not yet sent. Finish the revision and communicate it before collecting against the updated amount. The revised-quote guide shows how to make that customer handoff clear.

Get the vendor's agreement as well

A revised customer order doesn't prove that a maker has changed its production instruction. If the PO has already gone out, purchasing needs to establish whether the affected work can still be changed, then edit the supported unreceived lines and resend the revised PO. Keep the maker's acknowledgment on the PO. With reply capture configured, the vendor's reply and attachments stay with that purchase order. Compare the acknowledgment with the revision: size, fabric, finish, quantity, cost, and timing. The correct customer quote and an outdated factory order are still a mismatch.

When the maker says cutting has started, tell the customer exactly which change is unavailable. Offer only alternatives the store can actually support, such as keeping the accepted order or discussing a separately priced replacement arrangement. Don't describe the request as accepted and hope the vendor will become more flexible tomorrow.

Set change cutoffs by vendor and production stage. “Before cutting” is a practical milestone when the maker uses it; a universal number of days copied from another store isn't. Record the maker's answer, including when the cutoff was reached.

Write a policy the team can apply

A change policy should explain the decision process without promising that every request will be possible. Late-change fees are a store policy, not an automatic OrderPilot rule. A named fee can document an agreed charge, but the terms and local law determine whether the charge is appropriate. Check with your attorney before adopting the policy.

A starting paragraph for review:

Please send change requests through your order conversation or contact your sales associate. We will check the maker's production stage and explain any price difference, change fee, or revised timing before proceeding. Changes take effect after we confirm they can be made and you accept the revised agreement. Customer-facing revisions require a new signature where requested. Once the maker has passed the stated change cutoff, some changes will no longer be available.

Adapt the cutoff and fee language to what the store actually offers. The swatch book can hold an impressive number of alternatives; the accepted order should still identify one.

Keep the customer portal as the place where the customer sees the settled result. For a complete example after acceptance, follow a change request after signing.

Sources

1. N.J.A.C. 13:45A-5.1: Delivery practices — New Jersey administrative regulation, amended January 17, 2012; Cornell Legal Information Institute.