A Shopify agency's work is repetitive in a useful way. Every new store needs a theme built or customized in Liquid, product data migrated from somewhere else, apps chosen and wired together, checkout and shipping rules tested, and a launch checklist run the night before. Then the retainer begins: speed fixes, a new collection template, a broken integration after an app update, a Black Friday code freeze. The same problems appear across dozens of merchants, solved slightly differently each time.
That repetition across many stores is what makes an agency's archive different from any one brand's. It shows how experienced developers solve the same e-commerce problem in different contexts, in pull requests, tickets and client threads. Mercor takes GitHub repositories, PRs and issues and names e-commerce as an industry. Troveo names code with commits, reviews and bug history. Polyshares names both software and retail.
This page is for Shopify Partner agencies and other e-commerce development shops (BigCommerce, headless, Magento migrations) with ten or more staff. It describes a week of agency records, which buyers fit, why merchant store data and client-owned themes need sorting first, and what to ask before offering anything.
Worth
What a agency's data may be worth
Set for a typical agency, 25 staff and 7 years of records. Move the sliders to match yours. Our estimate, not an offer.
Buyers
Which buyers want this data
Buyers whose own published rules fit Shopify and e-commerce agencies. We can introduce you to the ones we work with.
Featured partners
Polyshares
Names software and retail, buys Slack and tickets, and excludes data held on behalf of clients, which decides how merchant work is handled.6,12,3
- $100K to $2M+, Polyshares says10
- None, Polyshares says13
- An offer in 1 to 2 weeks, then paid in 30 to 60 days14
Watch out for: Exclusive by default, and every deal it lists is exclusive with no end date.15,16
Everyone else we reviewed
By score, with full reviews. We have no referral agreement with these companies, so we do not link out to them.
Mercor
Takes GitHub repositories, PRs and issues, and names retail and e-commerce, so both the code and the domain fit.1,2
Watch out for: It confirmed a cyberattack in 2026, and class actions followed.20,21
Troveo
Names code with its commits, reviews and bug history, the record a theme and app shop builds on every project.4
- Six figures and up for a whole company, Troveo says22
- A share of the revenue; the percentage is not published23
Watch out for: You are paid from a revenue share, so ask what percentage you keep.23
Who wants this
Do buyers want Shopify and e-commerce agencies?
No buyer publishes prices by industry, but their own intake forms show which industries they rate higher.
- Troveo puts developer tools, data and AI infrastructure, and cybersecurity in its top demand tier, and business and consumer apps in its third.24,25
- Polyshares takes software and saas, without marking it premium.26
- VMS, a broker, gives software or tech extra weight when it estimates value.27
Which buyers take a agency your size
Shown for 25 staff, a typical agency. Ask whether contractors and part-time staff count.
micro1
Polyshares
No headcount rule; the length and texture of the record matter more30
Mode
20+ full-time US office staff (accounting firms 10+, law firms 6+)31
Pewter
20+ staff and 3+ years; by industry, from 10+ (healthcare) to 50+ (manufacturing, finance)32,33,34
Grepped
No headcount minimum stated35
Ventra
30+ US employees and 3+ years of records36
Mercor
None stated37
Troveo
No minimum stated; its estimator starts at 2038
Nyne
20+ US W-2 employees and 3+ years39
Endless
Roughly 30+ employees40
Supersoniq
50+ employees and 5+ years41
What buyers value
What in a agency's records buyers value
What buyers look for in your records, and what to talk through with your buyer before anything leaves your systems.
| Data | Where it lives | Why a buyer values it | Raise with the buyer |
|---|---|---|---|
| Theme and app repositories | GitHub with Shopify CLI | Liquid, JavaScript and app code with review history, solving the same store problems across many merchants. | Themes and apps a build contract may assign to the merchant. |
| Migration runbooks and data mapping | Notion, spreadsheets, scripts | Step-by-step moves from other platforms, with the edge cases that broke last time. | Merchant product, customer and order data inside mapping files. |
| Retainer tickets | Jira, ClickUp, Gorgias-to-agency handoffs | Small, real problems on live stores, diagnosed and fixed with the merchant watching. | Store URLs and merchant staff names. |
| Launch and QA checklists | Notion, Google Sheets | The process the agency wrote for taking a store live without losing orders. | Nothing specific |
| Client Slack channels | Slack Connect | Merchants explaining what they need in plain language, and developers translating it. | Anything a merchant shared about its sales or customers. |
A week of records
A week of data at a agency
- Monday: a migration kickoff, with a mapping sheet for 4,000 products and three custom metafields.
- Tuesday: a PR for a new collection template, two rounds of review comments, then merged.
- Wednesday: an app update breaks a merchant's subscription widget, and the fix is traced in a ticket thread.
- Thursday: a pre-sale speed audit written up with six recommendations and estimates.
- Friday: a launch checklist run for a new store, signed off in the client channel at 11pm.
Process
How it works with each buyer
In each buyer's own words. Where a buyer publishes nothing, we say so.
Polyshares
Mercor
Selling or closing
Selling or closing your agency? License its data first
If your agency is rolled into a larger commerce consultancy or wound down when a founder moves on, the archive is worth a look first. The internal starters, checklists and app code the agency built for itself are the parts least tied to any one merchant. Before a deal, ask each licensing company whether those can be licensed on their own and how merchant work in the same repositories would be kept out.3,4
FAQ
Shopify and e-commerce agencies: questions, answered
That depends on your build contracts, which is a question for the buyer and your advisers. Polyshares says it excludes data held on behalf of clients. Starters and private apps the agency built for itself are the safer place to begin.3
Nalandadata ran "We buy private codebases to train AI" and DataFactor "Get paid $5k+ to license your code repos". Both are intermediaries' own ad claims, not AI lab prices.53
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Before you sign
Questions to talk through with your buyer
Every business is different, so these are best talked through with the buyer you're working with. Their team goes over them with you before anything is signed.
Questions for this kind of business
- Which build contracts assign themes and apps to the merchant?
- How are merchant product, customer and order data removed from migration files?
- How are API keys and store credentials removed from repositories?
- Who owns this data: the company, an estate, or someone else?
- How do CCPA, GDPR, UK GDPR and state privacy laws apply, and is de-identified data still personal information?
- Do customer, vendor or platform contracts, NDAs or API terms restrict this?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?