Every order change leaves a trail: activity history and restore

The customer remembers walnut legs. The associate remembers changing them to oak at the customer’s request. The PO went out with oak. Both people are certain, and the sofa has become an unexpectedly effective memory test.

Start with the saved agreement and follow the changes in order. OrderPilot’s activity history, version comparison, and restore preview help the team establish what changed before deciding how to correct it. The useful outcome is a clear explanation and an authorized next step.

Read the trail before choosing the correction

A useful activity history connects a change to a person, a time, and the values that changed. Comments supply the reason when the values alone cannot. A move from walnut to oak says what happened; a note about the customer’s request explains why the associate made it.

Read status changes alongside the specification changes. The timeline can say what triggered a status move, helping you distinguish an action taken by staff from a move caused by an event in the configured process. Payment activity and signing evidence answer separate questions about money received and the agreement accepted. Treat the history as evidence to investigate, rather than a shortcut to assigning blame. A colleague may have acted on an instruction that was never attached. Another may have opened an old PDF. Find the missing connection before deciding that the person who made the edit made the mistake.

Follow the walnut-to-oak example through the order

Use this sample case to work through a disagreement. The customer originally selects walnut legs for a Madison sofa. An associate later records oak, and purchasing sends a PO showing oak. The steps below establish whether the buying instruction matched the accepted agreement.

1. Read the signed version. Open the stored signing evidence and identify the finish the customer accepted. A current quote can differ from the signed document, so use the actual saved signed copy.
2. Locate the specification change. Compare the relevant versions and identify the walnut-to-oak edit, its time, and the recorded actor.
3. Read the explanation. Look for the customer’s message, the associate’s comment, and any review of the request. An internal note is useful context; it is not the customer’s signature.
4. Check what followed the change. Establish whether the revised agreement was signed and whether purchasing received that settled version.
5. Read the vendor record. Compare the PO and acknowledgment with the agreed finish, then decide whether the vendor needs a correction.

If the customer signed oak, the team can explain the sequence from the saved documents. If the customer signed only walnut, the team needs to resolve the later change before treating oak as accepted. The signing evidence guide explains the records behind that distinction.

If the PO has already reached the maker, ask purchasing to establish whether a change is still possible. Restoring a field on the order does not establish the maker’s acceptance of a revised instruction. Keep that conversation attached to the purchase.

Preview a restore against the record as it stands

An available earlier version is a candidate for restoration, not an instruction to replace everything immediately. OrderPilot’s Restore this version preview shows what returning to that version would change. Read the whole comparison, including changes unrelated to the original mistake. In the sample order, an older walnut version might also predate a delivery-address correction. Restoring it without reviewing the comparison could put the legs right and the address wrong. Establish the intended current order first, then choose the correction that preserves the settled details.

Order restores use the normal save process and leave their own history entry. Normal checks still apply, including permissions and restrictions around the record’s current state. Purchasing and stock activity can make a past version unsuitable for replacement. When the preview explains that a version cannot be restored, use that explanation to plan a supported correction.

Restoring requires the rights needed to make the resulting changes. A person with ordinary edit access cannot use history to obtain price, cost, sales-credit, or status powers they have not been given. Set those responsibilities through the roles and permissions guide.

Keep signed evidence when the specification changes

A restore cannot turn an old agreement into proof that the customer accepted a different current order. OrderPilot preserves the signed evidence and applies the normal signature rules to customer-facing edits.

If putting walnut back changes the customer-facing agreement, the current signature can be invalidated and the revised version needs signing through the store’s required process. The earlier signed record remains part of the evidence. This is why a manager should inspect both the proposed restore and the signed copy before proceeding.

The change-order and re-signing guide follows that handoff in more detail. Finish the correction by bringing the customer agreement and vendor instruction into alignment, with the decision and responsible person recorded.

Use the same discipline on POs, templates, and settings

OrderPilot’s Activity card also appears on purchase orders, product templates, options, and settings. Those records matter because a problem can begin before an associate creates the quote. A mistaken template change can affect later work, while a settings change can alter how the team handles orders.

Read the record that owns the disputed decision. If the question is what the vendor received, inspect the PO. If the question is why a choice appeared in the catalog, inspect the template and options. If the question is why an order moved, inspect its status history and the configured process. Keep the distinction between current catalog choices and the saved sale. Updating a template’s price does not automatically reprice saved quotes. A catalog correction and a customer-order correction therefore need separate consideration.

Read the warning when two colleagues have the order open

OrderPilot’s Admin order page shows who else has the record open and warns when it has changed since the version on your screen. Reloading can keep compatible edits instead of silently overwriting someone else’s work. Pause at that warning. If purchasing has just corrected the vendor and sales is adjusting the finish, each person needs to understand the other change before saving. A quick conversation can settle an ambiguity that a merge of fields cannot.

POs also refuse stale saves. The two-people, one-order guide explains how to continue work after another colleague saves. The shared aim is a current record that reflects both people’s valid decisions.

Use history for coaching and exception review

Review a mistaken edit privately with the person who made it. Ask what they believed the action would do and what information they had. The answer can reveal a missing instruction, an unclear handoff, or a training exercise worth repeating.

Exception review serves a different purpose. An owner can inspect unexplained price changes, unusual status moves, and corrections around payments, then compare them with the supporting records. Activity history is one part of that review, alongside permissions and reconciliation.

A 2024 FOX Carolina report described deputies’ allegations of forged contracts in a furniture-store investigation. It is a reason to examine supporting documents, not evidence that software history alone prevents misconduct. The internal-fraud controls guide covers the wider checks.

Write comments that explain the decision. “Changed finish” repeats the comparison. “Customer requested oak in the attached message; purchasing is checking whether the maker can accept the change” tells the next colleague what remains unresolved.

Ask these questions before closing a dispute

Close the review when the evidence answers the agreement, the change, and the next action. Keep this short checklist with the order desk:

• What did the customer sign?
• What changed after that agreement?
• Who made the change, and what supported it?

Then record the resolution and who will carry it out. A readable history should let the next colleague explain the outcome without reopening the argument. Continue with signing evidence and the accepted agreement when the dispute turns on which version was approved.

Questions

Can someone delete the history?

The ordinary record Activity tools provide viewing, comments, comparison, and restore; they do not offer a control for clearing the recorded change trail. That is not a promise of permanent, tamper-proof storage. Keep the signed and financial records your store needs through its recordkeeping process.

Do changes made on the POS iPad appear too?

POS shows the order’s activity and comments, including recorded actions from the shared order. That does not mean every POS action has a restorable Admin version. Inspect the available trail and restore warnings; the changed-since banner described above is an Admin feature.

How far back does the history go?

Use the versions available on the record. The product sources do not establish a fixed record-history retention period, so there is no supported number of months or years to promise. The separate Staff & roles access Activity log is a different record.

Sources

1. Furniture-store investigation involving alleged forged contracts — Anisa Snipes, FOX Carolina, October 25, 2024.