The fix window
Some Plus packages include a thirty-day fix window. Where a service includes one, its package says so.
Every package includes two revision rounds and ends with written notes and a recorded walkthrough. Here is exactly what that means in practice.
The scope sets the target. Revisions bring the result to it.
Before work starts we confirm the scope in writing. A revision is a change that brings the finished work closer to that scope: a color that is off, a spacing that does not match, a behavior that differs from what was agreed. Each package includes two rounds of these.
A round is one batch of feedback from your approver. Collecting all your notes into one message keeps a round efficient and leaves the second round for anything you only notice after the first changes land.
New scope is different. If you want something that was not in the written scope, such as another page, a new feature or a different layout, it is quoted before we start it. This keeps the fixed price honest for both sides.
| Request | Counts as | Why |
|---|---|---|
| Change a color to match the brand file you sent | Revision | The scope was your brand |
| Move a button that sits wrongly on a small phone | Revision | The scope included phone behavior |
| Add a second popup that was not requested | New scope | Not in the written scope |
| Redesign the section after approving it | New scope | The approved design was the target |
| Fix something broken in the delivered work | Revision | It does not meet the scope |
Where it is unclear, your project lead will say which it is before any extra work begins.
Published on your store after you approve it.
A record of what changed and where, in plain words.
A short recording that shows the work and how to manage it.
Any files made for you, delivered in the formats the scope names.
Further changes are quoted as small tasks with a fixed price.
Some Plus packages include a thirty-day fix window. Where a service includes one, its package says so.
Anything outside the scope is quoted as a small task with a fixed price.
Maintenance services cover continued support. See the support page for what ongoing help looks like.
Two rounds are enough for almost every job when you use them well. Here is how to do that.
A revision round is one batch of feedback from your approver. Because each package includes two rounds, the way you collect feedback matters more than the number of changes in it. These habits make rounds efficient and keep projects on time.
Gather notes from everyone who has a say, resolve any disagreements between them, and send a single list. Several small messages across a day can look like several rounds, and conflicting notes can undo each other's work.
Say which page, which section and which device, and describe the gap between what you see and what was agreed. A screenshot with a circle around the problem is worth a paragraph.
The written scope sets the target. When feedback points to a line in the scope, we can check it quickly. When feedback goes beyond the scope, we tell you and quote it as new work, so the price stays honest.
Some things only show up after the first changes land, such as how a section looks on a real phone. Keeping the second round for those discoveries means you are not left without a way to fix them.
Name one person as the approver for your project. One voice makes rounds shorter and decisions clearer.
A round is a short, predictable cycle.
All notes in a single message, tied to the written scope.
We mark each note as a revision or as new scope, with a fixed price for anything new.
Revisions are made in the safe copy and tested on real devices.
You review the updated work and note anything still open.
When you approve, we publish and move to handover.
Handover is how the work stays useful after we leave.
Every job ends with a record of what changed. It is written in plain words so that you, your team or the next person can understand it without asking us.
If you ever hire someone else to continue the work, the handover notes save them time and save you money.
Examples of where the line falls between revision, new scope and support.
| Request | How it is handled | Where to look |
|---|---|---|
| Fix a color that does not match your brand file | Revision | This policy |
| Move a button that overlaps on a small phone | Revision | This policy |
| Add a page that was not in the scope | New scope, quoted as a small task | The services page |
| Change checkout code | Not possible on most plans | The data security and terms pages |
| A problem after you edited the theme yourself | Quoted as a small task | Support after launch |
| Ongoing monthly help | A maintenance service | Shopify maintenance plans |
Short answers to questions people often search for on this topic.
A Shopify handover is the end of a project when finished work is published and the notes, files and a walkthrough pass to the owner. Shopify project handover from us includes written notes and a recorded walkthrough.
A web design revision policy says how many rounds of changes are included and what counts as a revision. Ours includes two rounds in every package.
Shopify rules and policies cover how stores may operate on the platform. Your store also needs its own policies, such as refund, shipping and privacy. To edit a refund policy on Shopify, use Settings, then Policies.
To request a review of a Shopify policy decision, use Shopify's own support channels. For our policy, contact us with your order number and a short description.
Project management software for Shopify projects tracks tasks and approvals. For a fixed-price job, the written scope and one message thread keep it simple.
Owners reach this page from different searches. These are the common ones.
You may also have come across “shopify request review of policy”, “project management software shopify” or “shopify reviews complaints and refund policy”.
Owners also search for “shopify overview and tips”, “shopify inventory onhand new” or “how to edit refund policy on shopify”.
People looking into Shopify Revision and Handover Policy | Store Design Expert also type “how is shopify innovative”, “best multi vendor shopify tutorial” or “shopify overview and pricing”.
Related searches include “shopify plans and pricing”.
Rounds, handover and what happens after. Open any question for the full answer.
Two revision rounds in every package.
One batch of feedback from your approver, which we apply together.
A change that brings the work closer to the written scope, including fixes to anything that does not meet it.
Anything not in the written scope, such as another page, another feature or a different design after approval. It is quoted before we start.
The published work, written notes, a recorded walkthrough and any files named in the scope.
Some Plus packages include a thirty-day fix window. The package states it where it applies.
Yes. Extra rounds are quoted before we begin them.
If it is covered by a fix window it is repaired. Otherwise a repair is quoted as a small task with a fixed price.
You can, but messages sent close together may be counted as one round. A single list is faster and leaves your second round free for later discoveries.
Name one approver whose feedback decides each round. Conflicting notes from several people can undo each other and use up a round.
Further changes are quoted as small tasks with a fixed price, so you always know the cost before work starts.
Yes. Each round's changes are tested on real phones, tablets and desktops before you see them.
Yes. A short screen recording with your voice is a clear way to show what you mean, and we are happy to receive links or screenshots.
The handover notes and recorded walkthrough show you how to manage what we built. If you want more, the catalogue includes training and support services.
See each service's package and what it includes, then place the order with the revision rounds already included.