Use this article to test and launch Ingrid Promise, phases 4 and 5 of your Ingrid Promise implementation: the three testing layers, the warehouse and shopper experience checks, the end-to-end booking flow, and the go-live steps.
This article is for testing leads, testers and project leads on an Ingrid Promise implementation. You lead both Ingrid Promise testing and go-live. Ingrid supports you, helps resolve what you find, and runs hypercare alongside you after launch. You lead testing because you know your delivery logic, your downstream systems and your edge cases. Nothing goes live until it passes testing.
Phase 4: Ingrid Promise testing
Test Ingrid Promise across three layers:
System integration: does data move correctly between your e-commerce platform, Ingrid, and your WMS (warehouse management system) or ERP (enterprise resource planning) system?
Carrier logic: does each carrier service behave and respond correctly?
End to end: from the shopper choosing a delivery option in the checkout to a printed label.
Agree your testing lead and named testers early. Testing that is unresourced at the start of the project is one of the most common causes of a slipped go-live date.
Warehouse checks for Ingrid Promise
Set cut-off times per warehouse. The cut-off time is the time of day after which Ingrid adds another day to the delivery promise. For example, if a delivery category shows 1–3 business days with a 15:00 cut-off time, orders placed after 15:00 show 2–4 business days.
Confirm that warehouse addresses and coordinates are correct. Learn more about warehouses
Shopper experience checks for Ingrid Promise
Run these shopper experience checks in order:
Load every country with the correct locale. Learn more about locales and translations
Confirm the preselected delivery option is correct per market. Learn more about preselection order
Review delivery category naming in every language your sites use. Learn more about translations
Test the delivery time promise on each delivery option. Learn more about delivery time
Test shipping prices, including any price rules. Learn more about shipping prices
Check the free delivery indicator across multiple countries and cart values. Learn more about the free delivery indicator
Confirm every external method ID is set correctly per region. Learn more about external method IDs
Confirm information forwards correctly to your WMS.
Confirm the correct label prints, end to end.
The end-to-end booking flow for Ingrid Promise
The end-to-end booking flow runs from the checkout to a printed label. Each end-to-end test covers order creation, shipment creation, shipment booking, label generation, label print, carrier confirmation, customs declarations where international shipping applies, and debugging anything that fails using the trace ID.
Check every carrier service rather than a sample:
Book one or two shipments with each shipping method, and keep the booking requests, responses and labels.
Build multiple scenarios to cover the range of things shoppers actually do.
Once a label is generated, confirm its size, format, fonts and content are correct, or say what needs changing.
Activating a new carrier method in Ingrid Promise
When a carrier method is new to your setup, also check the add-ons, that the carrier credentials are correct and activated, that the customer ID is right, the labels themselves, and that EDI (electronic data interchange) files reach the carrier and are correct. For products shipping outside the EU, verify the customs declarations for the carrier product in question.
Phase 5: Ingrid Promise go-live
Going live with Ingrid Promise means your configuration is published in Ingrid production and the Ingrid Checkout widget is switched on for shoppers. The Ingrid Promise go-live steps are:
Replicate your configuration into staging. Ingrid copies your production configuration across before launch, so that from go-live onward you have a configured staging environment to test future changes in. The two Ingrid environments do not sync, so this is a deliberate copy.
Choose your rollout. Every market at once, or a pilot market first and the other markets in waves. See Big bang or phased.
Launch. You lead the cutover.
Hypercare. Ingrid runs hypercare alongside you immediately after launch, so issues get resolved quickly while volumes ramp up.
Handover. When hypercare ends, the Ingrid Customer Success and Support teams become your ongoing contacts. Your own Ingrid administrator owns the Ingrid Promise configuration from here.
What Ingrid Promise go-live produces
At the end of go-live, you have:
Successful end-to-end tests
Ingrid Promise live on your production site
A configured staging environment for testing future changes
A team that can administer and change the Ingrid Promise configuration themselves