StoreBuilt reviewed Shopify’s current wording editor documentation for this guide. The practical starting point is ownership: two labels that look identical on a storefront can come from different settings. Editing the wrong one creates the impression that Shopify has ignored the change, even when the saved setting is working exactly where it belongs.
If you want to change default theme content in Shopify, start with the customer’s action and the screen where the text appears. UK shops may prefer “basket” to “cart”, clearer delivery messages or less generic button wording. Those changes should make the journey easier to understand while preserving the behaviour behind each message.
Contact StoreBuilt with the page, current wording and intended replacement if the source is unclear.
Table of contents
- Create a small wording brief
- Find the system that owns the words
- Use the default content editor deliberately
- Preserve dynamic values and useful meaning
- Keep default wording separate from translation work
- Check checkout and account surfaces independently
- An illustrative basket-label change
- Review wording as part of interaction QA
- Keep a reusable copy register
- StoreBuilt point of view
Create a small wording brief
Record the current phrase, the proposed replacement and the URL where it appears. Add a screenshot showing the surrounding controls. A request to “change the basket text” may refer to the header, drawer, full basket page or checkout. Each location needs a specific acceptance check.
Describe why the replacement helps the customer. A shorter label may fit mobile more cleanly; a clearer error may explain the next step; a delivery note may remove an ambiguity. Brand personality can be useful, but it should not obscure whether clicking a button adds an item, submits a form or leaves the page.
Keep the first release deliberately small. A few related strings are easier to review than a global rewrite across the shop. Group changes by the journey they affect, then test those journeys in full before continuing with the next group.
Find the system that owns the words
Inspect the relevant theme section or block before assuming the phrase is a default string. Promotional headings and button labels may be entered directly into section settings. Product descriptions belong to product content. A reviews widget or subscription selector may have its own app-controlled language settings.
Use the default theme content editor when the phrase belongs to supported theme or system wording. Shopify’s wording documentation explains the editor and its categories. The existence of a similar phrase in the editor does not prove that it controls the specific element you are looking at.
| Text location | Likely place to investigate | Confirmation test |
|---|---|---|
| Header basket label | theme content or navigation settings | open the live header |
| Promotional section button | section or block settings | preview that section |
| Product description | product content | check the exact product |
| Reviews widget control | app settings | inspect the widget itself |
| Translated storefront label | translation workflow | select the target language |
| Custom-coded banner | theme code and its data source | trace the rendered element |
If the ownership remains unclear, ask a developer to trace the source before editing code. That investigation should identify the setting or translation key, not simply replace every matching word across the theme. Broad replacements can alter unrelated messages or technical identifiers.
Use the default content editor deliberately
In Online Store, open the menu beside the theme you intend to edit and choose Edit default theme content. Search for the existing phrase or browse the relevant category. Note the theme name before saving so a draft-theme edit is not mistaken for a change to the published shop.
Read neighbouring fields and their labels. A search may return a singular label, a plural message, an accessibility description and an empty-state message. Update the entries needed for the brief rather than selecting the first match and assuming it covers every appearance.
Save the change, then open the appropriate storefront context. The editor is the place where you enter wording; the customer journey is where you verify it. Keep the original value in your change note so a confusing replacement can be reversed without reconstructing the previous copy.
Preserve dynamic values and useful meaning
Some messages contain placeholders for values such as counts or product names. Treat these as part of the message’s function. If you do not understand a placeholder, ask the theme developer what it supplies before removing or renaming it. A grammatically polished sentence can still be wrong when its dynamic data disappears.
Test quantities and states that change the wording. One item and several items may use different strings. An available product and a sold-out variant may expose different controls. A successful form submission and an error message should both tell the customer what happened and what they can do next.
Avoid using wording to imply a capability the shop does not provide. Changing a button to “Reserve for tomorrow” does not add reservation logic or guarantee availability. If the desired phrase changes the customer’s expectation of the transaction, review the underlying behaviour as part of the same brief.
Keep default wording separate from translation work
A default-language edit is not proof that every published language has been updated. List the languages and markets used by the affected journey, then check the relevant translation workflow. A shop can show the new English phrase while retaining an older translation in another language.
For a UK merchant, consistency may also involve regional vocabulary without adding another language. Decide whether “basket”, “delivery” and other chosen terms should apply across the whole journey. Keep a short terminology list so later app or theme edits do not quietly reintroduce conflicting labels.
Use the translation quality assurance guide when the work extends into multiple languages. This article focuses on locating and editing default wording; a translation review adds another set of screens, fallbacks and customer expectations.
Check checkout and account surfaces independently
Do not assume every screen inherits the storefront theme in the same way. Record whether the target phrase appears in the theme, customer accounts, standard checkout or an accelerated payment journey. That context determines which supported controls and limitations apply.
Shopify documents that some Checkout & system wording changes carry into Shop Pay and others do not. Verify the specific field against the current documentation rather than promising universal control. If a phrase is not customisable through the supported route, explain that boundary in the change brief.
Never remove important purchase disclosures merely to shorten the screen. Copy editing should preserve the information required for the actual transaction. If a proposed rewrite affects a subscription, delivery commitment or policy statement, involve the person responsible for that promise before publishing it.
An illustrative basket-label change
Imagine a UK fashion shop changing its header from “Cart” to “Basket”. The new wording appears in the header, but the drawer still uses “Your cart”, and a third-party upsell panel has another label. The team initially thinks the saved theme edit has failed.
A source map separates the three owners. The header and drawer use different theme strings, while the upsell panel belongs to an app. The team updates the appropriate settings and tests an empty basket, a single item and a mixed-variant basket on mobile.
This is an explanatory scenario, not an asserted StoreBuilt client outcome. The point is that a vocabulary change can cross several components without being a single global setting. The release is complete when the intended customer contexts agree, not when one editor reports a successful save.
Review wording as part of interaction QA
Use a test matrix that covers the states the edited copy describes. Capture the actual result, including the selected variant or quantity where relevant. This is more useful than a screenshot of the settings page because it connects the words to the behaviour the customer experiences.
| Test case | Look for | Reason |
|---|---|---|
| Narrow mobile screen | wrapping and button height | longer copy can disrupt controls |
| Empty basket | accurate next step | empty states use separate messages |
| One and several items | correct grammar and counts | dynamic values change the sentence |
| Unavailable variant | honest availability language | labels must match purchase rules |
| Form validation error | clear recovery instruction | customers need a next action |
| Supported alternate checkout | correct inherited wording | surfaces have different controls |
Include keyboard focus and accessible naming in a developer review if the change reaches custom code. A visible label and the name announced by assistive technology should describe the same action. Do not let a cosmetic replacement leave an old, misleading label hidden in the markup.
Keep a reusable copy register
Store the final phrase, its setting or key, the owning theme or app and the date checked. This register makes future theme updates easier to review. A screenshot alone shows the outcome but does not tell the next developer where the wording came from.
Revisit the affected strings after a theme replacement or app migration. Custom copy can be lost or moved even when the new design looks familiar. The theme update guide explains why recorded customisations are useful when comparing releases.
StoreBuilt point of view
Good storefront wording makes an action predictable. StoreBuilt would choose clarity over cleverness, identify the owner of each phrase and test the resulting interaction. A small copy change is successful when customers understand the same behaviour more easily across the screens they actually use.
Explore Shopify design and development or Contact StoreBuilt for a focused theme-copy and interaction review.