What you write on the order during a dispute becomes part of the record

Choose the audience before composing the note

WooCommerce's order-page documentation distinguishes system notes, private notes and customer notes. System notes can record payment results and stock changes. A staff member's private note belongs to the internal order record. A customer note is an outgoing email, even though staff write it from the order administration screen. The location of the editor does not determine the audience; the selected note type does.

Before saving, identify whether this entry is a buyer update or an internal handoff. Check the selected type and the order it belongs to. An internal investigation may need the provider case reference, the colleague responsible and a question still awaiting an answer. The buyer needs the relevant confirmed status and what the business will do next. Do not paste the entire internal handoff into a customer note simply because it is easier than composing an accurate update.

Separate observation, report, assessment and commitment

A reliable note identifies the source and time of the fact. Distinguish what the provider record shows from what the buyer reports, and both from a staff member's interpretation. A suspicion is not an established event. If an assessment is necessary to the investigation, record its factual basis and what would confirm or disprove it. Avoid accusations, sarcasm and statements about motives that the records cannot establish.

A promised action needs its own wording. Record who authorized it, who will perform it and whether it has merely been agreed or has actually happened. For a refund update, use the observed provider status; do not turn a support promise into a claim that funds arrived. For a provider conversation, retain the original communication and summarize its scope faithfully, including any unresolved qualification. A support representative's explanation is not an issuer outcome.

Evidence references should point authorized colleagues to the original record without copying unnecessary personal or payment data into the note. Keep secrets, card numbers, authentication codes and full bank details out of order notes. Restricted source records should remain in the merchant's authorized systems.

Write the buyer's update from the same facts

Build the customer message around the issue the buyer raised, the status you have verified and the next action your team owns. If a fact is still being checked, say which point remains unresolved. A follow-up time is a commitment to communicate again, not a prediction that the issuer will decide the dispute or that money will arrive by then. Only include a follow-up commitment the responsible person has accepted.

Internal and customer versions can differ in detail while remaining consistent in meaning. A customer update can omit staff assignments or internal document locations without denying an unresolved fact. Do not give the buyer certainty that the internal record explicitly lacks. Check the previous outgoing message before sending another, especially when several staff members have spoken about a refund or shipment.

Before choosing Customer note, read the text as a message the named buyer will receive. Confirm that it concerns that buyer's order, contains no other customer's details and makes no unsupported promise. If the message is unsuitable because it is inaccurate or accusatory, changing it to Private does not repair the problem. Correct the wording and preserve any existing record under the business's actual record-retention policy.

Preserve corrections and keep the dispute response separate

Stripe's dispute-response guidance says to retain communications. Preserve original inbound and outbound messages, their dates and the record of subsequent corrections. When staff discover that an earlier note was wrong, add a dated correction that identifies the earlier statement and the evidence that changed the understanding. Do not backdate an entry, erase a contradiction or relocate material to make the dispute history misleading.

A WooCommerce note is not itself a submission to the issuer. Stripe describes a limited response window and a response that can be submitted once and cannot then be edited; the issuer decides the outcome. The person responsible for that submission must use the actual case deadline and the relevant records. A continuing buyer conversation does not replace that work.

If the recurring problem is that order controls or customer messages make the record inconsistent, use Prism's checkout-review consultation to describe the platform, the note types involved and the observed mismatch. Confirm the requested communication or dispute-support responsibilities, scope, fees and terms before work. Keep the public inquiry to a non-sensitive description; do not attach the customer conversation or dispute file.

Note-visibility decision sheet

Use this before the next entry on one real disputed order. In the final column, record the chosen audience, the evidence check and the responsible role. Keep original messages and case references in authorized systems; enter only non-sensitive findings here. An unresolved assessment must remain unresolved in both internal and customer wording.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.