Guides
E-commerce web design scope Chicago agencies can adapt
E-commerce web design scope Chicago agencies can adapt: retail discovery questions, phased estimates, staffing, accessibility, and ongoing care planning.
What to take away
This e-commerce web design scope is a general retail-agency framework Chicago agencies can adapt, not a guide to local rates or vendors.
- Size a retail e-commerce build by SKU count, integration count, and the fixed launch date, not by page count.
- Run discovery for two to four weeks and close it with a phase table, a written scope, and a published change order rate.
- A common split in agency estimates is 20 to 25 percent discovery and design, 55 to 65 percent build, and the rest launch and care.
- Put accessibility, content entry, and maintenance in the first estimate, because retrofits cost more than planning.
Discovery questions that set the estimate
Six questions decide whether a retail build lands near the low or the high end of a range.
Discovery questions
- How many SKUs are active today, and how many will be active a year from now?
- Which system is the record of truth for stock, price, and orders?
- Who writes product copy and shoots photography, and on what schedule?
- Which states and provinces do you collect sales tax in, and who files the returns?
- What does one return cost you, including shipping and restocking labor?
- Which date is fixed by a buying season, and which date can move?
A retailer with a few hundred SKUs, one warehouse, and a hosted platform signs a shorter scope than one with drop ship vendors, a distribution center, and a custom checkout.
Unanswered questions become assumptions, and assumptions carry a price. Write them into the scope document so the client sees the cost of deciding late.
How a mid-market retail build gets phased
| Phase | Typical length | What the client signs off |
|---|---|---|
| Discovery and data audit | 2 to 4 weeks | Scope, integration list, change order rate |
| Design system and templates | 3 to 5 weeks | Home, category, product, cart, checkout screens |
| Build and integration sprints | 8 to 14 weeks | Staging site, ERP and tax connections, test results |
| Launch and stabilization | 2 to 4 weeks | Redirect map, tracking, rollback plan |
| Care plan | Monthly or quarterly | Ticket limits, response times, release schedule |
Deliverables to name before build
- List the storefront templates and states in scopehome, category, product detail, search results, cart, checkout, account, and order status, including mobile layouts.
- Name the actual catalog and commerce systems. Common platform examples include Shopify, WooCommerce, and Adobe Commerce (Magento); specify which one the client uses rather than leaving the platform undecided.
- List the payment gateway, shipping carrier, and any POS or ERP connections. Examples include Stripe or PayPal, UPS, FedEx, or USPS, and—if they are in the client’s stack—Square POS or NetSuite.
- Define product-data migration, inventory and order sync, tax and shipping calculations, and the test cases for payment failures, refunds, and checkout. Record who owns PCI DSS compliance and what payment data the agency will handle.
Phases keep the client paying for decisions rather than open ended hours. Each phase ends with a sign off and a list of what the next phase covers.
Retail build phases and sign-offs
- Discovery and data audit2-4 weeks Scope, integration list
- Design system and templates3-5 weeks Home, category, product screens
- Build and integration sprints8-14 weeks Staging site, ERP, tax
- Launch and stabilization2-4 weeks Redirect map, tracking, rollback
- Care planMonthly or quarterly Ticket limits, response times
Discovery is the cheapest place to find an integration that adds six weeks to a build. Skipping it moves that discovery into a build sprint, where the answer arrives later and costs more.
Where retail builds break the first estimate
Content entry is the usual gap. A few hundred products need names, descriptions, images, alt text, and variants, and clients often expect the agency to absorb that work.
Tax and shipping rules come next. For Illinois sales, scope who configures tax calculation, collects and remits tax, and files returns. The Illinois Department of Revenue says a remote retailer that meets or exceeds either threshold for a 12-month period must collect and remit all applicable state and local retailers’ occupation tax administered by IDOR on all retail sales to Illinois purchasers and file all applicable returns for one year, under the Illinois remote-retailer rule. For additional city or county tax questions, confirm the relevant obligations with the Chicago Department of Finance or Cook County Department of Revenue and the retailer’s tax adviser. Free-shipping thresholds and return labels each need a rule set, a test plan, and a named owner on the client side.
Promotional calendars break estimates quietly. A retailer running weekly markdowns needs scheduled price changes, banner swaps, and clearance logic inside the templates.
Example: a few hundred SKUs and one warehouse
Suppose a Chicago apparel retailer sells a few hundred SKUs from one warehouse and takes store orders through a POS.
A first scope covers discovery, a design system, a hosted storefront, tax and shipping configuration, and a launch checklist.
A second scope, priced on its own, covers ERP sync, loyalty, and a care plan. Presenting both scopes together keeps phase two from arriving as a surprise.
Staffing the build: employees, freelancers, and paperwork
Retail builds spike. Agencies bring in contractors for photography, front end work, or data migration, then scale back after launch.
Classification matters. The IRS test for an independent contractor weighs behavioral control, financial control, and the working relationship.
Employees carry payroll tax and overtime obligations. The Department of Labor explains those rules in its wage and hour overview.
Collect a Form W-9 from each contractor, store it with the signed scope, and pay on a schedule the client can audit.
Write the deliverable, the rate, and the ownership terms into the contract before hiring starts.
Accessibility and the launch checklist
Retail builds answer accessibility expectations from shoppers and regulators. WCAG 2.0 Level AA is the common target, so plan the work as a checklist item rather than a rescue project. Record the applicable ADA requirements in the scope, and include Section 508 criteria when federal agency work or contract requirements make them relevant.
Accessibility launch checklist
- Target WCAG 2.0 Level AA for product, cart, checkout
- Write alt text for every product image and swatch
- Test keyboard operation through search, cart, payment
- Check form error messages for screen reader output
- Answer AODA rules for Ontario information and communications
Clients shipping into Ontario also answer AODA rules for information and communications. Fixes cost less at the template stage than after content entry.
What the client pays for, and how the fee conversation goes
Retail clients ask for one number before discovery. Agencies answer with ranges tied to the phase table, plus an hourly rate for work outside the written scope.
A care retainer covers releases, patches, and small template changes. Agencies without one absorb those requests at no charge.
Branding fees follow the buyer rather than the deliverable. The New York agency branding pricing breakdown explains how finance and fashion clients sign differently, and that pattern repeats when a retail client asks for a discount.
When the retailer is also rebranding, the page on how to price branding work for finance and fashion buyers shows how the buyer type sets the final fee.
Common questions
How long does a retail e-commerce build take?
Scope sets the timeline more than the platform does. A hosted storefront with light integrations moves faster than a custom build with ERP and POS sync.
Should we hire employees or freelancers for the build?
Spikes favor freelancers, and steady care work favors a small in house team. Check classification rules before committing, because the tax treatment differs.
What belongs in a care plan?
Ticket limits, response times, and a release schedule. Add hosting, plugin updates, and a monthly report on checkout errors.
