How it works
Identifier history search applies to MaestraID and to unique identifiers, as long as there’s no restriction in place that blocks merging customers with different IDs. After two customer profiles are merged, the main identifier of the higher-priority customer becomes the active one. The ID of the lower-priority customer is preserved in history. From that point on, Maestra accepts either identifier — both for passing orders through and for updating customer information. In other words: to your external system, it still looks like two separate customers. Inside Maestra, it’s one customer with a single combined profile.How MaestraID behaves
All MaestraIDs of merged customers are stored in history. Unlike unique identifiers, customer priority does not decide which MaestraID stays active after a merge. MaestraID follows its own rules — every MaestraID from the merged profiles is kept and remains searchable through history.Example
Two customers share the same email address and get merged on that basis. The old identifier doesn’t disappear — it’s saved in history. Maestra continues to accept operations sent under either identifier and applies them to the same combined customer profile.Identifier history search is what keeps your integrations stable across merges. If an order comes in with the older identifier after a merge, it still lands on the right customer profile.