No magical merging
Adding amounts is not the hard part. First you need to establish which orders, invoices and accounts belong to the same relationship, and retain an explanation for every match.
Operational guide, reviewed 13 July 2026LTV can mean gross revenue, net revenue, margin, or the value of paid transactions after returns. Any definition can be valid, but a report cannot mix them without losing credibility.
Separate store and marketplace orders from wholesale invoices, returns and corrections. Record which system is authoritative for payment status.
Use one format for phone numbers, lowercase emails and digits-only VAT IDs. Keep original values too, so the result remains auditable.
A matching VAT ID is stronger evidence than a similar company name. A shared phone can confirm a retail account. A similar name alone should not merge customers automatically.
Only merge records that pass the agreed threshold. Route the rest to a short review queue with the evidence for the proposed match.
Every LTV amount should point to a document, date, system and status. That makes duplicate detection, corrections and recalculation possible.
A one-off import is only a snapshot. Ongoing synchronisation, monitoring and recovery from failures keep the calculation useful when source data changes.
In the demonstration profile, the same customer buys through retail and wholesale. The result is not one opaque number.
This is demonstration data, not a Bridgefold customer result. A real implementation agrees the value definition, returns, corrections and currency before the first calculation.
Describe where orders, invoices and customer identifiers live. The first response will assess whether the data can answer the question.
Check your fit