Genwright rarely replaces everything, and should not try.
Most operations keep their accounting system, their TMS or ERP, their telematics and their payroll. Genwright fills the gaps between them. Integration scope is agreed during scoping, because it is usually what sets the timeline.
What Genwright typically connects to
Connections are built per deployment against documented interfaces rather than drawn from a marketplace of pre-built connectors. That is slower to advertise and more likely to survive contact with your actual instance.
Finance & accounting
General ledger, accounts payable and receivable, job costing and payroll. Typically the destination for approved time, settlements, invoices and vendor charges originating in the field.
ERP & order systems
Orders, inventory valuation, purchasing and master data. Genwright reads master data rather than duplicating it, so the ERP stays the authority on what a part or a customer is.
Transportation & dispatch
TMS and dispatch platforms. Genwright commonly holds the workflows around freight movement — qualification, inspections, breakdowns, exceptions — rather than the movement itself.
Telematics & ELD
Vehicle and asset telemetry, hours of service and location feeds, used to prefill records and to reconcile what a field entry says against what the asset was doing.
HR & identity
HRIS, payroll and single sign-on. Person records and employment status flow in; qualification, credential and time records flow back out.
Documents & messaging
Document storage, email and SMS. Generated PDFs, evidence packs and field notifications go where your operation already looks for them.
Three things that make an integration hold
One system stays the authority
For every shared entity — a customer, a part, an employee — one system is the source and the other reads it. Two systems both believing they are correct is the most common cause of integration failure.
Failures become records, not log lines
A sync that fails surfaces as a visible exception someone owns, rather than an error in a log nobody reads until month-end reconciliation goes wrong.
Scoped before the estimate, not after
Integration is usually what determines a project timeline. It is agreed during scoping so the number you are given is the number that holds.
Integration questions
Does Genwright have pre-built connectors?
Connections are built per deployment against documented interfaces rather than drawn from a connector marketplace. Common integrations are well-trodden and quick; the honest reason for not advertising a connector catalog is that catalog connectors frequently do not fit a specific customer instance, and discovering that in week five is expensive.
Can Genwright write back into our ERP or accounting system?
Yes, where the target system supports it and where writing back is the right design. Often it is better for Genwright to hold the operational record and hand over an approved, reconciled result rather than to write continuously into a financial system of record.
What if our system has no API?
Scheduled file exchange, database-level integration and other approaches are common with older systems and are assessed during scoping. This is precisely the constraint worth raising on the first call, because it materially affects the estimate.
Who maintains the integration when the other system changes?
That is agreed in the contract rather than assumed. Ask about it during scoping, along with how a breaking change on the other side surfaces and who is expected to notice it first.
Bring the list of systems that have to keep working.
Who owns them internally matters as much as what they are. Both belong on the first call.