Create Custom Messages in Point of Sale

Customize messages that appear on different screens based on different events.

Set up Customizing Messages in CMS

By default, the user can see default messages from different groups. The user can then customize those messages using the CMS.

Create a Customized Message

To create a message:

  1. In CMS, go to Store Management > Custom Messages.
  2. To create a custom message, select CREATE in the top right of the screen.
  3. Enter a message key and a custom message.
  4. Select Save.The Custom Messages screen in Point of Sale CMS, where you can create or edit a ustom message.

Edit a Custom Message

To edit an existing message:

  1. Select the pencil icon to the right of a message.
  2. Turn on Customize Message.
  3. Enter a custom message.
  4. Select Save.

Field Mapping Message Key Field Transformation | Custom Messages

Field mappings in CMS include field transformations. For example, using the To Uppercase field transformation "transform" the lower case colors to capitalized colors. For example "blue" transform to "BLUE", "red" transform to "RED", and so on.

There are many types of field transformations, one of which includes Message Key. With this method, rather than manually entering a custom message, the message instead shows automatically using key-value pairs.

To use the Message Key field transformation:

  1. In CMS, go to Feeds > Field Mappings.
  2. Select the area you'd like to add a custom message.
  3. Select the green line associated with a Source Field.
  4. Select Message Key under Transformation Type.
  5. Fill in the fields and select SET.
  6. Select SAVE in the top right of the screen. The Field Transformations section of Custom Messages in Point of Sale CMS.

The Message Key field transformer has two optional transform parameters: Message Key Separator and Default Message.

Let's say you have a string of message keys, "order.failure|promocode.redeem.failure". Notice that a pipe (|) separates the message keys. This is the Message Key Separator because it's separating the many keys in a string. If the message keys are split for each message key, Salesforce looks up an entry (value) for it in the brand's custom messages. If no custom message is found, the message key itself is used as the message. Additionally, if the message key is blank, then the message to be displayed is whatever you entered in the Default Message field.

After all messages are retrieved for the given keys, the messages are recombined into a single string with the Message Key Separator separating them. This string is what is stored in the target field.

Key Is it in the system? Value
order.failure Yes Your order has failed!
promocode.redeem.failure Yes Your promotion code is invalid!
order.partial No Order.partial
Blank Not applicable because there's no key Default message

A string of message keys:

"order.failure|promocode.redeem.failure|order.partial| "

Final result:

"Your order has failed!|Your promotion code is invalid!|Order.partial| Your order cannot be processed at this time."