Integrations
The seams are where these projects fail
A beautiful configurator that reaches the cart as a text blob nobody can fulfil is worse than no configurator. These are the systems we connect to, and the specific thing each connector gets right.
- 30
- Connectors
- 26
- Live in production
- 6
- System categories
- 2 weeks
- Typical new connector
How we build them
Three rules for a connector
Against a real instance
Never against a specification document. Every connector is built and tested against a live instance of the system, because the documented behaviour and the actual behaviour differ in ways that only show up under load.
One source of truth, never a fork
Where a PIM already owns the option catalogue, or SAP VC already owns the rules, we consume and render rather than duplicating. Two rule engines disagreeing is a worse problem than a slow one.
Versioned payloads
A configuration serialises to a versioned, schema-validated payload. A configuration saved last quarter still resolves — which matters the first time a customer returns to a saved basket after a catalogue change.
Need a connector we do not have?
Most take a fortnight. Tell us the system and the direction data has to flow, and we will tell you whether it is a fortnight or a genuinely hard problem — some of them are.
We reply to every enquiry within one business day, in your timezone — with a frame budget, not a brochure.