Justing bumping this since there has been no activity since it was marked as 'planned'

I agree and have previously posted a similar suggestion so would like to add my support for this.

We handle warranty servicing on behalf of manufacturers, Distributors and customer direct. Customers’ items are often sent by (or collected from) the retailer/shops to be invoiced to manufacturers/distributors (Example: We handle UK warranty repairs for US based manufacturer where customer’s (i.e. OWNER's) equipment is sent by the SHOP for repair and then possibly returned directly to the owner, the shop, or back to the distributor if the item has been swapped out - or scapped for parts (i.e. not returned).

It's can be disastrous if equipment is inadvertently dispatched to the wrong place by, say, a new member of staff while I'm not looking!

Declaring a job as warranty can be still slightly ambiguous and a clearly definable BILL TO field is also essential. Checking (i.e. searching by) the BILL TO field is actually more useful that checking whether defined as “warranty”.

We handle warranty repairs for several brands but the actual company paying for the repair must be carefully clarified. Some shops offer 5 year warranty so if the failure occurs within year 1 the manufacturer pay but in year 5 the shop is responsible.

In order for a warranty repair to proceed we require a prop-of-purchase (purchase invoice etc). If this proves to be unavailable the job must be invoiced to the owner and status may be changed to non-warranty.

so we currently need multiple contact/name/address fields/etc

• “Collect from”: For jobs pre-booked online we can arrange UPS collection (with optional carriage insurance if required at 1% of“Declared value”)
• “Invoice to”: For invoicing at the end of each month in one batch.
• “Owner”: To discuss the actual fault
• “Return to”: This is often different – i.e. return to warrantor (etc) if replacement has been sent out. It can be very awkward to rectify when an item is wrongly returned to the sender even when they have received a replacement.

It is essential to be able to define each and any of these at any point in the workflow.

(On my current system we have each of these overlayed, with tabs to select whichever is viewed. Buttons below each tab on each page allowing copying from one to another also proves useful since these fields are frequently all the same.)

I appreciate there may be different workflow scenarios so perhaps the headings of these fields I have listed could perhaps be definable by the user:
Name/address1, Name/address2, Name/address3, Name/address4, Name/addressetc

For the service industry it would be nice to see site address as well and have that site address trackable via GPS tracking.