Ingrid offers three ways to bring delivery selection into your checkout. They differ in two things that matter: who builds the interface, and which capabilities are available. This page explains what each option is, so you can tell which one fits your setup.

If you are already on V1 and want to move to V2, see Migrating from Checkout V1 to V2.

The original Ingrid checkout integration. Ingrid returns an HTML snippet that you embed, and the widget handles delivery selection for the shopper.

V1 is legacy and no longer actively maintained. Existing V1 integrations continue to work and no retirement date has been announced — but V1 receives no new capabilities. The address form, delivery groups, the return promise, and the Ingrid AI features (predictive delivery times and profit-optimized delivery) are all V2 only.

If you are on V1, plan a move to V2 rather than building anything new on it. See Migrating from Checkout V1 to V2.

The current widget-based integration, and the evolution of V1. It embeds the same way, and adds:

If you want delivery selection working quickly, with a proven interface you do not have to build or maintain, V2 is the option to choose. To move an existing V1 integration across, see Migrating from Checkout V1 to V2.

Headless gives you the delivery data and expects you to build the interface. There is no widget and no HTML snippet — you render the delivery categories, options, pickup points, and prices yourself.

It suits retailers who need full design control, or whose storefront architecture is decoupled. In exchange, you take on more: building and maintaining the delivery selection UI, collecting the address yourself, and managing checkout state in your own frontend.

Headless is not a standard part of a Checkout purchase. Using it requires explicit, written permission from Ingrid Sales, so talk to your Ingrid contact before planning an integration around it.

Choose V2 if you want the fastest route to a working delivery experience, you would rather not build a delivery selection interface, or the built-in address form, pickup point maps, and delivery time display are useful to you. This suits most retailers.

Choose Headless if you need a checkout design the widget cannot produce, your architecture requires a decoupled frontend, or you want delivery options rendered natively inside an existing custom checkout — and you have frontend resources to build and maintain that UI.

If you are on V1, migrating to V2 is the smaller step: the embedding model is the same, and the work is mostly on the API and response-parsing side. Moving from V1 straight to Headless means building a delivery UI from scratch.