DBC: Promotional Personalization

PROMO Personalization Item Configuration

Follow the PROMO Workflow procedures with the addition of the following Personalization steps outlined in this section.

Note: Batch ordering DOES NOT work with promo personalization.

You will use the following data on the Variants tab later to create actions within your Chili template:

  • Vendor Variant Code
  • Vendor Option Code

Setting up a CHILI Document for Personalization Item Overview

A Chili document is used to display the personalization fields and is set up slightly differently than your traditional Chili customization items. Below is the list of areas that will be used as well as how set them up correctly for promo personalization.

Pages > Page List:

You will at least have two pages in your Chili document. The first page will always be the end users view of the item that they will see within their DB Commerce site. If you have multiple views of an item, this will be controlled by layers and will still reside on page one. The second page and any additional pages will be received by the vendor. The system is automatically designed to remove page one, so it’s not received by the vendor.

Document > Document Settings:

The document will be set up to the page height and width of 7.75 x 7.75, so it fits within the promo personalization widow. Any document set to a different page height and width will not display correctly within the promo personalization window.

Document > Layer List:

Layers will be the various views of your item. You will at least have two layers in your Chili document. A layer for the view to the end user and a layer for vendor information. It is recommended that you name your layers according to the end user view(s), for example, Chest, Sleeve, Back, etc. and layer to the Vendor Info.

Each layer will contain the necessary data to be displayed. The layers shown to the end user may see images and personalization fields. The layers shown to the vendor may only contain personalization fields.

Variables:

You will have two kinds of variables. Variables that will be used for the end user to enter their personalization as well as variables that represent your variants that will be used to create actions.

Variables for Personalization:

  • Only short text variables are valid.
  • The Name is the name of your personalization field.
  • The Display Name is the name of your personalization filed seen by the end user.
  • The required permission is valid to make use of.
  • The Max. Characters are valid to make use of and recommended to set on each personalization field.

Variables for Variants:

  • Each variant when selected that will show a change to the end user will have an equivalent variable.
  • The variable equivalent to the variant will need to have the same code that is defined under the Variant tab for the "Vendor Variant Code."
  • When an end user selects for example a color and begins entering a value in the personalization filed, based on the action the end user will see these changes happen.
  • When creating an action and referencing for example a specific color, the “displayValue” referenced in the action will need to have the same code that is defined under the Variant tab for the "Vendor Option Code."
  • If an image will change for example a color, an image variable will still be needed and applied to your images and will be referenced in the actions.

Actions:

Actions will be applied to your variant variables to show a change. For example, if the end user selects a color from the variants and begins entering a value in the personalization filed, based on the action applied the end user will see the colors change according to their selection.

This action is changing the color of the hoodie. It’s saying when the variable COLOR value is I (Indigo) set the variable "COLOR_CHEST_IMAGE," "COLOR_SLEEVE_IMAGE," "OVERLAY_SLEEVE_IMAGE," and "COLOR_BACK_IMAGE," to show the Indigo hoodie. The file location for these images is referenced with the image path. Based on the personalization filed the end user is on, they will see the correct view of the hoodie.

This action is changing the text color of the hoodie. It’s saying when the variable SCREEN value is B (Black) set the color ScreenColor, to the color value of black on the hoodie. When the variable SCREEN value is W (White) set the color ScreenColor, to the color value of white on the hoodie. The change of color in this example is breaking out the CMYK values of black and white.

Workspaces/View Preferences:

You will not be able to set a workspace/view preferences for promo personalization items. DemandBridge has set up a predefined workspace and view preference named Promo set up as your distributor default.

Note: DO NOT MODIFY. If you accidently have modified either, please contact DB Support.

PROMO Personalization Item Overview

Personalization

General Settings

Once your Chili Document has been set up and saved within Chili Backoffice, you can Associate a Chili Document with your promotional item. Once on the Personalization tab, simply click “Associate Chili Document,” a pop-up window will appear displaying a list of your Chili Documents, and you can select which Chili Document to associate with your promotional item.

This follows the same workflow you see under Work with Items > Chili Admin, when associating a Chili Document to an item code for customization.

Once the Chili Document has been associated, you will see a preview of the Chili Document, the "Chili Document Name," and have the ability to delete the document and reselect. You will also have a Personalization State of “Active” or “Inactive.” This will allow you to deactivate the Personalization if needed while working on or making necessary changes to the personalization areas.

Personalization Fields

The Personalization Fields are where you will select what Chili Variables to display to the end user for personalization. You will select from a dropdown, “Select Display Name,” that contains all your variables set up within your Chili Document.

"Display Name," "Variable Name," "Max Character Count," and "Required Field" are all values set up within Chili Backoffice but presented as informative read only fields to the administrator.

The order in which Personalization Fields are listed within the Promotional tab under the Distributor Admin interface is the order in which they will display to end users when viewing the item detail page on a DB Commerce site. To manage the display order for items containing multiple personalization fields, administrators can hover over a personalization field, click the widget that appears to the left of its header, and drag the personalization field above or below other the personalization fields as desired.

Note: This is the same action when ordering variants.

Personalization Field Markups

When configuring personalization, administrators may also apply a "Field Markup Cost" and Sell if applicable. End customers shopping for items on DB Commerce sites will only be privy to Sell prices, so if it is desired to pass an additional cost based on how many fields you personalize, regardless of which fields those are, the way to do so would be to apply a Sell Modification.

Live Preview

The Live Preview is the thumbnail that shows at the beginning of your media images when you click a personalization filed. Here you will upload an image the represents that area of personalization, as this image will not change based on the variants selected and/or the personalization fields that are entered.

Select Chili Layer: Select a chili layer that will display based on the end user's selection of the live preview image or value entered into the personalization field. In most items, you may only have one Chili layer showing one area of your item. In some items where you wish to show multiple views of that item, you will have multiple live previews.

Static Thumbnail: Upload an image that represents this area of personalization.

Note: This image will not change based on change based on the variants selected and/or the personalization fields that are entered. To avoid confusion by the end user, you may choose to use neutral colors for your static thumbnail images.

Personalization Field Tags: This dropdown displays a list of all the variable set up in your Chili document. You will want to “tag” the variable(s) that show on the Chili layer you have selected above. When a personalization field is entered, the end user will see the correct layer and static image in which the personalization resides.


PROMO Personalization User Experience

It was our goal to carefully retain the user experience for basic promo variant selections and extended that with the addition of personalization fields. Below are a few things to note that will be different than a traditional customized Chili item.

  • The end user will not View Proof like other customizable Chili items.
  • The end user will not be able to Edit a promo personalization item from cart.
  • The end user will see the personalization fields appended after item description in the cart (this is not set by using "Line-Item Descriptors" but automatically appended by the system. Line-Item Descriptors are not valid with promo personalization items).
  • The end user will receive an order confirmation email, but it will not contain a .pdf proof of the promo personalization item.

PROMO Personalization Vendor Experience

The vendors Print Order Request hasn’t changed from what they typically have seen in the past. Their email will still contain a "High Res PDF" file along with the personalization field(s). This information will appear below the item specifications. Service vendors can still be used with promo personalization items.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.