Skip to content

Systems we know, and how we take on new ones

We list what we have worked in and how deep, and we say plainly when a system is new to us.

Where we are deepest

Around them

The databases, reporting tools and connections a distributor or manufacturer runs alongside the ERP.

GroupSystems and tools
Databases and reportingSQL Server, Crystal Reports, SSRS and Power BI.
IntegrationREST and Transaction APIs, Scheduled Imports, EDI, e-commerce connections, QuickShip, BarTender labels, and QuickBooks as a migration source.
Epicor toolingDynaChange business rules in Prophet 21, and Epicor 10.x.

Other ERPs and systems

If a system is new to us we say so, and we start with a paid discovery before any commitment.

How we take on a system that is new to us

  1. Paid discovery

    A small piece of work, with a written scope and price, to learn how your system is set up and used.

  2. Documentation and data model

    We read the vendor documentation and map the tables, keys and interfaces behind the work you need.

  3. A small first change

    We make one small change in a test environment, so you can judge the work before anything larger.

  4. Then scope

    With what we learned, we write the scope and a fixed price for the real work.

Tell us what you run

Name the system, the version and the work. The first call is free and without obligation.

Related work

  • ERP assessment

    A fixed-price review, including a health check for any system.

  • Reporting and data

    Crystal, SSRS, SQL, Power BI and data cleanup.

  • For partners

    Overflow and specialist engineering for firms that serve ERP clients.

  • Our services

    Support, implementation, integration and automation.