Slimstock (Slim4) vs dvstock on Business Central

If your company runs Microsoft Dynamics 365 Business Central and you are evaluating an inventory optimization and demand forecasting tool, Slimstock has very likely shown up on your screen. It is the most visible player in the European market — category leader, international footprint, AI in the product and a very strong brand story.

But it is not the only option. And, depending on your company’s profile, it may not be the most efficient one.

This article compares, with no spin, Slim4 (Slimstock’s product) against dvstock — Davisa Informática’s native Business Central extension. The comparison covers technical architecture, features, TCO, support and typical use cases. If your case fits Slim4 better, we say so too.

Context note: dvstock is a Davisa Informática product. We have tried to keep the comparison as objective as possible — we call out what Slim4 does better and what dvstock does better.

Summary table — what to weigh before choosing

Dimension	Slim4 (Slimstock)	dvstock (Davisa)
Origin / headquarters	Netherlands (global, 75 countries, 1,700+ customers)	Spain — Davisa Informática
Supported ERPs	BC, SAP, AX, Oracle, JDE, others (multi-ERP)	Business Central and NAV only (native)
Architecture	Standalone SaaS + connector to your ERP	AL extension inside BC
Modules	Inventory + Demand + Supply Chain + Data + Commerce	Inventory + Demand + Replenishment
AI / ML	Yes, agentic data cleaning, advanced ML	Fine-tuned classical mathematical algorithms
Multi-warehouse / multi-country	Mature, proven on multinationals	1-5 domestic warehouses, manual configuration
S&OP / Integrated Business Planning	Yes (dedicated module)	No
Pricing & promotions	Yes (Commerce Management)	No
Pricing model	Premium SaaS license + implementation	Annual license + scoped implementation
3-year TCO (Spanish SMB, 1 BC)	High reference	~50-70% lower on comparable projects
Implementation	4-8 months typically	6-10 weeks typically
Support	Global, multiple languages, 24/7 (premium)	Spain, Spanish, same team that implements BC
Track record	25+ years, European market leader	15+ years on Spanish customers

Architecture — the detail that decides

Both tools say they “integrate with Business Central”. But how they do it is very different, and that has concrete consequences 6-12 months into the implementation.

How Slim4 does it

Slim4 runs on Slimstock’s own infrastructure (Azure/AWS cloud). The product consumes data from your BC through a connector + sync service:

• BC publishes data (catalog, transactions, purchases, sales) which Slim4 caches/normalizes on its side.
• Slim4 runs the optimization, forecasting and replenishment algorithms against its copy.
• Order proposals are pushed back to BC via API.

Pros:

• Product decoupled from the ERP — Slim4 keeps running even if BC is under maintenance.
• The same Slim4 keeps working if you migrate to SAP tomorrow. Useful if you have an ERP-change roadmap.
• Product algorithms update independently from the BC release cycle.

Cons we see in customers (the ones who migrate to dvstock):

• Permanent two-source-of-truth: the catalog and transactions live in BC but also in Slim4. When something does not match, somebody has to decide which system is right.
• Scheduled synchronization: Slim4’s proposals reflect the data from the last sync. If that was 2 hours ago, Slim4 has not seen the last 2 hours of sales.
• Connector maintenance cost: every major BC update (semi-annual release) or Slim4 update can require connector tuning.

How dvstock does it

dvstock is an AL extension inside Business Central. The math engine reads directly from the ERP’s standard tables:

• Item, Item Variant, Item Ledger Entry — catalog and real transactions.
• Purchase Line, Sales Line — purchases and sales with their history.
• Resource, Vendor — vendors, lead times, prices.
• Plus dvstock’s own configuration tables (Pareto, service levels, per-SKU forecasting parameters).

This means:

• Single source of truth: the transaction that hit BC 30 seconds ago is already part of dvstock’s calculation.
• No scheduled syncs: there is no copy. dvstock reads BC live.
• No connector maintenance: the code lives inside the ERP and follows BC updates automatically.
• Cross-trace: from a dvstock order proposal you can navigate to the SKU, the history, the vendor’s last invoice — all within BC.

The trade-off is honest: native AL integration ties dvstock to BC/NAV. If your company is going to migrate away from BC in 2-3 years, it makes no sense. If BC is going to be your ERP for the next 5+ years, dvstock is the efficient match.

Features — where Slim4 has more reach

Slim4 is a broader product. It has modules dvstock does not cover (nor intends to):

• Supply Chain Planning: planning of the full chain, not only end-stock.
• Integrated Business Planning (IBP) / S&OP: the monthly cycle where sales, operations and finance align forecast and budget.
• Commerce Management: assortment management, dynamic pricing, promotions, merchandising.
• Data Management: in-house framework for data cleaning and orchestration with AI agents.

For a multinational with a mature demand planning department, this matters a lot.

For a Spanish mid-market company running BC (typically 50-300 employees, 1-3 warehouses, a purchasing team of 2-5 people), most of these modules are oversized. What is actually needed — and dvstock covers cleanly:

• Automatic ABC and Pareto analysis of the catalog.
• Demand forecasting with trend, cycle and seasonality.
• Optimal stock per SKU with customer-configurable service level.
• Automatic replenishment (purchasing + production).
• Per-vendor lead times and delays.
• Minimum lot, purchase multiple, logistics zone.
• Service KPIs, stockouts, obsolescence.

TCO — the real math, not the cover page

Slimstock does not publish pricing. Market references for a Spanish mid-market company (~100 employees, 1 BC, inventory optimization + forecasting):

• Slim4 annual license: ~30,000-80,000€ depending on active modules.
• Implementation: 80,000-200,000€ (4-8 months, Slimstock consulting + local partner).
• Connector maintenance and support: 15-25% annually on top of license.

dvstock for the same scope:

• Annual license: scoped, sized to catalog volume and number of warehouses.
• Implementation: 6-10 weeks, budgeted against the agreed scope.
• Support: included in the annual license, no separate fee.

On comparable projects (1 BC in Spain + stock optimization + forecasting + replenishment + 1-2 warehouses), customers who have benchmarked both products report a 3-year TCO 50% to 70% lower with dvstock. Main drivers: no escalating SaaS license, no recurring integrator cost, the consulting team is in Spain with no international overhead.

Support — the day after go-live

• Slim4: international support with premium SLA, multiple languages. For customers in Spain, the first line is usually a local partner with tickets escalating to Slimstock central in the Netherlands.
• dvstock: direct Davisa Spain support, in Spanish, same technical team that implemented BC and the extension. Response times in business hours.

The difference, which looks minor in an RFP, is what defines operational calm when 6 months down the road an unusual deviation shows up in the forecasting engine.

When to choose each — no spin

Choose Slim4 if:

• Your company is a multinational with several ERPs (BC + SAP + AX) and you need a single layer on top.
• You operate 20+ warehouses with complex multi-country policies.
• You need S&OP, IBP, dynamic pricing or advanced promotion management.
• Your demand planning team is mature and will leverage Slim4’s algorithmic depth.
• You will replace BC with SAP in 2-3 years and do not want to tie yourself to a BC-native product.

Choose dvstock if:

• Business Central / NAV is your ERP and it is going to be your ERP for the next few years.
• You are a Spanish small/mid-market company (50-500 employees, 1-5 warehouses, 1-3 countries).
• Your priority is real operational outcomes (reduce inventory, improve service), not academic algorithmic depth.
• You want a 6-10 week implementation, not a 4-8 month one.
• You value local Spanish-language support from the same team that maintains your BC.
• TCO matters — you want an option that does not need to justify itself to the CFO every year.

Real case: wholesale distribution, Slim4 to dvstock migration

Davisa customer (2024): national wholesaler of industrial spare parts, 60 employees, 1 BC Spain, 2 warehouses, ~3,500 SKUs. Had Slim4 since 2021 through a partner. Before migrating:

• Slim4 annual license + support: around 55,000€/year.
• Connector maintenance (partner + internal IT hours): ~12,000€/year.
• Total annual stack cost: ~67,000€.
• 3-year result: good (−24% inventory, +1.8pts service) but the ROI did not convince the CFO.

Migration to dvstock in 7 weeks. 12-month result:

• Total annual stack cost: −62% vs Slim4.
• Inventory: −26% (similar to Slim4, slightly better).
• Service level: +2.1pts.
• Weekly purchasing team close time: −35% (everything in BC, no need to reconcile two systems).
• IT tickets for sync issues: practically zero.

The CFO signed off the decision in two meetings. The purchasing team took 2 weeks to confirm dvstock was hitting “as well or better” than Slim4 on their catalog. Slimstock is a great product — but it was oversized for a company of that profile.

Closing — decide with your company’s case

Slim4 is a solid product, market leader, and for multinationals with advanced demand planning it is the reasonable choice. For every company coming in with the typical Spanish case — Business Central, small/mid-market, 1-3 warehouses, a purchasing team that wants tools that work without friction — dvstock is built exactly for that case, with a much lower TCO.

Want a firm comparison against your concrete scope? Talk to a Davisa advisor — in less than a week you have a firm proposal to benchmark against.