WEBSITE PLANNING

Choose the Record That Owns Customer Updates

Assign ownership to individual customer fields and resolve conflicting updates before connecting your website, CRM and billing records.

Choose ownership per field

Saying that the CRM owns the customer is often too broad. A billing system may own invoice status while a service desk owns a support case. Create a field-level list: customer identifier, preferred contact address, consent state, invoice status and assigned staff member. Beside each field, name the system allowed to change it and the systems that may display a copy. This is a design worksheet, not a description of an existing North Front Digital integration.

A fictional conflict to resolve

At 10AM a customer changes a contact address in a portal. At 10:02 an older CRM export arrives containing the previous address. If every arriving message overwrites the record, the old address wins simply because it arrived later. A better specification decides which system owns that field and how its version is recognized. Receipt time and the time of the original change should remain separate in the discussion.

Write the handoff rules

Use columns for field, owning system, stable record identifier, allowed editor, update direction, conflict behavior and manual reviewer. For example, the worksheet might say billing status flows from billing to the portal, while a contact correction goes to a review queue. These are illustrative choices. Confirm them with the people who handle the actual workflow before implementing anything.

Test disagreement deliberately

Ask the developer to demonstrate stale updates, two changes close together and a deleted record using synthetic data. The result should show which value survived and why. Stripe’s documentation offers a useful real example of notifications that can arrive out of order; see its event-handling guidance. A successful connection is only the beginning: the integration must preserve the meaning of the records. Discuss your actual systems through the project inquiry form.