Data

The shared record model: custom fields, forms, import and export, and what each product writes.

What "one record" actually means

"Shared record" is the most overused phrase in business software, so here is the test we hold ourselves to: a fact should never have to be entered twice. A customer's address, a contract's payment terms, an employee's reporting line — each is stored once, and every product that needs it reads that one copy.

Not a sync

Two systems joined by a sync are still two systems, and one of them is always slightly wrong. A sync is a copy with better manners: it narrows the window in which the two disagree without closing it. Treepie has no sync between products because there is nothing to sync — Loop reads the customer row Flow writes.

Custom fields and forms

Fields you add are added to the record, not to a product, so a field created for a Books workflow is visible to Flow if you permit it. Forms write to the same fields rather than into a separate submissions table that somebody later reconciles.

Import and export

Import maps to the shared record with the mapping reviewed before anything is written. Export gives you your data back in a format you can use — the specifics belong in the terms of service, which are not published yet.