Two people, one order: editing without overwriting each other

The associate adds two throw pillows while purchasing changes the vendor on the same sofa order. Both have been working from the version they opened earlier. Without a check, one save could quietly replace the other person's work.

OrderPilot's Admin Edit page shows who else has the record open and notices when it has changed elsewhere. Staff can reload the current version while keeping compatible unsaved edits, then review the result before saving. The aim is to preserve the work and make any remaining decision visible.

Notice the other person before a large edit

The presence indicator on the Edit page shows other staff who have the order open. Use it as a prompt to coordinate changes that affect the same specification or commercial decision. Someone viewing the order may only be answering a question, but it is useful to know they are there. Agree who is changing what when the work overlaps. Presence does not mean the page is locked to everyone else, and it does not decide which proposed finish the customer wants. The record and the conversation still need an owner.

The behavior shown here is the Shopify Admin editor, not a promised presence or merge interface in Shopify POS on the iPad. For work moving between POS and the desk, coordinate the change and reopen the current record before continuing.

Read the changed-since notice

When a saved change makes the open copy out of date, OrderPilot explains that the quote or order changed since it was opened or last saved. Saving pauses so the older page cannot silently replace the current record. Use the page's reload action. It brings in the current version and puts back unsaved changes where they do not clash. The result explains which edits were kept and which were not. Inspect it before pressing Save; reapplying compatible edits to the form is not the same as saving them.

That distinction matters on a long furniture quote. The pillows may still be in the form after reloading, but staff should check their quantity, configuration, and the rest of the order before treating them as part of the saved sale.

Resolve a conflict as a business decision

A conflicting edit is one the editor cannot safely put onto the current version without replacing another change. Two different choices for the same finish are a clear example. A changed or removed line can also make an earlier unsaved edit inappropriate.

If sales changes walnut to oak while purchasing works on the same affected line, read the explanation and compare the current version with the intended change. Ask which choice the customer approved and whether the vendor has already committed to it. The latest click is not a good way to choose a leg finish.

Compatible changes are different. An added item and an unrelated note may be retained together where the editor can reconcile them. Still read the result; the banner describes what happened on that particular order rather than making a blanket promise about every simultaneous edit.

Purchase orders also refuse a save from an out-of-date copy. Reopen the current PO, compare the vendor commitment, and make the intended update against the version the team now shares.

Find the existing record before creating another

Search first when a colleague may already have started the quote. Partial search can match words in a different order, phone numbers typed differently, and product names or SKUs on any line. Searching “sofa madison” can find the sample quote without remembering its exact title. Check active filters too. A colleague's quote may be outside the current salesperson selection. The tags and filters guide helps distinguish a missing record from a narrow list.

Let autosave pause when the record needs attention

Quote autosave is optional, off by default, and begins after the first manual save. It does not remove the need to resolve a stale copy. A conflict stops autosave until the record is reloaded.

After reloading with kept changes, inspect the form and complete the manual save requested by the editor. The autosave and quote-details guide explains the wider routine. An automatic save should reduce lost typing, not replace checking the agreement.

Use history when the question is what changed

The Activity card keeps changes, timing, and staff attribution where available, alongside comments and earlier versions. Use it to establish what happened before deciding how to correct the order. Restore provides a preview of an earlier version; review it against the current sale and the restrictions protecting signed evidence and purchasing commitments. It is not a way to erase a vendor action or retrieve furniture already delivered. The history and restore guide covers that recovery process.

Keep a named owner for the order, record decisions in comments instead of side conversations, and check presence before substantial edits. The status map can organize the next work, while those habits keep the people doing it aligned.