Case study
How a Spanish building-materials company integrates purchasing, warehousing and collections in a single Odoo
A Spanish building-materials company runs its physical store on a single Odoo system installed on-premise: purchasing, warehousing and counter sales, with collections in the sector's real modalities — cash, N-day payment terms, and promissory notes.
The starting point
The business needed a system installed on its own infrastructure — on-premise, with no dependency on a cloud provider — able to hold the full cycle of a physical building-materials store: buying from suppliers, running the warehouse, and selling at the counter. The most demanding part wasn't the catalogue or the stock, but collections: in this sector, the customer doesn't always pay in cash.
What was implemented
Purchasing
Supplier purchasing management integrated with the warehouse and the counter, in the same system.
Warehousing
Warehouse stock control connected in real time with purchasing and counter sales.
Counter sale
The physical point of sale runs on the same stock and purchasing data, with no separate systems.
Cash collection
The simplest collection modality, integrated as one more option within the same sales flow.
Term-based and promissory-note collection
Credit sales with N-day payment terms, and collection via promissory notes — the sector's two usual modalities, inside the same Odoo.
The differentiator: the real Spanish collection circuit
Generic ERPs tend to cover cash sales well, but fall short on the rest of the collection circuit common in Spain: N-day payment terms and promissory notes. This system integrates all three modalities — cash, terms and promissory notes — inside the same on-premise Odoo, with no dependency on a spreadsheet or a separate system for anything that isn't a cash sale.
The methodology: client-layer modules, zero core changes
As with any uKodeIT implementation, the customizations that back this collection circuit are built in the client's customization layer — never by touching Odoo's core. So when Odoo ships a new version, the upgrade lands clean and the collection circuit keeps working exactly the same, instead of getting stuck on the version it was implemented on.
And the project keeps its own AI trainer
uKodeIT and uKITAIz are the same company. As part of the implementation, the project is handed over with its own AI model trained as a special trainer: the client's team can ask, at any time, about the specifications and processes of their own project, in natural language. It's always a private AI — trained for this client and deployable on controlled infrastructure, with no dependency on third-party clouds. It's offered as part of the implementation service, not as a uKore feature.
Frequently asked questions
- For confidentiality we don't reveal the client's name: we describe it as a Spanish building-materials company. The technical details of the case — modules, processes, methodology — are real.
- Because the client chose to install the system on its own infrastructure, with no dependency on a cloud provider — a valid Odoo deployment option, just as compatible with the rest of the methodology.
- Two credit-collection modalities common in the sector in Spain: a promissory note is a document promising payment at a future date, and an N-day payment term is a payment deadline agreed with the customer. The system manages them alongside cash collection, inside the same Odoo.
- A private AI model, trained on this specific project's specifications and processes, queryable in natural language — an implementation service from uKodeIT/uKITAIz, not a feature included in uKore.