Tricky.
The process seems to work better (or only that way) when I start with a purchase instead of a sale.
Doing so, I can follow the process, but at the end, no customer invoice (my customer, paying to me) is created. Purchaser invoice is.
Does this module not create the customer invoice - or did I miss a step or made another mistake?
Cheers,
Wolf
No if you do not start from a sale.
Hm.
I regret having to say that I’ll give in now. After more than 10 hrs of tinkering and kindly granted support of my fellow friend @rmartin I could not find out how to run this module.
Sad.
W
Sorry to hear that but for me the main blocker to help you is that we do not have a precise description of what you are doing (from the beginning). Mainly we just see random post about being block here and there (each from different usage/scenario).
Thank you very much for your care and your commitment, I deeply appreciate this.
My problem is that I do not really know what to do, documentation does not tell that. So I tried numerous variants, hoping that one would be successful some day.
My task, I think is a very vanilla one: Place an order of two articles at a supplier, deliver one article to my own warehouse, deliver half of the other article to a customer and half to my warehouse. (I tried to describe that under #7 and #8). My guess is that this
window is the main problem, because it’s not clear to me which entries are required.
So I think I rather do not need a particular solution for a very special problem, but very basic instructions to handle the task.
Cheers,
Wolf
This is not supported, you must have two purchase order.
I do not know what screen this is because I do not speak German.
The drop shipment is working only from a sale order on which some products sold are configured (for the best supplier) has supporting drop shipment.
When such order are confirmed, they create purchase requests for each product which must be converted into purchase orders (which will have a customer (read-only) field filled.
The important thing is that as soon has there is a problem in the supply chain (missing quantity, order cancelled etc.), the sale order will fallback to the standard workflow by creating a customer shipment.
Had a nice talk with fellows @jgras and Frederik J. In the end we agreed that all of us do not really understand how this module is supposed to work, and we believe it lacks essential features. So, here comes a suggestion of what I’d regard as crucial - certainly this is incomplete, maybe it’s too ambitious. Just my 2cts.
I think we need both:
Business case is products to be delivered from one supplier to various customers - e.g. in a collective order to acquire a quantity discount.
With the module installed, the user should be able to decide at any product he adds to the purchase, whether this product comes from his own warehouse or from a drop shipment. Such, the process could look as follows:
User actions:
The same - mirror-inverted - should be possible with a sale. Business case could be a customer, who is supplied by various sources, because my own warehouse does not have enough in stock to satisfy this demand, I do not have the capacity to store big amounts, drop shipment is faster etc.
Both cases frequently occur even in my really small business.
Fellow friends @rmartin and Frederik J. do have a (AFAIK much more) sophisticated drop ship module, AKAIK they’ll be happy to provide it as a blueprint.
Sorry. Wolf
This is not drop shipment but stock_supply
Drop shipment is when the supplier delivers directly to the customer without sending the goods to the company warehouse
This is defined at product level. So for each product you have a static configuration for all sale orders.
This is managed by the supply_on_sale and drop_shipment checkboxes under the customer tab in products. Note that you must check the first to see the later.
When both are set, whenever a sale order is confirmed containing the product a purchse request linked to both supplier and customer will be created by the system. Such purchase requests should be used to create the supplier purchase.
HIH
As far as I see they mainly want to be able to configure that on the sale order instead of having static configuration on the product.
I have always been reluctant to have this in standard because for me it is not the job of the salesmen to decide about the supply. But it is quite easy to implement it in custom module (we already did) to add a fields on the sale line to customize the supply_on_sale and get_purchase_request.
But I think what could be implemented would be the possibility at the purchase request to change it (if it has a sale has origin) into a drop shipment request by filling the customer and delivery address. Such wizard should take care of updating the stock move of the sale to become a drop move. I think this new feature could be in standard module because it is the right level (the purchaser) to overrule the default behavior.
For me this is clearly a bad workflow. The salesmen have nothing to do with the purchases.
Also if such purchase can not be fulfilled by the supplier there will be no trace anymore of what was requested by the customer. We always need a sale order to record what a customer requested.
I would not be against such feature if someone proposed it. But it should still provide the simpler design which is one purchase order per customer by default. Also once the customer and delivery address are on the purchase line, they must be grouped in the same drop shipment.
Indeed I’m wondering if it will be simpler to group purchase orders for the same supplier under a single printed document/reference.
To me, this is essential. Sourcing is such a complex thing, I would never leave it to an algorithm, not even the most sophisticated one. And things are getting worse with supply chains getting more fragile these days.
This may be the case in a big company. In far most companies (see: Where is Tryton’s largest potential of customers?), all of them are one person - or at least sitting in the same office and will discuss how to do best sourcing at a given moment.
Had another intense talk with fellow friend @udono on this - but even this Grand Master could not make it work.
We simplified use case as far as possible, just one product going from one supplier to one customer. Product is marked as salable, purchaseable, supply on sale; supplier is marked as “drop shipment”. Stock is lower than amount to be sold.
We create a sale - but when confirmed, a “ordinary” shipment is created, not a drop shipment. How can I tell Tryton to create a drop shipment? - I think, there must be some kind of control (“drop shipment instead of shipment to own warehouse”) to achieve this, but we could not find such.
Cheers,
Wolf
it must create a purchase request if it is correctly configured. So which means that the product must be supply on sale but also the shipment method must not be manual, the quantity must be positive and there should be no existing stock move attached that are not in staging or cancelled.
Actually, it does. And I can turn that into a purchase. But still have no idea how to continue.
So once the purchase is confirmed, a drop shipment is created which is linked to both the purchase and the sale. Once your supplier inform you that the shipment has been sent, you can mark the drop shipment as done so the sale will be marked as sent.
This does not happen in my install. Instead, a ordinary shipment is created.
That’s mean that the purchase request did not have a customer filled this can be because either no product supplier was choose at the creation (for example supply delay was too long) or that the product supplier was not configured for drop shipment.
So when you want to do drop shipment, you must ensure that the purchase request is filled for a customer otherwise the setup must be fixed and the purchase request must be deleted to recreate a new one.
I filled Issue 11926: Allow to edit customer on purchase request - Tryton issue tracker because this constraint could be improved.
Sorry to be so persistent here. But I still think the very subtle automatism which is used (as far as I understood it) can only cover some quite special cases.
Yet I’m not convinced that we do not need a very simple and straight forward manual trigger for drop shipments. One may argue whether it only is required at sale - or as well at purchase. But any case - I think that at sale, we should be able to elect any sale position to be handled as a drop shipment. And such was the opinion of literally any of my German fellows, who tried so hard to help me in understanding this module.
Cheers,
Wolf
I strongly disagree. As I already said, it is not in the rights of the salesmen to make such business decisions.
This does not make it right.
Understood. It’s always difficult for me to take the perspective of a bigger company.
But don’t you think that people working in such will talk to each others and find out the best solution? - So maybe “sales” is not the right place - but in some other this manual trigger could be applicable anyway.
I agree that allowing to manually trigger a drop shipment in purchase request will be a good idea
