Brand identity: set your logo, colors, fonts and tone
The Brand Identity tab holds the colors, fonts, tone and assets that Commander uses when it generates creatives and copy. Open it at Settings > General > Brand Identity.
When you add a brand, the brand form fills its Brand Identity step from your website. The logo, colors and fonts you keep there, and the tone you pick, become the first values on this tab. You can change them here at any time.
Save your changes
The page has no Save button of its own. When you change a field, a save bar appears with Save and Discard. Click Save to keep your changes. Click Discard to go back to the last saved values.
If a save fails, the page shows a red message that starts "Couldn't save brand settings:" and gives the reason. Fix the reason, then click Save again.
If someone else saved brand settings while you edited, Commander shows a notice. Reload the page, then make your changes again.
Brand name
Type your brand name in the Brand name field. Commander renames the brand when you click Save.
In Demo Mode, the rename does not save. The page shows the red message "Couldn't save brand settings: Disable demo mode to manage brands".
Brand logo
Click the logo picture to upload a file. You can also drop a file on it. The upload control shows the accepted formats (PNG, SVG or JPG) and the maximum size, 500 KB. If the file is too large, Commander shows the size of your file, followed by "Maximum file size is 500 KB." If the file has another format, Commander shows "Unsupported file type" followed by the type.
To remove the logo, click Remove logo, then click Remove to confirm.
Two checkboxes control how Commander uses the logo:
- Embed logo on creatives places your primary logo in a corner of every creative that Commander generates. When the image Commander generated already shows your logo, it is not added a second time. Turn the setting off to get creatives without a logo. You can still add one by hand in the Studio editor at Layers > Add logo.
- Use a dark logo on dark backgrounds switches to your dark-background logo when a creative has a dark background. This box is available only when Embed logo on creatives is on. Without a dark-background logo, Commander keeps the primary logo.
Under Dark-background logo (optional), upload a reversed version of your logo. Use light artwork that stays readable on dark creatives.
Color palette
The palette has three colors: Primary, Secondary and Accent. For each one, use the color picker or type a hex value in the form #RRGGBB. Commander also accepts a short value such as #fff.
Commander uses these colors as fallback colors in generated creatives.
INFO
A blue notice says "These are placeholder colors" when Commander has not found your brand palette. Generated creatives use the placeholder colors until you change them. Edit any color and save to set your palette.
The notice goes away when Commander finds your palette, or when you edit a color and save. While you edit a swatch, it hides at once.
Typography
Open the Typography section to choose fonts. It has three lists: Heading fonts, Body fonts and CTA fonts. Search a list, then tick the fonts you want.
In each list, one font is the primary font. The first font you pick becomes the primary. To change it, click the star next to another selected font. The selected fonts lead the font list of the Studio editor, in a group of their own above Your fonts. The description under Typography reads "Pick the brand fonts for each role. The starred heading and body fonts also set the fonts on your landing pages. The starred primary seeds new design sets, and the selected fonts appear under “Brand fonts” in Creative Studio."
The lists hold the fonts Commander found on your store, then web fonts. The fonts from your store come first, under Your fonts, and each one has a small label that says where Commander found it: Theme, Google, Shopify library, Adobe, Uploaded, Ad match or Your store. A licensed brand font such as Avenir is in the lists only when your store uses it. Otherwise, searching the name shows the closest font the lists do hold, and the row reads "Closest to" the name you searched. Tick that row to use it. For a name Commander does not know, the list stays empty.
A font that ads cannot draw as it is, such as a licensed store font, stays in the lists and shows Ads use a similar font beside it. A font your store no longer has stays in the lists and shows No longer found on your store beside it.
Your fonts
Under the three lists, the Your fonts card shows the fonts Commander found on your store or in your ads, and the fonts you uploaded. It says "Found on your store, in your ads or uploaded by you. They appear in your font lists." Each row tells you the font's name, the weights Commander found, where it found the font, and what your landing pages do with it.
The card reads your saved settings. While the form holds unsaved changes, the card says "This card shows your last saved heading and body fonts until you save your brand settings". Click Save in the save bar and the card updates.
The card then gives one line about your landing pages, and the line depends on whether one of your fonts is really on the page. These are the lines:
- At least one of your heading and body fonts is on your page: "Your landing page uses your heading and body fonts. The other fonts here aren’t on it. Set them with the star in Heading fonts and Body fonts above."
- You chose a heading or body font but none of them is on your page: "Your landing page uses your theme’s fonts. None of the fonts here are on it."
- You picked neither: "You haven’t picked a heading or body font, so your landing page uses your theme’s fonts. Set them with the star in Heading fonts and Body fonts above."
When the card has found a font in one of your ads that your page draws, the line adds "plus the best match from your ad", or "plus 2 best matches from your ads" for two. In that case the line drops the sentence that says the other fonts aren’t on the page.
You can pick a font that Commander already knows, such as a Google font that your store has never used, and so is not in the list on the card. The card then adds a line under its first line. For a font your pages load, it reads, for example, "Headings on your landing pages use Poppins, loaded from Google Fonts" or "Body text on your landing pages uses Lato, loaded from Google Fonts". When both use the same font, it reads "Headings and body text on your landing pages use Poppins, loaded from Google Fonts". The end of the line can also say "loaded from Commander’s copy", "loaded by your theme", "loaded from your Adobe Fonts project" or "loaded from the font you uploaded". For a font your pages cannot load, it reads "Your heading font Name isn’t on your page." or "Your body font Name isn’t on your page.", followed by the matching line from the list below. When the same font is missing for both, one line says "Your heading and body font Name isn’t on your page." and the matching line follows once.
Your landing pages use only the primary font of the Heading fonts list, which is your heading font, and the primary font of the Body fonts list, which is your body font. The card lists those two fonts first, the heading font and then the body font, and marks them with a Heading font or Body font tag. A font you use for both shows both tags. A tagged row also has a label that says what happens on your published page, with an icon: a check mark for a font in use, a warning mark for a font Commander cannot load.
| Label | What it means |
|---|---|
| Used on your page | The real font appears on your published page. For a font that loads from your Adobe Fonts project, the line under the font name says "Loads from your Adobe Fonts project. If this family isn’t in the project, your theme’s font shows. Add it there to use the real font." This shows once you save your project ID. A font that your theme loads on every page needs no Adobe Fonts project ID or upload to be used on your pages, and shows no line about the project. A font your store no longer has can still be used. The line then says "No longer in your theme, but your page still loads it from Google Fonts" or, for a font from your Adobe Fonts project, "No longer in your theme, but your page still loads it from your Adobe Fonts project". |
| Not on your page | Commander cannot load this font for your published page, so your theme’s font shows instead. A line directly under the font name says why and what to do. The lines are listed below. |
These are the lines under a font that is Not on your page:
- A font from Adobe Fonts that your theme does not load, with no saved project ID: "Add your Adobe Fonts project ID below to use it. Until then, your theme’s font shows."
- A Google font that Commander has no copy of: "Commander can’t load this Google font on your page, so your theme’s font shows instead. Pick another font to change that."
- A font you uploaded that Commander could not prepare for your page: "Commander couldn’t prepare this uploaded font for your page, so your theme’s font shows instead. Upload it again, or try a .woff2 file."
- A font found on a host Commander does not know, when your theme does not load it on every page: "Commander can’t load this font on your page, so your theme’s font shows instead. Pick another font to change that."
- A font your store no longer has: "This font is no longer on your store, so your theme’s font shows instead. Pick another font, or press Re-detect fonts if you added it back."
A font that shows Best match from your ad is the closest match Commander found for a font in an ad of yours, and it can be wrong. Your landing pages can draw it for the heading and the button that match your ad, so its row has a label even when it is not your heading or body font. The label and the line under the font name tell you which font your page draws:
| What the row shows | What your page draws |
|---|---|
| Used on your page, with the line "Landing pages made from this ad use it for the heading and buttons" | The font itself, because Commander has a font with that name. |
| Stand-in on your page and "Showing Name, the closest font Commander has. Upload a font named Font name and your page can use it." | The closest font Commander has, named in the line. The row keeps the name of the font found in your ad. |
| Not on your page and "Commander doesn’t have Font name, so your theme’s font shows. Upload a font named Font name and your page can use it." | Your theme’s font, because Commander has no font close to it. |
| Used on your page and "Your page uses your uploaded Name" | The font you uploaded. |
Commander finds the closest font in one of two ways. It can come from a table of font matches, or Commander can look at the ad itself and pick the closest font it has. When no font is close, the page keeps your theme’s fonts. The closest font is a best guess and can be wrong.
To make your page draw the real font, click Upload a font and upload a file of that font. The name in the line after Upload a font named is the name your upload has to match. When the name of your upload matches the name of the font in the ad, the row changes to "Your page uses your uploaded Name" and the page uses your upload instead of the closest font or your theme’s font. Your uploaded font keeps its own row, and that row says the same. The match ignores capital letters and endings such as Pro, Std, LT or Bold, in the name of the font in the ad and in the name of your upload.
The other fonts on the card, apart from a font found in your ad, have no tag and no label. A row that is not your heading or body font does not repeat a line about it, because the card’s first line already says those fonts are not on your page. Two fonts are the exception, because they tell you something about using them on your page. A font that your theme loads on every page reads "Your theme loads this font, so your page can use it". An Adobe font that your theme does not load reads "To use it on your page, add your Adobe Fonts project ID below" until the Adobe Fonts project ID field holds a valid ID. To use one, tick it in the Heading or Body list if it is not selected, then click its star to make it the primary font, and save. Inter, the default every store starts with, does not count as your choice. Until your store uses Inter, the card treats Inter like any other font that is not your heading or body font.
Muted text under the font name lists the weights and where Commander found the font: Found in your theme, Found in your Shopify fonts, Found on Google Fonts, Found in your Adobe Fonts project, Uploaded by you, Best match from your ad or Found on your store. Weights read as names, such as Regular, Bold, Italic. A font that covers all weights reads All weights. The same line adds Ads use a similar font for a font ads cannot draw as it is, and No longer found on your store for a font your store no longer has. A font that ads draw as it is has no line about ads.
The card has these states:
- Fonts found. The card lists them and shows when your store was last read, under Re-detect fonts.
- No fonts found. The card says "No custom fonts found on your store. You can still pick any font from the lists above."
- Storefront refused the read. A password page or a blocked storefront stops Commander from reading your fonts. The card says so and tells you the next step: remove the storefront password or let Commander in, then press Re-detect fonts. If Commander found fonts earlier, the card keeps them and gives the date of that read. A font that is no longer on your store reads "No longer found on your store".
- Read may be incomplete. When the last read did not finish properly, the card says "The last read of your store may be incomplete, so some fonts could be missing". Press Re-detect fonts to read again. If you press it and the read is still incomplete with the same fonts, this message is also the result, in place of "Same fonts as before".
- Couldn’t load. A red message says "Couldn’t load your fonts" with a Try again button.
Click Re-detect fonts to read your store again. A short message confirms that Commander is re-detecting your fonts. While Commander reads, the button reads Reading your store… and the card says the list updates when the read is done. If the read takes longer than the card waits, the card says "Still reading your store. Check back in a few minutes." When the read finishes, the card names the fonts it found or lost, says Fonts updated with the number found, or says Same fonts as before. Commander limits how often you can re-detect and shows a message when you reach the limit. In Demo Mode, Re-detect fonts is turned off, and a note beside it says Demo Mode keeps the sample fonts as they are.
Under the list, click Upload a font to add font files of your own. Choose one or more files that end in .woff2, .woff, .ttf or .otf. The line under the button shows the limits: the size of each file, how many files you can keep and their total size. Commander reads the font’s name, weight and style from the file itself, so the file name does not matter. While a file goes up, the button reads Uploading…. When it is done, a line under the button says which font was added, for example "Uploaded Brand Sans Bold". A file that Commander cannot use gets its own red message under the button, and the other files in the same batch still upload. If you upload the same weight and style of a family again, the new file replaces the old one.
Commander also tries to copy the file to the Files section of your Shopify admin. If that copy is not made, for example because Commander doesn’t have permission to add files to your store, the upload still counts, and the line says the copy was not made.
Commander also prepares the file so that your landing pages and your ads can use it. If it cannot prepare a file, the upload still counts, and the line adds "Commander couldn’t prepare Brand Sans Bold for your pages and ads. Upload it again, or try a .woff2 file." When several files in one batch could not be prepared, the line counts them and names them: "Commander couldn’t prepare 2 fonts for your pages and ads (Brand Sans Regular, Brand Sans Bold). Upload them again, or try .woff2 files." Until you upload a file that works, your pages show your theme’s font and your ads use a similar font. This also holds when you replace a font and the new file cannot be prepared: new pages show your theme’s font and new ads use a similar font until a working file is uploaded. A landing page you already published keeps the font it was published with until Commander generates it again or you apply a Remodel.
A font you uploaded can be used in your ads, and you can pick it in the Heading, Body and CTA lists and on the Custom page when you create a creative. It takes a moment after the upload before this is true: until then its row says Ads use a similar font, and the lists show it as Not available in ads.
A font you uploaded shows Uploaded by you and a Remove button. Click Remove and a question appears: "Remove Name from Commander?" When your landing pages use that font, it adds "Your landing pages will use your theme’s font instead." Click Remove font to confirm, or Cancel to keep it. If the removal fails, a red message appears in that font’s row. Removing a font does not delete a copy that is already in your Shopify Files. Commander removes every version of the font it had made public, including earlier versions from files you replaced. Your ads and your new landing pages stop using it, and a landing page you already published that used it shows your theme’s font.
A font you uploaded can also be your heading or body font on your landing pages. Pick it in the Heading fonts or Body fonts list and make it the primary font. The row then reads Used on your page. A landing page you already published shows the font the next time Commander generates or remodels that page. If your upload has the same name as a Google font, your upload is the one the page uses. When Commander could not prepare the file, the row says your theme’s font shows instead, as in the list above. In Demo Mode, uploading and removing fonts is turned off.
If your store uses Adobe Fonts, you can type your project ID in the Adobe Fonts project ID field. The field is optional: the card asks for it only for an Adobe font that your theme does not load itself. The project ID is the code in your Adobe Fonts embed link (use.typekit.net/abc1234.css). It has 5 to 10 letters and digits, like abc1234. A red message appears under an ID that does not fit. The field reads "Saved when you save your brand settings", so the ID saves with the rest of the page, through the save bar. A save with an ID that does not fit is refused: the page tells you to fix it under Typography, opens the section and puts the cursor in the field. To disconnect the project, clear the field and save.
Below the field, About Adobe Fonts projects opens more help. It says where to find the ID: you see it on the Web Projects page in Adobe Fonts, and Find your Adobe Fonts project ID opens Adobe’s guide in a new tab. It also says the project must include the font families your theme uses, and that a family missing from it shows your theme’s font. In Demo Mode, the field is read-only, the note reads "Connecting an Adobe Fonts project isn’t available in Demo Mode", and the help is not shown.
At the bottom, the card carries a license notice: "Make sure you have the right license for fonts you use. Commander doesn’t verify font licenses."
Your brand fonts on landing pages
A landing page that Commander generates uses the Heading font and the Body font you set in the Typography section. Headings use your heading font. Text and buttons use your body font. When the page starts from a Commander ad, the main heading and the main button at the top of the page keep the font of that ad, and every other heading and button uses your brand fonts.
A font counts as set only when you chose it. A store that never chose a heading or body font keeps the font of its theme for that role, and so does a font that Commander cannot load. Inter counts as chosen only when your store really uses it. If a brand font does not load on a visitor's device, the page shows the font of your theme instead.
The fonts are written into the page when Commander generates it or when you apply a Remodel. A page that is already published keeps its fonts until then, and a font you change later reaches it at the next generation or Remodel.
Tone of voice
Open Tone of voice and click one card. The tone shapes the brand voice in generated copy.
| Tone | What the card says |
|---|---|
| Premium | Sophisticated, elevated, luxury feel |
| Playful | Fun, energetic, casual tone |
| Technical | Data-driven, precise, expert |
| Minimalist | Clean, simple, less is more |
| Casual | Conversational, relaxed, approachable |
| Authoritative | Confident, decisive, expert |
| Friendly | Warm, helpful, supportive |
| Bold | Striking, daring, attention-grabbing |
Visual styles
Open Visual styles and pick the image styles you prefer. Commander leans new generated images toward the styles you pick.
Ad languages
Open Ad languages to choose the languages for your ads. The list offers English, Spanish, French, German, Italian, Portuguese, Dutch and Romanian.
- Primary language is the language Commander writes your ad copy in.
- Secondary languages are a saved list. Click a language to turn it on or off. A selected language shows a check mark.
Your primary language is not in the Secondary languages list. The line above the list names it. When you pick a new primary language, Commander removes it from the secondary list.
Image guidelines and copy guidelines
Both sections hold two lists: Do's and Don'ts. Type a rule and click Add. Click the X on a rule to remove it.
To fill the lists from a document, click Extract from document and choose a brand-guidelines file. The file can be a PDF, a TXT file or an MD file. One upload fills both sections. Commander adds new rules and keeps the ones you wrote. A usage limit applies to this action. If the file is too large, Commander shows "File is too large — the maximum is 10 MB."
To fill the lists from your own ads, click Build from my ads. You mark the ads that look like your brand, and Commander suggests rules for both sections. With a connected ad account that has enough winning ads, Refresh from winning ads suggests rules from those ads instead. Both show a review first. The buttons do not show when Commander has found none of your ads. See Brand rules from your ads.
A rule that Commander added shows a label: From document, From your ads or From winning ads. Click From your ads or From winning ads to see why Commander suggested the rule. Rules you write yourself show no label. When you edit a rule, its label goes.
Brand CTA phrases
Add the exact call-to-action phrases that your brand approves. When a generated ad uses one of these phrases as its call to action, Commander locks it. For that ad, Commander turns off the automatic CTA and text rewrites from Meta.
You can add up to 5 phrases. Remove one to add another.
Remove a brand
Inside Shopify Admin, the page has no archive control. To remove a brand, uninstall the app.