Switching Size Chart Apps: Four Reasons, and When Not To Bother

Four reasons merchants start looking

The motive is nearly always one of these. Decide which one is yours before you read any comparison table — without a named reason, a feature grid cannot tell you anything.

1.You hit a plan ceiling

Most leading size chart apps step their pricing by the number of charts you can build. The typical shape, read in July 2026: 2–3 free, around $5 for 10, around $12 for 20, unlimited around $25.

In apparel, tops and bottoms need different tables, menswear and womenswear differ again, and every wholesale brand brings its own — so 20 fills up sooner than you would expect. Once you are there the choice is to pay the top tier, or move to an app that doesn't bill by chart count at all.

If this is your reason: options exist at roughly $5 for unlimited charts and at roughly $12 for unlimited. If the ceiling is genuinely the only problem, both are worth pricing up before you commit to the top tier.

2.Multi-language turned out narrower than expected

This comes up repeatedly in reviews. One low-rated review from July 2026 reports that the translation feature covers buttons and headings but not the content itself, and that per-locale size guides are not supported.

The pricing is consistent with that shape. Multi-language tends to be designed as something you buy at a higher tier — stepped as English and Spanish, then six languages, then twenty-two — and what the translation reaches has limits.

If this is your reason: establish two things before choosing a replacement. First, does translation reach the contents of the table — size names, fit notes — or only the furniture around it? Second, can you translate it yourself through Shopify's own translation tools? An app that allows that isn't capped by the vendor's language list at all. Translating one chart on a free plan settles it faster than any feature list.

3.You discovered you cannot get your data out

Reviews also mention discovering, after years of use, that the data cannot be exported. This is the single biggest obstacle to switching, and the later you find out, the more it costs — the more charts you have built, the more manual work a migration becomes.

If this is your reason: make the exit a selection criterion. Two checks:

• Can you export to CSV? The minimum escape hatch, and testable on a free plan in minutes.
• Is the data written to your own Shopify metafields? If it is, it stays in your store after uninstall.

There is an irony worth noticing: choosing an app that passes both means you can also leave that app easily when it stops suiting you. A vendor that builds the exit is telling you something about how they expect to keep you.

4.Customising the look requires CSS

Reviewers also ask for easier design options that don't require CSS. Wanting the chart to match your brand without touching code is an entirely ordinary position for a small store.

If this is your reason: on the free plan, check how far colour, type and spacing can be changed without code in the candidate's settings. This is one you have to touch to know — screenshots routinely make adjustable-looking things look adjustable when they are fixed.

Price the switch before you make it

Whatever the reason, switching always costs something. Estimate these three first.

Weighed against that, if reason 1 is your only motive, paying the higher tier is sometimes simply cheaper. Put the monthly difference next to half a day of work plus a gap in coverage and see which one you would rather spend.

What to check on any replacement

Whichever candidates you shortlist, run these on the free plan first. All four take minutes.

1. Compare product page speed before and after. Use PageSpeed Insights and watch CLS especially — a chart that loads late and pushes the page down moves the buy button while someone is reaching for it.
2. Run a CSV export. Confirm you can get data out before you put data in.
3. Check whether it is a theme app extension. Apps built as theme app extensions run without editing theme code and survive theme updates far better. "Add the block in the theme editor" means yes; "paste this tag into your theme code" means you will be fixing it after every update.
4. Read the negative reviews from the last year. Not the star average. Your current complaint may well be sitting in there.

How Mitasu for Apparel handles those four reasons

What follows is not a claim to be better than anyone — it is the design we chose in response to each of the four reasons above, with what we gave up alongside it.

Reason 1(ceilings): no unit that grows

Chart count, product count and order volume do not change the price. It is flat. The design premise was to remove the situation where hitting a limit is what starts you looking.

The trade: there is no high tier for large stores, and our revenue does not grow when a merchant's sales do.

Reason 2(languages): translation isn't capped by our language list

Everything a merchant types — size charts, Q&A — can be translated with Shopify's own translation tooling (Translate & Adapt and similar), because the data lives in your store's metafields and metaobjects and is therefore visible to those tools. There is no ceiling of "how many languages the vendor has added".

The app's own fixed labels ("Size guide" and the like) ship in six languages.

The trade: there is no automatic translation. You supply the wording. That is more work, and we chose it over letting a machine decide how your brand speaks.

Reason 3(data portability): build the exit first

Data is stored in your store's metafields, not on our servers. So it stays in your store after uninstall, and CSV export is on the free plan.

Having told you to confirm the exit on the way in, we could not design something that fails that check. Which also means that if our app stops suiting you one day, you can leave without the problem this article is about. We think that is the correct arrangement.

The trade: data has to fit what metafields can hold, so no elaborate proprietary structures.

Reason 4(CSS): the settings panel has to be enough

Colours, heading typeface and presentation (tabs or a modal) are changed from settings in the theme editor. No code.

The trade: you cannot go beyond what those settings expose. An agency that wants to shape every detail in CSS may find that limiting.

And about the cost of switching itself

This article said switching always costs something. Moving to us is no exception: charts have to be rebuilt, and the block has to be placed again. The 68 bundled templates exist to shorten that rebuild as far as possible, but they do not reduce it to zero.

So if your current app is working for you, staying is the rational choice. This article is only useful to someone who can name what is actually wrong.

It is available now on the Shopify App Store; the details are on the Mitasu for Apparel page.

So: switch or stay?

• If you cannot name the problem in one sentence, stay. Moving on a vague feeling repeats the same outcome somewhere else.
• If it is only the chart ceiling, do the arithmetic first. The migration can cost more than the tier difference.
• If it is languages or data portability, switching is justified. Those are structural, and a higher tier does not fix them.
• Whatever you choose next, confirm the exit on the way in. So the same problem cannot catch you twice.

Apply those four checks to our app exactly as you would to any other. And to repeat: if nothing is actually wrong with what you have, not switching is the cheapest decision available to you.