Bomshteyn
Consulting

Canadian-led · Serving businesses across the US and Canada

Custom ERP development around your operation

Give purchasing, inventory, sales and operations a shared system built around the way your business works. We develop custom ERP software and modernize legacy applications, connecting the records and daily workflows your staff depend on.

Discuss your ERP project

  1. 01

    Map

    Your existing records, decisions and handoffs.

  2. 02

    Replace

    One agreed operational workflow at a time.

  3. 03

    Connect

    Departments working from related business records.

Keep the operational detail. Improve the system.

An established business has years of knowledge in its desktop tools, spreadsheets and staff routines. Custom ERP development starts by understanding that knowledge and turning it into connected records, useful screens and clearly defined workflows.

01

Replace a legacy desktop ERP

For a wholesale distributor, we replaced a desktop ERP with a browser-based portal covering purchasing, receiving, inventory and sales. The system brings vendor offers, purchase orders, bills, stock lots and sales documents into related workflows.

Receiving teams can record discrepancies, while sales staff can allocate available and incoming stock using customer-specific pricing. The replacement also imports third-party warehouse inventory snapshots. This work shows how legacy system modernization can preserve the operational detail a business needs while giving departments a shared application to work in.

02

Move beyond the single-PC application

Our rental-system modernization replaced a Windows application installed on one computer. Staff can now work in the cloud-based system simultaneously from phones, tablets and laptops, using connected customer, rental, garment and payment records.

Returns update garment status and rental completion, while availability follows the item's current state. Overdue items and cleaning fees sit within the rental workflow. The remote desktop to cloud article explains the move from a shared physical computer to a web application built for the staff using it.

03

Bring spreadsheets into an operational workflow

A spreadsheet often holds part of an order, stock movement or payment process. A custom business system can turn those separate records into a workflow with a defined next action and a consistent relationship to the underlying order or account.

Our construction supply platform connects dispatch, yard stock, deliveries, returns and shipment-based invoicing. Drivers see assigned work on a mobile agenda, while yard teams work with stock and backorders for their location. Its audit trail keeps an operational record of activity, supporting the team as work moves between roles.

04

Modernize a portal as well as the back office

Legacy replacement can include the screens customers or clients use alongside staff administration. We rebuilt a pooled-trust portal around applications, account records, deposits, bill decisions and monthly statements.

Clients can use the statement archive while staff manage the approval and payment workflows behind it. This connects self-service to the same account lifecycle as the back office. During ERP discovery, we identify which outside users need access and which parts of the operation should stay focused on internal staff.

A phased path from the old system to the new

Delivery is Canadian-led, with our senior developers in Europe building Laravel/PHP applications. We start with paid discovery and plan a phased replacement around the workflows your business needs to keep running.

  1. 01

    Map the current operation

    We review the desktop application, spreadsheets, reports and staff handoffs together. Discovery identifies what each record means, which workflows depend on it and where the current system creates manual work.

    We use read access for this assessment and define the first replacement boundary. The result is a practical scope covering the workflow, data and people involved in the first build phase.

  2. 02

    Build and check the first workflow

    We implement a focused operational area and review it with the people who use it. Where records need to move, we agree the mapping and compare imported samples with the source.

    Staff review the results before the workflow becomes part of daily operations. Role-based access follows the work people need to do, as in our rental system's separation of administration and standard staff tasks.

  3. 03

    Roll out department by department

    Later phases expand the connected operation, adding the next department, report or integration. In our wholesale ERP work, historical records moved from CSV and teams rolled into the replacement department by department.

    Each phase gives the owner a clear point to review the next operational change. Existing systems retain their agreed role until the corresponding workflow is ready to move.

ERP and modernization work in practice

These projects show desktop replacement, connected operational workflows and portal modernization. Explore how purchasing, rentals, client accounts and construction logistics fit into applications built around the business.

Questions about custom ERP and legacy replacement

When does custom ERP development make sense?

It is worth exploring when the way your business operates is difficult to fit into disconnected tools or an existing application. Discovery examines the workflows, data and reporting needs first. That gives you a basis for deciding which parts justify a custom build.

Can you replace an old desktop application?

Yes. Our work includes replacing a desktop ERP and a single-PC Windows rental application with browser-based systems. We review the existing records and the details staff rely on, then plan a replacement that carries those operational requirements into the new workflow.

Do we have to replace every system at once?

A phased plan can keep the replacement focused on one operational area at a time. We identify dependencies and agree what stays in the existing tools during each phase. That lets the team review the new workflow before extending it across more of the business.

What happens to our historical data?

Discovery establishes which history is needed, where it is stored and how it maps to the new records. Our wholesale ERP work includes bringing historical records across from CSV. We define the import and review process around the specific sources available in your business.

Can an ERP include customer or vendor access?

Yes, a portal can be part of the wider operational system when outside users need a defined view or action. We map that access separately from staff administration. The aim is a focused experience for each role connected to the business records behind the work.

Related services

Bring the system your business has outgrown.

Show us the desktop software, spreadsheets and handoffs that keep your operation moving. We will help define a first modernization phase that preserves the detail your team needs and connects the next useful workflow.

Start a project brief
DWG SVC · 01
Label Custom ERP development
Rev A
Sheet 01