ZeDaq.ai
Shopper using virtual try-on for a tailored suit

Custom Checkout Fields for Measurements on Any Platform

By the ZeDaq.ai team · · 4 min read

On this page
  1. Should you collect measurements at checkout at all?
  2. Which measurements should you ask for?
  3. What methods work on any platform?
  4. How do you validate measurement input?
  5. How do you get the data to your team?
  6. What does a worked setup look like?
  7. What about privacy?
  8. Which platform makes this easiest?

To add measurement fields at checkout, pick the few measurements you really need, add them as custom fields or order notes on your platform, validate the input, and make sure the values reach your production team with the order. The method differs by platform, but the design rules are the same everywhere.

This guide is for store owners and developers selling made-to-measure or alterable clothing. If you run WordPress, see virtual try-on for WooCommerce for the sizing side. Platform-specific steps also exist for WooCommerce custom fields for customer measurements, and the principles below apply to any store.

Should you collect measurements at checkout at all?

Sometimes. Checkout works for made-to-order items where the buyer has to give numbers to place the order. For ready-to-wear, a size recommendation on the product page is usually easier.

Typed measurements have a weakness: shoppers guess, mismeasure or mix units. Treat them as a starting point you can confirm, not a guarantee.

Which measurements should you ask for?

Ask for the fewest numbers that let you make the garment. Every extra field loses some buyers.

Garment Common fields
Tops and shirts Chest, waist, shoulder, sleeve length
Dresses Bust, waist, hips, length
Trousers and skirts Waist, hips, inseam or length

This is an example table. Replace it with the fields your pattern maker uses. Add a short help text and an image for each field.

What methods work on any platform?

You have four main options.

Option 1: Native custom fields

Some platforms let you add text or number fields to products or checkout. This is clean when available, but plans and themes limit it.

Option 2: Product line-item properties or order notes

Many platforms save extra form data on the cart item or order note. It is the most portable option. The downside is free text, so validation is limited.

Option 3: A separate measurement link

Instead of asking at checkout, send the buyer a link after purchase. The shopper opens it on their phone and gives measurements. Tailors use this with clients; see sending a measurement link for the idea.

Option 4: A script-tag widget plus your size chart

For ready-to-wear, the ZeDaq.ai widget works on WooCommerce, Wix, Squarespace, BigCommerce and custom sites. Paste <script src="https://www.zedaq.ai/widget/zedaq.js" data-key="…" defer> into the product template. Lock the key to your domain in Dashboard → API keys. It adds "Try it on" and "Find my size", and recommends sizes from the size chart you entered. Setup is in the widget docs.

How do you validate measurement input?

Bad data causes remakes. Add these checks:

  1. Use number inputs, not free text.
  2. Let the shopper choose centimeters or inches, and save the unit with the value.
  3. Set a sensible minimum and maximum for each field and show an error if the value is outside it.
  4. Show a "how to measure" image beside each field.
  5. Ask the shopper to confirm a summary before paying.

Plan for a human check. If a waist looks larger than hips, email the shopper before cutting.

How do you get the data to your team?

Make the measurements appear on the order email, packing slip or production sheet. If staff must open another screen to find them, they will be missed.

For custom stores, store the values as structured fields in your database, not in a single note. Then you can search and reuse them.

For developers who want a body scan in the flow, the REST API exposes try-on at POST /api/v1/tryon with an x-api-key header. Read the API guide for developers and the API reference.

What does a worked setup look like?

Take a small brand selling made-to-measure trousers on a custom-built store.

  1. The product page shows three number fields: waist, hips and length, with a unit switch.
  2. Each field has a short help line and a picture showing where to measure.
  3. The server rejects values outside a set range and shows a clear message.
  4. The order email lists the values and unit in a table.
  5. A staff member reads the table before cutting and emails the buyer if anything looks odd.

Nothing here needs a special tool. It needs consistent fields, checks and a person who reads the data.

What about privacy?

Body measurements are personal data. Tell shoppers why you collect them and how long you keep them. Put this in your privacy policy, and collect only what you need.

Which platform makes this easiest?

It depends on your theme, plan and developer time. The comparison of the best ecommerce platform for a small clothing brand helps if you are still choosing.

Add sizing to your store through the API

FAQs

Can I add checkout fields without coding?

On many platforms, yes, through plugins or built-in options. Custom stores need a developer.

Should measurements be required?

Only for made-to-measure items. For ready-to-wear, make them optional and offer a size chart instead.

How do I reduce wrong measurements?

Show images, validate ranges and ask for a final confirmation. A quick staff check before cutting also helps.

Can the shopper edit measurements after ordering?

Decide this in advance. Many stores allow changes until production starts.

Try ZeDaq.ai free

Virtual try-on and Find my size for your store, plus client, order and invoicing tools for tailors, in one subscription.

Related articles