Community mailing list archives


Re: Usability/design in relation to res.partner

Open For Small Business Ltd, Graeme Gellatly
- 18 أغسطس, 2015 06:23:16

Maybe in USA,  but the world is bigger.  As I said it is a localization thing. 

Definitely not expected in NZ by payment providers. Always one field. In NZ we generally have first name surname and it still causes lots of problems when the fields are split. 

What is a Chinese persons first name. Which field to put generational name etc. A  ninth of our population is Chinese.

Anyway the modern standard is not to seperate the 2 AFAICT from reading respected authors. 

On average our customers have 90 to 100 delivery addresses at any given time plus deliver to other customers . Honestly I find it hard to fathom what your exact issue is,  for us it just works. Sure people need training but it isn't exactly challenging. 

Maybe we did some view customisations but  very little,  I think just setting the default to delivery if created from delivery field.

Yes the model changed,  but the functionality you refer to is identical almost since I ever can  remember,  definitely 6.0 maybe before. In any case,  that function was always part of res partner. 

Sent from TypeMail

On 18 Aug 2015, at 6:09 PM, OpenERP Master <> wrote:

Graeme, There may not be case to have multiple invoice address, but there is certainly case where a business entity needs goods shipped to multiple distribution centers. Or i a customer sends a product as a gift, the delivery address would be different.

The code has changed significantly in the introduction of version 7 was it? There was res partner address

On the firstname lastame thing, I am surprised to see some joy with this. There are lots of software that have mandatory requirements for this. Any shipping software, other ERP, Website software, Credit card procesing, requires firstname and lastname separately. I would go so far as to say its data industry standard to support at least firstname and lastname. When Odoo start doing integration, etc, you have to have it.

On Tue, Aug 18, 2015 at 12:48 AM, OpenERP Master <> wrote:
I am very open minded to an explanation for the current functionality design. It seems there are those out there that like it as is. I anticipated this but not why. Also nobody commented on the code quality of the method I mentioned.

In our case with B2C or eve B2B, all of the companies I ever worked wtih have simple concept of Customer record (partner) and billing / shipping addresses. When you first start a sale/quote workflow you select a customer. You will also ask them their billing address and or shipping address. Worth noting 100% of my clients are product based businesses that deliver goods to a customer or other vendor.

When they select a customer, they need to select an address that is an address of the customer. This can be any address or in a different country even, as long as the address is attached to the customer/business partner. The current functionality has no filter and allows you to select a partner, contact, delivery address, or invoice address.

When you add a partner to a sale order, if no shipping/invoice addresses are attached as children of the partner, the software defaults to the partner id. In most if not all of my implementations, the partner itself would have no address and a specification must be made for each billing/shipping.

In software like Magento, you can specify a default for each type. When you add a customer/business to a sale order, it could populate each respectively. If I add an address of type default, it has no distinction between shipping and billing.

Also, in the source code for get_address a domain is passed to retrieve ['contact', 'invoice', 'delivery'] but contact type is never retrieved and used. You said a contact is not an invoice or delivery address, but it is used as a possible entry in the code, just never called.

Some clients set up new addresses in Odoo but do not think to check other than contact, which is checked by default. I feel like generally there is something missing in terms of invoice/delivery management. The fact you have to enable this to even select a delivery/invoice address further tells me that there is an Odoo disconnect on how B2C businesses work today. I would ask you to please compare the feature of adding to a sale order against other reputable software and from what ive seen is consistency and Odoo is the odd one out.

On Mon, Aug 17, 2015 at 10:48 PM, Nhomar Hernández <> wrote:

2015-08-17 22:32 GMT-05:00 Graeme Gellatly <>:
You forgot the most important one, web_m2x_option to stop all those creations.

That's true.! (but it is supported by default in 8.0)
Saludos Cordiales

CEO at Vauxoo Odoo's Gold Partner.
Nhomar Hernandez

Post to:

Post to: