Loading…

Descartes Systems (DSG.TO) backlog: remaining performance obligations

How much revenue Descartes Systems already has under contract, how fast it converts, and who it is with.

Data as of .

Descartes Systems backlog history

$0$200M$400M$600MJan 2019Jul 2022Jul 2023Jul 2024Jul 2025Jan 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
31 Jan 2026$647M$729M0.9 yrs$119M
31 Jul 2025$554Mn/an/a$118M
31 Jan 2025$528M$651M0.8 yrs$105M
31 Jul 2024$430Mn/an/a$105M
31 Jan 2024$446M$573M0.8 yrs$86.0M
31 Jul 2023$478Mn/an/a$87.2M
31 Jan 2023$344M$486M0.7 yrs$69.4M
31 Jul 2022$372Mn/an/a$68.3M
31 Jan 2022$367M$425M0.9 yrs$58.7M
31 Jan 2019$200M$275M0.7 yrs$35.1M

Questions

What is Descartes Systems's backlog?
Descartes Systems reported $647M of remaining performance obligations at 31 Jan 2026, up 23% from a year earlier. That is 0.9 years of trailing revenue already under contract.
How fast does Descartes Systems's backlog turn into revenue?
Over the last twelve months Descartes Systems recognised revenue equal to about 138% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.