Get more out of the ERP you already run, without replacing it

Replacing an ERP is expensive, risky and slow, and the new one will have the same blind spots if nobody puts the data together. Most of what a shop needs to see coming trouble is already recorded in the system it has. What is missing is a layer that reads it, joins it and says what it means.

What it reads

Jobs, with their due dates, status, quantities and start dates.
Operations: the routing, with estimated and actual hours per step and the work center.
Materials each job needs, and stock on hand.
Purchase order lines: ordered, expected and received dates, quantities received and rejected, the supplier, and the job they were bought for.
Costs booked to each job, and its quoted price.
Sales order lines and the ship dates promised on them.

Not every system has every field, and that's fine. Shop Traveler says plainly what it can't work out from what your system records, rather than guessing.

Where it reads from

Shop Traveler isn't tied to one ERP. A small connector runs on a machine in your building and reads:

Databases, including SQL Server and any database with an ODBC driver.
CSV and Excel files, from a folder or a web link, on the same schedule.
Web APIs that return JSON.

Other sources, such as Access, FileMaker or Google Sheets, are small additions rather than new products. Shops running JobBOSS, E2 Shop System, Global Shop, Made2Manage, ECI M1, Fishbowl, a home-grown system or spreadsheets keep that data in one of these forms, and the connection is worked out with you during setup.

A mapping, not custom software

Every ERP names things differently: a job might be a work order, a traveler or a router; an operation might be a step, a sequence or a routing line. One mapping file, written during setup, translates your system's tables and fields onto jobs, operations and orders. A new system needs a new map, not new code, and a change in your system needs a change to the map.

Read-only, and checked before the first sync

Read-only. The connector signs in with an account that cannot change anything. Nothing in your ERP is written to, and your people keep working in it exactly as they do today.
Dry run first. Before anything is sent, the connector reads your system, maps and checks it, and shows what it would send.
Bad data refused loudly. A record that doesn't fit is reported, never quietly dropped or guessed at.
Numbers you can check. Every read is recorded, and totals can be set beside your ERP's own to the cent.

Hosted, or on your own server

We host it, with each customer's data kept apart, or run the same containers on your own server if the data must stay in the building. Either way, we delete your data on request under a written retention policy.