Sound familiar?
What shops selling in person on Square and online on Shopify tell us before a project starts.
- We sold the last one in the shop and the website kept taking orders for it.
- I change a price in Square and then do it again in Shopify.
- New products are typed into both systems by hand.
- Online and in-store sales sit in two reports and I add them up myself.
- Returns in the shop never put the item back on the website.
What we build
Each one is a working piece you can open and check when it's done.
Which side is the master
We agree which system owns products, prices and stock, and map titles, variants, SKUs, categories and images across, so each item has one source and no one edits it twice.
API integrations and data sync Custom Shopify appsStock counts across locations
Stock is tracked per location, so the shop counter, a market stall and a warehouse each keep their own count and the website shows what is truly available.
API integrations and data sync n8n, Make and Zapier automationRefunds, discounts and duplicates
In-store returns, discount codes, bundles and items sold at the same moment on both sides are handled by rules written first, and repeated webhook messages are ignored.
Python scripts and utilitiesAlerts on a failed sync
A SKU that exists on one side only, a rate limit or an out-of-range count goes to email or Slack with the item name and cause, and is retried once repaired.
n8n, Make and Zapier automationInitial catalogue and history load
Your existing catalogue is matched by SKU or barcode and loaded in a dry run first, so mismatches are reviewed by you before any live change.
ETL and data pipelines Python scripts and utilitiesCombined sales report and notes
A daily sheet totals sales from both channels by product and location, and handover notes explain how to add products or change the rules.
Dashboards and reportingThe two tools: Square, Shopify.
Also connected on request: Square, Shopify, Google Sheets, Slack, QuickBooks Online.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Last item sold in the shop
Example: a ceramics studio with a Square counter and a Shopify store wants a sale at the till to lower the online count within minutes, so it stops overselling one-off pieces.
Square webhooks, Shopify Admin API, Slack alertsExample project
Market stall and web store
Example: a bakery selling boxed goods at weekend markets and online wants stock kept per location, with the stall count separate from the web count.
Square inventory, Shopify locations, scheduled jobExample project
New product entered once
Example: a bike shop wants a product created in Shopify to appear in Square with its variants and barcode, instead of being keyed in a second time.
Shopify webhooks, Square catalog API, Google SheetsQuestions people ask first
Isn't there already a native connector or app for this?
Apps that sync Square and Shopify exist, and some shops get on fine with one. We check yours first. If it fits, we set it up properly. If its limits are the trouble, such as how it treats variants or multiple locations, we build around them.
Will it change our existing catalogue?
Only in the ways agreed. We run a dry run, show you the proposed changes, and apply them after you approve.
Who owns what you build?
You do. It runs in your own Square and Shopify accounts, with notes on how to change it.
How do we start?
Tell us how many products and locations you have and which system you trust for stock. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com