Start with two reading systems, not mirrored artwork
Arabic and English perfume packaging needs a shared information hierarchy, not two copies of an English layout. Arabic generally reads right to left; English reads left to right. Product codes, dates and other mixed-direction strings require additional care. Build the layout around how shoppers identify the fragrance, find its size and distinguish variants, then give each language a deliberate place.
Choose a layout by four criteria: correct language rendering, equivalent information, readability on the assembled package and repeatable production. Decorative symmetry should not override them. This guide addresses artwork localization and sourcing decisions, not a complete account of market labeling law; confirm destination-market requirements separately.
Set the bilingual hierarchy before choosing the decoration
Create an approved copy register before designing panels. Record the brand name, fragrance name, description, concentration, nominal volume and other required or approved wording in both languages. Distinguish names that remain unchanged from those requiring translation or transliteration. A native Arabic reviewer should judge meaning and naming consistency; the designer should not invent a phonetic spelling to fill space.
Decide whether the front uses stacked language blocks, separate aligned zones or a shared central composition. Equal importance does not require identical point sizes: Arabic and Latin typefaces have different proportions and densities. Compare apparent prominence at actual size. Keep each fragrance name clearly associated with its description, especially when neighboring variants share a brand mark.
For narrow branded perfume cartons, reserve front-panel space for identification and place longer supporting copy on suitable secondary panels. Establish that allocation before adding ornament. If approved copy cannot fit legibly, reconsider the panel plan or structure rather than compressing every line.
Protect Arabic joining and control mixed-direction strings
The Unicode Standard, Chapter 9, describes Arabic contextual shaping and joining behavior; its bidirectional text rules are specified in Unicode Standard Annex #9, the Unicode Bidirectional Algorithm. These provide the technical basis for treating joining and direction as distinct checks. Arabic letterforms depend on their joining context, and some letters do not connect onward. A reviewer must distinguish legitimate breaks from broken shaping.
Use software that supports Arabic shaping and right-to-left paragraphs. Avoid manually spacing letters to imitate Latin tracking, which can disrupt joining or produce unnatural word shapes. First check the Arabic paragraph's base direction; then check the handling of embedded left-to-right content. Right alignment alone does not establish correct paragraph direction.
Treat English names, codes, percentages and dates as separate proofreading tasks. A string such as EDP-07 includes letters, punctuation and digits whose displayed arrangement depends on directional context. Where necessary, handle the complete code as a left-to-right unit using the application's supported direction controls. Inspect the exported result, including adjacent punctuation, rather than trusting the editable document alone.
Do not mirror an entire panel to create its Arabic counterpart. Preserve approved logos, numeral sequences and barcode artwork. Choose numeral style through the localization brief, not assumptions about all Arabic-language markets. Use an agreed, unambiguous date format and verify its component order against the copy register.
Choose typefaces for small panels and licensed production
Select Arabic and Latin faces together using actual packaging copy. Compare weight, density, punctuation, numeral design and space above and below each line. Arabic dots and marks must remain distinct at the intended printed size. A pairing that looks balanced on a presentation slide may become uneven on a narrow side panel.
Confirm that font licenses cover packaging use and the intended file-sharing workflow. Ask who may receive editable files, whether the converter needs a separate license and which embedding permissions apply. Outlining is not a substitute for permission. Retain a controlled editable master so later variants do not require reconstructed lettering.
Approve correctly shaped, correctly directed editable text before outlining. Then compare the outlined export visually with that approved version, checking letter shapes, dots, marks, punctuation and line breaks. Outlining preserves existing shapes; it does not validate language or direction. Avoid a universal minimum type size: request actual-size proofs on representative material and redistribute copy if details become ambiguous.
When small lettering depends on contrast, the perfume packaging color-matching guide helps define which material and finished surface the color approval must represent.
Let the structure and paperboard constrain the layout
Confirm dimensions, closure, insert and material before locking artwork. PackMojo's custom-box ordering guide recommends using the dieline for the confirmed configuration and respecting its specified safe zones. A language approval on an obsolete dieline is not approval of the final package.
Creases, corners and wrapping turn-ins can interrupt typography. Holmen's Graphics Handbook states that paperboard should be creased before folding; its knowledge material supports use of Invercote and Incada boards. That does not establish every stock's behavior. Ask the converter to demonstrate the proposed board and finish, particularly near fine lettering and folds.
Rigid perfume gift boxes offer additional presentation surfaces but introduce lid overlaps, wrapped edges and separate components. Keep essential identification visible when closed. A larger lid does not solve every bilingual copy problem: inserts, ribbons and opening orientation can change what the customer sees next.
Use the perfume carton dieline guide to resolve panel orientation, fold boundaries and artwork placement before approving either language on the assembled carton.
A hypothetical project: one fragrance, two package formats
Imagine a hypothetical 50 ml fragrance in a folding carton and a two-piece gift box. The proposed front centers the English name above the Arabic name, with descriptions beneath. The Arabic description needs more space. Rather than shrink it, the designer moves both descriptions to corresponding side-panel blocks, retaining the names on the front and gift-box lid.
During a folded mock-up review, EDP-07 appears incorrectly within the Arabic block. The designer first checks that the surrounding paragraph has right-to-left base direction, then separately checks that the complete code is handled as left-to-right text. The reviewer compares the code and adjacent punctuation with the copy register. After approval of the corrected editable text, the designer outlines it, compares both versions and exports a fresh proof. This illustrates a workflow, not tested production results.
For a fragrance range extending into sample formats, the discovery-set packaging guide helps plan the sequence of vial identification, supporting information and access rather than simply shrinking the main carton layout.
Turn the sourcing brief into an approval checklist
Send suppliers a versioned brief covering structure, dimensions, board or wrapping paper, finishes, languages and approvers. Request the production dieline, safe zones, artwork requirements and proof stages. Ask how outlined Arabic lettering, finishing layers and barcode clear areas will be preserved. Require proposed material or process substitutions to return for approval.
Assign each sample a question. A structural mock-up checks orientation, closure and product fit; an artwork proof checks content and placement; a representative printed sample checks legibility on the proposed material. Establish which production processes each proof represents. A digital printout alone cannot establish whether tiny reversed lettering will remain clear under the chosen finish.
Before production release, compare approved editable text, outlined artwork and exported PDF. Have a native Arabic reviewer check spelling, joining, punctuation and mixed-direction strings, then inspect assembled orientation. Identify the approved file version, material and finish, resolve exceptions and recheck affected panels after corrections. These checks complement rather than replace market-specific labeling review.
Verify bilingual artwork through production stages
- Register approved copy — Confirm names, code order and punctuation in both languages.
- Check editable text — Review paragraph direction, code boundaries and Arabic joining.
- Compare exported shapes — Match outlined PDF against approved editable text.
- Inspect assembled sample — Check dots, contrast and visibility on the proposed finish.
Why a code boundary is different from a letter boundary
Unicode UAX #9, Section 3.5, Shaping, explains that contextual shaping follows bidirectional level resolution and is limited to characters within the same level run. It also notes that letters do not join across a directional isolate. Thus, direction controls are structural text boundaries, not decorative spacing tools. Placing them inside an Arabic word can affect the connections that the reviewer expects to see.
For a bilingual carton, keep an approved Arabic word intact and treat an embedded Latin product code as a separate directional unit. W3C’s Inline markup and bidirectional text in HTML, under “If you know the direction of the phrase,” recommends tightly wrapping the complete opposite-direction phrase and setting its direction. This is HTML guidance, not a command recipe for page-layout software: use the application’s supported equivalent, then inspect the exported code, surrounding punctuation and Arabic joining separately. Retest after edits that move the code or change adjacent text.
A buyer’s conditional approval record
Assume a hypothetical 50 ml folding carton with approved bilingual wording, a confirmed dieline and a proposed matte finish. The record identifies the editable master, outlined PDF, board and finish versions, plus the Arabic reviewer and buyer responsible for approval. It asks whether EDP-07 matches the register, whether Arabic dots remain distinct, and whether descriptions remain visible after folding.
Use explicit branches rather than a general “looks good.” A code or punctuation mismatch rejects the artwork: correct direction handling, repeat language review and replace the export. Correct wording with indistinct dots rejects that print-and-finish combination, not the translation; revise the finish or text allocation and request another representative sample. Only matching content, distinct details and unobscured assembled panels permit approval of the recorded configuration. A digital proof may clear content, but production release remains on hold until the physical checks pass; any proposed board or finish substitution reopens those affected checks.
Conditional approval decisions
- Code or punctuation — Mismatch: reject artwork and repeat language review.
- Dots and contrast — Indistinct details: revise finish or text allocation; resample.
- Assembled visibility — Obscured description: revise placement before releasing production.
FAQ: Should Arabic and English always occupy equal space?
No. Aim for equivalent access to information rather than equal rectangles. One language may need more line length or different spacing. Establish prominence according to the brief and applicable labeling requirements, then assess balance at actual size. Neither language should read like a fragmented afterthought.
FAQ: Is an outlined PDF enough to approve Arabic artwork?
No. Outlining can prevent font substitution, but it also preserves existing mistakes. Compare it with approved editable text, then inspect a representative printed and assembled proof for clipping, missing details and legibility. Wording changes require another language check; material or finish changes may require renewed print approval.
Sources and editorial method
This evidence-based packaging selection guide still requires physical samples to verify small lettering, finished-surface contrast and assembled visibility.
Unicode UAX #9: Unicode Bidirectional Algorithm, Section 3.5 — Contextual shaping follows bidirectional level resolution, is limited to the same level run, and does not connect letters across directional isolates.
W3C: Inline markup and bidirectional text in HTML — For known-direction HTML phrases, tightly wrapping the complete opposite-direction phrase and setting its direction separates it directionally from surrounding text.
PackMojo: How to Order Custom Printed Boxes: From Artwork to Delivery — Confirmed packaging specifications determine the dieline; digital proofs, structural samples and production-representative samples answer different artwork, fit and finished-surface questions.