Translations¶
Shoptsy lets you translate storefront text and email/notification content so your customers see the right language across your store. You can manage translations by uploading translation files and assigning them to the correct path (location) in your store.
What you can translate¶
On the Translations page, you’ll typically see two main areas:
1) Frontend¶
Translate text that appears on your storefront, such as: - Buttons (Add to cart, Buy now, Continue) - Headers, labels, menus - Checkout text and system messages - Theme/static text used across pages
2) Emails¶
Translate text used in communication templates, such as: - Order emails (order placed, shipped, delivered, cancelled) - Returns (return created, approved, rejected) - Customer notifications - Draft order emails (if enabled) - Staff notifications (if enabled) - Local delivery / pickup text (if enabled) - Shipping-related notifications (if enabled)
Tip: If you want customers to receive emails in their selected language, ensure the Emails section is translated too—not just the storefront.
Add a new translation file¶
Click Add new file to upload a translation file and map it to a specific path.
You’ll see a popup with:
- File: Choose the translation file from your computer
- Path: Search and select where this translation should apply
Step-by-step¶
- Open Online Store → Translations
- Click Add new file
- Click Choose file and select your translation file
- In Path, select the correct translation target (example: Frontend → Checkout, Emails → Orders, etc.)
- Click Save
After saving, Shoptsy will associate that file with the chosen translation area.
Understanding “Path”¶
Path tells Shoptsy where the translations belong. Think of it as the “bucket” of text being translated.
Common examples:
frontend(storefront UI)emails/ordersemails/returnsemails/customershippinglocal-pickuplocal-delivery
Your actual paths may differ depending on how your store is configured and which modules are enabled—always pick from the dropdown list shown in your dashboard.
Translation file format (recommended structure)¶
Use a simple key-value format so the system can reliably map translations.
Example (JSON)¶
```json { "add_to_cart": "Add to cart", "buy_now": "Buy now", "out_of_stock": "Out of stock" }