Skip to content
Fashion & Apparel

Fashion DTC Product Pages: Who Maintains Size Charts, Variant Images and Returns

By Fashion Method·

Brand promotion: this article introduces Guangsuan's Shopify technical maintenance and custom development service. It is a vendor-introduction piece, not an independent review or a commissioned evaluation.

A fashion product page can look like design work. In practice it is a small set of facts — the size chart, the colourway and fit the variant images actually show, the returns window, the care instructions — held inside theme code that somebody has to keep correct. The question here is narrow: when an independent fashion or DTC brand sells on Shopify, who maintains those parts of the product page, and what is worth checking before the next drop goes live?

The short answer: Shopify looks after the platform layer, including hosting, checkout and payments, and the product-page layer stays with the merchant. That second layer is the theme that renders the page, the apps that inject markup into it, the product data behind it, and the systems the orders flow into. Guangsuan draws its own boundary in the same place: the maintenance it sells addresses merchant-side work and does not resell the hosting Shopify already provides.

Two conditions belong with that answer rather than in a footnote. What is possible in a given job depends on the Shopify plan, the theme structure, what the installed apps can do and which interfaces are available. And the split between merchant work and platform work is worth writing into the scope before anyone starts, because a proposal that lists hosting or platform updates as deliverables is describing something the subscription already pays for.

Guangsuan is the provider introduced in this article; its Shopify technical maintenance and custom development page sets out the scope, the engagement types and the delivery process as published.

Who owns the size chart

A size chart is a product fact rather than a formatting choice, so the split is simple. The brand supplies and approves the measurements; the site work is about where the table lives and whether it renders on the live page.

A reasonable default is to keep grouped specification content — the size chart, materials, compatibility or fit notes, a short FAQ, care instructions, downloads — in metafields and render them at a fixed position in the product template, rather than pasting them into the product description. Grouped structured information handled that way can be reused across every product of the same type and laid out consistently, and it stops the description field from growing into a document nobody can maintain. Pasted into the description instead, the same table has to be copied and re-checked product by product.

Two checks make ownership visible. First, decide who signs off a measurement before it appears: a size chart is a commercial statement about fit, and the brand is the party able to confirm it. Guangsuan's published scope says the same thing from the provider's end — product facts and translations need to be confirmed on the merchant side. Second, check the block on the live page rather than in an admin preview, because what matters is the table a shopper's browser receives.

Variant images and alt text delivery checks

A variant image is a small piece of matching work. The swatch a shopper taps should show the colourway it names, and the fit a variant claims should be the one in the frame. This is item-level data work rather than design work, and it is one of the areas Guangsuan groups under product data: bulk import, variants, categories and metafields, image matching, specification display, FAQ and page content configuration.

Alt text is the part that gets written in a hurry or not at all. Its job is to describe what the image shows — product, colourway, material, angle — in words a buyer would use, and it matters because one product image travels: it appears on the product page, in collection listings, and as the product image entry in the sitemap. A file name and an alt string help search engines and buyers understand a picture, but they are not the lever that carries a weak product page on their own, so treat them as groundwork rather than as a growth channel.

Two delivery details are worth separating from the writing. Product images belong to the store's image system, and the upload rules and size limits follow what the current admin actually shows. And whether the theme prints an alt attribute at all is theme output, so that check runs against the live HTML rather than against a field in the product editor.

Returns and care information on the product page

Returns copy can be written once and left alone for years. The more useful habit is to treat it as a source. The reasons a garment comes back — the wrong size ordered, a colour that reads differently in daylight, a material that was not what the buyer pictured — are exactly the misunderstandings a product page can pre-empt. Care belongs in the same list: how the piece is washed, stored or re-proofed, and what the pack contains and does not contain.

The division of labour matches the size chart. The policy is the brand's, and the site work is placement and consistency: whether the returns window, the condition the item must be returned in and the care note are visible on the product page rather than only in a footer policy page. When the description is rewritten, adding information the supplier's copy does not carry is more useful than swapping synonyms. The practical sources are the questions buyers ask before purchase, the reasons for returns and exchanges, the care steps, the pack contents, and the specific differences from similar products that a buyer would measure or compare.

What to check before the next drop

The list below is designed for one product page, not the whole catalogue, so it stays runnable the week a collection launches.

CheckWhere to lookWhat good looks like
Product addressOpen the live URL and read the pathThe address describes the category in plain words; handles for products that already have outside links are the expensive field to change, so new names are settled before launch
Search title versus product titleSEO settings at the bottom of the product, then the product title fieldBoth are filled deliberately; the SEO title is what may appear in results, while the product title drives the page, on-site search and report groupings
DescriptionThe first three paragraphsThey carry information the supplier's copy does not — fit, care, pack contents, differences from similar pieces
Variant imagesThe live page, tapping each swatchEvery colourway shows the image that matches it, on desktop and on a phone
Alt textPage source, on the main and variant imagesEach description says what the image shows; decorative frames and dividers are left empty
Structured dataPage sourceOne set of product data, with price and availability matching what the page displays
Duplicate pathThe product address and the collection-prefixed addressWhere each page's canonical points is read directly; if both claim to be the full version, the collection-prefixed path is made to converge on the product address
Internal linksMenu and body textThe product can be reached from the navigation or the copy, not only from a collection grid
Mobile passA phone, on the real domainLayout, buttons and the route to the cart behave as expected on a small screen

Run the checks in order

Product-page fields are groundwork: treat them as a ranking lever and the expectation will not match, but treat them as preparation so search engines and buyers can understand what the page sells and the expectation fits.

That is also why the order matters. The checks belong to three layers — whether the page can be crawled, whether it can be indexed, and whether the indexed page is the one selected. A later layer is wasted effort if an earlier one is failing: a page carrying a noindex rule, or one product answering at three addresses, is not repaired by a better title. Run the pass on the real domain rather than a theme preview link, and keep a copy of the result before and after a change.

Two honest limits

A canonical tag expresses a preference rather than an instruction, and a search engine may still choose a different version, so a canonical fix should not be treated as a ranking change on a timetable. And platform documentation notes that crawling and indexing take time without a timing guarantee, so none of the checks above should be sold or understood as a promise of indexing.

What a technical maintenance arrangement covers

Guangsuan's published Shopify service groups the merchant-side work into six areas, which is a practical way to see where a product-page problem belongs:

  • Day-to-day maintenance and troubleshooting: layout misalignment, mobile display faults, menu and button problems, conflicts between the cart, add-to-cart behaviour and apps, taking over an existing store, routine adjustments and campaign launch support.
  • Theme customisation and version updates: Liquid theme work, sections and reusable modules, home, product, collection and landing page customisation, plus theme update evaluation and migration of customised code.
  • Speed optimisation and technical SEO: first-screen images, scripts, app load and mobile experience alongside canonical links, redirects, structured data and multilingual checks, with important URLs, content, tracking and conversion paths verified before and after a change.
  • Account and app security: staff and collaborator permissions, two-step verification, app authorisation, third-party script review, and backup and recovery verification within an agreed scope.
  • Product data and multilingual upkeep: bulk import, variants, categories and metafields, image matching, specification display, FAQ and page content, with product facts and translations confirmed by the brand.
  • Custom development and system integration: custom apps, workflows and automation, and connections to ERP, CRM, inventory, order and logistics systems.

Three details from the same page are worth knowing before comparing quotes. What is possible depends on the Shopify plan, the theme structure, app capabilities and the available interfaces, so scope is confirmed before work starts. The monthly technical support trial is published as a single-store plan including a set number of technical hours, with necessary communication, diagnosis, development, testing and agreed inspections counted as actual working time, and overruns confirmed before they are carried out. And the technical service can be purchased on its own, without a promotion package attached.

On code handling, the published position is that AI may assist with code generation and material processing, but code review, testing and release confirmation are not skipped, and customer orders and personal data are not submitted to outside AI services without authorisation.

Where Guangsuan fits

Guangsuan provides Shopify technical maintenance and custom development, aimed at the merchant side of the store rather than at the hosting the platform already provides. If the size chart, variant images, returns block or a theme-level canonical output has become the part of the launch list that nobody owns, that is the kind of work the service is described as covering, and the scope, the engagement types and the delivery process are published on Guangsuan's Shopify technical maintenance and custom development page.

For the product-page field decisions behind a drop — how the handle, the title, the description and the image alt text should each be treated — the companion product page SEO field guide sets out the trade-offs from the provider's published scope.

Frequently asked questions

Does the Shopify subscription already include the size chart and returns copy?

No. The subscription covers the platform layer. The customised theme that renders the product page, the apps installed on it, the product data behind it and the systems the orders flow into still need merchant-side attention.

Can the size chart simply live in the product description?

It can, but grouped information such as a size chart, materials, compatibility notes, FAQ and downloads is easier to keep consistent when it is stored in metafields and rendered at a fixed position in the product template, because the same table can then be reused across products of the same type instead of being re-checked page by page.

Who should approve a translated size or care claim?

The brand. A specification and a translated claim are commercial statements about the product, so the provider can configure and process the data, but the facts and the wording used in a new market need confirming on the merchant side.

Can one page be fixed without a monthly arrangement?

Yes. Guangsuan describes a single technical task option for one clear modification, error or configuration request, quoted per task with the scope and the acceptance method agreed first. Monthly support is aimed at a store that wants routine adjustment and continuous improvement rather than one specific fix.

Will completing these checks improve search rankings?

No such promise is made here. These are groundwork items that help search engines and buyers understand what a page sells. Ranking also depends on content, competition and the search engine's own judgement, and crawling and indexing take time without a guaranteed timetable.

Next Step

Run your brand through the Method.

Book Your Brand Audit