For the complete documentation index, see llms.txt. This page is also available as Markdown.

Order notes

Attach notes to an order, who they are attributed to, and how they differ from product info.

An additional note is free text attached to an order — what the customer asked for, what was agreed, why something was discounted. Notes are attributed and timestamped, so an order carries its own history rather than relying on whoever happened to serve the customer.

What a note records

Note

The text itself

Author

The user who wrote it, by name

Created / modified

When it was written and last changed

Notifications

Any notifications raised from the note

Because a note carries its author and timestamp, it is the right place for anything that might be questioned later — a promised delivery date, a verbal agreement, the reason behind a manual discount.

Notes are not the same as product information

Three different things put text in front of people, and they are easy to mix up.

Attached to
Who sees it

Order note

One order

Staff working that order

Internal info

A product

Staff, every time the product is sold

External info

A product

The customer, on the receipt or offer

If the same sentence needs saying on every sale of a product, it belongs on the product as internal or external info — not copied onto each order. See Product fields reference.

What this means for you

  • Write the why, not the what. The order already records what was sold. It does not record that the customer agreed to collect on Friday.

  • Use a discount reason code for discounts, and a note for the story behind it. The reason code is reportable; the note is not — see Discounts on an order.

Limitations

  • Notes are free text and are not reportable. Anything you need to count or filter on needs a structured field instead.


Last updated 19.09.2026

Was this helpful?