Skip to main content
All updates
Bug fix·Mon Sep 07·

Merging a duplicate keeps every migrated reference

A reviewed merge now moves the whole booking and every original Salonized reference to the client you keep, so a re-import finds them instead of creating a second record.

When you merge two records for the same person, everything that identified them
now follows the client you keep.

**Every original reference is kept.** If both records came from Salonized, both
of those original references survive the merge and both now point at the client
you kept. Nothing is renumbered or thrown away: the original Salonized
reference, the client ID it was imported under and the newsletter consent
recorded against it all stay exactly as they were. The client you kept also
keeps their own Booking Bible client number.

**A later import finds the right person.** Before this, an import of a
reference that had been merged away could create a second account for someone
you had already merged. Now it resolves to the client you kept and creates
nothing new.

**A multi-appointment visit stays in one piece.** A visit booked as several
appointments together used to move its individual appointments but leave the
visit itself — the part that holds the payment — attached to the record you
merged away. The whole visit now moves as one, and its payment, refund terms
and the staff who handled it are unchanged.

**Work that is still running stops the merge instead.** If a visit is still
being booked or its payment is still moving, or if an import of that person has
not finished or is waiting for someone to review it, the merge stops and tells
you which one — rather than moving records out from under work in progress.
Nothing is changed when it stops, and no message is sent to the client at any
point.
Next update

Clearer extras and AI Studio tier changes

Prepared billing controls clarify eligible extras and AI Studio tier changes; new catalog purchases remain subject to rollout and payment readiness.