Caliq ecommerce integration for wholesale brands
Trade ordering and D2C on top of Caliq — with Caliq staying in control
If Caliq runs your wholesale operation, it holds the pricing structures, customer terms, stock positions and order history your business depends on. The risk in any ecommerce project is not the website — it is what a badly built integration does to that data: stock levels that drift, trade prices shown to the wrong buyers, and web orders rekeyed by hand into Caliq every morning.
Coretonomy runs a purpose-built Caliq connector in production. The Integration Data Hub connects Caliq to B2B trade ordering and D2C ecommerce through one controlled layer — Caliq remains the system of record, and the channels around it can grow without touching your ERP.
ERP-first Caliq integration, live with UK wholesale clients
Caliq integration architecture — Coretonomy's Integration Data Hub connects Caliq with B2B trade ordering and D2C ecommerce while keeping Caliq as the system of record. Explore the interactive version →
Why Caliq businesses get stuck without proper ecommerce
Caliq is a specialist wholesale ERP — which means there is no app store of ready-made webshop plugins the way there is for mainstream platforms. Businesses running Caliq typically face:
No off-the-shelf connectors
Generic ecommerce platforms don't speak Caliq. One-off custom builds go stale the moment the developer who wrote them moves on.
Phone-and-email ordering
Trade customers ring or email orders, the office keys them into Caliq, and everyone waits — while competitors take orders online around the clock.
Pricing complexity
Caliq's customer-specific pricing is exactly what makes wholesale work — and exactly what naive integrations get wrong, showing the wrong prices to the wrong accounts.
Stock in the dark
Without live availability online, customers order what isn't there — and the office spends the day untangling it.
Rekeying and drift
Every manual step between the web and Caliq is a place for orders to be missed, duplicated or mistyped.
One controlled layer between Caliq and every channel
Coretonomy's Integration Data Hub synchronises the data that matters, in the right direction, with Caliq authoritative throughout:
Products & catalogue
Items, variants and attributes flow from Caliq outward — enriched for the web without touching ERP master data.
Stock & availability
Stock levels synchronised to every channel continuously, with allocation and back-order behaviour controlled centrally.
Customer-specific pricing
Caliq's pricing structures mapped to trade accounts online, so each customer sees exactly the prices Caliq says they should — and retail shoppers see only retail.
Customers & accounts
Accounts, terms and credit rules from Caliq govern who can order what, on which terms.
Orders
Orders from trade and retail channels validated by the hub before entering Caliq — correctly attributed, with no manual rekeying.
Invoices & documents
Invoice data flows back out so trade customers self-serve documents online instead of emailing your accounts team.
Caliq stays the system of record
Coretonomy is built for ERP-led businesses. Caliq remains authoritative for:
Stock allocation and availability governed by Caliq, not fragmented across channels.
Customer-specific pricing and account structure remain in Caliq as the single source.
Order history, reporting, financial accuracy and fulfilment integrity stay in ERP.
The integration hub ensures you do not create a "shadow ERP" across ecommerce tools and marketplaces.
Live example: Sea Gems runs on Caliq + Coretonomy
Sea Gems, a UK jewellery and giftware wholesaler, runs its trade ordering on Coretonomy, integrated with Caliq through the hub:
Caliq-governed pricing
Trade customers log in and see their own Caliq pricing — the discrepancies of quoting by phone and email eliminated.
Real stock, online
Availability on the site reflects Caliq stock, synchronised continuously through the hub rather than read live off the ERP.
Orders straight into Caliq
Web orders arrive in Caliq validated and attributed — no rekeying, and the office team works in Caliq as before.
The pattern is repeatable: your Caliq configuration stays as it is, and the hub adapts to it — not the other way round.
Connect Caliq to trade ordering, D2C, Shopify and Faire
Each channel connects to the same hub rather than directly to your Caliq ERP software. That matters more as you add them: the second and third channel are configuration against a layer that already exists, not another bespoke integration to build, monitor and eventually inherit.
B2B trade ordering
A trade portal where customers log in to their own Caliq pricing, terms and account history, and place orders around the clock instead of by phone and email.
D2C storefront
Retail selling from the same Caliq stock pool, with retail pricing kept strictly separate from trade — so a consumer never sees a wholesale price.
Shopify
Already invested in Shopify for D2C? Keep it. The hub syncs stock, orders and customer data between Shopify and Caliq rather than asking you to replatform.
Faire
The wholesale marketplace where retailers discover brands. Stock and pricing flow out, orders come back into Caliq attributed correctly — see the Faire integration.
Channels are added in stages, not all at once. Which order depends on where your commercial pressure actually is — for most Caliq businesses that is trade ordering first, because it takes the most manual work out of the office.
Implementation approach: staged, parallel, reversible
Most established Caliq businesses cannot afford a big-bang rebuild — and don't need one. The rollout is designed around change control:
Discovery against your Caliq setup
We start from your actual Caliq configuration — pricing structures, customer accounts, product data — not a generic template.
Staged channel rollout
B2B trade ordering first, then D2C, then marketplaces — each validated before the next goes live.
Parallel running
Existing processes keep working during transition; nothing is switched off until its replacement is proven.
Monitoring & clear ownership
Sync activity is visible and auditable, exceptions are surfaced, and when something needs attention you know exactly who owns it.
Caliq ecommerce: the three realistic options
Because Caliq is a specialist wholesale ERP rather than a mainstream platform, the usual shortlist of B2B products does not apply — most of them have no Caliq connector at all. In practice a Caliq business is choosing between three approaches, and the right answer depends on how central the ERP is to your operation.
A one-off custom build
An agency writes a bespoke connection between a website and your Caliq ERP software. Fastest to quote, and often cheapest on day one. The risk is ownership: the integration is understood by whoever wrote it, and when they move on, changes get slower and riskier. It also tends to be rebuilt each time you add a channel.
Generic platform plus middleware
A mainstream ecommerce platform joined to Caliq through a general-purpose integration tool. Viable, and sensible if your pricing rules are simple. The strain shows with customer-specific pricing and account terms — the parts generic field mappings model least well, and exactly what wholesale depends on.
A maintained Caliq connector
What we do: the Caliq connector is a product we run in production and maintain, not a project we hand over. Channels attach to one hub, Caliq stays the system of record, and there is one place to look — and one owner — when something needs attention.
The question worth asking is not which option has the most features. It is what happens in year two — when the pricing rules change, when you add a channel, and when the person who built it is no longer available. That is where these three diverge sharply.
Designed for Caliq businesses where the cost of getting it wrong is high
This is a fit if you:
- Rely on Caliq operationally
- Run customer-specific pricing, account terms, or complex catalogues
- Want trade customers ordering online instead of by phone and email
- Are adding D2C or marketplace channels alongside B2B
- Want stability, clarity, and accountability over hype
Caliq integration questions
Do you integrate with Caliq?
Yes. Coretonomy runs a purpose-built Caliq connector in production. The Integration Data Hub connects Caliq to B2B trade ordering and D2C ecommerce while Caliq remains the system of record for stock, pricing, orders and invoices.
Can Caliq power a B2B trade ordering portal?
Yes. Coretonomy provides a proprietary B2B ordering platform synchronised with Caliq — customer-specific pricing, account terms and catalogues come from Caliq; orders flow back in validated and correctly attributed.
How does customer-specific Caliq pricing work online?
Pricing structures are maintained in Caliq. The hub synchronises them so each trade customer sees their own prices when they log in, and retail shoppers only ever see retail pricing.
Can we run D2C retail alongside trade ordering with Caliq?
Yes. A retail storefront runs on the same platform as your trade store — same catalogue, same Caliq-governed stock pool, retail pricing — managed from one back office.
Do orders and invoices sync back into Caliq?
Yes. Orders from every channel are validated by the hub before they reach Caliq, and invoice data flows back out so trade customers can self-serve documents online.
Will the integration disrupt our existing Caliq setup?
The integration is designed around your existing Caliq configuration. Rollout is staged and runs in parallel with current operations, with validation before each channel goes live.
Can we sell on marketplaces like Faire with Caliq?
Yes. Marketplaces such as Faire connect through the same hub, drawing on the stock and pricing Caliq governs, with orders routed back into Caliq — added in stages once core channels are stable.
Why not just have an agency build a Caliq integration for us?
Sometimes that is the right answer, particularly for a single connection that will not be extended. The difference is what happens afterwards. A one-off build is understood by whoever wrote it, so changes get slower and riskier once they move on, and each new channel tends to mean building again. We maintain the Caliq connector as a product in production, so the second and third channel are configuration against a layer that already exists.
Does the ecommerce platform hold its own copy of our Caliq data?
No — and this is the distinction that matters most. The storefront reads data the hub has synchronised from Caliq, but it never becomes authoritative for it. Stock, customer-specific pricing, account terms and order history stay in Caliq. The aim is to avoid creating a shadow ERP inside your ecommerce tools, which is what makes the two disagree and forces manual reconciliation.
Discuss your Caliq setup
We start with your current Caliq configuration, channels and operational constraints, then recommend the lowest-risk path forward.