User identifiers on store orders, and formatted redemption instructions
Order Details shows the user identifier saved at purchase, and redemption-method descriptions take formatting and links.
01 ·The client's user identifier on each new store order
In Order History, the Customer Details section of an order shows the client's user identifier on a row beneath Email, labelled with the identifier field's own name. The field is the one the community has set as its active user identifier.
The platform saves the value with the order at the moment of purchase. A client with no value shows a dash, and orders placed before this build have no identifier row.
The team fulfilling a reward can match the order to the client's account using the identifier the brokerage already works with, straight from the order.
02 ·Formatting and links in redemption instructions
When a store redemption method asks the client to type something in, the description above that field takes bold, italic, underline, text colour, alignment and links. The redemption method's own description uses the same editor. Both work wherever an admin sets up custom redemption methods, at store, category and product level, and an inherited method shows the description it follows as read-only.
Clients see the description formatted above the field, with clickable links. Translated descriptions keep their product field placeholders.
An admin can link the client to a page explaining what to enter and highlight the detail that matters, so the redemption step carries its own instructions.
In the API Log, a bulk import row opens a state panel with its status, row and batch counts, any failure reason and its timestamps, plus Refresh and Copy JSON.
6 OctEvery log under Community Settings shows the same loading placeholders, fills the available width and height, and folds roles that do not fit into a +N tag that lists the rest on hover.
6 OctConnecting Salesforce to an org without the Returning.AI app installed opens install guidance with a link to the installer, then resumes with Continue connecting.
6 Oct