“In stock” does not tell a customer when their chosen size will arrive. They need delivery information for that exact variant to make the decision. If the cart suddenly shows a lead time of several weeks, you therefore need to explain which new information changed the earlier statement.

Trace one variant through the systems

A product with differently available variants lets you trace where the delivery information comes from. Stock, permission to sell, preorder status, handling time and transit time may come from different sources. Once you understand that mapping, you can decide what the data supports showing without exposing every internal field on the product page.

Stock at another location does not necessarily mean the item can leave your dispatch warehouse today. “Ships in two days” also differs from “Arrives in two days”.

Shopify’s documentation distinguishes fulfilment time from delivery-date options. Check the actual basis of the display in your system. A checkout feature is not automatically available on the product page too.

Match the wording to the state

Agree product states with the people responsible for stock and dispatch. Ask:

  • Which variant is selected, and is the selection complete?
  • Can that variant currently be ordered?
  • Is the destination known, or does the information apply to a stated region?
  • Is the date confirmed, a range or an estimate?
  • What should appear if the source is unavailable?

A failed request needs its own message, such as “Delivery estimate currently unavailable”. The last date loaded for a different variant must not remain on screen.

Update information when selection changes

Changing colour, size or version shows whether delivery information keeps up with the selection. If the old text remains until the next response arrives, someone may already assume it describes the new variant. A visible loading state avoids that confusion without implying that an unknown date has been confirmed.

During rapid successive changes, a response may arrive after someone has already selected another variant. A response for Variant A must not overwrite the displayed Variant B. Recording the selection sequence and the delivery information left on screen lets the developers reproduce that exact order of events.

For an unavailable combination, make it clear which choice needs changing. Do not silently remove a selected size simply to display an available combination.

Keep the cart and checkout consistent

In the cart, you can check whether the label and delivery information still match your selected variant. Changing the quantity or destination then shows whether the expected delivery updates clearly before someone completes the purchase.

Multiple items introduce another question: will they ship together or separately? The earliest item’s date does not automatically describe the entire order. Establish how existing fulfilment rules become a customer-facing statement.

Start acceptance checks with a few deliberate cases: an available variant, a preorder, an unavailable combination and a failed data request. Expected wording must come from your actual rules.

Use these cases to accept a shop interface change. If the data mapping is missing before design starts, resolving it belongs in the CRO brief rather than in a check after publication.