Internal tools
Admin screens for jobs your team does in spreadsheets today: approvals, checklists, supplier records and exception queues.
Custom Shopify app development
A Shopify app built around how you already work.
Some workflows are too specific for an app listing: a supplier portal, a warehouse rule, a link between Shopify and the system your team already uses. Describe the process. We scope it in writing, build it on a development store and hand it over once it passes the checks we agreed.
Taking project enquiries
What we build
Software for the step your tools skip.
Admin extensions
Buttons and blocks inside the Shopify admin, placed where your staff already work.
System connections
Data moving between Shopify and an ERP, warehouse system, accounting export or supplier feed through their APIs.
Scheduled jobs & reports
Nightly syncs, exception reports and alerts that run without anyone pressing a button.
Is it worth building?
Signs a custom app will pay for itself.
A custom app makes sense when the same manual work repeats every week and mistakes in it cost real money. If none of these sound familiar, an existing app is probably the better buy, and we’ll say so.
- Someone copies data between two systems every day
- A spreadsheet is the source of truth for something Shopify should know
- An existing app covers most of the job but misses the step your team cares about
- A process only works because one person remembers how
- Errors in the process show up as refunds, stockouts or write-offs
How a project runs
Four steps, written down before the build.
You know the deliverables, the price and the checks before any paid work starts.
- 01
Tell us the process
Email what happens today, which systems are involved and what should change. A few paragraphs is plenty.
- 02
Written scope
Before paid work, you get a statement of work: deliverables, price, schedule, responsibilities and the checks the build must pass.
- 03
Build and review
We build on a development store with representative, anonymized data and review progress with you against the agreed checks.
- 04
Handover
Installation on your store, the documentation agreed in the scope, and support on the terms we wrote down.
Your first email
What to put in it.
Plain language is fine. We will ask follow-up questions.
- What happens today, step by step
- Which systems are involved, Shopify included
- What should be different when it works
- Any deadline that matters, and why
Please don’t email passwords, recovery codes or customer exports. Access is set up through Shopify collaborator permissions once the build starts.
Questions
About custom projects.
What does a custom app cost?
It depends on the scope. You get a written price before any paid work starts, and changes to the scope are agreed in writing too.
How long does a project take?
The schedule is part of the written scope. Shopify reviews and third-party approvals can move dates, and we flag those dependencies up front.
Will it be listed in the Shopify App Store?
Usually not. A custom app is installed on your store. A public listing is a different product that needs Shopify’s review.
Who owns the code?
Ownership and licensing are set out in the written agreement before work starts.
What do you need from us?
One person who owns the decision on your side, collaborator access when the build starts, and sample data without real customer details where possible.
Next step
Describe the process. We’ll tell you what it takes.
Tell us what happens today and what should change. The first deliverable is a written scope with a price, agreed before any paid work begins.
Prefer plain email? Write to support@merchavelo.com