What people ask about Kargon

Kargon™ is an enterprise logistics platform that unites the shipment, fleet, warehouse, accounting and e-document processes of logistics companies engaged in transport, warehousing and distribution in a single database. LTL (partial loads), full truckload (FTL) and tonnage transport are managed in the same system, together with your branch network, subcontracted carriers and own fleet.

No. Kargon™ is a single platform; LTL, FTL, tonnage and warehouse business models run in the same system under one license. Shipment, fleet, warehouse, accounting and HR modules are activated as you need them.

Kargonsoft is the brand under which Triyon Yazılım presents the Kargon™ Logistics Management Platform. Kargon™ is developed by Triyon Yazılım Sanayi Ticaret Ltd. Şti.; discovery, setup, training and support are also carried out by the Triyon team.

It works at every scale, from a single-branch transport company to multi-branch LTL networks. The scope of branches, users and modules is tailored to your needs.

Our engagement model has four steps: 1) Discovery — your business model (LTL / FTL / tonnage / warehouse), branch structure and existing systems; 2) Setup — chart of accounts, templates, branches, e-document and bank connections; 3) Data migration — accounts, vehicles, stock and opening balances; 4) Training and go-live — role-based training and on-site support at the first period close.

Yes. Current accounts, vehicles, stock and opening balances are migrated during the data migration step of the rollout. The scope of the migration is agreed together in the discovery meeting.

Kargon™ runs in the browser. Handheld terminals are supported for barcode scanning and stock counts in the warehouse, TWAIN / WIA-compatible scanners for multi-page document scanning, and dot-matrix (ESC/P) printers for pre-printed forms.

Yes. Operations, finance and management users receive role-based training, and we continue to support your team's questions after go-live.

Yes. It is fully integrated with GİB through the Hızlı Teknoloji e-Connect private integrator; documents are generated in UBL-TR 2.1 format and validated against the XSD schema before sending. The recipient's taxpayer status is detected automatically from the GİB list (e-Invoice or e-Archive); incoming and outgoing e-Waybills and waybill responses are supported. Each branch can work with its own integrator account.

When you select a branch pair and period, the system pulls in all related trips; acceptance revenue, freight, advances, depot transfer fees and intermediate haulage are shown in separate columns. Each branch's earnings are calculated automatically by share percentage, and acceptances not linked to a waybill are flagged as warnings.

Yes. Your customers sign in to the customer portal with their own accounts; they follow their shipment status step by step, download documents as PDF and view their account transactions.

A CMR document is generated from the operation record; MRN (NCTS), T1 / T2 transit and TIR carnet, HS code, ADR and reefer cargo details are stored. Expiry dates are tracked for vehicle documents — authorization certificate (K1 / L2), CEMT, transit permit, TIR approval certificate, green card, traffic and CMR insurance, casco, roadworthiness inspection, tachograph calibration and ATP — and for driver documents — passport, visa, SRC4 certificate, psychotechnical certificate, ADR, tachograph card, driving licence and international driving permit.

Yes. The Warehouse Module manages contract warehousing (3PL), customs bonded warehouses, cross-dock and transfer, e-commerce and distribution, and special-condition (reefer, ADR, food, pharmaceutical) storage models in the same system as transport operations. Goods receipt, location addressing, consigned stock, picking, stock counts and monthly billing form a single flow.

The GİB e-Waybill Application Guide (art. 15.7) defines two scenarios for shipments from a logistics center, and Kargon™ supports both. In Scenario I, the goods owner issues the e-Waybill and e-Invoice, with the logistics warehouse entered as the point of origin; the warehouse issues its own transport waybill. In Scenario II, the warehouse issues the e-Waybill including the goods owner's details and also issues a transport waybill. This is for information only; consult a certified public accountant for your company's specific practice.

No. Stock held in the warehouse belongs to the goods owner, both legally and for accounting purposes; the warehouse operator does not take consigned goods into its own inventory or balance sheet. Kargon™ keeps stock separately per customer, controls commingling and invoices storage and handling charges as a separate service invoice.

Storage charges are calculated automatically from the daily stock snapshot (pallet / day, m² / month, m³), inbound and outbound handling from goods receipt and dispatch records, value-added services from work orders, and transport from the shipments module; any minimum commitment shortfall appears as a separate line. The billing statement is shared with the customer and, once approved, an e-Invoice / e-Archive invoice is created in one click. Storage and transport can be combined on the same invoice.

Kargon™ restricts access across five layers: page-level role permissions (view, add, edit, delete, export), branch visibility, fields masked for unauthorized roles (freight and net profit visible to managers only), financial controls (closed periods, debit = credit, reversing entries) and an audit trail. Every insert, update and delete is recorded with old and new values, user, IP and timestamp.

Support is provided by phone, email and WhatsApp by the Triyon Yazılım team that develops Kargon. You can reach us on weekdays between 09:00 and 18:00.

Yes. Company-specific reports and pre-printed form designs can be created with the DevExpress report designer. Since Kargon™ is backed by Triyon's custom software development team, workflows and integrations specific to your company can also be planned once the scope is defined.

Pricing depends on the modules you use, the number of branches and users, and your business models. After the discovery and demo meeting, we share a tailored proposal with a clear line-item breakdown.