In this guide 6 sections
Every shared field gets one owning system. List the field, the owner, the direction the change flows and the rule that applies if the other side edits it, then ask each lead to sign. Customer name might belong to the CRM, price to the ERP and payment status to accounting, and the table must exist before anyone builds a sync.
One owner per field, not per record
Teams say the ERP owns the customer. Too coarse. In a HubSpot or Salesforce setup the CRM holds the contact’s mobile number, lead source and account owner, while NetSuite or Odoo holds the credit limit and billing address.
Ownership works at field level. For each field exactly one system may originate a change while the others only receive it, because without that rule two systems overwrite each other quietly for months. Then a salesperson quotes a dead discount.
Write the owner in one word. If the room needs a whole sentence to explain who owns a field, then it has two owners and one of them is wrong.
The template columns
Make one row per field. Start with customer, item, price, tax and status, then add whatever your teams argue about, and fill the table in one room with sales, stores and accounts together. Bring real examples.
Five columns carry the weight. A blank cell blocks the sync.
- Field name and its format
- Owning system
- Direction: one-way or two-way
- Conflict rule when both sides edit
- Who approves a change
Choosing the owner
Pick the system where the field is born or the one an auditor reads, so VAT numbers, exemption certificates, invoice sequences and credit notes belong to QuickBooks or Xero. Bin locations, barcodes, lot numbers and SKU dimensions belong to the warehouse module, because stores staff touch them first and nobody in the office can check them.
Prefer one-way flow. Two-way sync doubles the failure modes. Use two-way sync when two teams edit in their own tools, such as a rep correcting a contact in the CRM while a dispatcher fixes it on the order.
- Item code, unit of measure, pack size: ERP
- Price list and discount slab: ERP
- Contact, lead source, stage: CRM
- Invoice number and tax lines: accounting
- Payment status: accounting
Decide the conflict rule before it happens
Sooner or later a rep and a billing clerk edit the same credit limit within the same minute, and the sync has to pick one value without asking anybody. Choose the answer now. Your options are owner wins, latest timestamp wins, or hold both values in a queue until a person decides which one is right.
Latest timestamp feels fair. It destroys good data when a CSV import stamps ten thousand rows with today’s date and the old Shopify price overwrites the negotiated contract price. Owner wins is safer for money fields. Send anything touching a contract or a tax identity to a review queue, where a named approver clears it before the value moves.
Log every overwritten value with the old value, the new value, the system and the time, so a disputed price traces to one edit, not memory.
- Price and tax: owner always wins
- Phone and email: latest edit wins
- Status: only forward steps allowed
- Address: send to a review queue
Fill the first ten rows this week
Do not map every field. Take the ten that cause the most corrections, such as duplicate customer records, stale quotation prices, delivery notes with a closed warehouse address and cartons confused with pieces. Complete the template for those rows only.
Hand the sheet to whoever builds the sync, and treat any row they cannot build from as a missing decision that goes back to the room.
Once the first ten rows run cleanly for a month, add the next ten, and keep the sheet pinned where whoever changes a field next will see it.
Field ownership table
One wide page holds twelve blank rows. Columns are field, format, owning system, direction arrow, conflict rule, approver and a note, with a header strip that lists every connected system beside a tick box. A footer line holds the date of the last review and a signature box for whoever approves changes, so a reader sees how old the decisions are.
Open a blank worksheet to printQuestions owners ask
What is a system of record?
It is the system whose value counts as correct when two systems disagree about the same customer, price or stock figure, and every other system simply follows it. Copies elsewhere are read only.
Can two systems own the same field?
Only with a strict conflict rule, an audit trail and a named approver for each change, and even then it costs more to debug than one owner. One owner is safer.
Who should fill in the template?
Someone from sales, stores and accounts who edits the data, plus whoever manages the integration, and a decision maker who can settle arguments on the spot. Each team knows different fields. Each disagrees about a few.
How often should the table be reviewed?
Review it whenever you add a system, a field or a sales channel, and otherwise check it every few months, because new fields creep in unowned. Date every review. Sign the page again.