How can I remove certain fields from the checkout process?

Store Design
1

Hope everyone is well. We would like to remove a few fields from the Checkout as we have noticed they are increasing abandonment. Our sector regulated and we thought that adding another age gate field at check out was a good idea, but it is just confusing most people and we want to remove it.

We want to remove Please Confirm Your Birthdate and the text below it with the green background.

Any help would be appreciated.

2

Convenience , ease of use, or even bad UX does not overrule legal responsibilities.

So be certain this will not cause sever legal issues. And try to confirm and validate what the “confusing” even means; after all the confused people could just very well be the segment you want to avoid as a risk.

adding another age gate

TRIPLE check you are not using things like buybuttons, permalinks, or channels, etc that send customer directly to checkout and thus bypass any age gate in /cart for the online sales channel thus making having another age gate in checkout absolutely critical. Don’t muck about here.

Alternative take , If customers are going directly to checkout, then instead you may just need a way to flag checkouts that have already age validated in the /cart and that flag hides the second age gate in the checkout step. So online-sales channel based checkouts are not having to double verify.

checkout.liquid

Modifying checkout.liquid yourself requires a store to be on Shopify Plus plan

https://shopify.dev/themes/architecture/layouts/checkout-liquid

If this was added by an app you should contact that app for uninstallation support.

If this was done by Shopify support contact shopify support https://help.shopify.com/en/questions ,or the Plus stores MSM

If you made NO other customizations you need to keep, then just back up your theme along with the current checkout.liquid then just get a new copy of your theme|checkout.liquid then replace the current checkout.liquid; contact me if you need help with that approach.

Once undone TEST thoroughly.

3

@PaulNewton

Thanks for your advice. I have not altered any the checkout.liquid.

If I delete

{% include “checkout-age-gate” %}
will this remove age gate filed from check out?

The entire checkout.liquid file is below:

{{ page_title }}

{{ content_for_header }}

{{ checkout_stylesheets }}
{{ checkout_scripts }}
{{ ‘checkout.scss’ | asset_url | stylesheet_tag }}
{{ ‘checkout.js’ | asset_url | script_tag }}

{% if template != “index” %}{% endif %}

{% render ‘shogun-head’ %}

{{ skip_to_content_link }}
{{ content_for_logo }}

{{ order_summary_toggle }}

{{ content_for_logo }} {{ breadcrumb }} {{ alternative_payment_methods }} **
{% include "checkout-age-gate" %}
**

To ensure that your order reaches the correct person, Photo ID matching the name on the credit card is required, and the billing address must match what the credit card company has on file.

{{ content_for_layout }} {{ content_for_footer }}

{{ tracking_code }}

4

As long as your sure you know WHO did it and WHY, especially if this is a problem you inherited that’s gone undocumented.

If I delete ** {% include “checkout-age-gate” %}
** will this remove age gate filed from check out?

Seems reasonable to me.

Do basically the following process during low traffic hours , retesting the order process like a customer to minimize expensive problems.

First, in checkout review the developer console for any current errors and make note of them for another step.

Second ,I’d comment out the snippet instead of outright deletion . i.e. as part of process for obsoleting features when your not using version control.

{%- comment -%} 2022-01-05 

**Third** , once the snippet is disabled once again [open the developer console for errors](https://developer.chrome.com/docs/devtools/open/#console) to see if any new error has been created the can correlate to the change.

**Fourth** , If there's an app involved make sure if it needs to be disabled as it may be injecting javascript that expects that HTML element(s) to exist and if it doesn't exist anymore that javascript could cause issues, possibly showing as new errors in the console.

If sucha n app does not have a specific setting for the checkout then make if it's the same one used for the cart page that it's not now also disabled for the cart page completely disabling all age-gates.

*If your not sure if an app is involved inspect the theme file for that snippet 'checkout-age-gate' for possible clues.*

Beyond that,

There's also ' {% render 'shogun-head' %} ' which isn't clear if related at all? if the age-gate form was created in shogun and shogun isn't used elsewhere in checkout then *maybe* disable it for checkout? Be sure it's not used for undocumented things.

Going forward at minimum entries like that age-gate and shogun render in the checkout liquid really need to be given **aggressive** & **verbose** comments at time of creation as a matter of business policy. That way there's some sort of living documentation about what's going on in the most critical file of a store.

Goodluck.