Skip to main content

Promise implementation

Implement Ingrid Promise in your checkout: the phases, your integration route, your environments and what Ingrid provisions.

J
Written by Jakub Talarek

Use this article to implement Ingrid Promise in your checkout: what each implementation phase covers for Ingrid Promise, how to choose your integration route, how your Ingrid environments work, and what Ingrid provisions for you.

This article is for retailers implementing Ingrid Promise (the Ingrid delivery checkout), and for their developers and agencies. Implementing Ingrid Promise follows the same five implementation phases as any Ingrid implementation. This article covers what is specific to Ingrid Promise.

The implementation phases for Ingrid Promise

The table below shows each implementation phase for Ingrid Promise, who leads it, and what it covers:

Phase

Who leads

What it covers for Ingrid Promise

Ingrid

Your delivery offerings, markets, carrier products, and the systems Ingrid needs to work with.

Joint

Warehouses, regions, carrier products, delivery categories, prices, translations and preselection.

You

Embedding the Ingrid Checkout widget or building against the Ingrid API (application programming interface), and deciding how transport data flows to your other systems.

You

End-to-end testing from checkout to printed label, then launching Ingrid Promise on your live site.

Two ways to integrate Ingrid Promise

Ingrid Promise connects to your storefront in one of two ways, and which one you use shapes the integration phase more than anything else:

  • The Ingrid Checkout widget, through a platform plugin: the fast, low-effort route on a standard e-commerce platform. Ingrid renders the delivery options for you.

  • The Ingrid headless API: you build the delivery experience yourself and keep complete control. More work, more control.

Your Ingrid environments for Ingrid Promise

Ingrid gives you two separate environments in the Ingrid Merchant Platform. The table below shows the purpose and address of each Ingrid environment:

Environment

Purpose

Address

Production

Where you configure Ingrid Promise, and where live operations run. Changes are held as drafts until you publish them.

Staging

Integration development and testing, against your own staging site. Also where your configuration is replicated before go-live, so you have somewhere to test changes afterward.

Each Ingrid environment has its own API keys and its own configuration, and changes in one environment do not sync to the other.

  • Configuration is done in production, where drafts let you build safely without anything reaching shoppers. Before go-live, Ingrid replicates that configuration into staging, so from launch onward you have a configured staging environment for testing future changes.

  • Integration development belongs in staging from the start, against your own test site.

What Ingrid provisions for Ingrid Promise

During scoping, Ingrid creates your accounts in both Ingrid environments. Each account includes:

  • Access to the Ingrid Merchant Platform for that environment

  • Ingrid API authentication tokens (API keys) for that environment

To find your API keys, log in to the Ingrid Merchant Platform for that environment and click the information icon (i) in the header. The Your Ingrid credentials fold-out opens, with one tab per product: Checkout, Upsell, Faq, Product page, Tracking and Receipt. Each tab lists the Site ID, Private key and Private key (base64), with a copy icon next to each. For more detail, see Your Ingrid API keys.

If you have not received your Ingrid credentials, ask your Ingrid implementation consultant or ask Iris, Ingrid's AI assistant, in the chat on the Ingrid Help Center. Don't paste credentials in the chat. Share them securely through secret.ingrid.build. If you can't reach Iris, email [email protected].

Choose your Ingrid Promise integration route

Pick the integration route that matches your e-commerce platform. Confirm the choice during scoping, because it determines how much build work the integration phase involves. The Ingrid Promise integration routes are:

Getting help with your Ingrid Promise implementation

Did this answer your question?