As a catalog grows, the problem is not always a missing size chart. It may be the wrong chart appearing on the right product. Algoshop AI Sales Chatbot helps merchants answer shopper questions, but those answers depend on clear product information. Size-guide maintenance should follow verified fit and construction, not merely a seasonal collection name.
Lemon Size centralizes reusable Shopify size charts and assigns them by product, collection, vendor, type, or tag. Its listing also supports guide images, tips, and disclaimers. The catalog benefit is keeping one verified family consistent while giving a different construction its own guide.
This guide follows chart creation, assignment and maintenance without inventing supplier specifications or storefront test results. The operating checklists are merchant recommendations, not claimed Lemon Size defaults.
When one size chart can serve several products
Shared charts work when the underlying measurement specification is shared. Three colorways of one shirt construction may use one chart. Three shirts in a “New arrivals” collection may not: the collection describes merchandising, not fit.
Use four criteria for sharing: the same measurement method, compatible size labels, the same specification values and the same fit notes. A flat garment-width table and a body-circumference table need separate treatment even when both contain S, M and L. Different supplier names are a clue to investigate, while identical supplier names alone do not prove compatibility.
Treat reuse as a product-data decision: the team should be able to point to the specification that makes the shared chart appropriate. A product title or copied tag is not that evidence. Record genuine exceptions before building assignment rules.
Create reusable charts with Lemon Size
The official product page describes a simple sequence: create or import a chart, assign it using product data, then publish it on the storefront. Manual creation supports rows, columns, units and measurements; CSV import provides another route for supplier data already held in a spreadsheet.
Prepare the approved values and measuring method before importing. Confirm the accepted CSV format with the app rather than inventing column names. After import, inspect the headings, units and actual values; a completed upload is not evidence that the supplier's chart was correct.
The site describes a theme app block and product-page display. Chart preparation and storefront integration are separate checks: a correct chart in the app is not useful if customers cannot find it in the theme. Review the intended product template and the live customer-facing experience before expanding.
Keep the source document and its review date in the team's product record. This is merchant recordkeeping, not a claim that Lemon Size has a built-in supplier revision system.
Why a reusable guide matters as the catalog grows
The strongest reason to consider Lemon Size is not that a table looks better than a paragraph. It is that sizing information can be managed around product families rather than copied repeatedly. Its official listing describes a central place for reusable charts and several ways to decide which products show them. That suits a catalog where the next new color should use an existing specification, but the next new cut should not.
Consider a merchant adding seasonal colors to a regular shirt. The measurement work is already done. The new product needs the correct guide and its supporting measuring note, not another independently maintained copy. Now consider adding a boxy shirt from the same supplier. Reusing the regular chart would save work at the cost of misleading the buyer. The useful distinction is construction, not merely vendor or collection membership.
Two catalog changes that should not receive the same treatment
Another color of the same construction
Check that its measurements and fit match the maintained family. Use the appropriate assignment condition and review the published page. Reuse keeps the product's sizing explanation aligned with the other colors.
A different cut from the same supplier
Create or select a separate verified guide. Keep its measuring images and fit notes with that chart, even when both styles appear together in a storefront collection.
Guide images, tips and disclaimers are useful because a measurement table cannot explain everything by itself. A simple diagram can distinguish flat width from circumference; a verified fit note can explain the intended silhouette. Keep those explanations product-specific. A disclaimer should clarify a genuine limitation, not replace accurate measurements.
Lemon Size is therefore a good product to evaluate when organization and correct placement are the bottleneck. If the main need is an automated fit recommendation, investigate that requirement separately rather than assuming it follows from reusable-chart support. The map below shows what to record before configuring assignments.
Build a product-to-chart assignment map
Make the intended storefront result explicit before configuring rules. Do not begin with an invented catalog ID scheme and assume the app expects it.
What the team should record
Shared specification
Identify the products that genuinely share measurements, size labels and fit notes.
Source material
Keep the supplier's approved chart and measuring instructions accessible to the person maintaining it.
Exceptions
Identify different cuts, suppliers or stock batches that must not inherit the shared guide.
Assignment owner
Name the person who checks the rule and the product-page result when a product is added or changed.
These are merchant responsibilities, not required Lemon Size database fields. A reference sheet can connect products to their intended guide without implying that the app imports every internal column.
For each product requiring sizing, record its expected chart and source. That lets a reviewer find incorrect assignments which a neat chart library alone would not reveal.
Choose assignment conditions that reflect your catalog
Every assignment method has an operating consequence. Use the condition your staff can maintain accurately when products are added or changed.
Swipe horizontally to read the full table.
| Condition | Good fit | What the merchant should check |
|---|---|---|
| Product | Individual exception | New exceptions need explicit review |
| Collection | Collection contains one verified family | Seasonal groups may mix constructions |
| Vendor | Supplier has one sizing specification | One supplier may use several incompatible specifications |
| Product type | Type reliably separates construction | “Shirt” may include both regular and boxy shapes |
| Tag | Team maintains a dedicated sizing-family tag | Missing or copied tags can silently change coverage |
Use the method your team can maintain reliably. A dedicated sizing-family tag can be useful, but it is a merchant convention—not a required app field. A vendor-wide rule is appropriate only when the vendor's relevant products actually share a specification. Fewer rules are not better if they make exceptions invisible.
Match the guide to the product so customers compare the right measurements.
Handle products that match several rules
A product can belong to a collection, vendor and product type at the same time. If separate assignment rules could match it, do not assume a product-specific rule always wins: the public pages do not establish precedence.
Reduce accidental overlap before expanding. Use a narrower positive group for a verified family; do not claim exclusions or priority settings exist without checking the installed app. Where multiple rules remain, inspect the actual product page and ask support to clarify the result.
Keep a short review record: the product, matching conditions, expected guide, observed guide and corrective action. This is the team's check, not a native conflict report. A chart that looks correct in an admin preview can still be missing or wrong on the published product template.
Update charts when supplier measurements change
A supplier revision changes the source of truth. Before editing a shared guide, establish exactly which dimension changed, which products use that construction and which stock is actually being sold.
| Revision check | Why it matters |
|---|---|
| Approved source | Distinguishes a genuine specification change from a transcription error. |
| Affected products | Identifies where the shared guide needs review. |
| Sellable stock | Old and new batches may not match the same measurement table. |
| Supporting instructions | Measuring images and fit notes must still match the values. |
| Storefront result | Confirms the intended guide is visible after the actual publish/assignment steps. |
If old and new stock share a product and variant, immediately replacing the guide may misdescribe goods still shipping. Ask fulfillment which specification applies. The merchant may need to separate the products, delay the revision or explain the variation accurately; chart software cannot decide that physical-stock policy.
Retain the previous source for earlier-customer questions. Verify how editing a shared chart affects assigned products in the installed configuration instead of inferring automatic propagation from the word “reusable.” Also review every displayed unit after a change; an old conversion beside a new source value is contradictory information.
Audit a sample catalog before expanding
Use actual catalog cases: an existing assigned product, a newly added compatible product, a different construction and a known exception. Inspect labels, units, measuring notes and expected chart on each page.
Then test a catalog change. Move a regular shirt into a merchandising collection that also contains knitwear. If sizing is controlled by a dedicated family group, its chart should remain correct. Inspect a new product missing its sizing-family assignment; identify the missing guide before publication rather than letting it inherit a vendor chart.
Keep the release record actionable: product, expected chart, observed chart, revision, reviewer and corrective action. Do not reduce it to “all charts checked.” The record should show which exception and new-product behaviors were tested.
The useful result is specific: every product requiring sizing shows its intended current chart. Count a missing or wrong chart as unresolved work rather than inflating coverage with accessories that do not require sizing.
Keep chart ownership part of product publishing
The product owner decides the measurement source and family; the storefront reviewer checks the customer-facing result. Add a sizing-family decision to the new-product process, and review revisions when construction, supplier or stock batches change.
Lemon Size is a useful candidate when your bottleneck is repeated chart maintenance and product assignment. Start with the official listing, implement a small family map and prove the exceptions before rolling it across the catalog. For measuring instructions and the customer-facing comparison itself, use the separate Shopify size-guide tutorial.
