Use a small palette deliberately
The current brand-colour screen exposes primary, secondary and accent values. That is a focused way to adapt the storefront's identity. It is not a free-form design editor. Choose colours that work with your product photographs and keep important information readable.
Prepare valid values before saving
The inspected form accepts three- or six-digit hexadecimal colour values. Record the existing palette before changing it so you can compare the result. A colour code passing validation only means its format is acceptable; it does not prove the resulting text and controls have enough contrast.
Inspect the states customers actually use
After saving, look at navigation, product choices, the cart and important buttons on a phone. Check both ordinary and muted text. Avoid judging a dark button on one screenshot while overlooking a disabled or selected state elsewhere. If the template uses colour differently from your expectation, evaluate the actual rendered result.
Keep the promise bounded
This workflow changes supported colour settings. Custom font uploads, arbitrary CSS and every possible layout adjustment are not established by the source checked for this page. If those are essential requirements, ask for a demonstration of the exact capability rather than assuming a brand-colour control includes them.
UNDERSTANDING THE WORKFLOW
Three brand colours still need a readability check
Choosing brand colours is not simply finding three shades that look attractive together. The colours have jobs: communicating actions, supporting emphasis and highlighting smaller details.
What the editor exposes The inspected brand-colour screen provides primary, secondary and accent values, checks the entered colour format and sends a save request. A valid hex value proves only that the value can be interpreted. It does not prove readable contrast in every rendered component.
Keep the main action recognisable when you apply your palette. Check text over light and dark surfaces, badges, disabled controls and focus indicators. A logo colour may be useful as a small accent without being suitable behind paragraph text.
Test content states Inspect an actual long product name and a real error message, not only an empty preview. A colour that works in a large heading can be difficult to read in smaller supporting text.
Keep claims proportionate Changing colours does not establish accessibility compliance, conversion improvement or a complete custom design. Those outcomes require broader checks.
The feature page explains the available controls; the help article owns saving instructions. This piece addresses why a technically valid colour choice still needs a customer-facing readability review.
Bring this checklist to your evaluation
- Valid colour codes
- A recorded previous palette
- Readable text and controls
- A mobile check after saving
Check the workflow that matters to your business
Read the relevant setup and troubleshooting guide, then explore getting started with oBizee. Confirm current account availability and terms before committing.