Odoo success stories, in our clients’ own words

Challenge

Orders reach Odoo from three places: the Shopify web shop, the Shopify POS in their own shop, and Amazon, which passes its orders through Shopify. The team packs its spices and teas in-house, so every batch needs a lot number and a best-before date, and parcels go out with DHL. All of it had to keep working as Odoo moved from version 14 to 16, 17 and 18, and when DHL retired its old SOAP interface, the labels had to move to the new REST API before the switch-off.

Our solution

The TeqStars Shopify Connector, extended for the way they sell, pack and ship:

• Web shop, Shopify POS and Amazon orders imported into Odoo, with free products added automatically by order tag
• Manufacturing orders for in-house packing, with lot and best-before labels and a report with batch, scrap and partial-production fields
• DHL labels moved from the SOAP API to REST ahead of the shutdown, and printed in picking order
• HS codes on delivery notes for parcels leaving the EU, and shipping weight that includes the box and filler
• DATEV export columns for accounting, and overtime tracked in Planning
• Upgrades from Odoo 14 to 16, 17 and 18, with their custom modules carried forward each time

Collaboration

Each upgrade was done one version at a time, and day-to-day requests were handled alongside, such as a barcode app layout for the pickers’ iPad.

Result

Web shop, POS and Amazon orders, packing and DHL shipping run in Odoo 18 on the same Shopify connector.

Challenge

Supplier bills arrive as PDFs, sometimes several bills in one email or one long file, and one supplier sends a monthly statement of 10 to 20 pages covering around 800 invoices. Every bill had to be entered, matched to its purchase order, checked for duplicates and then ticked off against the statement. The team wanted one complete picture: every customer billed and paid, every supplier bill entered and paid, and every item shipped.

Our solution

AI bill digitization on Odoo 17, built on the TeqStars digitize module:

• PO numbers read from each bill with instructions per supplier, and bill lines matched to PO lines by quantity and price, then by subtotal, with AI settling the close calls
• Duplicate bills detected and locked automatically
• Emails with several bills split into separate bills, and long PDFs split per bill through a queue
• Supplier statements uploaded and matched line by line to bills, with payments reconciled and differences highlighted in red and green
• TaxJar refunds, including tax-only refunds, and orders renumbered by date across every linked document after the Magento import
• A low-margin alert by product category, and a replenishment report that shows how many days of stock are left

Collaboration

Built against their real paperwork, supplier by supplier, and delivered as fixed-price pieces of work.

Result

Supplier bills are read and matched in Odoo, and tax is calculated the same way on every order.

Challenge

Every appliance has its own serial number, and the serial has to follow the unit from receipt to sale, even when a unit is swapped between two customer orders. The catalogue comes from AVB LINQ, the BrandSource buying group’s portal, with more than 4,000 products that change brand by brand. All of it had to carry over when the store moved from Odoo 14 to 17.

Our solution

Serial-number tools, a buying-group integration and a two-version migration:

• Receive and unreceive with serial swaps between sales orders, and scanning of several items per location during stock counts
• An AVB LINQ integration that fetches products brand by brand on a weekly or monthly queue, and sends stock levels back to LINQ
• A Product Analyzer report the team uses for purchasing decisions
• Margin on orders, special prices by quantity, and one payment reconciled against several invoices
• A migration from Odoo 14 to 17 with about 40 custom modules, and a stock count screen rebuilt to work the way the team knew from Odoo 14

Collaboration

The migration was prepared module by module on a new server, before the live database moved to Odoo 17.

Result

The store runs on Odoo 17 with its serial and catalogue tools, and its Odoo data now answers questions through AI assistants.

Challenge

Orders came in from five Magento storefronts and were paid through Braintree, and each payment had to be matched to its order. The official order records lived in Magento while the sales team worked in Odoo, where duplicate contacts and unclear account ownership got in the way of Inside Sales and the Account Managers. Some orders ship straight from the manufacturer, and some are invoiced in parts.

Our solution

A Magento connector and a staged order-to-cash flow in Odoo, plus a CRM set up around their sales team:

• Magento orders, customers and addresses imported into Odoo, with Braintree transactions fetched and matched to each order
• Orders moved through clear stages: under review, payment review, purchase order, delivery and invoicing
• Manufacturer dropship, partial invoicing, and a credit and return process
• Duplicate contacts blocked by email, companies assigned by email domain, and contact permissions for Inside Sales, Account Managers and the Sales Manager
• Last-touch dates and phone call logging, a CRM dashboard, and a Sales Support button that opens a Helpdesk ticket from a lead or an order
• An upgrade from Odoo 14 to 16

Collaboration

Requirements come from their team as GitHub issues, and the order flow was built and switched on one stage at a time.

Result

Orders from every storefront now run through Odoo from order to invoice, and sales reports combine the older Magento orders with the new ones.

Challenge

Visitors book pot-making workshops online through Rezgo, make a pot on the wheel, and the pottery ships it to them about four weeks later, so every booking is also a future shipment. The web shop ships worldwide in several currencies, and the shipping apps needed volumetric weight rather than actual weight. The catalogue of about 28,000 variants sat in Cin7 Core, and only around 10,000 had come across from Shopify.

Our solution

Odoo 17 with each booking and shipping service connected:

• Rezgo workshop bookings and payments imported as orders for shipping and accounting, in the booking’s currency, with Rezgo SKUs mapped to variants
• A direct DPD Ireland integration when domestic parcels moved from GLS to DPD
• Volumetric weight on products for Easyship and ShippyPro, one shipment for several orders from the same customer, and GLS returns
• Kiln numbers on manufacturing orders, and 32 x 25 mm product labels
• The full catalogue imported from Cin7 Core, with old Shopify orders, currency gains and outstanding accounts cleaned up

Collaboration

Integrations were added as the business needed them: shipping first, then workshop bookings, then the direct DPD link.

Result

Kilns, shop, web shop and workshops run in one Odoo.

Challenge

B2B deals, contacts and their call and email history lived in HubSpot, while B2C orders came from Shopify, so the full picture of a customer sat in two systems. Reordering relied on people checking stock and sales, which is hard to keep right when a product suddenly starts selling faster or a supplier is slow to deliver.

Our solution

Their CRM moved into Odoo, with replenishment rules that update themselves:

• HubSpot contacts, deals, notes, calls and emails imported into Odoo CRM, with each customer marked as B2B from HubSpot or B2C from Shopify
• Shopify connected, Make.com sign-ups flowing into Marketing Automation, and Google Calendar synced
• Reordering rules generated from average sales, and an ARIMA demand forecast that picks up products starting to trend
• Rules for on-demand products, and products with no sales in the last 60 or 90 days left out of purchase orders
• Order timing based on each supplier’s real lead time and reliability, with best sellers protected from running out
• An upgrade from Odoo 16 to 18

Collaboration

Each round of replenishment work started with their buying questions, answered in writing before anything was built.

Result

Sales history and reordering live in Odoo, with purchases suggested from real demand.

Challenge

Progsum’s clients include plastic packaging and cosmetics manufacturers, a clothing retailer with several stores, and companies that follow Colombian finance rules. Their requests go well past standard Odoo: planning several linked manufacturing orders in one run, calculating purity on manufacturing orders, selling invoices to a factoring company through an API, and adding withholding taxes to invoices that are already posted.

Our solution

A development team behind Progsum’s projects, one module at a time:

• Manufacturing Replenish Planning, which creates parent and child manufacturing orders in one run and plans their work orders together
• Purity calculation on manufacturing orders, with lots assigned automatically by nearest expiry date and purity above 100% handled
• Reverse invoice factoring, with API endpoints that post invoices and read back the negotiated ones
• Colombian finance: withholding taxes on posted invoices, advance payments, assets depreciated under two methods, and exchange rates from the Superfinanciera
• POS work for the clothing retailer: sales data by API, discounts and loyalty, and Mix & Match offers by collection
• Faster Shopify stock checks using GraphQL bulk operations

Collaboration

Progsum scopes each feature with its client and answers our questions in the spec, and we deliver the module at a fixed price.

Result

Progsum delivers these features to its own clients on top of standard Odoo, across more than 700 hours of work.

Challenge

Hotmer sells in five stores and online through PrestaShop, and its companies also sell to each other. Management wanted turnover, margin and stock by store, warehouse and company in one place, and a profit and loss statement for each store that includes rent, payroll and overheads. Orders between their companies sometimes used the wrong pricelist, and in-store sales needed to reach Brevo, where their email marketing runs.

Our solution

Odoo 18 set up for management reporting across stores and companies:

• A sales and warehouse dashboard with turnover, margin and stock value by company and warehouse, including web shop and intercompany figures
• Analytic accounts assigned automatically to sales and POS sales, and expense accounts per store for rent, payroll and overheads, giving a P&L for each point of sale
• Existing records back-filled, so the reports cover earlier sales too
• Intercompany sales and purchase orders priced from the right pricelist, with a script that corrected past orders and logged each change
• POS orders exported to Brevo automatically, and warehouse columns in the replenishment and variant views

Collaboration

It started as one Brevo job and grew into regular support hours as reporting and accounting work was added.

Result

Each store’s margin, stock and P&L are visible in Odoo.