Whether and when to collect Codice Fiscale is for you and your accountant to decide. This guide only compares the ways to do it, with the benefits and limits of each.
1. Optional native field
In Italian checkouts Shopify can show the Codice Fiscale field, one of the native tax fields of the Italian checkout. According to Shopify’s help page, these fields appear after the payment details, and after the order the value is on the order details page.
Pros. No app and no theme changes. There is a single question, inside checkout, and the value stays in Shopify.
Cons. With the standard settings the field is optional: customers can complete the order without filling it in. For orders that need an invoice, the merchant then has to ask for the code after the purchase and may have to delay the invoice.
2. Native Codice Fiscale field made required by an app
An app can make the native field required and check its format before the order is completed. This is CF Ready’s approach: it uses the native checkout field for orders with delivery and billing in Italy.
Pros. It works on the Basic, Grow, Advanced and Plus plans, with no theme changes and no new fields. The value stays in the native field. With CF Ready you choose between optional and required, independently for Codice Fiscale and PEC, with messages in Italian and English.
Cons. It needs an app. It only works where Shopify shows the field: an app cannot create it. Since 6 November 2026 the native field itself rejects numeric codes and omocodia, before any app. In some express payment flows Shopify does not show the field. The formal Codice Fiscale check does not verify who the code belongs to.
3. Renamed Address 2
The label of the second address line is changed and the line is used for Codice Fiscale.
Pros. No app. Shopify’s checkout form options let you make the second address line required.
Cons. The requirement applies to every customer, including those abroad, and Shopify warns that some may not be able to proceed. The field does not check the code’s format. The value sits in an address field, so it may travel with the address into integrations. If Shopify also shows the native field, customers see two similar requests. The details are in the guide on Codice Fiscale in Address 2.
4. Cart or theme field
A box is added to the theme’s cart page, often through an app or custom code. The value travels as a cart attribute and reaches the order.
Pros. Available on every plan, with free choice of wording and position.
Cons. The field sits on the cart page, before checkout. Express payment buttons and direct checkout links can skip it, and any requirement depends on the theme code. It has to be maintained whenever the theme changes. The value stays an order attribute, separate from the native tax field.
5. Checkout UI Extension
A developer or an app can add a custom field inside checkout with a Checkout UI Extension.
Pros. The field is inside checkout, with tailored wording and behaviour.
Cons. According to Shopify’s developer documentation, extensions on the information, shipping and payment steps are only available to stores on Shopify Plus. It takes development work or a dedicated app. The value is custom data, separate from the native field: if Shopify shows that one too, customers may see two requests.
6. Asking for Codice Fiscale after the order
The merchant contacts the customer after the purchase, by email or with a form.
Pros. Checkout stays as it is. It suits rare cases, or codes that the native field currently rejects.
Cons. Customers may not reply, the invoice is delayed, and staff have to chase each reply and match it to its order. The value arrives outside Shopify and has to be copied by hand.
How to choose
- If it is enough for customers to add it when they want, the optional native field will do.
- If you need it on every order and want to leave your theme as it is, consider the native field made required by an app.
- If you are already on Plus and need fields other than the native ones, consider a Checkout UI Extension.
- For customers with a numeric or omocodia code, a channel to send it after the order is still useful today, if it fits your case.
Address 2 and cart fields do not check the format and can create duplicate requests: it makes sense to replace them once the native field is available.
Frequently asked questions
Can I make Codice Fiscale required on Shopify without an app?
Not with Shopify’s standard settings: the Codice Fiscale field in the Italian checkout stays optional. Making it required takes an app that works on the native field, such as CF Ready.
Do I need Shopify Plus to collect Codice Fiscale?
Not to make the native field required: CF Ready works on the Basic, Grow, Advanced and Plus plans. Plus is needed for Checkout UI Extensions on the information, shipping and payment steps.
Which option also works with express payments?
A cart field can be skipped. The native field is inside checkout, but Shopify does not show it in some express payments: with CF Ready you decide in the app how to handle these orders. Before you make the field required, test the express payments you offer in your store.
Do the same options work for Partita IVA and Codice Destinatario?
This guide covers Codice Fiscale only. CF Ready handles Codice Fiscale and PEC and does not handle Partita IVA, the SDI Codice Destinatario or e-invoicing.