><
A Lynx Devs product
The platform that connects your ERP with your online store
1
Platform
3
Systems it connects
Real time
Synchronization
Tailored
Parameters and rules
Every new connector, a development from scratch
Connecting an ERP with an online store usually means one of two things: a generic plugin that breaks with your specific setup, or a custom build you have to repeat from zero every time you change platform. Lynx Hub is the third option.
Marketplace modules that don't hold up
They promise to connect any ERP with any store, but fail as soon as your setup goes beyond the standard: custom fields, multi-warehouse, your own business rules.
Redoing the build for every ERP
A point-to-point connector only serves one ERP and one store. Change ERP tomorrow, or open a second store, and you start from zero again.
No visibility into what's happening
When the sync fails at 3am, a loose script won't warn you. No dashboard, no logs, no way to know what synced and what didn't.
Maintenance nobody owns
Custom scripts without active maintenance break with the first version update to your ERP or your store. And when it happens, you don't even know where to start.
We connect your ERP without touching your catalog
The ERP doesn't run your store. Your PrestaShop store is the sales channel, and what already ranks keeps ranking. Here's what we don't touch, and how we make it possible.
We never delete anything, even with data already on both sides
The hard case is having a catalog in PrestaShop and records in your ERP at the same time. That's exactly the one we solve, without recreating products or changing their URLs.
Sync only when something changes
No periodic full dumps that overload your store or your ERP. Only what changed gets synced, when it changed — your store doesn't slow down during peak sales hours.
We build the fields your ERP is missing
Your ERP has no fields for SEO title, description or friendly URL. If you want them synced, we create them on both sides — we don't leave them empty or regenerate them from the product name.
Maintenance and support included, and a clean exit
The plan includes compatibility updates and support from the team that built it. And since we never touch your catalog, if you ever leave, your store stays intact — only the sync stops.
Ask this to any connector provider — we already have the answer
- What happens to my current catalog? Would it get deleted?
- Does the connector place a heavy load on my store and ERP, or does it only connect when something changes?
- If I stop working with you one day, what happens to my store?
What Lynx Hub is
A synchronization layer between your ERP and your online store. The engine is the same for any platform it connects — what changes is the specific connector for each integration.
One engine, several connectors
Lynx Hub isn't a single, closed connector: it's a platform with a common sync engine (queues, retries, logs, dashboard) on top of which a specific connector is built for each integration. Today: Odoo ↔ PrestaShop.
Real bidirectional sync
It's not a scheduled export/import. Changes in the ERP are reflected in the store and vice versa, with the direction configured per data type — not everything has to sync both ways equally.
Dashboard and logs
Every sync is logged: what synced, when, and what failed if something failed. No silent scripts breaking at 3am without anyone noticing.
Parameters tailored per integration
Custom fields, your own business rules, mappings specific to your setup. The engine is common, but each connector is configured for your case — it's not one-size-fits-all.
Multi-store and multi-warehouse
Setups with multiple stores or warehouses aren't a special case: the Hub is built to manage several points of sale and stock locations from the start.
Performance at scale
Incremental sync: only changes are processed, not the whole catalog on every cycle. Built for catalogs with thousands of items without collapsing.
Support from the people who build it
It's not an ownerless marketplace module. The team that develops the Hub is the same one that supports it when something fails.
Start with the connector you need
You don't need to adopt the whole ecosystem at once. You activate the specific connector your business needs today — the rest of the platform is there for when you need it.
How a connector gets activated on the Hub
It's not installing a plugin and crossing your fingers, nor a from-scratch build every time. It's activating a connector already built on a common platform, and tuning it to your setup.
01
Analysis of your setup
We study your ERP and your store: versions, installed modules, custom fields, your own workflows. The connector adapts to your case, not the other way around.
- Technical audit
- Field and entity mapping
- Identification of special cases
02
Connector activation on the Hub
The sync engine already exists. What gets configured is the specific connector for your ERP and your store, with the parameters and business rules you need — no new script built from zero.
- Odoo ↔ PrestaShop connector
- Secure webservice
- Dashboard and logs included
03
Initial synchronization
The current state is loaded: full catalog, customers, stock. Both systems start with the same information before continuous sync is activated.
- Migration of existing data
- Integrity validation
- Testing before going live
04
Automatic operation, with visibility
From here, the Hub syncs on its own: in real time or scheduled, depending on the data type. With a dashboard and logs, not a black box.
- Dashboard monitoring
- Sync failure alerts
- Technical support included
Why a platform and not a loose connector
The difference isn't cosmetic. It changes what happens the day something fails, or the day your business grows.
-
You don't depend on a script only its author understands
A loose, custom build with no platform behind it is fragile: if the person who wrote it isn't available, no one else knows how to touch it. The Hub is a maintained product, with documentation and a team behind it.
-
You see what's happening, you don't guess it
Dashboard and logs for every sync. When something doesn't add up between your ERP and your store, you don't have to guess where it broke — you check.
-
The engine isn't reinvented with every integration
Work queues, automatic retries, error handling: already solved in the platform. Development focuses on what's specific to your ERP and your store, not on reinventing sync from scratch.
-
Built to grow with you
Multi-store, multi-warehouse, more catalog volume. These are cases the platform already accounts for, not exceptions that break a script built for a simple case.
Connectors
The Lynx Hub engine is common. This is what's active today and what it supports.
Odoo ↔ PrestaShop
- Connector available now — see full details
- Odoo 14 to 19 (Community and Enterprise)
- PrestaShop 1.7.x, 8.x and 9.x
- Bidirectional sync of products, stock, orders and customers
Sage 50 ↔ PrestaShop
- Connector available now — see full details
- Sage 50 (Spain)
- PrestaShop 1.7.x, 8.x and 9.x
- Bidirectional sync of products, stock, orders and customers, with your own SEO fields
The platform
- Secure REST API with OAuth authentication
- Real-time or scheduled sync (cron), depending on data type
- Work queue with automatic retries
- Dashboard and detailed logs
What ERP do you use?
If you use Odoo or Sage 50, the PrestaShop connector is already available. If you use a different ERP, tell us your case — we'll assess whether it's worth building the next connector on the same platform.