Scope of work
What I can take on
- 01 I integrate ERP systems, including Comarch, Subiekt, enova and Symfonia, covering products, stock, prices, orders and documents.
- 02 I connect stores with Allegro, Amazon and eMAG, covering offers, availability, orders and statuses.
- 03 I automate WMS, courier and parcel locker handling, including labels and shipment tracking.
- 04 I implement payments and instalments, including non-standard methods and B2B settlements.
- 05 I build PIM integrations and product feeds for Google Merchant, Ceneo and other price comparison sites.
- 06 I create modules for processes that available off-the-shelf solutions don't cover.
What happens when synchronisation breaks
I design for the situation where an external system stops responding. I use queues, retries, logs and alerts so that interrupted operations can be identified and handled. This keeps data exchange under control even during an outage.
Which system owns the data
Before quoting I agree with you where prices are set, which system manages stock and who changes order statuses. These arrangements can take up about half of the integration time. Without them, systems may overwrite each other's data even when the technical connection works correctly.
Your own module with accessible code
I write modules against the platform's API, without core changes and with future updates in mind. The code and its documentation go into your repository. Ending our cooperation doesn't switch off the module or your right to use it.
Selected systems
Integrations I implement most often
Each of these systems connects to a store differently. Below is what we actually synchronise and where such implementations most often go wrong.
-
PrestaShop and Subiekt GT integration
Products, stock levels, prices, customers and sales documents between the store and Subiekt GT. Through Sfera, not by writing straight to the database.
-
PrestaShop and Comarch ERP Optima integration
Exchanging products, stock, price lists and documents between the store and Comarch ERP Optima - through a supported API, with control over document numbering.
-
PrestaShop and WAPRO Mag integration
Connecting the store with WAPRO Mag: product records, stock, prices, orders and sales documents, with support for multiple warehouses and price lists.
-
PrestaShop and enova365 integration
A store connected with enova365 through the system's API: products, stock, price lists, sales documents and customers, including multi-branch setups.
-
PrestaShop and BaseLinker integration
Store, marketplaces and couriers managed from one place. With a clear decision on which system owns stock, so you never sell the same item twice.
-
PrestaShop and Allegro integration
Listing offers, importing orders and syncing stock between the store and Allegro - through the official API, with category parameter mapping.
-
PrestaShop courier integration: InPost, DPD, DHL, GLS
Creating shipments, labels, pickup points and status tracking without retyping addresses between courier panels.
Practical information
Questions about working together
Is integration possible if my ERP has no API?
We can consider file exchange or an intermediate database. This approach requires extra checks of data consistency on both sides. I assess the options once I know the system.
How long does it take to connect a store with an ERP?
A typical two-way integration takes 3 to 6 weeks. About half of that time can go into agreeing how data is handled, especially prices and stock levels. The timeline depends on the scope of the exchange and the availability of the systems.