Free template · CSV
Ecommerce ERP Integration Launch Checklist
What to verify before the first real order flows into your ERP — and who signs it off.
Download CSV
26 rows · opens in Excel, Google Sheets, or Numbers · no sign-up
Integrations rarely fail on launch day because of code. They fail because a credential expired, a webhook pointed at staging, a tax code was never mapped, or nobody knew who to call. This checklist covers what has to be true before go-live, grouped by area, with a way to verify each item.
Use it as a shared sign-off sheet: each item gets an owner and a status, and launch happens when every “must” item is done.
How to use it
- Assign an owner to every item — a name, not a team.
- Mark items that don’t apply as N/A with a short reason instead of deleting them.
- Run the checklist in a dress rehearsal one or two days before launch, then again on launch day.
- Keep the completed file with your launch notes; it’s the starting point for the next integration.
What each column means
- ID
- Stable reference for the item.
- Area
- Group: access, mapping, reliability, data, operations, finance, rollback.
- Check
- What must be true at go-live.
- How to verify
- The concrete test or evidence that proves it.
- Priority
- Must (blocks launch) or Should (fix within the first week).
- Owner
- Person responsible for the item.
- Status
- Not started, In progress, Done, or N/A.
Preview
The full template, exactly as in the download.
| ID | Area | Check | How to verify | Priority | Owner | Status |
|---|---|---|---|---|---|---|
| A1 | Access | Production credentials are created for the integration only, with least-privilege scopes | Review app scopes and ERP role permissions | Must | Not started | |
| A2 | Access | Secrets are stored in a secrets manager, not in code or chat | Search repo and config for keys; review secret store | Must | Not started | |
| A3 | Access | Token expiry and refresh are handled, with an alert if authorization is revoked | Force a token refresh; revoke in a test store and confirm alert | Must | Not started | |
| A4 | Access | Webhook subscriptions point to the production endpoint | List subscriptions via API and compare URLs | Must | Not started | |
| A5 | Access | Webhook signatures are verified on the raw body | Send a request with a bad signature and confirm it is rejected | Must | Not started | |
| M1 | Mapping | Every active SKU in Shopify exists in the ERP | Run a SKU comparison report; zero unmatched | Must | Not started | |
| M2 | Mapping | Every payment gateway, shipping method, and tax line maps to an ERP code | Review mapping tables against last 90 days of orders | Must | Not started | |
| M3 | Mapping | Locations map one-to-one between Shopify and the ERP | Compare location lists | Must | Not started | |
| M4 | Mapping | The field mapping is documented and signed off by finance and operations | Signed mapping document in repo | Should | Not started | |
| R1 | Reliability | Orders are created with an idempotency key / external reference | Replay the same webhook twice; one ERP order | Must | Not started | |
| R2 | Reliability | Transient errors retry with backoff; permanent errors go to a review queue | Simulate ERP timeout and a validation error | Must | Not started | |
| R3 | Reliability | Rate limits on both systems are respected under peak load | Load test with expected peak-day volume | Must | Not started | |
| R4 | Reliability | A scheduled reconciliation job catches missed events | Disable webhooks briefly; confirm reconciliation recovers orders | Must | Not started | |
| D1 | Data | Opening stock is loaded and matches the ERP | Compare per-location quantities for top SKUs | Must | Not started | |
| D2 | Data | Historical/open orders are either migrated or explicitly excluded | Written decision; spot-check migrated orders | Must | Not started | |
| D3 | Data | Customer and B2B account mapping is complete | Count unmatched accounts; zero for B2B | Should | Not started | |
| O1 | Operations | Dashboards show order lag, failures, and queue depth | Open dashboard; confirm live data | Must | Not started | |
| O2 | Operations | Alerts reach a person who can act, with a runbook | Trigger a test alert; confirm it is received and acknowledged | Must | Not started | |
| O3 | Operations | Support knows how to find an order across both systems | Walk through lookup by order number | Should | Not started | |
| O4 | Operations | Warehouse or 3PL has confirmed the fulfillment flow end to end | Ship a test order to an internal address | Must | Not started | |
| F1 | Finance | Sales, tax, discounts, and shipping post to the agreed accounts | Post test orders; review journal entries with finance | Must | Not started | |
| F2 | Finance | Refunds and partial refunds reverse correctly | Run refund test cases from the test plan | Must | Not started | |
| F3 | Finance | Payout reconciliation works for at least one real payout | Reconcile a payout; clearing account returns to expected balance | Should | Not started | |
| B1 | Rollback | There is a written plan to pause the integration without losing orders | Pause and resume in staging; no orders lost | Must | Not started | |
| B2 | Rollback | Manual fallback process exists for orders if the integration is paused | Document who keys orders and how they are reconciled later | Must | Not started | |
| B3 | Rollback | Launch timing avoids peak sales days and has the team available | Calendar check; on-call roster for first 72 hours | Should | Not started |
Notes
- This checklist is a starting point. Add items for your ERP, warehouse, and compliance requirements.