E-commerce
Connect Shopify and Chrono24
A watch that sells on one channel comes off the other, from one product record.
- Data flows
- 4 automated, two-way where safe
- Built with
- Shopify, Chrono24, SmartSuite
- Timeline
- Live in 2 to 8 weeks from scope
- Owned by
- You, with accounts, credentials and code in your name.
Connecting Shopify to Chrono24 keeps a watch dealer from selling the same piece twice. SBD built this for a D2C watch reseller using one SmartSuite product record, Make scenarios and a connection to Chrono24 through the Missive app. Update time fell by 80%, and inventory mismatches dropped to zero over the following 90 days.
What runs between Shopify and Chrono24
Each line is one automated workflow, with the same checks, logs and alerts on all of them.
-
Watch dealers on several channels
WhenA watch is added to the master record
ThenPrepare and push listings for each channel
-
Fast delisting after a sale
WhenA watch sells on any channel
ThenRemove it from the others and update the record
-
Per-channel listings
WhenA listing is rejected
ThenTell the owner what the channel needs changed
-
One product record
WhenA daily check runs
ThenCompare what is live on each channel with the record
Where the simple setup breaks down
A one-step Zap connects Shopify and Chrono24 in an afternoon. This is what goes wrong once volume grows.
Most watches are one of one
A normal store can absorb a small delay because it holds more stock. A pre-owned watch cannot, so an out-of-date listing can mean selling something you no longer have.
Each channel wants different listing data
Titles, categories, images and details that work on Shopify do not suit Chrono24 as they stand. A single description copied across leads to rejected or weak listings.
The connection needs choosing carefully
Check what access Chrono24 gives your account before designing anything. On our build, the connection runs through the Missive app.
A marketplace sale may need manual steps
Chrono24 sales can involve enquiries and negotiation before they complete. The sync has to treat a reserved watch properly, and not only a finished sale.
Used for
- Watch dealers on several channels
- Fast delisting after a sale
- Per-channel listings
- One product record
- Chrono24 with Shopify
- Chrono24 with eBay
- Listing clean-up
- Reserved watch handling
- Daily listing checks
- What is live where
Built with
- Shopify
Chrono24
SmartSuite
Make
Missive
Standards on every build
Validation, retries, reconciliation, audit logs and alerts come as standard, with credentials and accounts in your name. Read the integration standards
Where we have done this
What people ask about this pair
Can this include eBay as well?
Yes. Our build covered Shopify, eBay and Chrono24, with mapping for each.
How fast is delisting?
It depends on the access each channel gives you. We measure it during the build and agree what happens during any gap.
Do we need SmartSuite?
Not necessarily. The key is one master record. SmartSuite is what we used, and Airtable or a database can do the same job.
Related pairs
-
Shopify and eBay
One stock record behind both channels, so a unit that sells on one comes off the other.
-

SmartSuite and Make
SmartSuite holds the record, and Make sends changes to the other systems within the API quota.
-
Shopify and Airtable
An Airtable base that stays in step with Shopify through refunds, partial fulfilment and edits.
- Solution
Operations
The workflows we automate for this kind of team.
Connect Shopify and Chrono24
A watch that sells on one channel comes off the other, from one product record.
Start with a discovery call











