What is the best practices with regards to dummy customer when doing webshop integration? We don't want to create every real customer from webshop because these customers are not companies and most likely they are one time customer. So for us that dummy customer in the invoice record would be ok, but it would hold millions of sales records and I'm afraid of some limits we can encounter. So anybody has real practice in such type of integration?

We have the same dilemma. We are considering the use of an ETL middleware to consolidate daily sales into one or a handful of Cash Sales per day instead of creating one for every sale.

Create a custom shipping and custom billing address on the transaction record for the webshop customer and use one main customer record for webshop. The addresses will be created under the addressbook subrecord on the transaction record.

unfortunately we can't aggregate sales as they must be reported invoice by invoice to tax authorities. So the same customer record and different address and addresee on the invoice so far are the only acceptable solution we can think.

For sublists on the customer record (and any sublist for that matter) that hold addresses, you will be limited to "seeing" 1000 rows.

In my sample above, the transactions are paid immediately via credit card usually. We also have web transactions that must be reported by invoice for another Subsidiary and like you said there's really no other option but to create separate records for each sale.

I prefer to use individual customers