BD ERP brings sales, purchasing, inventory and warehouse together in one system. Every inventory movement goes into a ledger that cannot be altered, so the inventory balance is always exactly the sum of the movements.
BD ERP 1.0 is the first complete process chain. Production, planning and projects are coming. Before use with real data, an independent security test comes first.See the roadmap
Quote, order, pick list and delivery in one chain
Inventory can never go negative
Nine roles with permissions per action
Emergency switch and encrypted backups
What BD ERP does for you
01 · Sales
From quote to delivery in one chain.
A quote becomes an order exactly once. Then you reserve stock, create a pick list with location advice and deliver, in parts if needed. Order, delivery and accounting status are tracked separately.
What is not in stock stays open as a backorder
Discounts above the maximum require approval
Quote, pick list and packing slip as PDF
02 · Purchasing
Purchasing with the four-eyes principle.
A purchase request or an order above the threshold is reviewed by someone other than the requester. On receipt you book what actually arrived, even if that is only part of it.
Requester and creator never approve their own
Rejected goods do not go into stock
Reorder advice based on reorder point and order multiple
03 · Inventory
Every movement counts.
Every receipt, delivery, transfer and adjustment becomes a movement in the inventory ledger. The balance is always their sum; the database calculates it itself and refuses negative stock.
Movements cannot be changed or deleted
Weighted average cost per movement
An action sent twice is booked once
04 · Warehouse
The warehouse in view.
Multiple warehouses with locations for receiving, storage, picking, shipping, returns and quarantine. Warehouse work shows in one overview what needs to be received, picked and shipped.
Transfers, also between warehouses with ‘in transit’
Counts with approval above the threshold
Access per user can be limited to certain warehouses
05 · Integrations
Neatly through to the accounts.
Deliveries, receipts, returns and adjustments go into a queue in the same transaction as the inventory movement. From there they go to your own accounts as CSV or through a signed webhook.
Every event exactly once, with a unique key
Signature (HMAC) and retries in case of an outage
Webhooks never to internal addresses
06 · Security
Business data under lock and key.
Passwords with argon2id, two-factor authentication and sessions that only exist as a hash in the database. Every action checks the role, the company and the warehouse on the server.
Companies within one organisation strictly separated
Three-layer emergency switch, down to a hard 503
Encrypted backups with verified recovery
Modules
From dashboard to warehouse floor.
The most important components, each with a sample screen. The data comes from the BD ERP demo environment and is made up.
Spotting bottlenecks before they arise
The dashboard shows revenue, margin, open orders, inventory value and warehouse work, and puts what needs attention at the top: late orders, backorders and items below minimum stock.
Every card opens the underlying records
Period from 7 days to this year
Inventory per warehouse
Sample screen with made-up data (the app itself is in Dutch).
DashboardGoedkeuringenVerkoopordersInkoopordersVoorraadMagazijnwerkRapportagesGebruikers en rechten
Goedendag, Sanne
Verwachte operationele knelpunten
1 verkooporder over de gewenste leverdatum
1 orderregel in backorder (onvoldoende voorraad gereserveerd)
5 producten onder de minimumvoorraad
1 inkooporder te laat geleverd
Omzet (geleverd)
€ 2.776,90
Marge € 1.217,21 (43,8%)
Openstaande verkooporders
3
€ 5.670,79 · 5 regels te leveren
Totale voorraadwaarde
€ 7.910,80
12 artikelen op voorraad
Gereserveerd
196
eenheden voor open orders
Roadmap
Honest about where BD ERP stands today.
Version 1.0 is the first complete process chain, built and tested. This is what exists now, what is coming, and what is needed before you work with real data.
Ready and tested (version 1.0)
Contacts, products, variants and price lists with tiers
Quotes, sales orders, pick lists, deliveries and returns
Purchase requests, purchase orders, receipts and reorder advice
Inventory ledger, transfers, counts and adjustments
Eleven reports, financial outbox and signed webhooks
82 unit and integration tests and 11 browser tests
Coming, and needed before real data
Production, bills of materials and production orders
Capacity planning and MRP
Projects, time registration, service and work orders
Quality management, document management and automations
A ready-made integration with an accounting package
An independent security test and a DPIA
Backups in a second location and monitoring
In the app, the planned modules are listed under ‘In development’, with a page that honestly says they have not been built yet.
Made for the Netherlands
Dutch SMEs as the starting point.
Not a translated foreign package, but terms, statuses and overviews the way wholesalers, installers and distributors in the Netherlands use them.
Multiple companies
Companies, branches, warehouses and locations within one organisation, with data that stays strictly separated per company.
Prices as in practice
Price lists per customer and customer group, tiered discounts and a validity period. VAT of 0, 9 or 21% per product.
Units and batches
Alternative units, order multiples, barcodes and a batch or serial number per movement (without a per-item uniqueness check).
PDFs that are right
Quotes, purchase orders, pick lists and packing slips as PDF, with the details of the company placing the order.
Excel without hassle
Exports as CSV with semicolons, ready to open in Excel and protected against formulas in cells.
The accounts stay leading
Invoices, receivables, payables and the general ledger stay in your accounting package. BD ERP supplies the events.
Security
Business data deserves the strictest lock.
Customers, prices, margins and inventory are the core of a business. That is why security in BD ERP is the design itself, not something added later.
Web security CSP · HSTS · no framing
Sign-in Argon2id · 2FA · lockout
Permissions Nine roles · per action
Companies Strictly separated
Inventory Guarded by the database
Two-factor authentication
A code from the authenticator app that only works once, ten one-time recovery codes, and mandatory for platform administration.
Strong passwords
At least 12 characters, stored with argon2id. After five failed attempts the account is locked for fifteen minutes.
Segregation of duties
Whoever creates a request or document cannot approve it themselves. The code checks requester and creator; the database also refuses any approval by the requester.
Sensitive fields shielded
Cost prices, purchase prices and value columns in exports are only visible to roles that are allowed to see them.
Audit log
Append-only: who did what and when, including refused attempts. Without passwords, tokens or 2FA secrets.
Three-layer emergency switch
In the app, via the command line and hard-wired with NOODSTOP=aan, where every route returns a 503, even without the database.
Verified backups
Encrypted with AES-256-GCM and verified immediately. Recovery only in emergency mode, with checks on counts and inventory balances.
Independently reviewed
A separate reviewer, without knowledge of the design choices, found 13 findings. All 13 have been resolved, with a test where possible. An external pentest is still to come.
Who it is for
One system, everyone their own role.
From sales on the phone to the employee in the warehouse.
Sales and inside sales
From quote to delivery in view.
Prices per customer and tier
Backorders visible right away
PDFs for the customer
Purchasing
Ordering on time, without ordering too much.
Reorder advice per warehouse
Approval above the threshold
Supplier performance
Warehouse and logistics
Every action booked once.
Picking with location advice
Receiving, transferring and counting
Optionally limited to their own warehouse
Finance and controller
Figures you can trace back.
Reports with calculation explanation
Outbox to the accounts
Audit log and approvals (controller)
Approach
This is how we look at it together.
Step by step, with your own processes as the yardstick.
01
Step 1: Introduction
We discuss how sales, purchasing and warehouse run today and show the complete chain in the demo environment.
02
Step 2: Try it out
With fictitious data you go through an order yourself: quote, reservation, pick list, delivery and report.
03
Step 3: Setup
We tailor companies, warehouses, locations, roles and approval thresholds to your organisation.
04
Step 4: Further development
Feedback goes straight to the developer. New modules follow in tested versions.
Questions
Frequently asked questions
Is your question not listed? Ask it during the introduction.
Can we already use BD ERP?
Version 1.0 works from quote to delivery and from purchase request to receipt. Before you work with real data, an independent security test, a DPIA, backups in a second location, monitoring and an acceptance test with your own processes are needed, plus agreements on which system is leading per data type. During the introduction we discuss what that means for you.
Does BD ERP also create invoices?
No, and that is a deliberate choice. Invoices, receivables, payables and the general ledger stay in your accounting package. BD ERP prepares deliveries, receipts, returns and adjustments as events that you export as CSV or forward through a signed webhook.
Is there an integration with Exact, AFAS or Twinfield?
Not ready-made yet. The queue, the signed webhook and the CSV export work; a specific package needs a separate integration. A delivered order is therefore not automatically invoiced or paid.
Can inventory go negative?
No. The database refuses any movement that would take inventory below zero. The balance is always the sum of the movements, and a movement can never be changed or deleted; an adjustment is a new movement with a reason.
What if someone clicks send twice?
Then the action is booked once. Deliveries, receipts, inventory actions and the outbox use a unique key, also from the form.
Does it include production or planning?
Not yet. Production, bills of materials, capacity planning, projects, service and quality management are planned. Reorder advice and the batch traceability report already work.
Who sees the purchase prices and margins?
Cost prices, margins and value columns in exports are only seen by the organisation administrator, purchasing, finance and the controller. Purchase prices are also seen by those who may create purchase requests, such as the planner, and a requester sees the amounts of their own request. This is also enforced on the server.
What happens in case of a breach or outage?
A platform administrator takes the system offline immediately with the emergency switch: all sessions of regular users are ended and nobody else can sign in. Encrypted backups can be restored with checks on counts and inventory balances.
Introduction
Curious about BD ERP?
We show the complete chain in the demo environment, from quote to delivery, and discuss how it fits your processes.