ERP and Supply Chain Software Buyer's Glossary
Plain definitions of the contract, pricing, integration and compliance terms buyers meet when evaluating ERP, WMS, TMS, procurement and fleet vendors.
- Accessorial charges
- Fees a carrier adds on top of the base freight rate for extra services or conditions, such as detention, liftgate, residential delivery or redelivery. They're a frequent source of invoice disputes.
- Continuous transaction controls (CTC)
- A tax-compliance model where invoice data is reported to or cleared by the tax authority in real time or near real time, as in India, Brazil, Italy, Saudi Arabia and Poland. Systems must integrate with the government platform rather than only archiving invoices.
- Data residency
- A requirement, set by law or contract, that certain data be stored or processed within a specific country or region. It affects which cloud data centers and vendors a buyer can use.
- Electronic data interchange (EDI)
- Standardized electronic messages exchanged between trading partners, such as ANSI X12 sets (204 load tender, 214 status, 210 invoice) and their UN/EDIFACT equivalents used more widely outside North America.
- Fit-gap analysis
- A structured comparison of a company's required processes against what the software does out of the box. Each gap is resolved through configuration, process change, an extension or a third-party add-on.
- Freight audit and payment (FAP)
- A service or software that checks carrier invoices against contracted rates and shipment data, flags errors, pays approved invoices and produces freight spend data for analysis.
- Hypercare
- The period right after go-live, usually two to eight weeks, when the implementation team provides extra support and fixes issues quickly before handing over to normal support.
- Labor management system (LMS)
- Warehouse software that sets engineered labor standards, tracks worker productivity against them and supports incentive pay. It's often sold as a separate module from the core WMS.
- Master data
- The core reference records a system runs on, such as items, customers, suppliers, locations, carriers and charts of accounts. Poor master data quality is a leading cause of failed migrations and bad planning output.
- Peppol
- An international network and set of standards for exchanging e-invoices and other procurement documents through certified access points. It's used in many European countries and in Singapore, Australia, New Zealand and Japan, among others.
- Renewal uplift cap
- A contract clause that limits how much a SaaS vendor can raise the subscription price at renewal, typically stated as a fixed percentage or tied to an inflation index. Without one, renewal increases are at the vendor's discretion.
- Sales and operations planning (S&OP)
- A monthly cross-functional process that aligns demand forecasts, supply capacity and financial plans into one agreed operating plan. S&OP software supports it with scenario modeling and consensus workflows.
- Service level agreement (SLA) and service credits
- The vendor's committed uptime and support response times, and the fee credits owed if it misses them. Credits are usually small, so buyers should also negotiate termination rights for repeated failures.
- Statement of work (SOW)
- The document that defines what an implementation partner will deliver, the assumptions behind the price and what counts as a change request. Vague assumptions in the SOW are the most common source of budget overruns.
- Total cost of ownership (TCO)
- The full cost of a system over a set term, usually three to five years, including subscription, implementation, integrations, hardware, internal staff time and support. It's the right basis for comparing quotes because the license fee is often less than half the total.
A
C
D
E
F
H
L
M
P
R
S
T