Overview
Understanding Gillig integration
Who this is for: Tier 1, tier 2 and component suppliers, logistics providers and equipment makers that supply Gillig, and the planning, shipping and finance teams that serve them.
Scope: This guide describes typical practice for this kind of trading relationship; Gillig's own program details are confirmed during onboarding.
Gillig manufactures transit buses. ECOM's directory lists it under buses. Suppliers to vehicle makers typically work from planning schedules and shipping releases, ship to assembly plants on tight windows, and follow industry labeling and quality practices.
Most integration problems with a vehicle maker come from mismatched item data and late changes, not from the file format itself. Gillig's own EDI or API specification is not part of this guide and no Gillig document was read: treat what follows as typical practice for a vehicle maker, and confirm the documents, X12 version, delivery method and testing steps with Gillig.
ECOM maps the documents to your ERP and warehouse systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.