Hourglass Content Intelligence
Website ↗
← All conversations

Conversation

21 Oct 2026, 09:28 UTC · 2 questions · ID 7924102438d4
Who asked
Persona
CTO (Chief Technology Officer)
Company
Whirlpool Corporation
Industry
Manufacturing
Pages visited (1)
  1. /products/dataQuestions 1 and 2 asked here
Question 1

“How does the two-way ERP sync handle conflicts?”

Answer
Partly answered

The Data Hub page says you map fields once and set field rules that decide which system wins when they disagree, with read-only fields where needed. It doesn't say what happens when no rule is set, how simultaneous edits are timed and settled, or whether conflicts are logged or flagged for review.

Section on the siteStatusTicket
/products/dataTwo-way syncs, without custom code (card)Partly answers it
Add sync conflict handling detail to /products/data

Ticket

Paste this into your ticketing tool.

Add sync conflict handling detail to /products/data

Who needs it: IT and data teams setting up syncs (this visitor: Whirlpool Corporation)
Section: /products/data › Two-way syncs, without custom code (card)

What is missing:
- The default outcome when a field changes in both systems and no rule is set is not stated.
- How changes made at the same time are ordered and settled, and how often syncs run, is not stated.
- Whether conflicts are recorded in the change history or flagged for a person to review is not stated.

Where: Update this section: add lines to the card's list after "Field rules that decide which system wins" and "Read-only fields where you need them".
  Related sections: The tools in Data Hub · Change history

What to do:
1. Confirm with engineering the default conflict behaviour, how simultaneous edits are settled, sync frequency for ERP syncs and whether conflicts are logged or queued for review.
2. Add the confirmed default behaviour, timing and conflict logging to the card's list.
3. Link the card to the Change history card or a guide on setting field rules.

Done when: /products/data states what happens when both systems change a field with and without a rule, how often syncs run and where conflicts are recorded.

From: conversation 7924102438d4, question 1: "How does the two-way ERP sync handle conflicts?"
Who needs it: IT and data teams setting up syncs (this visitor: Whirlpool Corporation)
What is missing
  • The default outcome when a field changes in both systems and no rule is set is not stated.
  • How changes made at the same time are ordered and settled, and how often syncs run, is not stated.
  • Whether conflicts are recorded in the change history or flagged for a person to review is not stated.
Where
Update this section: add lines to the card's list after "Field rules that decide which system wins" and "Read-only fields where you need them".
Related sections
The tools in Data Hub · Change history
What to do
  1. Confirm with engineering the default conflict behaviour, how simultaneous edits are settled, sync frequency for ERP syncs and whether conflicts are logged or queued for review.
  2. Add the confirmed default behaviour, timing and conflict logging to the card's list.
  3. Link the card to the Change history card or a guide on setting field rules.
Done when: /products/data states what happens when both systems change a field with and without a rule, how often syncs run and where conflicts are recorded.
Answer full page
When a field changes in both Hourglass and the connected system, Data Hub resolves it with set conflict rules, and you can make the other system the source of truth for a given field. The docs article below explains how conflicts are resolved.
Sections in the answer pageStatus
/products/dataTwo-way syncs, without custom code (card)Partly answers it
Question 2

“Which system wins when both change the same field?”

Answer
Partly answered

/products/data says you map fields once and choose which system wins when they disagree, with field rules and read-only fields. It never says which system wins by default when no rule is set, or how simultaneous edits to the same field are timed and logged.

Section on the siteStatusTicket
/products/dataTwo-way syncs, without custom code (card)Partly answers it
Add the default sync conflict rule to /products/data

Ticket

Paste this into your ticketing tool.

Add the default sync conflict rule to /products/data

Who needs it: CTOs and IT or data teams setting up ERP syncs (this visitor: Whirlpool Corporation)
Section: /products/data › Two-way syncs, without custom code (card)

What is missing:
- The default winner when both systems change the same field and no field rule is set is not stated.
- How near-simultaneous edits are ordered (for example by timestamp or sync cycle) is not explained.
- Whether the overwritten value is kept in change history is not stated.

Where: Update this section: add to the card "Two-way syncs, without custom code", beside the line "Field rules that decide which system wins".
  Related sections: Change history

What to do:
1. Confirm with engineering the default conflict rule, how simultaneous edits are ordered and whether overwritten values are logged.
2. Add a line on the default rule and a line on how the losing value appears in change history to the card.
3. Link the card to the docs article on conflict resolution.

Done when: /products/data states which system wins by default when both change a field and where the overwritten value can be seen.
Depends on: Add sync conflict handling detail to /products/data

From: conversation 7924102438d4, question 2: "Which system wins when both change the same field?"
Who needs it: CTOs and IT or data teams setting up ERP syncs (this visitor: Whirlpool Corporation)
What is missing
  • The default winner when both systems change the same field and no field rule is set is not stated.
  • How near-simultaneous edits are ordered (for example by timestamp or sync cycle) is not explained.
  • Whether the overwritten value is kept in change history is not stated.
Where
Update this section: add to the card "Two-way syncs, without custom code", beside the line "Field rules that decide which system wins".
Related sections
Change history
What to do
  1. Confirm with engineering the default conflict rule, how simultaneous edits are ordered and whether overwritten values are logged.
  2. Add a line on the default rule and a line on how the losing value appears in change history to the card.
  3. Link the card to the docs article on conflict resolution.
Done when: /products/data states which system wins by default when both change a field and where the overwritten value can be seen.
Depends on: “Add sync conflict handling detail to /products/data”
Answer full page
You can choose which system is the source of truth for each field, so that side's value wins when both change. The docs article below explains how Hourglass resolves conflicting changes and how to set this up. If you'd like to walk through your ERP fields with the team, I can put you in touch.
Sections in the answer pageStatus
/products/dataTwo-way syncs, without custom code (card)Partly answers it

Questions and answers are shown as recorded. Status, what is missing and what to do are our analysis of the live site, read 22 Oct 2026.