Integration Onboarding Checklist

Use one copy per provider connection. Complete this with the customer’s business owner, provider administrator and Nyoma implementation lead.

Customer / tenantProvider & version Business ownerProvider administrator Nyoma implementation leadTarget go-live date

Do not write passwords, API keys, client secrets or access tokens on this form. Record only the owner and approved transfer method. Secrets are entered through the secure setup process.

1. Business scope

The current order-to-cash and/or warehouse workflow is documented. The system of record is chosen for every in-scope domain. Required sync direction is marked as inbound, outbound or two-way. Supported actions are agreed: read, create, update, cancel, reverse, return and/or credit. Invoice, shipment, return and credit-memo ownership is explicit. Edit-after-sync and provider-outage policies are approved.

Complete: Data ownership worksheet (CSV)

2. Environment & authorization

Provider product, edition, version, region/data center and hosting model are recorded. A non-production sandbox/test company is available. The customer has authority to approve the integration and provider terms. A dedicated least-privilege integration/service user is available where supported. Required API features, licenses, modules and scopes are enabled. Redirect URIs, network allowlists, firewalls or on-premise agents are identified. Credential rotation, expiry and revocation owners are named. Production credentials will be transferred only through the approved secure channel.

3. Data & mapping

Stable external IDs are available for customers, products and transactional records. Customer codes, SKUs, UOMs, currencies, price lists, taxes and warehouses are mapped. Duplicate, inactive and missing records have an agreed resolution owner. Opening balances and historical cutover scope are defined. Personal, payroll and financial data minimization is reviewed. Attachments and documents are included only when required and access-controlled.

Complete: External ID mapping template (CSV)

4. Sandbox acceptance

Authentication, renewal/reconnection and revocation are tested. Every enabled read and mutation is tested against the exact provider version. External IDs remain stable through retries and reconciliation. Duplicate retries do not create duplicate orders, shipments, invoices or credits. Partial delivery and backorder quantities remain correct at line level. Invoiced returns create the approved return/credit path without rewriting history. Provider outage, rate limit, validation failure and stale state are tested. Tenant isolation, roles, audit trail and attachment access are verified. Reconciliation totals and exception ownership are accepted by the business owner.

5. Production readiness

Additive database migrations have been reviewed and scheduled separately. Backup, rollback and disable-connection procedures are documented. Initial sync/cutover window and business freeze are approved. Health monitoring, alerts and retry ownership are assigned. Support contacts and escalation paths are shared. Customer acceptance is signed below before production activation.

Acceptance

By signing, the parties confirm the agreed scope and sandbox results. This checklist does not itself authorize access to production credentials or production deployment.

Customer business ownerName, signature, date Provider / IT administratorName, signature, date Nyoma implementation leadName, signature, date Production change referenceApproved ticket / change ID