At a glance
- Industry
- Trading, export–import and recycling
- Scale
- Two legal entities, two countries, two Zoho data centres
- Timeline
- 11 weeks across 10 phases, discovery to go-live
- Zoho products
- Zoho CRM (India DC), Zoho Books (Canada DC), Campaigns, Voice, Meeting, Cliq
- Custom & integration work
- Cross-data-centre CRM to Books sync via custom Deluge functions and OAuth, a custom Order Tracker module, claim and settlement automation with credit and debit notes
Running sales and finance in different countries? See how one connected system handles it. Get a free automation audit
The Challenge
The business was split across two countries for good commercial reasons. The systems were split for no reason at all.
- Sales in India, finance in Canada, nothing joining them. One entity agreed the deal, another invoiced it, in a different Zoho data centre under Canadian tax rules. Every hand-off between the two was manual, and the CRM had no reliable view of what had been billed or paid.
- The order lifecycle lived outside any system. Offers, specifications, photos, bills of lading, assembled over email. Once a shipment left, its status, carrier, vessel and ETA sat on a spreadsheet that two people could read and nobody else could.
- Claims ran on memory. Quality disputes, shortfalls and adjustments had no consistent record, no status, and no clean route to the credit or debit note that settled them. In commodity trading, that is money.
What We Built
One decision shaped the whole build: Books in Canada stays the financial system of record, CRM in India runs the commercial lifecycle, and custom code keeps them in step instead of people. Zoho supplied the platform on both sides. The Deluge integration layer and the custom Order Tracker are what made two data centres behave like one business.
One lifecycle from offer to paid invoice
- Offers created in Zoho CRM with product, specification, origin, quantity, price and Incoterm, plus photos and structured tags, then sent through Campaigns with engagement written back to the record.
- Interested leads convert to a deal on confirmation, which generates the supplier purchase order and the buyer proforma invoice through Books.
- A document pack held against the deal, with an internal bill-of-lading draft approval and a "Docs Complete" gate before anything moves. That gate exists because a shipment leaving on incomplete paperwork is the most expensive mistake available in this business.
A custom Order Tracker for the part Zoho doesn't do
- A purpose-built module capturing order overview, carrier and forwarder, vessel or truck, tracking reference, status from planned to closed, ETD and ETA, and logistics notes with attachments.
- Deliberately light. Booking and container management stay with the specialist systems that do it properly. The business just needed one place that answers "where is this order?" without phoning someone.
Finance in Canada, connected not copied
- Zoho Books configured with the chart of accounts, document numbering, provincial tax treatment and reconciliation preferences. Invoices raised from the deal with correct province tax, and invoice IDs written back to CRM.
- Supplier bills for freight, trucking and terminal charges raised directly in Books, with payments pulled back into CRM so sales can see settlement without access to the ledger.
- Custom Deluge functions with OAuth keep customers, invoices and payments synchronised across the two data centres. This is the piece no out-of-the-box connector covers, and it is the reason the project needed building rather than configuring.
Claims that close properly
- Claims raised against the order in CRM, moving from raised to under review to settled, with evidence attached.
- Settlement generates the matching credit or debit note in Books, so the commercial record and the financial record close on the same day.
The conversation stays with the deal
- Zoho Voice click-to-call with automatic logging and recording against the record, Meeting logging to CRM, and Cliq for internal channels.
- Role-based access throughout, with finance data hidden from non-finance roles.
Results
- Two countries, one commercial record. A deal agreed in India and invoiced in Canada moves through a single tracked lifecycle, with invoice and payment references visible in the CRM.
- "Where is this order?" has an answer. Status, carrier, vessel, tracking reference and ETA live in the Order Tracker with the document pack attached.
- Claims carry a status and settle into Books.
- Compliance sits where it legally belongs. Canadian tax handled in Books as the system of record, with access controls separating finance from sales.
Why It Worked
We drew a line and held it.
It would have been easy to agree to run shipments, containers and inventory inside Zoho as well. The client would have said yes. It would also have failed, because that is not what the platform is for, and eleven weeks would have become eleven months of building a worse version of software that already exists.
So the line went in early: Zoho owns the commercial and financial lifecycle, specialist systems keep doing execution, and the Order Tracker holds just enough shipment detail for the business to stay informed. Ten phases, eleven weeks, with UAT and a hypercare period afterwards instead of a hand-off and goodbye. Saying no to scope is the most underrated thing a partner does.
Frequently asked questions
Can Zoho CRM in one data centre talk to Zoho Books in another?
Not natively. Zoho's regional data centres are separate environments and the standard CRM–Books integration does not span them, which surprises a lot of businesses halfway through a cross-border setup. It is solved with custom Deluge functions and OAuth-authenticated API calls, which is what was built here for India to Canada. See our integration services.
Why would you run CRM and Books in different countries?
Because the selling entity and the invoicing entity are different legal companies. Keeping Books where the tax obligation sits means compliance is handled properly, while the CRM stays the single commercial view. It's a structure decision before it's a software one.
Can Zoho handle export–import documentation and Incoterms?
At the commercial level, yes. Offers and deals carry origin, destination, Incoterm, specifications and a full document pack with approval gates, including a bill-of-lading draft approval before an order progresses.
Can Zoho CRM track shipments?
It can track shipment status: carrier, vessel, tracking reference, ETD and ETA in a custom module. For live container tracking and carrier booking, keep a specialist system. Rebuilding that inside a CRM is a common and expensive mistake, and we talked this client out of it.
How are post-shipment claims managed?
As records against the order, with status progression and attached evidence. When a claim settles, the matching credit or debit note generates in Books so both sides close together.
Can we stop sales staff seeing financial data?
Yes. Role-based profiles and permission sets control module and field access, so the ledger stays with finance while sales still see invoice and payment status.
How long does a cross-border implementation take?
This one ran about eleven weeks across ten phases: discovery, CRM build, sales automation, communication tools, Books configuration, order tracking, cross-DC integration, claims, migration and UAT, then training, go-live and hypercare. The cross-DC integration is the part that carries the risk, so it gets built and tested early, not last.
Facing the same challenge?
If your sales and finance run in different countries, or your order lifecycle lives in spreadsheets between them, we'll map what one connected system looks like for your business. Start with a free automation audit. Get a free automation audit


