---
title: "Checkout: configuration"
canonical: "https://ingrid-support.refined.site/space/KB/11436180/Checkout%3A%20configuration"
format: markdown
---
Configuration is phase 2 of your [Checkout implementation](https://support.ingrid.com/space/KB/11501718/Checkout+implementation). **It is joint work** — you bring the delivery logic, we configure it with you and coach your team to run it afterward.

This is the bulk of most projects. Most of go-live is configuration, not code.

## What happens

Ingrid runs an introduction workshop covering the platform and the fundamentals, then supports your initial configuration. By the end of the phase your own team should be able to administer the setup without us.

All configuration happens in the Ingrid Merchant Platform.

## What gets configured

These are the building blocks of a Checkout setup, roughly in the order you build them:

1. [Warehouses](https://support.ingrid.com/space/KB/11469312/Warehouse) — where you ship from, including addresses and coordinates
2. [Cut-off times](https://support.ingrid.com/space/KB/11502273/Setting+up+cut-off+time+in+Ingrid+Merchant+Platform) — the point in the day after which Ingrid adds another day to the delivery promise
3. [Regions](https://support.ingrid.com/space/KB/11436420/Regions) — the geographies each delivery offering applies to, by country or postal code
4. [Carrier products](https://support.ingrid.com/space/KB/11436854/Carrier+products) — the carrier services you offer
5. [Delivery categories](https://support.ingrid.com/space/KB/11469537/Delivery+categories) — what shoppers actually see and choose between
6. [Shipping prices](https://support.ingrid.com/space/KB/11436543/Shipping+prices), and price rules where you want the price to vary by cart value or contents
7. [Translations](https://support.ingrid.com/space/KB/14614543/Setting+up+translations) — so delivery options read correctly in every market you sell in
8. [Preselection order](https://support.ingrid.com/space/KB/11469608/Preselection+order) — which option is selected by default, per market

**Two companion pages worth having open:**

[Checkout: configuration walkthrough](https://support.ingrid.com/space/KB/458391554/Checkout+configuration+walkthrough) — the screen-by-screen build, with screenshots.

[Delivery setup patterns](https://support.ingrid.com/space/KB/740982790/Delivery+setup+patterns) — which setup shape fits your business, before you start clicking.

## What you bring

- **Your delivery logic** — the offerings, prices, and rules you agreed during scoping
- **The people who will own it** — the Ingrid administrator role trains during this phase, so name them before it starts rather than after

## What Ingrid does

- Runs the platform introduction workshop
- Configures the initial setup with you
- Reviews any customization you want beyond the standard configuration
- Coaches your team so they can make changes themselves afterward

## Where to configure

First, a point that causes confusion: **"Ingrid production" means your Ingrid environment, not your live website.** It is a brand-new instance with nothing running through it. During the build it connects to your staging site — your live site only connects at go-live.

The usual default is to **configure in production**. Changes are held as drafts until you publish, so nothing reaches shoppers before you are ready. Then, before go-live, Ingrid replicates your configuration into **staging**, so from launch onward you have a configured staging environment to test future changes in. The two environments do not sync, so this is a deliberate copy rather than something that happens by itself.

**The direction can also reverse.** If something production needs is not yet in place — most often carrier credentials — we start in staging, move to production once they arrive, and the final copy runs staging to production instead.

Which way round your project runs is agreed together during scoping. It varies from project to project, so treat the above as the common default rather than a fixed rule.

## What configuration produces

- Your delivery strategy reflected in a working Checkout configuration
- A widget that looks and behaves the way your business requires
- A configured staging environment to test future changes in
- A team that can administer the configuration without depending on Ingrid

## Next

[Phase 3: Checkout integration →](https://support.ingrid.com/space/KB/11534561/Checkout+integration)