How a Designer and Shopify Developer Split a D2C Launch

Most D2C launches in India now involve two teams: a designer or design studio that owns the look, and a Shopify developer who makes it work. Done well, the brand gets a store that looks custom and behaves reliably. Done badly, launch week is spent arguing about why the live site does not match the design file.

On AQUON, the hydration brand from Yuzvendra Chahal and Ishant Sharma, we did both the design and the Shopify development, which removed the handoff entirely. Most brands do work with a separate designer, though, so this is how we make the split work when there are two teams.

If you are a designer, this is what your developer needs from you. If you are a founder, this is what to check before you hire either side.

Who owns what between the designer and the Shopify developer?

The cleanest split we have found is this: the designer owns decisions about what the shopper sees and feels, and the developer owns decisions about how Shopify makes it happen. The overlap is small but important, and it should be agreed on paper before development starts.

On AQUON, where we held both roles, the design defined the brand's hero, flavour cards, founders story and ingredient cards, and each of those became its own custom Shopify section. You can still see the result in the store's code, where the sections are named after the brand.

What does a Shopify developer need in the design file?

Static screens are not enough. A design that only shows the happy path leaves the developer guessing, and guesses become inconsistencies. These are the things we ask every designer for before we write code:

• Mobile first, then desktop. For most Indian D2C stores, the majority of traffic is on phones. The mobile design is the real design.
• A section inventory. A list of every distinct block on the site, so we build each one once and reuse it, instead of building five slightly different versions.
• States, not just screens. Sold out, on sale, long product name, no reviews yet, one review, an empty cart, an error message.
• Real content. Actual product names, prices and ingredient text. Lorem ipsum hides every layout problem until launch day.
• A type and colour scale. A small set of named sizes and colours, so the theme settings map cleanly to the design.

What should the designer expect back from the developer?

The handoff runs both ways. A good developer does more than follow the file. They should flag what will cost performance, what Shopify handles differently from the design, and what the brand team will need to edit themselves.

Specifically, expect your developer to tell you early when:

• a design choice needs an app, and what that app adds to page weight
• a layout depends on data the store does not have, such as a per-product field that needs a metafield
• a pricing display conflicts with how Shopify variants and compare-at prices work
• an animation or effect will be expensive on low-end Android phones

None of that is a developer overruling the designer. It is the developer protecting the design from being broken by the platform later.

How do you keep custom sections editable after launch?

This is where many designed stores fail six weeks after launch. The brand wants to change a line on the homepage, and it turns out the text is hardcoded, so they need a developer for a copy change.

Our rule is simple: anything the brand might change goes into section settings in the theme editor. Headlines, body text, images, button labels, which products appear, and the order of blocks. On AQUON's ingredient cards, for example, each ingredient's name, amount per serving and explanation are the kind of content that should be editable, because a formulation update should not require a code deploy.

The designer's role here is to design with that in mind. If a section only works with exactly three items of exactly the same length, it will break the first time the brand adds a fourth.

What should the first handoff meeting cover?

One hour at the start saves a week at the end. We run the first handoff as a walkthrough of the design file with the designer present, section by section, and we leave with written answers to these questions:

1. Which sections repeat across pages, and which are one-offs?
2. What will the brand team edit weekly, monthly and never?
3. How do prices, discounts and pack sizes need to display, and does that match how the products will be set up in Shopify?
4. Which apps are already decided, such as reviews, checkout and tracking, and where do they appear in the design?
5. What happens on mobile for every wide layout, carousel and hover effect?
6. Who signs off on the build, and against which version of the design?

Shopify's developer documentation on theme sections and section settings is worth a designer's time too. Knowing what a section can and cannot expose as a setting makes designs that are easier to build and easier to live with.

What goes wrong most often between design and development?

In our experience the same handful of problems cause most of the friction, and almost none of them are about skill. They are about assumptions nobody wrote down.

• Fonts. A licensed font in the design file with no web licence, or four weights where two would do, each one slowing the page.
• Image crops. Product photos that look perfect in one layout and awkward in another, because the design assumed a crop the product photography does not have.
• Hover-only interactions. Effects that reveal information on hover, which simply do not exist on a phone.
• App widgets. Review stars, badges and pop-ups that arrive with their own styling and ignore the design system.
• Sign-off drift. The design changes after development starts, and nobody agrees which version the build is measured against.

Every one of these is cheap to settle in week one and expensive to settle in launch week.

How should credit be shared on a two-team build?

Openly, and accurately. When one team does both, say so. When two teams share the work, credit both. On AQUON we did both the design and the Shopify development, which we have written up in our piece on who built the AQUON website.

Clear credit helps everyone. Founders searching for help know who to call for which part. Designers get their work recognised. Developers stop being invisible. A footer line like "Design by Studio A, development by Studio B" costs nothing and settles the question for customers, journalists and search engines alike.

What should a founder check before hiring a designer and a developer separately?

Splitting design and development gives you specialists on both sides, but it also creates a gap between them that someone has to own. Before you sign either contract, check these four things:

• Have they worked together before, or with teams like each other? A designer who has handed files to Shopify developers before will already design in sections and states.
• Who owns the timeline? One person should be accountable for the launch date, even if two teams do the work.
• What is included after launch? Bugs found in the first two weeks, small copy changes and app issues all need an owner.
• Can you see live stores, not just designs? Ask the developer for links to stores they built and click through them on your own phone.

If the answers are vague, the gap between the two teams will become your problem during launch week.

What does this cost, and how long does it take?

It depends almost entirely on how many custom sections the design calls for and how complex the product setup is. A store with a handful of custom sections and simple products is a very different job from one with bundles, subscriptions, multiple markets and a custom product builder.

We would rather give you a real estimate from your actual design file than a range that fits nobody. Our breakdown of Shopify landing page design costs in India shows how we think about scope, and for a full store build the same logic applies section by section.

Are you a designer who needs a Shopify development partner?

We work with independent designers and design studios who own the brand and the visual system, and who want a Shopify team that builds their designs faithfully and keeps them editable. The design credit stays yours. We handle the Shopify build.

Send us a design file and a launch date, and we will come back with what is straightforward, what needs a decision, and a realistic timeline.