Integration
pimcore
Customers, orders and line items from the Pimcore shop flow into Caymland M4 – with a second pass that catches the orders of existing customers, which otherwise slip through the net.
- Area
- Shop data source for retail
- Direction
- Pimcore shop to Caymland M4
- Cadence
- On a schedule, changes only
- Vendor
- pimcore.com
The second order arrives too.
Repeat buyers are not lost.
Orders are queried separately, because a new order does not touch the customer record.
Several shops, one set of contacts.
Somebody buying in two shops is one contact with two purchase histories.
Changes only.
Each run asks for what has arrived since the last one. Runtime stays stable over the years.
The shop knows what was bought. Marketing hears about it last.
A Pimcore shop brings products, customers and orders together cleanly in one place. That is exactly what it is built for, and it does it well.
But its remit ends at the checkout. What comes afterwards – the second order, the win-back after a year of silence, the message that fits what was actually bought – happens in a different system. And the order data usually gets there as an export somebody sets in motion.
The Pimcore interface to Caymland M4 closes that gap. Customers and orders arrive in Caymland continuously, with line items and products, ready for segments, campaigns and reports.
What comes in
| Area | Content |
|---|---|
| Customer | Master data and addresses from the shop |
| Order | Number, status, time, amounts |
| Line items | The products bought, per order |
Out of this the purchase history forms on the contact. It is the basis for everything else: "bought this product", "ordered nothing for twelve months", "buys regularly in this category".
Two passes, and why there have to be two
This is the point at which naive connections lose orders.
A synchronisation that queries customers by their modification date finds new customers reliably. What it does not find is an order from a customer who already existed – because a new order does not touch that customer record. Its modification date stays as it was. The customer slips through the net, and their order with them.
That hits the most valuable group of all: repeat buyers.
So the interface queries both separately – customers by their modification date and orders by their own. The orders bring the customer, addresses and products with them. The second order therefore arrives just as the first one did.
Several shops in one connection
Anyone running more than one shop – by country, by brand, by range – sets them up side by side. Each shop has its own address and its own credentials and can be activated or stood down individually without touching the others.
The contacts still come together in one set. Somebody who has bought in two shops is one contact with two purchase histories, not two contacts.
How the connection runs
Direction: from the shop to Caymland M4. Nothing is written back. Your shop stays the authoritative place for products, prices and orders.
Access: through your shop's interface, with address, user and password per shop.
Rhythm: on a schedule. Each run asks for what has changed since the last one, not for the whole set. Runtime therefore stays stable over the years.
Page by page. Large volumes are collected in pages rather than in one response. Christmas trading runs through the same way a quiet Tuesday does.
What you need
On the Pimcore side:
- Access to the shop interface with user and password
- Release of the customer and order areas
On the Caymland M4 side:
- Activate the integration and store one access per shop
- Define the field mapping once
- Set the schedule
Setting this up is a matter of one appointment, not a project.
What this looks like day to day
The second order. It arrives even though the customer is not new. That sounds obvious and is precisely where simpler connections quietly miss.
The win-back. Someone who has ordered nothing for twelve months but bought regularly before that gets an offer of their own. The segment maintains itself with every run.
The fitting message. Someone who buys a particular category hears about that category. The rest of the list is not bothered with it.
Questions & answers
Frequently asked questions about this integration
Is anything written back to the shop?
No. The interface only reads. Products, prices and orders remain unchanged in the shop.
Why are orders queried separately?
Because a new order does not touch the modification date of an existing customer record. Querying only customers loses exactly the orders of repeat buyers. Orders are therefore collected by their own modification date and bring the customer, addresses and products with them.
Can we connect several shops?
Yes. Each shop gets its own address and its own credentials and can be activated or stood down individually. The contacts come together in one set.
Is everything fetched on every run?
No. Each run asks for what has changed since the last one. Large volumes are collected page by page.
What can we do with the data?
The purchase history sits on the contact and can be used in segments, campaigns, point awards and reports.
How current is the data?
As current as the last run. You set the rhythm.
