u/allegiancetech

Here is the situation I have, which does happen from time to time. I created a quote for a customer for two pieces of hardware - a monitor and a UPS. They accepted the quote, I created the sales order, and then the invoice, and then sent the invoice. They sent a check for the invoice. Now, before I ordered anything, they decided to go with a bigger monitor.

Should I:

A) Cancel everything and create a new quote/so/invoice, void the check and have them send a new one

B) Make a note in the invoice and sales order, and somehow update the sales order to reflect what they are actually buying, and create a new invoice for the price difference (I personally like this method, but I don't know best way to do it)

C) Make a note i the invoice and sales order, and create a new sales order and invoice for the difference and send that

Part of the reason I like option B is that I will be generating a purchase order linked to the sales order(s), and then receive the items. So, I'd like some kind of reflection of "this is what was originally ordered by the customer, that changed, here is what we actually ordered for them, now let's receive and bill for them"

There are times I make a personal choice to work on a ticket after-hours for any number of reasons, but may times in those instances I don't feel I should charge our overtime rate to the client for that time. They didn't ask me to work on it on a Saturday, it's not an emergency, etc. Maybe I just got behind because I was out a day earlier in the week and I want to get caught up before the next week starts. Is there a way, when I'm recording my time in the action, to designate that this action should be billed at the standard rate even though it was performed outside our normal work hours?

We have inventory we sell both online via odoo ecommerce, and through odoo Point Of Sale. Our retail store and warehouse are in the same building, all one "Warehouse" in odoo. Our primary stock storage is WH/Stock and we keep a smaller inventory in the retail store for customers to pick and buy, that location is WH/Shop. Many items are sold both online and in the retail store.

Here is what we would like to be able to achieve with routes and/or reorder rules:

- Inventory for both WH/Stock and WH/Shop to show as available to be sold online (it currently does do that now, but odoo does not reserve the stock in WH/Shop when sold and allows it to be sold multiple times online).

- If an item in the retail store (WH/Shop) runs out, we would like an internal transfer to be created to move stock from WH/Stock to WH/Shop. If there is not enough in WH/Stock, then a purchase or manufacturing order should be created.

- If an item sells online, we would like it to be able to look at what is on-had in WH/Stock and WH/Shop, reserve first from WH/Stock and then from WH/Shop. Ideally, an internal transfer order would request the move of the inventory from WH/Shop to WH/Stock from which the order will be completed, and the inventory in WH/Shop then reserved so it can no longer be available for sale.

- If an item in WH/Stock then is below order quantity, a purchase/manufacturing order is generated.

I fear this is just too cyclical to work - stock going back and forth between WH/Stock and WH/Shop. Someone at Odoo suggested setting up a virtual warehouse, and changing WH/Shop from a location to a separate warehouse "contained" in the virtual warehouse along with the WH/Stock. But, as I was trying to finalize this setup in testing, Odoo removed all documentation for virtual warehouse setup, so I fear that is no longer a supported option, even if it was the best option (which I do not know).

Would it help to have a third location - one for main stock storage, one for online sales inventory, and one for retail sales inventory? Or is that complicating things even more?

How is everyone (anyone?) handling the right of withdrawal directive that I believe is going live on 6/19. We are in the US and just heard about this. According to Odoo support:

To fully comply with EU regulations regarding the right of withdrawal, Odoo users typically implement the following:

1. Clear Information: Provide clear and prominent information on their e-commerce website about the right of withdrawal, including the conditions, time limits (usually 14 days), and procedures for exercising this right. This is often done through a dedicated "Returns Policy" or "Terms and Conditions" page.
2. Contact Method: Offer a clear method for customers to exercise their right of withdrawal, such as a contact form, a dedicated email address, or a downloadable model withdrawal form.
3. Backend Processing: Once a customer initiates a withdrawal request through one of these methods, the merchant uses Odoo's sales and inventory features to process the return (reverse transfer) and issue the refund.

However, there isn't a specific, pre-built "withdrawal button" that customers can click on the e-commerce frontend to automatically initiate a return process as a standard feature.

Does this sound like what everyone is doing who has online sales in the EU?

Also, I assume from the verbiage of the directive, this only applies to retail sales as it references "consumers", so we don't need to worry about it with our wholesale website?

Not sure if anyone here is using level.io for their RMM, but I have posted a feature request on their forums to update their HaloPSA API to have the ability to change ticket creation payloads destination to /api/incomingevent/process instead of the current location of /api/Tickets so that the Event Management module in Halo can be taken advantage of to process/route these events/tickets as they come into Halo vs just creating tickets. If anyone thinks this would be useful, please visit my post and upvote:

https://feedback.level.io/en/p/halopsa-integration-support-event-management-endpoint-or-make-webhook-url-conf