Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Statements of work for integrations

What a statement of work for an Exponential integration should contain - scope per flow, deliverables, customer obligations, assumptions, acceptance, change requests, ownership and licensing of the code, data…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/integrators/statements-of-work-for-integrations.md

On this page

Statements of work for integrations

This page is for integrators and their customers who write the statement of work (SOW) for an integration project. Integrations depend on systems and people the integrator does not control, so a good SOW is precise about scope, about what the customer delivers, and about what happens when the other system changes. This page is a practical outline, not legal advice; have contracts reviewed by your own counsel.

Contents

  1. The sections of a SOW
  2. Scope per flow
  3. Customer obligations and assumptions
  4. Ownership and licensing
  5. A template outline

The sections of a SOW

SectionPurpose
Background and goalsWhy the integration exists, in the customer's words
ScopeThe flows, each with its interface specification as an annex
Out of scopeWhat is explicitly not included (for example: changes in the other systems, data cleansing at the source)
DeliverablesThe integration extension, documentation, runbook, tests, training
Customer obligationsAccess, test instances, credentials, contacts, answers, decisions, by dates
AssumptionsEach assumption of the estimate, so a broken one becomes a change request rather than a dispute
Timeline and milestonesPhases from the playbook, with dependencies on the customer
AcceptanceAcceptance cases per flow, the acceptance period, what counts as a defect
Change requestsHow changes are requested, estimated and approved
CommercialsPrice model, payment milestones, expenses
Ownership and licensingWho owns which code; licenses of what is used
Data protectionRoles under data protection law, processors, data flows (not legal advice)
Hypercare, warranty, maintenanceWhat happens after go-live and for how long

Scope per flow

Describe each flow in the same way, and attach its interface specification:

ItemExample
Name and directionERP products into Exponential
Trigger and timingNightly at 02:15; a delta every hour from 07:00 to 19:00
VolumeUp to 25 000 products; up to 2 000 changes a day
MappingAnnex A, mapping table of the class product
Keyserp-product-<ARTNR>
RemovalsProducts missing from a full export are hidden
ErrorsInvalid records skipped and reported; a run stops when the file has less than 80% of the products
MonitoringAlerts as in Annex B
Acceptance casesAnnex C

Customer obligations and assumptions

Write them as dated obligations, not as hopes:

  • To do: Test instance of each other system available by <date>, with test data resembling production.
  • To do: Credentials for test and production provided through an agreed secure channel by <date>.
  • To do: A technical contact per other system who answers within one working day.
  • To do: Data owner decisions (mapping, removals, master data) within five working days of a question.
  • To do: Changes to the other systems' APIs announced at least <n> weeks ahead.
  • To do: The Exponential installation runs a supported version (for example 6.0.15) with the agreed extensions.

Ownership and licensing

Agree explicitly:

  • Customer-specific code (the mapping extension): usually owned by or exclusively licensed to the customer.
  • Generic connectors the integrator brings or builds: often stay with the integrator, licensed to the customer; or are published as open source with the customer's consent (Contributing integrations back).
  • Exponential and its extensions are GPL v2 (or any later version); the customer receives them under that license, and code distributed together with them must respect it (Licensing for partners).
  • Credentials and data belong to the customer and are handed over at the end (Handover).

A template outline

STATEMENT OF WORK  <project name>                       between <customer> and <integrator>     version <n>, <date>

1  Background and goals
2  Scope
   2.1 Flow 1: <name> (interface specification: Annex A1)
   2.2 Flow 2: <name> (Annex A2)
3  Out of scope
4  Deliverables
   - Extension <name> in repository <location>, release <version>
   - Documentation and runbook; tests; operator training (<hours>)
5  Customer obligations (dated)
6  Assumptions
7  Timeline and milestones
8  Acceptance (cases: Annex C; period: <days>; defect classes)
9  Change requests
10 Commercials
11 Ownership and licensing
12 Data protection (data flows: Annex D)
13 Hypercare (<weeks>), warranty (<period>), maintenance (separate agreement)
Annexes: A interface specifications, B monitoring plan, C acceptance cases, D data flows
Signatures

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x