Hi Jeremy,
We would like to let you know that customer data in Pabbly is maintained through an email address so a unique customer can have different subscriptions along with various sales associated with a registered email. The details on the above-mentioned case are the same due to the email address. So, in such a case if you are looking to fetch the updated customer name then as a merchant you'll be required to edit the customer name manually from the backend -
View attachment 2384
To understand this more properly, please refer to the below example -
============================================
Suppose Plan A is purchased using the email -
[email protected] by the name of Customer 1. Similarly, Plan B is purchased using the same email but this time by the name of Customer 2. This activity took place in May 2020 & the merchant accessed the data in May 2021. So, the system will then show the latest data by the new customer name i.e. Customer 2 but the last sent invoice was in the name of Customer 1 since that time only a single name was associated with this email -
[email protected].
Hence, the new data will reflect the new customer name & the old initial invoice will show the old customer name which is confusing.
A similar case is with the tax system, For eg: -
User purchased = Plan 1 with 10% tax which was levied on Region 1 (Using email
[email protected])
Again, Purchased = Plan 2 this time using the same email with Region 2 on which no tax rule has been created in the system.
So, the tax will not work in the case of Plan 1 because the user data will be modified as per Plan 2 credentials. Hence, if we allow this setting then it will create confusion later on.
Therefore, to avoid such a scenario, each customer record is identified with a unique name & email address. So, we request you to please manage this as per the system framework as it'll also minimize your hassle of maintaining the unique customer data.
Hope this helps!