---
title: "Checkout: scoping"
canonical: "https://ingrid-support.refined.site/space/KB/11436170/Checkout%3A%20scoping"
format: markdown
---
Scoping is phase 1 of your [Checkout implementation](https://support.ingrid.com/space/KB/11501718/Checkout+implementation). **Ingrid leads it.**

The purpose is to write down what your delivery experience needs to do, so that configuration and integration have something firm to build against. It ends with a dated plan owned by both teams.

## The SoW and the planning workshop

Two things shape scoping, and they do different jobs.

Your **statement of work** sets the high-level scope and the boundaries of the project — what is in, and what is not. It is the reference point whenever a scope question comes up later.

The **planning workshop** works through the finer detail: who does what, in what sequence, and what depends on what. This is where the scope becomes a dated plan with named owners on both sides.

> ℹ️ **If you are implementing more than one Ingrid product, sequence matters and it is rarely arbitrary.** A contract renewal with an existing provider, a peak trading period, or a replatforming date can all force one product to go live before another. Bring those dates to the workshop — they are usually the strongest constraint in the room, and they are much cheaper to plan around than to discover.

## What happens

Ingrid runs a kick-off, then the planning workshop with your leads. Between them we gather your requirements, review what is feasible, and agree the shape and timing of the project.

## What you bring

- **Business requirements** — your delivery strategy, the markets you serve, and the delivery offerings you want shoppers to see. You will receive a requirements template from your implementation consultant.
- **Your delivery offerings and carrier products** — which carriers and services, in which markets. Check the [carrier library](https://carrier.ingrid.com) to see what is already integrated.
- **A systems overview** — see below.
- **Any fixed dates** — contract renewals, peak periods, replatforming milestones.
- **Your project team** — named, with owners. See [The team you'll need](https://support.ingrid.com/space/KB/741081090/The+team+you+ll+need). This is the single biggest predictor of your go-live date.

### The systems overview we need

This tells us which integration route fits your setup, so bring it to kick-off rather than discovering it later:

- **E-commerce platform** — Shopify, Magento, WooCommerce, Centra, Norce, Prestashop, or custom and headless
- **Who builds your site** — your own development team, or an agency
- **Logistics systems, where they apply** — WMS (warehouse management), ERP, 3PL, TMS (transport management)

## What Ingrid does

- Explains how Ingrid works and how we run the project with you
- Reviews your delivery offerings and flags anything that needs a different approach
- Provisions your accounts, with API keys for each environment — see [Checkout implementation](https://support.ingrid.com/space/KB/11501718/Checkout+implementation)
- Confirms, per carrier, whether your own carrier credentials are needed or unified Ingrid credentials can be used

> ⚠️ **Start on carrier credentials now.** They are the most common critical path in an Ingrid implementation, and they are often held by your 3PL or logistics team rather than your e-commerce team. Finding out who owns them is a scoping task, not a later one. See [Carrier credentials](https://support.ingrid.com/space/KB/739868692/Carrier+credentials).

## What scoping produces

- A shared, written set of goals for the delivery experience
- A dated implementation plan, owned jointly by your team and Ingrid
- Named owners on both sides
- An agreed integration route, and a view of how much build work it involves
- Where several products are in scope, an agreed order to implement them in

## Next

[Phase 2: Checkout configuration →](https://support.ingrid.com/space/KB/11436180/Checkout+configuration)