Branches
Odoo for publishers
CRM, ad sales, reverse-billing portals, and integration with production systems for online and print, from weekly magazine to book.
Publishing is a trade with unique processes. An ad order is tied to a title, an issue, a position, and a closing date. A freelancer doesn't invoice, you invoice on their behalf. The production "shelf" for issues and the collection of ad materials make the process unique.
Most ERP packages assume a product that you purchase, stock, and sell. A publisher works differently. Your product appears on a date, your ad space is finite, your suppliers are authors and photographers, and your revenue comes from different product types, such as print or online.
We've been delivering solutions for publishers for a good while now: implementations, migrations from existing systems, and merging environments after an acquisition. We also set up the processes that fall outside the standard.
What we do for publishers
Three types of engagements, each with its own focus.
Implementations
Setting up Odoo for a publisher making the move from separate systems or from a package that no longer scales with them. The core isn't the installation, it's translating your publishing process into a model that still holds up in five years.
Migrations
Moving over from an existing system, taking the history with you. Subscriber and contact data, open advertising contracts, work in progress, and financial history: transferred without stalling ongoing production, because an issue doesn't wait for your ERP project.
Carve-in / Carve-out
Bringing two environments together into one after an acquisition or merger. That's rarely a technical matter alone: TSA, IT architecture, and merging two ways of working into one approach. We guide that process on substance, not just technically.
Ad sales
The process where standard packages get stuck fastest, because ad space doesn't behave like a product.
Why it doesn't fit the standard
An ad order isn't tied to an item number but to a combination: which title, which issue, which format, which position. That space is also perishable. What isn't sold by the closing date is lost. And the invoice doesn't follow the order, it follows the publication date.
What we set up
Rate cards with agency discounts and customer-specific agreements, orders per issue with occupancy and closing dates, combination deals across multiple titles or multiple placements, and invoicing that follows publication rather than the order date. Including visibility into what's still available, which your sales team steers by daily.
Reverse-billing portals for freelancers
Also known as self-billing: you create the invoice on behalf of your supplier. For publishers with many freelance authors, photographers, and designers, this is the difference between manageable bookkeeping and a monthly pile of inconsistent invoices.
The problem it solves
Dozens to hundreds of external suppliers who each invoice in their own way and on their own schedule, with their own descriptions and their own mistakes. Your bookkeeping then spends most of its time correcting and reconciling instead of paying.
How we set it up
A portal where the supplier submits or reviews their delivered work, linked to the rate agreement set in advance. Once approved, Odoo generates the invoice on the supplier's behalf, with the correct VAT treatment and an overview the supplier can view themselves. One fixed format, one moment, one source of truth.
What to watch out for
Self-billing requires an explicit agreement with each supplier and correct VAT treatment per situation: domestic, foreign, VAT-liable or not. That's not a reason not to do it, but it is a reason to set it up properly once.
From weekly magazine to book
Every publication type has different requirements. The same Odoo environment, configured differently.
Weekly magazines
High frequency and short turnaround times. Everything revolves around tight closing dates and a production schedule that starts over every week. There's no room for manual intermediate steps: what recurs every week needs to be automated.
Monthly magazines
Longer lead time, more room for planning, but also more parallel issues in different stages at once. The challenge shifts from speed to overview: which issue stands where, and what hasn't come in yet.
Specials and one-off issues
Project-based by nature, often with their own budget and their own result. Here you want to see per issue what was spent and what it delivered, something that gets lost in a regular title structure.
Books
A fundamentally different model: print runs, inventory with a long tail, returns from retail, and royalty agreements per author and per contract. That last part especially is work that's excellent to automate, and that consistently produces errors when done by hand.
Why Odoo fits here
Not because Odoo is a publishing package, it isn't. But because it's extensible exactly where it needs to be.
One system instead of four
Ad sales, content purchasing, production, financial administration, and reporting in the same environment. That saves not just integrations, but above all the discussions about which system is right.
Extensible where your process differs
What can be standard, we do as standard. For ad space and self-billing there is no standard, so we build that: as separate modules, alongside the core, so that an upcoming Odoo version never means a rebuild.
No license brake on growth
Editorial, sales, production, and administration all work in the same system, even though not everyone uses it as intensively. We're a member and sponsor of the Odoo Community Association and also implement on Community, where the number of users doesn't drive up your costs.
Do you recognize your own process in this?
Then the question isn't whether Odoo can handle it, but how much of it can be standard and where customization pays off. We're happy to map that out with you, including an honest verdict on what you're better off not building.
Schedule a strategy session →