---
title: "Checkout fails in non-default WPML languages"
description: "On a WPML site, checkout works in your default language, but in other languages the reservation fails with **Email value not found in form field** or…"
url: "https://homerunner.io/docs/why-does-checkout-work-in-the-default-language-but-fail-with-email-value-not-fou/"
updated: "2026-10-26"
category: Booking engine and checkout
---

# Checkout fails in non-default WPML languages

On a WPML site, checkout works in your default language, but in other languages the reservation fails with **Email value not found in form field** or **Bad Request**.

**Why this happens.** This is a known bug, fixed in HomeRunner Gravityform 0.4.1. The WPML Gravity Forms Multilingual addon translates checkout field labels. Older versions of the HomeRunner Gravityform plugin rely on those labels to read the guest's name, email, and phone. When the labels are translated, the plugin cannot find the values, and the reservation fails.

**What you can do.** Update the HomeRunner Gravityform plugin to 0.4.1 or later. No settings changes are needed after updating. If you renamed field labels to English as a workaround, you can revert those renames once the update is in place.

Still stuck? [Contact the HomeRunner team](https://homerunner.io/contact/) with your site address and what you tried, and we take it from there.