Quote:
Originally Posted by bob_romijn  Hi,
With all this saving in transportation you also need to send a bill to your customer for getting paid something (mandatory to survive in transport  ). You don't want to have the customers to have also visibility to orders from another customer. Because you want to build seperate shipments from the orders on the customer side to get something paid (you sell something), you need to consolidate a bit different. For the consolidation and visibility the sell shipment is always built in the customer (child) domain. |
Hi Bob,
Thanks for the explanation. However, in my case, sell side billing and reconciliation is a function of the "parent" domain because to the customer, regardless of how many legs (shipments) executed by the "child" domain, the customer only wants to be billed once - hence 1 sell shipment.
It is difficult to "gather" all the sell shipments from the "child" domain for consolidated billing. Rather, wouldn't it be more natural to allow users to choose where the sell shipment is to be built?
Another consideration is if there is a consolidated shipment with multiple legs, and each leg is executed by a "child" domain, the sell shipment would need to be built at the "parent" domain so that the orders can be easily linked together for a single consolidated bill to the customer.
Have you encountered such a scenario and what was the model applied?
Thanks!
Ian