%2520(28)%2520(1).png)
Last updated: October 2026
If you are trying to run subscriptions inside your ERP, you already know how this story goes
You launch a subscription or rental pilot for your consumer durable product. In the beginning, when you're just getting started, you're probably thinking:
“We already have an ERP. Let us just add the subscription workflow there.”
It sounds harmless. One more SKU. One more process. One more invoice type. But then subscriptions start breaking everything you thought was stable.
Operations that most commonly break when you add subscriptions to your existing ERP
- Recurring payments do not fit into one time invoicing.
- Returns break your outbound-only logistics flow.
- Asset lifecycle management has no place in a system built for sold products.
- Your team suddenly needs fraud checks, credit checks and customer verification.
- Your ERP cannot understand the subscription lifecycle and forces everything into a sales process that does not belong there.
If this feels familiar, you are not alone. Companies that tried this before you said the same thing:
"We stopped the first rental pilot because we tried to incorporate the rental business into our existing process of sales, finance and logistics, which was a huge mess and did not work out." - Bugaboo
This article explains why that happens, what your ERP should still do, and how to connect it to a subscription management system so both work together.
Can you run a subscription business on your ERP?
Short answer: keep your ERP, but don't make it run your subscriptions. Most physical product subscription businesses keep their ERP (SAP, Microsoft Dynamics 365, NetSuite or Odoo, for example) as the financial system of record and add a subscription management system for recurring billing, the subscription lifecycle, returns and asset tracking. The two connect via API and webhooks, so subscriptions, payments, invoices and asset status flow into the ERP without manual work.
What is an ERP?
An ERP (Enterprise Resource Planning) system is the operational core of most established businesses. It centralises critical business functions such as:
- Finance and accounting
- Logistics and warehouse management
- Order and inventory management
- Procurement
- Supply chain processes
- Sales order processing
- Company-wide reporting
For a traditional product business that sells items once, ships them once and finishes the process, the ERP is the ideal system. It ensures standardisation, compliance, financial accuracy and efficient handling of purchase and sales orders.
This is precisely why companies launching subscriptions begin here. The ERP already exists. Leadership assumes that subscriptions are simply another type of order or another way to place orders. So the team tries to add them inside the existing structure.
Unfortunately, the subscription business model does not fit the linear processes ERPs are designed for, and many businesses that have launched and are running subscription models for physical products have experienced the same issue.
What role does an ERP play in a physical product subscription business?
Even though a subscription business operates very differently from a traditional sales business, the ERP still plays an essential role. In fact, for physical product subscription businesses, the ERP remains an important system in the tech stack. However, its role is specific, focused, and fundamentally different from what many companies first assume when they begin exploring subscriptions.
An ERP was designed to create structure across finance, supply chain, procurement and operational planning. Those responsibilities do not disappear when a company introduces subscriptions. What changes is where the ERP sits within the overall architecture. Instead of acting as the engine that runs the business model, the ERP becomes the system of record that supports financial accuracy, operational governance and organisational visibility.
Understanding this distinction is critical. Many companies delay their subscription initiatives because they believe their ERP must handle every process. In reality, successful subscription businesses treat the ERP as a foundational layer rather than the operational core.
1. Financial system of record
At its heart, the ERP remains responsible for financial integrity. Subscription businesses introduce recurring revenue streams, deposits, asset depreciation and long-term contracts, all of which must ultimately be reflected in the company’s books.
2. Asset valuation and inventory control
Physical product subscriptions differ from digital subscriptions in one fundamental way: the product remains an owned asset. Instead of leaving the balance sheet after a sale, it continues to hold value and must be tracked over time.
3. Procurement and supply chain planning
Subscription models often increase pressure on supply chains because product availability directly impacts growth. If inventory runs out, subscriber acquisition slows. If too much inventory is purchased, capital is locked into unused assets.
4. Fulfilment infrastructure
Although subscriptions introduce reverse flows such as returns, swaps and refurbishments, outbound fulfilment still needs to operate with precision. ERPs typically coordinate:
- Order release to warehouses
- Picking and packing workflows
- Shipping documentation
- Integration with logistics providers
- Delivery confirmations
In other words, while the subscription lifecycle may be managed elsewhere, the ERP continues to anchor the physical movement of goods across the supply chain.
5. Governance, reporting and organisational visibility
As businesses scale, leadership teams need a unified view across departments. The ERP provides this operational oversight by consolidating data from finance, procurement, inventory and logistics.
7 reasons why an ERP cannot be the core system to run a subscription model
When companies launch their first rental or subscription pilot, they often assume the ERP can “run” the model. After all, the ERP is the central system in their existing business. It feels logical to extend it.
ERPs were designed for linear commerce, where products move in one direction: from manufacturer to warehouse to customer. Subscription businesses operate in continuous loops, where products return, revenue recurs, and customer relationships evolve over time.
1. ERPs are built for transactions. Subscriptions are built on lifecycles.
Traditional ERP logic revolves around discrete events:
order → invoice → ship → close
Subscriptions, on the other hand, introduce an ongoing lifecycle:
- activate
- bill repeatedly
- pause
- upgrade
- swap
- extend
- return
- refurbish
- redeploy
These states are dynamic and customer-driven. Most ERPs are not designed to manage objects that never truly “close.” When companies attempt to replicate lifecycle logic inside an ERP, they often end up creating complex process chains that are difficult to maintain.
2. Recurring billing is not native to most ERPs
While some ERPs offer billing modules, they are typically designed for predictable contract invoicing rather than flexible subscription behaviour.
Subscription billing requires capabilities such as:
- prorated charges
- mid-cycle changes
- automated retries
- usage-based pricing
- deposits
- partial refunds
- contract extensions
Building this logic inside an ERP usually demands significant development effort, and even then, it rarely delivers the flexibility modern subscription models require.
3. ERPs struggle with asset circulation
In a sales model, inventory leaves the balance sheet once sold. In a subscription model, the same asset generates revenue across multiple customer cycles.
This introduces operational questions ERPs were never built to answer:
- Where is the asset right now?
- What condition is it in?
- How many times has it been deployed?
- Is it profitable yet?
- Should it be refurbished or retired?
Without a system designed for asset lifecycle tracking, companies often rely on spreadsheets or disconnected tools, increasing operational risk.
4. Reverse logistics breaks linear workflows
Subscription businesses depend on products coming back. Returns are no longer exceptions. They are expected, frequent and operationally critical.
Each return triggers decisions:
- inspect
- repair
- clean
- refurbish
- restock
- redeploy
Linear ERP workflows typically focus on outbound fulfilment. Once reverse flows become central to the business, process gaps start to appear.
Industry conversations around circular operations reinforce this shift. Traditional supply chains were built for one-way movement, not for retrieving, inspecting and redistributing products in continuous loops. Businesses that rely on outdated operational structures often underestimate the requirements of these circular flows, which is where complexity begins to surface.
5. Customer relationship management goes far beyond the sale
In subscription models, the transaction is only the beginning. The real value is created over the duration of the customer relationship.
Businesses must support actions such as:
- subscription changes
- payment method updates
- swap requests
- cancellations
- renewals
- extensions
Most ERPs are not designed to power customer-facing journeys. Attempting to use them this way often results in fragmented experiences that increase support workload and reduce customer satisfaction.
6. Customising an ERP is expensive and slows innovation
It is technically possible to modify an ERP to support subscription processes. Many companies try.
The challenge is not whether it can be done. The challenge is what it costs.
Heavy ERP customisations typically lead to:
- long implementation timelines
- reliance on specialised developers
- high maintenance costs
- reduced system flexibility
- slower product launches
In fast-evolving markets, this loss of agility can become a competitive disadvantage.
7. Modern subscription businesses operate on multi-system architectures
Today’s most resilient subscription companies do not rely on a single platform. Instead, they build an ecosystem in which each system performs the role it was designed for.
Typically:
- the shop system handles checkout
- the subscription platform manages lifecycle and billing
- payment providers process transactions
- logistics partners enable fulfilment and returns
- the ERP anchors finance and governance
From an operational standpoint, this structure allows businesses to scale without forcing one system to do everything.
Across the subscription landscape, the companies that scale successfully tend to follow a similar principle: do not overload the ERP. Let it remain the financial backbone while specialised systems handle subscription operations.
Bike Club is a good example.
It's a subscription-only business: more than 60,000 families in the UK and Germany subscribe to its kids' bikes.
Still, it doesn't run those subscriptions in its business systems.
Salesforce and Klaviyo handle customer support, email marketing and business reporting, while circuly runs the subscription logic and operations, from sign-ups, swaps and billing to the self-service portal where families schedule upgrades.
Business processes live in business tools. Subscription processes need a dedicated one.
Subscription models need a subscription management system at the core, not an ERP
For physical product subscriptions, the ERP remains important, but it should not be the system that runs the subscription model itself. ERPs are built for linear sales flows, while subscriptions create circular product and revenue cycles that require dedicated tooling. A subscription management system sits at the core of the subscription operations, handles the lifecycle and payments, and then passes structured data into the ERP for finance and logistics.
How circuly connects to your ERP
circuly doesn't replace your ERP. It runs the subscription operations and triggers your ERP and logistics systems to do their part. In our conversations with subscription businesses, the ERPs we see most often are SAP, Microsoft Dynamics 365, NetSuite and Odoo. circuly doesn't need a separate plugin for each one: it connects through its API and webhooks, so it works with any ERP that can receive data via API or webhooks.
A typical data flow looks like this:
Recurring payments: no PSP integration needed in your ERP
A common question is how to connect the ERP to Stripe or another payment provider for subscriptions. Usually you don't have to. circuly connects natively to Stripe, Adyen, Braintree, Mollie and PayPal, runs the recurring charges and retries, and passes the results to your ERP. Your ERP receives clean payment and invoice data instead of having to manage recurring payment logic itself.
Invoicing: circuly or your ERP, your choice
You can let circuly generate invoices automatically and send them with all line items to your ERP, or let your ERP issue the invoices with its own numbering based on the payment data circuly passes on. For accounting teams that prefer files, invoices and invoice line items can also be exported as CSV.
For the full overview of native, API and webhook integrations, see how circuly connects to your existing tech and tools and our integrations page.
Signs you need a subscription management system next to your ERP
If two or more of these sound familiar, your ERP is being asked to do a job it wasn't built for:
- Your IT team is building proration, retries, deposits or buyout logic as ERP customisations.
- Returns and swaps are tracked in spreadsheets, emails or a ticket tool.
- You can't quickly say where each product is, what condition it's in and how many subscription cycles it has completed.
- Failed payments are chased manually instead of through automated dunning.
- Customers email support to pause, swap or cancel because there is no self-service portal.
- Every new subscription offer or pricing change turns into an IT project.
That's the point where most companies add a dedicated subscription layer instead of customising further. circuly works with consumer brands and enterprise teams that keep their ERP and run subscriptions next to it. Book a demo to see how it would connect to your setup.
Conclusion: ERP is not the foundation for subscription businesses
An ERP is a powerful system for managing the financial and logistical side of a traditional business. However, subscription businesses require a different operational logic. This is why companies like Bugaboo and Stokke eventually adopt a dedicated subscription management solution, and why even subscription-only businesses like Bike Club run on one.
Trying to run subscriptions inside an ERP feels natural in the beginning, but quickly creates complexity, manual work and customer experience issues.
If your business manages physical product subscriptions, the most efficient architecture is:
- Keep your ERP
- Add a subscription management system that handles lifecycle operations
- Connect both systems via API and webhooks for clean information flow
This combination provides the stability of your ERP with the flexibility required for modern subscription models.
Frequently asked questions
Can an ERP handle subscription billing?
Some ERPs offer contract billing modules, but they are designed for predictable contract invoicing. Physical product subscriptions also need proration, mid-cycle changes, payment retries, deposits and buyouts linked to individual products, which usually means heavy ERP customisation.
Do I need to replace my ERP to launch subscriptions?
No. The ERP stays your system of record for finance, procurement, inventory and reporting. A subscription management system runs the subscriptions and sends the data to your ERP.
Does circuly integrate with SAP, NetSuite, Microsoft Dynamics 365 or Odoo?
circuly connects to ERPs through its API and webhooks rather than ERP-specific plugins, so it can work with any ERP that can receive data this way, including these. You decide which events (new subscriptions, payments, invoices, shipments, returns, asset status) flow into the ERP.
Who creates the invoices, circuly or my ERP?
Either. circuly can generate invoices automatically and send them with line items to your ERP, or pass payment data to your ERP so it issues invoices with its own numbering.
How do I connect my ERP to Stripe for subscriptions?
With a subscription management system in between, you usually don't need to. circuly connects natively to Stripe and other payment providers, runs the recurring payments and sends payment and invoice data to your ERP.
What is the difference between subscription management software and an ERP?
An ERP manages company-wide processes like finance, procurement and supply chain. Subscription management software runs the subscription itself: billing, lifecycle, returns and assets. Read more in subscription management software vs ERP.
Related reading:
%20(18).png)
%20(17).png)
%20(16).png)
.png)
.png)
