A single batch of honey cannot ship with one label design. Every export market sets its own rules for which language the label must use, whether a second language is mandatory, how net weight is declared, and what warnings or country-of-origin statements must appear. This scene renders a pallet of honey jars whose labels are generated live from those rules, so you can see how the same product is relabelled market by market.
Under EU Regulation 1169/2011, the label language is set by each member state, not by the exporter's home country — so a jar bound for Germany and one bound for France need different artwork even though they leave the same warehouse. Canada goes further and requires English and French on the same principal display panel, in comparable type size, for virtually every prepackaged food.
A pallet of honey jars whose labels regenerate live to match the language, script and mandatory-field rules of five real export markets, from EU member-state language law to Canada's bilingual requirement and Gulf Arabic/English conventions.
Each market defines its own required label language(s), script direction and mandatory fields. Partial translation progress leaves some fields as untranslated placeholders — exactly the gap that trips up customs clearance.
Pick an export market, drag the localisation completeness slider to see fields fill in (or fall back to English placeholders), and toggle field highlighting to spot compliance gaps at a glance.
Canada's bilingual food-labelling rule means English and French text must appear in comparable type size on the same principal display panel — a formatting constraint, not just a translation one.