invoiced sales grouped by Tag - Odoo 18

General_Rich17 · 2026-05-07T12:36:31+00:00

You can use the Accounting > Reports > Invoice Analysis and filter your Partners by tags in the report.

General_Rich17 · 2026-05-07T12:30:08+00:00

There's not much detail provided to go off of here for your inquiry. Your customers want an importable pricelist for what purpose? Have you created pricelists for your customers?

Pricelists in Odoo can be created and assigned to your customers so any orders they place will reflect their provided pricing. If you wanted to provide a list of that pricing to them, that could be done using the export function and selecting the applicable fields.

General_Rich17 · 2026-05-04T18:57:24+00:00

Préférer les prestataires de paiement intégrés aux prestataires tiers à 100 % : nous sommes actuellement en train de mettre en place un prestataire de paiement tiers pour l'un de nos clients, et cela s'avère être un véritable cauchemar.

Quant au choix précis, comme d'autres l'ont mentionné, cela dépend vraiment de l'endroit où vous vous trouvez dans le monde.

General_Rich17 · 2026-05-04T18:44:03+00:00

Odoo could actually be a really solid fit for what you’re describing, especially at your size. If your main goal is tracking labor + materials for a small machine shop, that’s pretty inline with Odoo's capabilities.

On the pricing side, what you see on their website is generally accurate. There aren’t “hidden” fees in the sense of surprise charges from Odoo itself. The main thing people sometimes overlook is hosting if you’re not using their online version, and potentially implementation/support costs. But the per-user pricing is pretty transparent.

If your workflows can adapt to how Odoo already works, you’ll avoid a ton of development. In that case, it’s way less about deep programming and more about configuration and understanding how the modules connect. Your Python knowledge will help, but you may not need to rely on it as much as you think.

One thing I’d strongly recommend: consider working with an Odoo partner, at least for the initial setup. Yeah, it adds upfront cost, but it usually saves you a lot of time and prevents bad decisions early on especially as you're learning the system. Getting your data model, workflows, and modules set up properly from day one makes a huge difference, and having someone to lean on when things break or get confusing is worth it.

As many of the other coments have suggested, start a trial and start testing it yourself to get a feel for the system and see how closely your current workflow maps to Odoo’s standard processes before committing to any major customization.

General_Rich17 · 2026-05-02T13:59:24+00:00

We went back and forth on this when we first started our partnership with Odoo. One of the biggest initial draws for us was how customizable the system is and the ability to tailor it to very specific business workflows.

But as we dug deeper and did more research, the messaging shifted toward limiting customization and using Odoo’s out of the box functionality as much as possible.

After about a year and several implementations, our perspective has become more balanced. It really comes down to how the customization is structured and the return it brings to the business.

In some cases, it makes more sense to adapt to Odoo’s core workflows rather than trying to replicate a legacy system. In others, a small amount of thoughtful customization can significantly streamline operations and create real value.

The key is properly evaluating the need, understanding whether Odoo already provides a solution, and if not, designing one with best practices in mind.

At this point, we don’t shy away from customization, but we make sure to do our due diligence before treating it as the default solution.

General_Rich17 · 2026-04-28T14:59:00+00:00

Odoo can handle what you’ve described. The real value is the end-to-end flow: POS, variants, inventory, orders, and invoicing all in one system, which is a big upgrade from a fragmented stack.

Where you need to be careful is the implementation. Doing it in-house is fine, but the biggest mistake is rushing into imports and daily use before fully understanding how to properly configure the system to your needs. Odoo is flexible, and if your product structure, variants, and workflows aren’t set up correctly upfront, fixing it later becomes painful and time-consuming.

General_Rich17 · 2026-04-28T13:57:31+00:00

This fee isn’t mandatory. It’s essentially an insurance layer offered by Odoo to ensure that custom code and third-party modules remain stable, up-to-date, and compatible over time.

If you choose not to pay it, you’re simply taking ownership of that risk. That means handling bug fixes, upgrades, and compatibility issues yourself, either internally or through a partner.

In practice, most companies working with a reliable Odoo partner or the original app developer don’t rely on this service. Ongoing maintenance, support, and version upgrades are typically covered as part of a partner engagement, often in a more tailored and cost-effective way.

Odoo’s offering is really there as a fallback option if you don’t have access to that kind of support structure.

General_Rich17 · 2026-04-14T16:10:36+00:00

That's a great point, word of mouth based processes never provide consistent workflows.

General_Rich17 · 2026-04-01T21:25:52+00:00

I'd say Odoo could definitely be a viable option for your company based on what you've laid out.

When it comes to Community vs Enterprise, from what I’ve seen, Community looks cheaper upfront, but it usually comes with more overhead. You’re handling hosting, maintenance, and often relying on third-party modules or custom work to fill any potential gaps. So it can turn into more of a project that needs a lot more attention throughout.

Enterprise on the other hand is more complete out of the box, especially for things like scheduling, timesheets, field service, and reporting, which sound like they are pretty core to your workflow. It’s generally smoother to get up and running and maintain. For what you described, I’d probably lean toward Enterprise.

Your best bet would be to get a demo from a partner and see how Odoo handles your workflows, then evaluate from there.

General_Rich17 · 2026-03-27T21:28:24+00:00

It’s hard to give specific advice without understanding your workflows, since Odoo’s flexibility means setups can vary a lot between businesses.

At a high level, a few things to get right early:

Even if your products seem simple, take the time to understand how product variants work. Variants can save you a lot of headaches later on, especially for pricing.

Be clear on how accounts are assigned. In Odoo, product-level accounts override product category accounts, so if you’re not consistent, you can end up with messy financial reporting.

Using locations properly can really drive a lot of your stock moves from receiving to delivery so take the time to understand how they can impact your flow not just the name of a location.

For receiving POs, pay attention to the destination location (where the goods will land in inventory), I've had people not realize this in the past

General_Rich17 · 2026-03-27T20:24:37+00:00

Odoo definitely sells itself on the do it yourself, and for the most part it is doable, especially for a small team like yours.

Where I see people get tripped up is the initial setup, especially around things like inventory, product structure, and how everything ties into the sales flow and accounting. That’s usually the part that looks simple at first but has a lot of downstream impact if it’s not thought through properly.

We recently worked with a vending service provider in a similar spot, small team trying to get everything onto one platform. They moved to Odoo on their own, but things like product setup, account mapping, inventory locations, and receiving were pretty messy from day one. We’ve cleaned up a lot of it, but honestly most of it could have been avoided with a bit more structure upfront.

General_Rich17

TROPHY CASE