Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Two of our clients are running their businesses on LedgerSMB. In each
case, the company is a distributor who often drop-ships to a third
party. For example, their customer is a store, and the company
drop-ships to the store's customer.
I'm looking for best practice on how to set this up in LedgerSMB. Since
the company's customer is actually a store (i.e., not the ultimate
recipient of a shipment they are fulfilling), one approach is to add the
store as a customer (entity class) and the store's customer as a
shipping address. The problem with that approach is the gross number of
end-customers could become quite large.
Another approach might be to create a new entity class. For example, a
"third party". The question is how to connect the store (a customer in
LedgerSMB) with a "third party" entity. Plus, how to modify search /
results to filter "third party" entities in or out. Sane ideas very welcome.
Try out Activus Secure Payments^(TM), our recurring payments application.
Demo at http://demo.activustech.com