Use this article to prepare for Ingrid Engage scoping: the decisions to make, what to bring, what Ingrid does, and what scoping produces.
This article is for merchants and project teams starting an Ingrid Engage implementation. Scoping is phase 1 of your Ingrid Engage implementation. Ingrid leads Ingrid Engage scoping.
The purpose of Ingrid Engage scoping is to settle where your tracking lives, where its data comes from, and what your customers will be told, before anything gets configured.
The statement of work and the planning workshop in Ingrid Engage scoping
Two things shape Ingrid Engage scoping, and they do different jobs.
Your statement of work (SoW) sets the high-level scope and the boundaries of the Ingrid Engage 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 Ingrid Engage 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.
Ingrid Engage has a particular dependency on Ingrid Transport. If Ingrid Transport is also in scope, tracking data arrives in Ingrid Engage automatically. If Ingrid Transport comes later, or not at all, your own systems have to push tracking data to Ingrid, which is integration work that belongs in the plan.
Four decisions to make during Ingrid Engage scoping
These four Ingrid Engage decisions shape everything downstream, and all of them are cheaper to decide now than to revisit during testing.
Where Ingrid Engage tracking data comes from. If you use Ingrid Transport, orders and tracking numbers reach Ingrid automatically. If you book elsewhere, your systems have to push orders, parcels, and tracking numbers to Ingrid.
Your tracking page domain. The Branded order tracking page runs on your own domain, typically something like yourbrand.com/tracking. Decide the address early, because it appears in notifications and links.
Which carrier products you track. Each carrier product needs a carrier product mapping so Ingrid Engage can fetch that carrier's events. List them during scoping.
What your customers are told, and when. Ingrid Engage comes with default notification emails covering the main delivery milestones. Decide during scoping whether you want those defaults, your own wording, additional triggers, or text message (SMS) notifications as well, and in which languages. Changing this later means re-testing every market.
What you bring to Ingrid Engage scoping
The carrier products and services you want tracked in Ingrid Engage, per market
Your intended tracking page address
How your orders and tracking numbers will reach Ingrid
Your notification preferences, and the languages you need
Any fixed dates, such as contract renewals, peak periods, and replatforming milestones
Your project team, named, with owners (see The team you'll need)
What Ingrid does during Ingrid Engage scoping
Explains how Ingrid Engage works and how Ingrid runs the project with you
Reviews your carrier products and flags any that need particular handling
Confirms, per carrier, whether your own credentials are needed for status updates or unified Ingrid credentials can be used (see Carrier credentials)
Provides technical documentation and integration support
If Ingrid Transport or Ingrid Care is also in scope, your own carrier credentials are required for those carriers anyway, and the same credentials then cover Ingrid Engage. One collection of credentials covers every product.
What Ingrid Engage scoping produces
An agreed Ingrid Engage setup: tracking page address, data source, carrier products, and notifications
A dated plan owned jointly by your team and Ingrid
Named owners on both sides
Where several Ingrid products are in scope, an agreed order to implement them in