When you connect Merlin Business Software to your eCommerce platform, you open up a powerful stream of automation. But syncing everything just because you can? That’s not always the smartest move.
In this post, we’ll walk you through what data is worth syncing between Merlin and your eCommerce store—and what’s better left out to avoid clutter, confusion, or technical headaches.
The Goal of Integration: Smart, Not Overloaded
A good integration is about efficiency and control—not just volume. Syncing everything can slow systems down, create conflicting data, or unnecessarily complicate your workflow. The best approach? Sync what adds real value.
Let’s break it down.
What You Should Sync
1. Product Data
This includes product names, SKUs, descriptions, and pricing. Keeping these consistent across both systems is essential for accuracy, SEO, and customer trust.
2. Stock Levels
One of the most critical data syncs. Real-time stock updates from Merlin to your eCommerce store prevent overselling and keep your listings up to date.
3. Orders
Incoming orders should be pushed from your eCommerce site into Merlin so your team can handle dispatch, invoicing, and customer tracking from one system.
4. Customer Data
Syncing customer details like names, addresses, and order history helps with account management and personalised service.
5. Prices & Discounts
Pricing logic, including tiered pricing and discount rules, should flow from Merlin into your online store to ensure pricing consistency.
6. Despatch Status & Tracking
When orders are marked as dispatched in Merlin, syncing that status back to the eCommerce platform gives customers peace of mind and reduces support queries.
7. Credit Limits (for B2B)
For trade accounts, syncing credit limits from Merlin to your store allows customers to stay within approved boundaries without manual checks.
What You Probably Shouldn’t Sync
1. Legacy or Obsolete Products
Don’t flood your store with products that are no longer active, out of stock indefinitely, or discontinued. Filter these out at the integration level.
2. Internal Notes or Back-Office Fields
Data that’s only useful internally (e.g. cost prices, internal tags, supplier notes) should stay within Merlin. Customers don’t need it, and it can clutter your eCommerce backend.
3. Every Single Data Field
Just because Merlin contains 50+ fields for a product doesn’t mean your eCommerce platform needs them all. Keep your store lean and focused on what the customer needs to see.
4. Incomplete or Draft Product Listings
Only sync products that are fully ready with imagery, pricing, and descriptions. Drafts or placeholder data can hurt the customer experience.
5. Non-Customer Accounts
If Merlin contains placeholder accounts, test profiles, or internal records, make sure they don’t end up in your eCommerce CRM.
Choose Your Integration Scope Wisely
When setting up a Merlin integration—whether it’s with Magento, Shopify, WooCommerce or another platform—it’s not just about connecting everything. It’s about making smart decisions on:
- What your team needs to manage efficiently
- What your customers need to see
- What keeps your store fast and easy to use
That’s why we offer three levels of integration: Basic, Advanced, and Bespoke. You only sync what matters—and nothing more.
Need Help Planning Your Integration?
We help retailers identify what data adds real value and what’s better left out. If you’re unsure what to sync between Merlin and your eCommerce store, we’ll guide you through it.