Jun 22
Feature Request: Fallback Font Support for Unsupported Characters
Hi Customily Team,We would like to submit a feature request regarding font display stability: we hope Customily can add a built-in fallback font package.Currently, in some product configurations, the font package uploaded or selected by the merchant may not include all characters that customers may enter. For example, some fonts may not support the English apostrophe (’) or hyphen (-). In this case, if a customer enters unsupported characters, part of the preview or final design may fail to display correctly.We hope Customily can support the following fallback mechanism:When a customer enters characters that are not included in the currently selected font package, the system can automatically use Customily’s built-in default font package as a fallback, so the customer’s input can still be displayed properly instead of showing missing characters, blank spaces, or abnormal rendering.Competitor reference product:https://trendingcustom.com/products/congrats-graduation-seni… details:In this product, the option name is “enter school name”, and the corresponding font is Vogue Regular. This font does not seem to include the English apostrophe (’) or hyphen (-), but when customers enter these characters, the preview image can still display them correctly. This provides a better user experience and helps avoid display issues caused by incomplete font character coverage.This feature is very important for personalized products because customer input is unpredictable. Fields such as school names, personal names, and commemorative text often include apostrophes, hyphens, special symbols, or other characters. Without a fallback font mechanism, the storefront preview experience, conversion rate, and final production stability may all be affected.We hope Customily can evaluate whether this feature can be added.
Pending