Skip to content
KanchanFlow
Integrations

Every integration we ship, and what each one actually syncs

All 26 connectors, each with the fields that move in both directions, the setup steps, the errors you will hit, and the ceilings we cannot get past. Last full re-test 2026-08-27.

In short

KanchanFlow, the RFQ-to-Order CRM for job shops and contract manufacturers, ships 26 integrations covering accounting, compliance, payments, messaging, lead sources, email, scheduling and logistics. Every connector page prints the date a person last tested it end to end, along with the limitations we cannot engineer away.

Diagram titled "How connectors sit in the flow", showing the seven RFQ-to-order stages from enquiry intake through to accepted order.
Connectors shipped
23 live
In production today, not in a private beta
In development
3 building
Each one carries a visible target date
Re-test cadence
Quarterly
Every connector, end to end, against a live sandbox
Last tested
2026-08-27
Printed on every integration page

The part nobody else publishes

How we test integrations

An integration list is easy to write and hard to keep true. This is the process that keeps this page honest, and the reason every card above carries a date.

Once a quarter, one person works through all 26 connectors in order. For each one they authorise a clean connection from scratch, push a real record through in the outbound direction, read the write-back, and then deliberately break it: wrong credentials, a missing mapping, a rate limit, a revoked token. Every error message in the troubleshooting table on an integration page came from that exercise, not from a support article.

The date the connector passed is written to the shipping record and printed on its page. If a vendor has changed an API in a way we have not caught up with, the page says so and the status badge changes. A connector whose date is more than one quarter old is a connector we have stopped being able to vouch for, and we would rather you saw that than a static logo wall.

We publish this because the alternative is the industry norm: a grid of logos where “integrates with QuickBooks” can mean anything from a full bidirectional sync to a CSV export somebody wrote in 2019. You cannot tell from a logo. You can tell from a field list, a limitations section and a date.

What a quarterly re-test covers

  • Fresh authorisation — connected from zero, so a broken setup flow is caught before a customer finds it
  • Outbound write — a real record pushed through and opened in the other system
  • Inbound read — the write-back checked field by field against what this site claims
  • Failure paths — wrong credentials, missing mappings, rate limits and revoked tokens, deliberately triggered
  • Version floors — the minimum vendor version we claim support for, re-confirmed
  • Page correction — any drift between behaviour and copy is fixed on the page the same week

Every connector on this page is re-tested end to end against a live sandbox each quarter, and the date of that test is printed on the page. If a date looks stale, the page is wrong and we want to hear about it.

Questions people actually ask about integrations

It means a person at Soor LLC ran that connector end to end against a live sandbox on that date: authorised it, pushed a record through, read the write-back, and confirmed the error paths still behave as this site describes. It is not the date we last touched the code, and it is not a marketing timestamp. If a date on this site drifts more than one quarter behind, treat the page as unreliable and tell us.

See the connector you care about running against your own data

Fourteen days, no credit card, sample data pre-loaded. Bring your Tally company, your QuickBooks file or your IndiaMART key and we will connect it on the first call.

  • Delaware LLC
  • SOC 2 Type II
  • USA Data Centers (AWS)