I suggest you ...

Update customer table with updated member data

If a member is changed, the customer in UCommerce isn't updated. Hence, new orders won't get the updates.

2 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Lars-Erik shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • AdminSupport (Support, uCommerce) commented  ·   ·  Flag as inappropriate

    I didn't notice "new orders". Read that as "orders" :)

    Obvously new orders should reflect new information if the customer addresses are used.

    Generally the member is used only for login from uCommerce' perspective. Address info should be stored as just that and associated with the customer object, which in turn is associated with the member profile.

    Which information would you like to see reflected on the customer/customer addresses from the member and how do the changes occur on the member, e.g. changes in back-end, performed via API updates, or something different?

  • Lars-Erik commented  ·   ·  Flag as inappropriate

    If the Customer table is meant to hold 1:1 information per order, maybe it should be named otherwise? OrderCustomer for instance?

Feedback and Knowledge Base