Integrations
We would rather ship two ERP connectors that work
Distribution platforms like to count their integrations. We would rather tell you which ones are live, which are in progress, and which are on paper, because the ones on paper are where implementations go wrong. Carrot's backend exposes a documented API surface, so a new connector is a bounded piece of work rather than a platform change. If your ERP is not on this list, that is a scoping conversation, not a no.
Live
Running in production today
These are in daily use by distributors on the platform.
SAP Business One
ERP
A direct connector to SAP B1, reading items, business partners and price lists straight from the source, so the catalogue, the accounts and the pricing in Carrot are the ones your ERP already believes in. Bulk import covers the initial load.
Stripe
Payments
Card, PayTo and BECS direct debit, plus Afterpay and Zip. Payment events flow back into the order and invoice record, so finance is not reconciling two systems by hand.
Microsoft 365
Email and messaging
Transactional email through Microsoft Graph, sent from your own domain and mailbox, so order confirmations and invoices arrive from you rather than from a no-reply address at a vendor.
Amazon SES
An alternative transactional email path for distributors not on Microsoft 365, configured in the back office rather than by a developer.
Shopify
Commerce
For distributors already running a retail storefront: product imagery and catalogue content matched into the trade catalogue by SKU, so the wholesale side inherits work the retail side already did.
Klaviyo
Marketing
Order, application and enquiry events pushed into Klaviyo, so lifecycle and win-back campaigns run on real trading behaviour.
In development
Built, being proven
The code exists and works in testing. We will not call it live until it has run in production.
Microsoft Teams
Email and messaging
A Teams bot so your team can answer buyer chat from where they already work. Built, and not yet verified end to end in production.
Planned
Scoped, not yet built
On the roadmap, with the data model already mapped. Ask us about timing.
NetSuite
ERP
Scoped in detail against a real customer's data model, including the pricing waterfall, and not yet built. Talk to us about timing if this is your ERP.
Running something else?
Tell us what you are on. Carrot’s backend exposes a documented API surface, so a new connector is a scoping conversation rather than a platform change.