A shopper choosing between sizes needs more than a letter on a button. What is being measured? How will the larger size change the fit? Algoshop AI Sales Chatbot helps merchants answer customer questions, but the product's size information must first make sense. A clear chart and a clear measuring method are the starting point.
DEVNZO helps Shopify merchants combine size-chart data with measuring instructions and a suitable storefront display. Its App Store listing includes templates, media, unit conversion, collection reuse and a smart size recommender. The merchant still supplies the actual measurements.
This guide explains how to prepare reliable chart content, choose its placement and review shopper guidance. It does not present invented product measurements or assume that a size recommendation guarantees fit.
What a useful Shopify size guide should answer
Before choosing a template, answer four questions: What am I measuring? Which size labels can I buy? How does this garment compare with something I already wear? What changes if I move up a size?
A list of sizes and unlabeled numbers cannot answer those questions. Those numbers might describe centimeters, inches, flat width or body circumference. A heading such as “Finished garment chest width, measured flat in centimeters” removes several ambiguities at once.
Keep the guide close to the size selector, where the decision occurs. A central size-guide page can provide store-wide measuring instructions, but the product page should identify the chart for this item. A shopper should not have to infer that a dress and a shirt share measurements because both belong to the same collection.
Different colors can share a chart only when their construction and measurements really match. A similarly named item from another supplier may need a different guide.
How DEVNZO turns measurements into a usable guide
The official listing describes Excel/CSV import and collection-based assignment to new products. Those tools address maintaining a chart library; they do not validate a supplier's measurements.
Begin with one verified product family. Enter the approved rows, identify the measurement method and add the measuring note. Select a template suited to your columns rather than adding unnecessary measurements to fill a layout. Keep the supplier specification and revision date in your product-data record.
For import, use DEVNZO's current template. Prepare the approved rows, then map them to its required format. The listing confirms import capability but does not document a field-by-field schema, so a generic CSV from another app is not automatically ready to upload. Compare the imported chart with the original: labels, values, headings and precision should survive.
Combine a clear measurement table with the instructions shoppers need to read it.
Assign the guide only to compatible products. A shared seasonal collection is not proof that its products fit alike. Separate differing constructions before relying on collection assignment. The guide to managing Shopify size charts develops this process for multiple suppliers and exceptions.
Inspect an existing assigned product and a newly added one. Collection-based reuse saves repeated entry, but a new construction still needs review before inheriting an old specification.
Choose the right kind of help for the sizing question
A size guide does more than store numbers. It has to bridge the gap between a shopper's question and the information a merchant actually has. Choose the information format around that question. Avoid adding every available element to every product.
Swipe horizontally to read the full table.
| What the shopper needs | Helpful guide content | Why it belongs here |
|---|---|---|
| “How do I measure this?” | A labeled illustration or short measuring video | Shows the measurement points instead of relying on an unfamiliar term |
| “How does M compare with L?” | A concise table with the relevant dimensions | Makes the change in width and length visible together |
| “Can I read this in inches?” | The supported unit conversion and explicit headings | Lets the shopper use a familiar scale without guessing |
| “Where should I start?” | The supported size recommender, with clear measuring instructions | Offers guidance while leaving the detailed chart available |
These are merchandising recommendations, not a claim that the app supplies product measurements. For footwear, an illustration of how to measure a foot may be more helpful than a garment diagram. For jewelry, circumference and diameter need different labels. A template accelerates presentation; the product determines what the guide should explain.
Tabs are useful when they keep related information together: one part for the dimensions, another for the measuring method or a verified fit note. Keep the important decision easy to find. A customer choosing between two shirt sizes should not have to watch a long video to discover that the larger size is also longer.
The listing also offers JSON backup restoration and migration assistance. For a store moving an existing library, confirm the accepted format and compare a representative chart before migrating everything. A completed import still needs assignment and storefront checks.
Label garment and body measurements differently
A body chart measures the person; a garment chart measures the finished item. Flat garment width and body circumference are not interchangeable. Relabeling one as the other can mislead shoppers even when every number was copied correctly.
For a garment comparison, state how the item should be laid out and where each measurement starts and ends. For a body-range guide, use verified wearer ranges and explain tape placement. Construction, stretch and intended fit need their own approved notes; they cannot be inferred from a size label.
Build a complete size chart: a worked shirt example
Build a shirt chart from the supplier's actual specification, not a generic table borrowed from another garment. The review below describes the content to prepare; it is not a DEVNZO-generated chart or a measured customer's fit result.
Swipe horizontally to read the full table.
| Chart element | What should appear | What to verify before display |
|---|---|---|
| Size labels | The variant names shoppers can actually choose | The guide does not silently include unavailable sizes. |
| Measurement headings | Dimension, method and unit | Flat width is not labeled circumference. |
| Values | Approved measurements for each size | Every row matches the correct construction and source. |
| Measuring guidance | Start/end points explained in text or a diagram | A shopper can reproduce the method without guessing. |
| Fit notes | Verified information about cut or stretch | No unverified promise about comfort, shrinkage or fit. |
| Regional labels | Supplier-approved equivalents, if available | Unit conversion is not treated as a regional-size mapping. |
Turn the table into a shopper decision
Help the reader compare dimensions together. A larger size may add length as well as width; “always size up” hides that tradeoff. Encourage shoppers to use the published measurement method and their preferred fit, rather than declaring a universal best size.
Where unit conversion is enabled, keep labels and values aligned. Retain the supplier's original unit and precision as the source, and inspect the converted storefront values. Conversion changes the scale; it does not change the measurement method or establish a US/UK/EU size equivalent.
Add measurement instructions the shopper can use
Use the supplier's actual measuring points and a matching illustration where helpful. Explain whether the item is laid flat, stretched or measured on a person. A sleeve measurement needs its start and end point; the word “sleeve” alone may not be enough.
The listing supports images and video within guides. Use them to answer a question the table cannot answer, such as where to place the tape. Do not publish invented tolerances to make discrepancies look normal. If source documents disagree, resolve that disagreement before asking a shopper to use the chart.
Choose inline, popup, dropdown or floating presentation
The listing offers inline, popup, dropdown and floating presentation. The choices below are merchant layout recommendations, not app defaults.
Choose where the size guide belongs
Inline
Useful situation: Short chart central to selection
Layout consideration: Keep the short chart near the selector when space permits
Popup
Useful situation: Longer instructions or multiple tables
Layout consideration: Use a clearly labeled “Size guide” entry beside the selector
Dropdown
Useful situation: Guide stays in page flow while conserving room
Layout consideration: Make the label identify sizing, not vague “More information”
Floating
Useful situation: Guide must remain reachable on a long page
Layout consideration: Keep it clear of cart, consent and chat controls
A popup beside the selector can suit a page with a large image gallery. Its cost is an extra tap. If shoppers miss it, a more visible label or inline summary may help. These are layout recommendations, not DEVNZO default settings.
Keep sizing information easy to reach while shoppers choose a variant.
A floating guide and chat launcher can compete for the same phone-screen corner. Open both with the consent banner during review. Customers should be able to close the guide and continue selection without accidentally opening another control.
Use size recommendations with clear inputs
The listing includes a smart size recommender. Its public description does not establish the full input model or fit calculation, so review the actual fields in the installed app rather than assigning it an invented algorithm.
Keep measuring instructions accessible from that path. If an input requests chest measurement, establish whether it means body circumference or garment width. The public listing does not explain the complete model; do not assume it takes the same fields as this shirt table or applies a particular allowance formula.
Try a clear match, a boundary case and a value beyond the supported range. Record inputs, results and shopper-visible wording. Compare guidance with the manual table interpretation. A conflict needs explanation before release, especially when a recommendation changes length substantially. Keep the chart and the customer's choice available: advice does not establish comfort or preferred silhouette.
Test mobile readability and translated measurements
On a phone, follow the product image to the size selector, open the guide, change units, read every row, close it and add the chosen variant. Try long labels and enlarged text. When sideways scrolling is necessary, customers must still be able to associate each number with its size and measurement heading.
Use explicit headings such as “Chest width (cm).” When units switch, labels and values must change together. A centimeter heading above inch values is more consequential than a color mismatch.
For translated guides, review measurement terms as carefully as the numbers. Chest, width and circumference must retain their meaning. Right-to-left text and long translated headings deserve a storefront check. Language support helps presentation; a knowledgeable reviewer validates your wording.
Fix recurring size-guide problems at their source
If customers ask “Is this around the chest?”, improve the heading and measuring note. If the wrong fit family appears, fix assignment rather than changing accurate numbers to match an unrelated product. If the chart shows XL but the product stops at L, correct coverage or explain availability.
When a supplier changes a measurement, revise the source, identify affected products and inspect their published guides. Retain the old specification so support can answer questions about earlier purchases. Current information should not erase the record of what an older customer bought.
Before release, check correct size labels, consistent units, usable measuring instructions, verified fit notes, compatible assignments and a readable guide beside the selector. Use DEVNZO Size Chart & Size Guide for its display and reuse tools, then build the content around your product data.
