A change request after signing, start to finish

In the third week after signing, Jordan sends a message: “We repainted. Can the legs be black instead of walnut?” The sofa PO went out on Monday. The customer, salesperson, buyer, and vendor now need to agree on what that sentence will change.

This illustrative order at the invented Linden & Oak showroom follows the Madison sofa purchased from sample vendor Atelier Nord. The reliable sequence is vendor check, recorded decision, revised customer agreement, renewed signature, and accepted PO revision. OrderPilot keeps those decisions connected while the people responsible make them.

General information, not legal advice.

1. Keep the request attached to the actual option

Jordan opens the portal from the store's order email and pins the change request to the leg-finish option. The request identifies the affected choice, with the available alternatives coming from the product's offered options. The current sale does not change by itself. That distinction protects the purchasing instruction. The portal is a place to ask for the change, not a remote control for work already at the factory. A valid catalog option can still be unavailable for this particular order's production stage.

Use questions pinned to the exact quote line when the customer needs to explain what they mean. The team should not have to infer whether “black instead” refers to the sofa legs, a table, or the lamp in an earlier conversation.

2. Assign the decision before replying with a promise

The shared Inbox brings the request into the team's work. Dana takes ownership and leaves an internal note for purchasing: the PO has been sent, so check the vendor before agreeing. The customer gets an acknowledgment of the request, not an immediate confirmation that the finish has changed. One owner can coordinate several people's input. Dana handles the customer's choice; Priya handles the vendor commitment. The portal-to-Inbox change guide explains how the conversation stays with the sale while staff decide the next action.

If another associate covers the message, the internal note makes the hold visible. They can tell Jordan the team is checking feasibility without accidentally promising the same change Priya is still asking the factory to assess.

3. Ask the vendor what is still possible

Priya replies on the PO conversation with the exact requested finish change and asks for its effect on cost and timing. The vendor answers against the purchase it already has. With reply capture configured, the response stays on the PO with any attachment. In this example, the vendor can make the change and quotes an $80 addition with no revised delivery expectation. Those terms belong to this sample decision. Another production stage or finish could produce a different answer.

If the fabric has already been cut, establish whether that fact affects the requested work. A leg finish and a new sofa length have different production consequences. Do not convert “fabric cut” into a universal refusal of every possible change, or assume every change is possible because one component is untouched.

When the vendor cannot accept the request, Dana explains the specific reason and the options the store can offer under the agreement. A clear decline is more useful than leaving the customer expecting a change that the maker has refused.

4. Apply only the change the customer has agreed to

Dana presents the confirmed $80 addition and the unchanged timing to Jordan. Once Jordan agrees, Dana accepts and applies the request to the order. The sale now identifies black legs and the revised total, with the decision visible in its history. If the vendor instead proposes a later date, the customer needs that consequence before agreeing. Keep the price, specification, and delivery expectation in the same decision. A customer saying yes to black legs has not necessarily agreed to another month without a sofa.

Staff can initiate a proposed change too, such as a substitution after a vendor discontinues a finish. That does not remove the need for customer review of the changed agreement. Present the reason and alternatives, apply the accepted result, and obtain the required signature before treating it as released.

5. Renew the signature for the customer-facing revision

Changing the leg finish and selling price changes what the customer is buying. OrderPilot invalidates the current signature and asks for a new one where required, while keeping the earlier signed record. Relevant open questions and requests need to be settled before signing proceeds. Not every edit requires a new signature. An internal note or a vendor change that does not alter the customer-facing agreement is different from a new finish, size, price, or customer term. Review the effect of the edit rather than assuming every save needs another customer action.

The mid-production re-signing guide covers the broader process. The earlier signature remains part of the history; it does not authorize the newly revised configuration.

6. Revise the purchase and obtain the vendor's acceptance

Priya edits the supported still-unreceived PO line, reviews the revised PDF, and resends the purchase. The document identifies black legs and the accepted buying terms. She then keeps the vendor's confirmation that the revised instruction has been received and accepted. Only supported unreceived lines can follow that sent-PO edit path. If goods have already been received, the team needs the appropriate correction or replacement process. Do not erase a receipt to force a finished purchasing event back into an editable state.

The editing and resending a sent PO guide explains that boundary. The buyer's activity history records the edit, but a saved record is not the same as the vendor agreeing to stop the previous instruction.

Keep the sample finishes distinguishable through the handoff. Walnut and black are clear here. With more elaborate vendor color names, the buyer should also carry the correct identifier; “Evening” can be a finish, a fabric, or the time someone finally answers the phone.

7. Reconcile the balance without rewriting the deposit

The original customer deposit remains a completed payment. Suppose Jordan's sale was $4,800, with $2,400 already paid. The agreed $80 addition makes the new total $4,880 and the outstanding balance $2,480. The historical receipt stays $2,400.

If the store collects the difference immediately, use the supported payment route for the order's state and reconcile any open requests first. Otherwise, make the revised balance clear under the agreed payment schedule. A revised quote should not leave the customer with an old payment request whose amount no longer fits the sale.

Dana checks the signature, PO confirmation, and balance together before closing the request. That gives the next colleague a complete result: black legs approved, revised purchase accepted, and the correct amount left to collect.

Keep delivery promises aligned with the revised agreement

A documented change matters at delivery as well as in the workshop. In New Jersey, the household-furniture rule for future-delivery sales says that damaged goods or goods that do not match the contract's specified size, style, color, or condition do not constitute the required delivery; it also gives the customer choices on receiving such goods. See N.J.A.C. 13:45A-5.1(e), in force for this article's May 2025 setting.

The same rule addresses notice when the promised date cannot be met. This is a New Jersey rule, not a statement of every jurisdiction's requirements. Check with your attorney when setting the store's change and delivery terms, including how revised dates and customer choices must be documented.

OrderPilot keeps records of the agreement and changes; it does not guarantee legal compliance. The practical benefit is that the salesperson, buyer, and delivery team can identify the version the customer is expecting.

Set a review policy by production stage

A useful change policy explains the review required at each stage without promising a result before the vendor responds. The store can define fees and cutoffs in its terms, but those terms need to fit the product, agreement, and governing requirements.

Do not make “free before PO” or “impossible after cutting” a universal promise. Use a clear review process and tell the customer the actual result. Continue with one sofa from showroom to living room for the surrounding order history.

Sources

1. N.J.A.C. 13:45A-5.1, delivery practices — New Jersey Administrative Code, Cornell Legal Information Institute; subsection (e) on nonconforming goods and subsection (a) on promised delivery dates, last listed amendment effective January 17, 2012.