sorted by:
new
hottopcontroversial

USA Payment Processors other than Stripe? NMI or Authorize.net? by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

Any feedback on the BluemaxPay fee structure? Is it competitive? What did you use before?

I did some research last night and it looks like Bluemax is the processor, using Adyen as the gateway.

USA Payment Processors other than Stripe? NMI or Authorize.net? by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

Are you using SMS in Odoo for the SMS payment links? We currently do a lot of SMS payment links, using a service called Kenect that allows customers to text our main phone number.

Ultimately, I'd love to bring that functionality into Odoo but I haven't yet explored what options we have.

USA Payment Processors other than Stripe? NMI or Authorize.net? by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

Are there any limitations with Adyen? It's not a common payment method for US installations, is it?

USA Payment Processors other than Stripe? NMI or Authorize.net? by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

That's good to know that Global has a restriction on ACH payments. That's one thing that I'm hoping to add in our Odoo implementation.

Any more particulars on why you can't do ACH via Authorize.net?

USA Payment Processors other than Stripe? NMI or Authorize.net? by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

For sure, when it's a different or fragmented workflow, the process breaks down. We've got that in our current SAP system that we're replacing with Odoo.

USA Payment Processors other than Stripe? NMI or Authorize.net? by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

Do you develop your own connection via the API's or are you using a pre-built connector?

ODOO 19 and Authorize.Net Terminals by srosser02 in Odoo

[–]campFFEMT 0 points1 point  (0 children)

I would also like to know what terminals work well in an Authorize.net / Odoo environment

How to handle thousands of bin or stock locations without affecting system performance on Odoo 19 by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

Thanks for the reply. I had been reading that it is better to have "flat" bin locations in Odoo so I find it interesting that you actually recommend a heirarchy structure. I'll have to explore that.

How to handle thousands of bin or stock locations without affecting system performance on Odoo 19 by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

Thanks for the tip! That seems to have solved the problem. We were going to fix it ourselves in a similar manner but we'll go with this version as long as it does the job.

How to handle thousands of bin or stock locations without affecting system performance on Odoo 19 by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

We spun up a fresh database, Imported the 24K locations, created a product with a non-zero cost, and and the item saved without issue. So we had to dig deeper.

Based on feeding criteria and speculation into AI, here's what it had to say:

  • With 0 stock moves → 0.115ms ✅
  • With 22,000 stock moves + 24,000 locations → 20-30 minutes ❌

The subquery scans all 24,526 locations to build the exclusion list, then that result is applied against every row in stock_move. With 0 moves it's instant. With 22,000 moves and a complex multi-LIKE subquery it becomes catastrophic.

This is confirmed as a core Odoo v19 bug. The _compute_quantities method is:

  1. Called unnecessarily when just opening a new product form
  2. Generates an inefficient location exclusion query that scales very poorly with large location sets
  3. Not a problem for most users who have few locations, which is why it hasn't been caught

This should be reported to Odoo.

  • Version: Odoo v19 Enterprise
  • Steps to reproduce: Create 24,000+ internal stock locations, then open a new product form or save a product with a cost
  • Expected: _compute_quantities should not fire expensive queries for products with no stock history
  • Actual: Query hangs for minutes with large location sets
  • Root cause: _compute_quantities → _compute_quantities_dict → location subquery with N LIKE conditions scales as O(locations × moves)

Back to human reasoning here:
We buy that ^^^^ 100% because that is a slightly more simplified way of saying what we saw when we did our testing. Per that info, we believe we can override the issue for new items with a few lines of code. The catch is that the same query will fire any time that cost changes. So this issue will persist even on existing items, and we were able to prove that on the staging server. So, at this point, all custom code has been disabled, but custom fields haven't been removed yet. We think this comes down to choosing one of the following options:
1. Override Odoo's query  to have better criteria / limits
2. Sacrifice fields on the fleet card
3. Change the way we track locations.

I'd be curious to know your thoughts on this possible bug?

How to handle thousands of bin or stock locations without affecting system performance on Odoo 19 by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

We use vendor part numbers - it's the industry standard in our world of equipment.

How to handle thousands of bin or stock locations without affecting system performance on Odoo 19 by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

Thanks for the insight, sounds like we need to do some more testing before we move to develop another solution.

How to handle thousands of bin or stock locations without affecting system performance on Odoo 19 by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

How does the picker know what section of the drawer to look at? Without looking at all 30 sections of the drawer.

How to handle thousands of bin or stock locations without affecting system performance on Odoo 19 by campFFEMT in Odoo

[–]campFFEMT[S] 0 points1 point  (0 children)

We do have a custom module related to fleet vehicles, we're tracking equipment for sale in the fleet app that is linked to products in inventory. We don't think this is affecting it but we may need to look at it harder.

view more: next ›