E-commerce and marketplaces
Shopify automation, built around how you work.
The storefront for most of the e-commerce businesses we work with.
- Tool
- shopify.com
- Usually paired with
- Airtable, eBay, QuickBooks, WhatsApp Business API
- Timeline
- Most builds live in 3 to 5 business days from scope
- Owned by
- You. Accounts, credentials and code in your name.
What we build on Shopify
- Mirror orders, stock and customers into an operations base
- Post payouts and fees to accounting so the bank reconciles
- Sync listings and stock to marketplaces
- Tell customers where their order is on WhatsApp
What we sync
Workflows we are asked for
- Shopify order sync with edits and refunds
- Shopify payouts to QuickBooks or Zoho Books
- Shopify to eBay inventory sync
- Shopify order status on WhatsApp
- Shopify returns and exchanges workflow
Documented in depth
Shopify integrations with the full write-up.
-
Shopify and Airtable
Not a one-way order dump. A synced operational base that survives refunds, partial fulfilment and edits.
-
Shopify and eBay
One source of truth for stock, so the same unit is never sold twice on two channels.
-
Shopify and QuickBooks
Books that reconcile to the payout, not just to the order total.
Often paired with
Tools Shopify usually needs to talk to.
-
Shopify and Airtable
A relational database with a spreadsheet face, used as the operations base for teams who have outgrown sheets.
-
Shopify and eBay
The marketplace most multi-channel sellers add second, with its own listing rules and limits.
-
Shopify and QuickBooks
Intuit's accounting platform for small and mid-size companies, with an API that rewards care.
-
Shopify and WhatsApp Business API
The channel customers in most markets reply on, with templates, sessions and consent rules.
-
Shopify and Klaviyo
Email and SMS marketing for e-commerce, built on customer events.
-
Shopify and WooCommerce
The WordPress store, flexible and often held together by plugins.
In every build
The same standards, whichever tool.
Under the hood
- Upserts keyed on the record
Every write is matched on the source ID. A retry or a re-fire updates the existing record instead of creating a second one.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays, then parked for review, never dropped.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Every run records input, mapping result, action taken and who or what triggered it. Searchable by record.
For the team
- Slack or email notifications
The alerts go to a named person, not a channel nobody reads. You choose Slack, email, WhatsApp or all three.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from day one. If we leave, it keeps running.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
Keys and data
- Keys live in a vault, never in code
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts, not personal logins
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Every platform account we set up has two-factor authentication on, with recovery codes handed to you, not kept by us.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
The offer
Put Shopify to work with the rest of your stack.
A fixed scope agreed in a thirty-minute call, live in three to five business days for most builds, accounts in your name, and the engineers who built it on call for sixty days after.
- ScopeThirty minutes to agree the workflows, the fields and the owner. Written up the same day.
- BuildValidation, upserts, retries, reconciliation and an audit log, on n8n, Make or code.
- Go-liveSandbox first, then a switch. Longer only where a vendor approval sits on the path.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about Shopify.
Why not a Shopify app from the store?
Apps are fine for one-way, standard flows. Edits, refunds, multi-channel stock and your own accounting rules are where they stop, and where we start.
Shopify
Start with the one Shopify workflow your team still runs by hand.
Bring it to a thirty-minute call. You leave with a yes or no on fit, the shape of the build, and what we would do first.
Book the call