Trade CRM systems, an operations-backbone view of local and global options
A CRM selection guide for export and import teams: why generic CRMs fall short, trade-specific criteria, comparison of local and global options, an operations-backbone selection checklist.
Why a generic CRM does not carry a trade team
Most Turkish export and import teams try a CRM at some point. The common scenario: a tool that lets one person send emails, another make calls, and a third drop a meeting note. A generic CRM does all three. Trade operations are far more than these three.
The customer is in Germany, payment will arrive via L/C, goods will move by container, the Incoterm is CIF Hamburg, the duty depends on the HS code, and the VAT refund report is due at month-end. A generic CRM knows none of this. The team tries to patch the gap with "custom fields" and "workflows." The result: an unfinished CRM, three Excel files on top, and a WhatsApp group keeping it together. Right back where we started.
A trade CRM is a system that handles these as part of the data model, not as an afterthought. This article covers the criteria a trade team should look at when picking a CRM, the practical differences between local and global options, and what "operations backbone" actually means.
What separates trade operations from a generic CRM
To pick the right CRM you need the actual list of needs. A trade team\'s daily work touches:
- Multi-currency: EUR, USD, TRY, GBP. Every quote and order has its currency; ledgers keep a running balance per currency. Choice between daily central bank rates and manual rates.
- Incoterms 2020: 11 terms. The wrong term means the wrong price in the quote. One-click selection on the order screen and automatic propagation into the contract.
- HS / GTIP code: 12-digit, Turkey-specific. A workspace catalog matters; re-coding the same product on every order burns time.
- Letter of Credit (L/C) lifecycle: 5 stages (PREPARED, SUBMITTED, ACCEPTED, DISCREPANCY, CLOSED). Deadline cron, discrepancy validation, SWIFT message attachments.
- Shipments and documents: B/L, packing list, certificate of origin. Slot and version storage, share-link delivery to the customer/forwarder.
- VAT refund tracker: Monthly export amount, 12-month chart, country breakdown, per-declaration page. Without it, month-end means 4 to 6 hours of manual aggregation.
- Sanctions screening: OFAC, EU, UN lists. Triggered when a customer is added, and via daily cron. Catch it upstream, not when the bank rejects.
- 206-country profile: Incoterm suggestion, sanctions warning, payment-risk note, logistic channel suggestion. The minimum brief for entering a new market.
- Browser-based international calls: 206-country support, KVKK-compliant recording, replay. Not the same as calling from a mobile phone; team visibility is different.
- Multi-warehouse and lot tracking: For manufacturer-exporters, low-stock alerts per lot, FIFO/FEFO rules.
- Email discovery and verification: Decision-maker email lookup from a company domain, real-time verification. The yield of a cold-email campaign depends on this.
If more than 6 of these 11 items are real needs, a generic CRM cannot be your backbone. Patching with custom fields creates maintenance debt and fragmentation.
CRM options in the Turkish market
Three categories help structure the choices:
1. Local CRMs and SMB ERPs
The Turkish market hosts accounting-led ERP suites, CRM modules of enterprise ERPs, and price-led SMB CRMs. Their strength: local regulatory integrations (e-invoice, VAT) and Turkish support. Their weakness: the trade data model is typically missing. Orders and invoices fine, but the Incoterms picker, L/C lifecycle, and multi-currency ledger are often absent or limited.
2. Global CRM platforms
Salesforce, HubSpot, Pipedrive, Zoho, and similar. Strength: rich API ecosystem and scalability. Weakness: not trade-specific, KVKK and data-residency questions can be points of friction for enterprise customers, and license costs burn the trade SMB\'s SaaS budget fast. Turkish interface and local support are often limited.
3. Trade-specific operations platforms
Sighthem sits here. The data model is built for trade: multi-currency, Incoterms, L/C, HS code, VAT refund, and shipment items are at the core. EU-region hosting, KVKK and GDPR compliance, Turkish and English parallel interface. The category alternative name is "trade operations backbone."
Operations backbone versus CRM
A CRM manages sales and customer relationships: lead, task, follow-up email, pipeline. Important but not enough. An operations backbone keeps the entire chain on one data model:
- Lead acquisition (email discovery and verification, fair connections)
- Customer onboarding (sanctions screening, country profile)
- Quote and order (Incoterms, multi-currency, HS code)
- Shipment (document slots, share links)
- L/C (5 stages, discrepancy, SWIFT)
- Invoice and collection (ledger, terms, partial payments)
- Reporting (VAT refund, pipeline, country breakdown)
When the whole chain lives in one system, the team stops asking "which file is the latest"; customer handoff is smooth, and month-end reporting takes 15 minutes instead of 4 hours.
A 12-point selection checklist for trade CRM
- Data residency: is it in the EU, are KVKK and GDPR compliance clearly documented?
- Turkish interface and support: can the whole team use it comfortably?
- Multi-currency: does the ledger keep a running balance per currency?
- Incoterms 2020: 11-term selection, tooltip, automatic propagation into the contract?
- HS / GTIP: 12-digit lookup and a workspace catalog?
- L/C management: lifecycle, deadline cron, discrepancy validation?
- VAT refund tracker: monthly aggregate, country breakdown, 12-month chart?
- Sanctions screening: OFAC, EU, UN, triggered on customer creation?
- Shipments and documents: slot/version, share link, B/L and CO support?
- Browser-based international calls: 206 countries, KVKK recording?
- API and integrations: e-invoice, accounting, ERP, CSV import/export?
- Cost: per-user monthly price, seats included, annual discount?
If 9 or more of these 12 are checked, the backbone is solid; if 6 or fewer, expect maintenance debt from custom-field workarounds.
Local versus global, the choice
A single criterion does not decide it. The table below maps the trade-offs:
| Criterion | Local advantage | Global advantage |
|---|---|---|
| KVKK and residency | Explicit and local | Generic GDPR, KVKK-specific dialog limited |
| Turkish support | Direct team | Usually English, delayed |
| Local regulatory integration | e-invoice, central bank FX, VAT refund built-in | Usually absent or partner add-on |
| API ecosystem | Limited | Very broad |
| Cost in local currency | TL-priced, no FX exposure | USD/EUR, FX-driven |
| Trade data model | Present in local trade platforms | Not in stock, custom-built |
| Enterprise IT audit | Varies by certifications | Usually has global certifications |
Three decision scenarios
Scenario 1, SMB exporter, KVKK and cost priority: A local trade-specific operations platform is the right choice. EU-region data, direct Turkish support, regulatory integrations built in, TL pricing.
Scenario 2, mid-to-large company with multiple country offices, global teams: A global CRM with a local accounting/e-invoice integration may fit. Costlier but the scale absorbs it.
Scenario 3, fresh team that wants the backbone fast: A trade operations platform alone is enough. Set the backbone, add accounting/ERP integration in a second phase if needed.
Where Sighthem sits
Sighthem is a local, trade-specific operations platform. It answers all 12 items in the selection list. EU-region hosting, KVKK and GDPR compliance, Turkish and English parallel interface, TL-based pricing, the trade data model at the core. It adds layers like orders, shipments, L/C, VAT refund tracker, and browser-based customer calls on top of CRM functionality.
The most practical evaluation is the 14-day PRO trial. No credit card; run one end-to-end flow on 3 to 5 real customers and judge the system.
Frequently Asked Questions
Why does trade need a dedicated CRM?
A generic CRM tracks leads and customers, but trade goes far beyond that: multi-currency, Incoterms 2020, GTIP/HS codes, L/C lifecycle, VAT refund, customs documents, shipment tracking, multi-warehouse, sanctions screening, and 206-country profiles. When these are not part of the data model, teams pile Excel, WhatsApp, and email on top of the generic CRM and the whole thing fragments.
Local or global CRM, which should I pick?
The decision has multiple axes. Data residency (KVKK, GDPR), Turkish interface and support, integrations with local FX rates, e-invoice, and regulation, billing currency, your team's language proficiency, IT-audit questions from enterprise customers, all matter. If KVKK and Turkish support are critical, local options have the edge; if you need global scale and a vast API ecosystem, global choices win.
What is the difference between a CRM and an operations backbone?
A CRM manages sales and customer relationships: pipeline, tasks, email. An operations backbone keeps the entire flow from lead to cash on a single data model: lead, customer, order, shipment, L/C, invoice, collection, ledger. Sighthem covers CRM functionality and goes beyond, holding the daily operational flow of trade, hence the "trade operations backbone" positioning.
Is Salesforce or HubSpot a fit for SMBs?
They scale on paper, but three issues hit in practice: (1) no trade data model out of the box; the team has to build it with custom fields and workflows, which becomes a maintenance load; (2) license costs eat into the team's SaaS budget quickly; (3) local regulatory pieces (e-invoice, VAT refund tracker, central bank FX rates) are not in the stock product. For SMBs the combined load rarely pays back.
How should I evaluate a CRM?
Run the 14-day free trial on 3 to 5 real customers and orders. Focus on one scenario: take a lead through to a customer in 14 days, issue a proforma invoice, open a shipment, close the collection. If you can complete this end-to-end flow in one system, the backbone is solid. If you cannot, the CRM you patch will eventually fragment like the previous setup.