TemplateDocs
Statement of work
A statement of work template covering scope, deliverables, what's excluded, the timeline, payment schedule, and how change requests are handled.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your document
# Statement of Work: Storefront migration to Shopify
**Client:** Northwind Traders · **Vendor:** Anchorpoint Studio · **Date:** 2026-09-04
## Scope
Migrate the existing storefront (140 products, 3 collections) from WooCommerce to Shopify, including theme customization to match the current brand and a redirect map for SEO continuity.
## Deliverables
- Configured Shopify store on the Northwind domain
- Theme customized to match brand guidelines
- Product catalog migrated with images and variants
- 301 redirect map (spreadsheet) and a 2-hour handover call
## Out of scope
Custom app development, loyalty program integration, and any product copywriting beyond the descriptions the client already supplies.
## Timeline
Weeks 1-2: store setup and theme
Week 3: catalog migration
Week 4: QA and redirect testing
Week 5: launch and handover
## Payment schedule
40% ($6,000) on signing, 40% ($6,000) when catalog migration is complete, 20% ($3,000) on launch. Net 15 on each invoice.
## Change requests
Any request outside this scope is quoted separately and confirmed in writing before work starts; it does not change the dates or price above without a signed addendum.
How to use it well
- →The out-of-scope list is the part that actually prevents disputes - write down the requests you expect to get asked for, not just a generic "anything not listed above."
- →Tie each payment to a deliverable that has a visible, checkable finish line, not a calendar date - "on catalog migration complete" survives a slipping schedule better than "by week 3."
- →A change-request clause only works if both sides sign the addendum before the extra work starts; retroactively invoking it after scope has already crept is a negotiation, not a policy.