Phone: 0850 346 41 09 | Weekdays 10:00–18:00 · Technical support 24/7
ERP (enterprise resource planning) software brings purchasing, production, stock, sales, dispatch and finance onto one database, so every department works from the same numbers. Digital Bridge does not install a packaged system: we analyse how you work, build the ERP around your bill of materials, pricing rules and approval chain, and connect it to Logo, Mikro or Netsis accounting.
In growing manufacturers and trading companies the picture is familiar: purchasing keeps its own spreadsheet, production its own list, and accounts its own software. The same data is keyed in several times, questions such as "how many do we have, when will this order ship, what did this product actually cost?" get a different answer in every department, and month-end reconciliation takes days.
With custom ERP you do not buy modules on top of a packaged product; the system is built from your own processes. You pay no licence for modules you never use, and your statutory accounting stays in the software you already use, so your finance team does not have to learn a new package.
Staff attendance data does not have to be re-keyed into the ERP either: SmartPass access control and time attendance calculates timesheets against the shift plan and, once a month is closed, exports a monthly summary per person to your ERP as CSV or as JSON through its API. For SmartPass, you can request a quote.
Requisitions, quote comparison, purchase orders and goods receipt follow one flow. Price history and lead-time variance are reported per supplier, and you can see whose desk each request is waiting on.
Multi-level BOMs, work orders, raw material reservation and product costing. Semi-finished goods and scrap are recorded, so you know what a product really costs. Connects to MES for the shop-floor side.
Multiple warehouses, lot and serial numbers, bin locations and minimum stock alerts. Receipts and issues are barcode-driven, count variances are reported, and sales and production see the same stock figure.
Customer and supplier accounts, cheques and promissory notes, bank transactions and cost centres. Entries post automatically to your accounting software, such as Logo, Mikro or Netsis, so nothing is keyed twice.
Tiered approval by amount and department. Who approved what and when, and who changed which record, is logged for audit; each user sees only the screens they are authorised for.
Revenue, margin, stock turnover, collection periods and open orders on one screen. Reports are designed around the questions management actually asks and export to Excel in whatever breakdown you need.
We meet each department separately to map the workflow, the bottlenecks and where each piece of data originates. Output: a written proposal setting out scope, phases and cost.
The data model and screens are drawn up around your business; approval flows, the permission matrix and report formats are agreed with you.
Modules go live in order of priority. Existing account, stock and open-order data is cleansed and migrated to the new system.
Old and new systems run side by side for a period while the figures are compared. Training is delivered department by department, with a user guide.
In packaged systems, unusual pricing logic, an idiosyncratic bill of materials or a non-standard approval chain usually end up as add-ons and customisations that need reworking at every upgrade. We write those rules into the core of the system instead. To connect the ERP to the shop floor, see MES production management; to manage the warehouse by bin location, see warehouse and inventory management (WMS); to open it to your dealers, see our B2B dealer portal.
For more detail, see our guides: what ERP is and when an SME needs it, what drives ERP cost, how to evaluate ERP proposals and why ERP projects fail. Browse all topics on the software and ERP guides page.
In a process analysis meeting we map where the same data is keyed in more than once and what is dragging out your month-end reconciliation.
ERP (enterprise resource planning) software brings purchasing, production, stock, sales, dispatch and finance onto one database. It stops the same data being keyed in separately by each department, so questions such as how many we have, when an order will ship and what a product actually cost get the same answer everywhere. Month-end reconciliation becomes shorter as a result.
If your processes follow your industry's standard flow, a packaged ERP can be a fast solution. If you have unusual pricing logic, a distinctive bill of materials or a non-standard approval chain, packaged systems handle them with add-ons and customisations that need reworking at every upgrade. In a custom ERP those rules are written into the core, and you pay no licence for modules you never use.
The scope covers purchasing and supplier management, production with a multi-level bill of materials (BOM), stock with multiple warehouses and lot tracking, finance with customer accounts, cheques and bank movements, approval workflows by amount and department, and management reporting. The process analysis determines which modules you need, and only those are built, in order of priority.
Yes. Customer account, cheque, bank and expense records are transferred automatically to the accounting software you use, such as Logo, Mikro or Netsis, so no voucher is entered twice. Your statutory accounting stays in the program you know, while purchasing, production, stock and sales run in the ERP. MES for the shop floor and a B2B portal for dealers can connect to the same system.
It starts with separate interviews with each department and ends with a written proposal covering scope, phases and cost. The data model and screens are then designed and modules go live step by step in order of priority. Existing customer, stock and open-order data are cleaned and migrated, the old and new systems run in parallel for a while to compare figures, and each department is trained.
Cost depends on how many modules you need, how complex your bill of materials and pricing rules are, which accounting, e-invoice and warehouse systems the ERP must connect to, how much legacy data has to be migrated and how much training is required. That is why there is no fixed list price: a process analysis comes first, followed by a written proposal setting out scope, phases and cost.
Have a different question? Ask Us