Integrations and synchronisation
We connect your store to 1C, CRM, inventory systems and suppliers, so products, prices, stock and orders stop being moved by hand.
Discuss your project€20–30 / hour
Who it is for
- Prices and stock live in 1C or another back office, but the site is updated manually
- Orders are copied from the site into a CRM by hand — and some go missing
- You dropship: the supplier’s catalogue changes every day
- Several stores or marketplaces that must share one catalogue
- A sync already exists but it breaks, duplicates products or hits API limits
What is included
Systems and data audit
We work out where each piece of data lives and which system owns it. Without that, an exchange turns into a tug of war between two sources.
Catalogue exchange
Products and variants, categories, attributes, images. Matching by SKU so repeated exports never duplicate items.
Prices and stock
Scheduled updates that send only what changed rather than the entire catalogue.
Orders
Orders flow from the site into the back office or CRM automatically, and statuses come back.
Scheduling and resilience
Cron-driven exchange with a job queue and retries: a failed operation is not lost, and one bad product does not stop the rest.
Monitoring
Logs and an alert when the exchange stalls — so you hear about it before your customers do.
How the work goes
-
1
Audit and exchange design
We map the data: what syncs, in which direction, how often, and what wins when two systems disagree.
2–4 days
-
2
Prototype on test data
The exchange is built and run against a copy of the catalogue — production data stays untouched.
5–10 days
-
3
Go live
We switch the exchange on for the live store and reconcile product, price and order counts before and after.
2–3 days
-
4
Monitoring and support
We watch logs and API limits and adapt the exchange as the catalogue changes.
ongoing
Price
€20–30 / hour
The rate covers development, testing and the handover. Scoping your project, writing the estimate and answering questions before you commit are not billed.
Minimum engagement: 10 hours. Below that, the back-and-forth costs more than the work itself.
Rates and budgetsRelated projects
Chameleon: CS-Cart integrated with 1C
A manufacturer’s clothing store on CS-Cart: catalogue, price, stock and order exchange with 1C, plus ongoing support.
1,292 products in the catalogue
Sniky Fox: Shopify store with automated supplier sync
A wooden toy store on Shopify: design built from scratch and a dropshipping supplier integration running on Cloudflare Workers.
38 products synced
Questions and answers
Which systems do you integrate with?
1C, CRMs, inventory systems, shipping services and suppliers. On the store side: Shopify, WooCommerce, CS-Cart, BigCommerce and custom platforms.
What if the supplier has no API?
We work with exports — CSV, XML, on a schedule. For large catalogues that is sometimes faster than per-item API calls.
How do you stay within API limits?
By sending only changes, processing them in batches and putting them through a queue. The exchange fits inside the platform’s limits instead of running for hours.
What happens when the exchange fails?
The job returns to the queue and is retried rather than lost. One failing product does not stop the others, and we get an alert.
How long does an integration take?
Usually two to six weeks, depending on how many systems are involved, catalogue size and how consistent the data already is.
Can several stores be kept in sync?
Yes. The usual shape is a master store as the source of truth with regional stores receiving products, prices and stock from it.